Macros
AuraScore 81/100

Cross-Border Regulatory Macro Governance and Harmonization Report

Standardize client-facing communication templates to ensure strict compliance with regional regulations across multinational professional services.

Use this template when audit exposure or regulatory drift occurs in client success communications across multiple jurisdictions. It produces an enterprise governance report with compliant macro clauses, risk taxonomies, and control gates.

Template

Role: Lead Legal & Compliance Operations Specialist for multi-disciplinary professional firms.

Context

  • Professional advisory domain: {{advisory_domain}}
  • Operating jurisdictions: {{jurisdictional_scope}}
  • Regulated client entity profiles: {{regulated_entity_types}}
  • Regulatory record retention period: {{audit_retention_window}}
  • Mandatory legal disclaimer posture: {{disclaimer_strictness_level}}
  • Centralized legal clause repository: {{approved_clause_repository}}

Task

Author an enterprise compliance report establishing a harmonized macro governance framework that mitigates legal exposure, enforces standardized disclaimers, and ensures audit readiness across {{jurisdictional_scope}}.

Method

  1. Map existing client communication risks in {{advisory_domain}} against governing regulatory authorities across {{jurisdictional_scope}}.
  2. Review client profiles in {{regulated_entity_types}} to identify prohibited terms, mandatory forward-looking disclaimers, and advice boundaries.
  3. Extract and integrate mandatory standard legal language from {{approved_clause_repository}} into modular macro building blocks.
  4. Establish conditional logic rules governing which disclaimer variants are injected based on {{disclaimer_strictness_level}}.
  5. Define audit logging protocols ensuring communications meet the minimum {{audit_retention_window}} requirements.
  6. Formulate a multi-stage approval workflow for any future modifications or localizations to compliance-approved macros.
  7. Structure a non-compliance penalty and remedial training matrix for front-line support consultants.

Constraints

  • MUST explicitly address legal variations across all regions listed in {{jurisdictional_scope}}.
  • MUST NOT permit unvetted manual edits to core compliance disclaimers by support staff.
  • Every macro template must identify required metadata tags for audit traceability.
  • Report must be suitable for presentation to General Counsel and Practice Leaders.

Output format

  • Section 1: Regulatory Risk Exposure Assessment (max 300 words)
  • Section 2: Harmonized Macro Framework & Modular Clause Architecture (defining core body vs mandatory regulatory addenda)
  • Section 3: Jurisdictional Applicability Matrix (table: Jurisdiction, Entity Type, Mandatory Clause ID, Review Cadence)
  • Section 4: Macro Governance Operating Model & Approval Lifecycle (step-by-step workflow with RACI assignments)
  • Section 5: Audit Readiness & Archive Verification Standard

Self-review

  1. Validate that all clauses directly correlate with entries in {{approved_clause_repository}}.
  2. Verify that data retention and logging directives comply with {{audit_retention_window}}.
  3. Check that jurisdictional nuances between {{jurisdictional_scope}} are explicitly broken down in Section 3.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-macros
professional-services
compliance
regulatory
risk-management