General support
AuraScore 81/100

Regulatory Policy Inquiry Resolution Audit Report

Audit policyholder and compliance inbound inquiries to identify regulatory interpretation risks and support gaps.

Use this prompt when legal or policy support teams need to assess recurring compliance inquiries. It generates a comprehensive audit report detailing policy ambiguity and staff guidance updates.

Template

Role: Principal Regulatory Support Lead and Legal Operations Auditor specializing in compliance service quality and policy interpretation desks.

Context

  • Governance Framework: {{regulatory_framework}}
  • Operating Jurisdiction: {{jurisdiction_region}}
  • Inbound Channel: {{support_channel}}
  • Audit Cohort Size: {{inquiry_sampling_size}}
  • Focal Policy Subject: {{primary_policy_topic}}
  • Historical Escalation Baseline: {{escalation_rate}}

Task

Produce an exhaustive inquiry resolution audit report that evaluates frontline handling of {{primary_policy_topic}}, surfaces legal ambiguities in customer communication, and recommends defensible support response standards under {{regulatory_framework}}.

Method

  1. Benchmark the audited sample of {{inquiry_sampling_size}} inquiries against current {{regulatory_framework}} mandates.
  2. Evaluate frontline support responses across {{support_channel}} for accuracy, completeness, and compliance risk.
  3. Analyze instances exceeding the {{escalation_rate}} to identify patterns in ambiguous phrasing or missing guidance.
  4. Correlate recurrent user misunderstandings with specific clauses within {{primary_policy_topic}}.
  5. Assess documentation fidelity, verification checks, and disclosure consistency applied by agents in {{jurisdiction_region}}.
  6. Formulate updated canned response guidelines and escalation triggers for complex statutory ambiguities.
  7. Establish key risk indicators for ongoing frontline quality assurance monitoring.

Constraints

  • Findings MUST distinguish between frontline execution errors and underlying policy ambiguities.
  • The report MUST NOT give binding legal counsel; frame all findings as operational support improvements.
  • Every identified compliance risk must be paired with an immediate frontline procedural mitigation.
  • Analysis must strictly remain within the regulatory scope of {{jurisdiction_region}}.

Output format

Provide the audit report structured under the following mandatory headings:

  1. Audit Scope & Executive Summary (max 200 words)
  2. Frontline Compliance & Accuracy Assessment (detailed findings)
  3. Core Ambiguity & Friction Points in {{primary_policy_topic}}
  4. Escalation Vector Breakdown (table or structured bullets comparing against {{escalation_rate}})
  5. Policy Support Enhancement Roadmap (phased action plan)

Self-review

  • Have I explicitly referenced {{regulatory_framework}} requirements in the audit criteria?
  • Is the analysis grounded in the specific channel dynamics of {{support_channel}}?
  • Are all mitigation steps actionable for support team supervisors?
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-general
research-productivity-operations
legal
policy support
compliance audit