General email
AuraScore 81/100

Regulatory Email Risk and Privilege Pre-Clearance Checklist

Audit sensitive outbound communications for legal privilege, regulatory exposure, and data discovery vulnerabilities.

Use this checklist before dispatching critical emails concerning regulatory inquiries, litigation, or sensitive governance matters. It helps legal counsel and risk officers systematically scrub liabilities and protect confidentiality.

Template

Role: Senior Litigation Counsel and Regulatory Risk Auditor with 15+ years evaluating high-stakes corporate communications.

Context

  • Draft content under review: {{email_draft_text}}
  • Target recipient roster: {{recipient_group}}
  • Relevant legal jurisdiction: {{jurisdiction_framework}}
  • Internal confidentiality rating: {{confidentiality_tier}}
  • Associated legal or audit matter: {{matter_reference}}
  • Flagged regulatory exposure areas: {{known_risk_factors}}

Task

Generate a comprehensive pre-transmission legal audit checklist and redaction guide for {{matter_reference}} that evaluates the supplied email draft to prevent inadvertent waiver of attorney-client privilege, minimize regulatory exposure under {{jurisdiction_framework}}, and ensure bulletproof compliance prior to transmission.

Method

  1. Analyze {{email_draft_text}} against {{jurisdiction_framework}} to detect inadvertent admissions of liability or regulatory non-compliance.
  2. Evaluate {{recipient_group}} to identify third parties who could break common interest doctrine or attorney-client privilege.
  3. Audit all terminology within {{email_draft_text}} for speculative assertions, emotional language, or informal shorthand that creates evidentiary exposure.
  4. Cross-reference {{confidentiality_tier}} against required header classifications, disclaimers, and distribution list permissions.
  5. Map {{known_risk_factors}} to specific sentences in the text, formulating precise line-by-line mitigation edits.
  6. Formulate binary pass/fail verification checkpoints covering privilege preservation, factual precision, and discovery readiness.
  7. Construct an escalation trigger protocol indicating when the email must be held for executive general counsel sign-off.

Constraints

  • Checklists MUST use strict binary pass/fail gates with explicit remediation actions for failed items.
  • You MUST NOT approve broad privilege assertions over non-privileged business operational data.
  • All recommended textual revisions must preserve original business objectives while eliminating legal liability.
  • Recommendations MUST strictly adhere to the standards of {{jurisdiction_framework}}.

Output format

Provide the review strictly in these four sections:

  1. Executive Risk Summary (max 100 words summarizing privilege and liability risk)
  2. Pre-Send Gate Checklist (table with columns: Audit Item, Status [Pass/Fail/Flag], Legal Rationale, Required Remediation)
  3. Mandatory Textual Amendments (side-by-side comparison of original text vs. scrubbed text)
  4. Transmission Clearance Protocol (numbered sign-off steps and routing rules)

Self-review

  • Confirm every item in {{known_risk_factors}} has a corresponding checkpoint in the audit table.
  • Verify that external recipients in {{recipient_group}} are flagged if privilege waiver risks exist.
  • Check that all proposed line edits remove speculative risk without altering core business intent.
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.

emails
emails-general
research-productivity-operations
legal
compliance
email audit