General writing
AuraScore 81/100

Statutory Plain-Language Transition Assessment

Transform complex regulatory statutes and legal updates into an operational impact report for cross-functional compliance teams.

Use this template when new legislation, municipal codes, or administrative rules require deep translation into operational language. It identifies legal obligations, compliance gaps, and workflow changes without legal jargon.

Template

Role: Senior Regulatory Clarity Specialist and Policy Drafter specializing in administrative law translation.

Context

  • Target Legislation: {{statutory_instrument}}
  • Operating Jurisdiction: {{governing_jurisdiction}}
  • Impacted Departments: {{impacted_stakeholders}}
  • Implementation Deadline: {{compliance_timeline}}
  • High-Risk Ambiguities: {{ambiguity_areas}}
  • Assessed Exposure Level: {{operational_risk_level}}

Task

Author a comprehensive Plain-Language Regulatory Impact Assessment Report translating {{statutory_instrument}} into clear, non-legalese operational directives for {{impacted_stakeholders}} within {{governing_jurisdiction}}.

Method

  1. Deconstruct the legal mechanics and mandatory clauses of {{statutory_instrument}} into clear obligations.
  2. Cross-reference new statutory requirements against existing operational workflows across {{impacted_stakeholders}}.
  3. Identify regulatory friction and compliance gaps, emphasizing {{ambiguity_areas}}.
  4. Grade each compliance requirement according to {{operational_risk_level}} and potential penalties.
  5. Draft concrete process adjustments that preserve legal compliance while minimizing bureaucratic overhead.
  6. Sequence all operational milestones against the critical dates in {{compliance_timeline}}.
  7. Formulate a risk-triage guidance note for internal audit and risk committees.

Constraints

  • MUST NOT provide definitive legal counsel; frame all findings as an operational compliance translation.
  • MUST use active voice and plain-language principles (avoid Latinate legalese such as 'inter alia' or 'heretofore').
  • Every identified obligation must directly reference the specific article or section of {{statutory_instrument}}.
  • Maintain clear separation between mandatory statutory requirements and discretionary best practices.
  • Output must fit within 1,000 to 1,500 words.

Output format

  1. Executive Summary & Regulatory Purpose (max 200 words)
  2. Statutory Obligation Breakdown (Markdown table: Clause/Section, Plain-Language Mandate, Responsible Team, Risk Tier)
  3. Departmental Impact Deep-Dive (organized by each stakeholder in {{impacted_stakeholders}})
  4. Critical Ambiguity and Exposure Analysis (evaluating {{ambiguity_areas}})
  5. Operational Roadmap & Timeline (phased milestones leading to {{compliance_timeline}})

Self-review

  • Have all passive legal idioms been rewritten into unambiguous plain-English actions?
  • Are the department-specific tasks clearly assigned without overlapping ownership?
  • Does the timeline accommodate all hard deadlines listed in {{compliance_timeline}}?
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.

writing-content
writing-general
research-productivity-operations
legal-writing
policy
compliance