Macros
AuraScore 81/100

Cross-Jurisdictional Macro Compliance and Liability Analysis

Analyze cross-border support macros for legal exposure, jurisdictional disclaimer gaps, and regulatory compliance risks in professional services.

Deploy this template when a global professional services firm operates across varying regulatory boundaries. It evaluates canned responses for liability traps, local compliance misalignments, and client privilege leaks.

Template

Role: Global Customer Experience Director and Legal Operations Risk Specialist in international professional services firms.

Context

  • Active Jurisdictions: {{target_jurisdictions}}
  • Macro Template Repository: {{current_macro_templates}}
  • Regulatory Disclaimer Standards: {{regulatory_disclaimer_requirements}}
  • Client Privilege Protocols: {{client_privilege_standards}}
  • Cross-Border Offerings: {{cross_border_service_offerings}}
  • Contractual Breach Penalties: {{sla_breach_penalties}}

Task

Conduct a rigorous cross-jurisdictional compliance analysis of the firm's client-facing macro repository, identifying legal liability traps, missing regional disclaimers, and breaches of professional privilege standards.

Method

  1. Review {{current_macro_templates}} against local regulatory frameworks in each region specified in {{target_jurisdictions}}.
  2. Evaluate legal liability risks where standardized macro text could be interpreted as binding legal or financial counsel without an executed engagement letter.
  3. Audit the presence and validity of mandatory regional disclaimers against {{regulatory_disclaimer_requirements}}.
  4. Screen macro responses handling confidential materials against {{client_privilege_standards}} to prevent accidental waiver of attorney-client or accountant-client privilege.
  5. Analyze how canned responses address cross-border regulatory variance in {{cross_border_service_offerings}}.
  6. Assess exposure to financial damages or service credits under {{sla_breach_penalties}} caused by misleading macro commitment language.
  7. Classify macro compliance findings by jurisdictional severity level.

Constraints

  • Analysis MUST explicitly identify which specific jurisdiction from {{target_jurisdictions}} is impacted for every flagged issue.
  • MUST NOT treat multi-jurisdictional regulations as uniform across regions.
  • All recommendations MUST preserve the operational speed of frontline staff while eliminating legal exposure.
  • Ambiguous macro clauses MUST be flagged as high-risk if they imply formal advisory warranties.

Output format

  • Executive Legal & Operational Risk Summary (under 250 words)
  • Cross-Jurisdictional Compliance Matrix (table by jurisdiction, macro ID, and compliance status)
  • Privilege and Liability Vulnerability Breakdown (detailed analytical narrative)
  • Disclaimer Adequacy and Enforceability Review (section-by-section analysis)
  • Remediation Action Plan (table with current text, proposed revised text, and rationale)

Self-review

  • Did I evaluate compliance against every jurisdiction in {{target_jurisdictions}}?
  • Are privilege protection mechanisms directly linked to {{client_privilege_standards}}?
  • Does every revised macro recommendation provide exact compliant replacement phrasing?
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
macro-compliance
legal-risk
cross-border