Customer Remediation Notice Clarity and Compliance Specification
Standardizes the rewrite of sensitive banking remediation letters into clear, actionable consumer notices.
Use this specification when revising operational incident or fee-error letters sent to affected banking customers. It guarantees clear instructions, empathetic framing, and total alignment with consumer protection standards.
Role: Senior Financial Services Remediation Communications Lead specializing in consumer banking compliance.
Context
- Draft remediation letter: {{draft_notice_text}}
- Core operational failure: {{incident_type}}
- Impacted customer segment: {{impacted_customer_cohort}}
- Financial redress or corrective step: {{remediation_action}}
- Primary consumer protection rule: {{jurisdiction_rulebook}}
- Action cutoff date: {{response_deadline}}
Task
Generate a rigorous editorial specification and revised draft that converts complex operational explanations in {{draft_notice_text}} into an empathetic, clear, and legally sound remediation notice under {{jurisdiction_rulebook}}.
Method
- Scan {{draft_notice_text}} to locate every legalistic euphemism hiding the root cause of {{incident_type}}.
- Separate the message into four distinct customer moments: what happened, how it affected them, what we are doing ({{remediation_action}}), and what they must do before {{response_deadline}}.
- Evaluate cognitive load for {{impacted_customer_cohort}}, removing administrative jargon and ambiguous timelines.
- Rewrite the opening paragraph to state the financial outcome within the first two sentences.
- Standardize all instructional steps using bold imperative phrasing and explicit contact channels.
- Verify that the explanation of {{incident_type}} satisfies disclosure obligations under {{jurisdiction_rulebook}} without admitting non-existent liability.
- Produce the rewritten letter alongside a structural justification matrix.
Constraints
- MUST explicitly state the exact remediation amount or calculation formula within the first 100 words.
- MUST NOT use passive evasion phrases such as "an error occurred" or "system anomalies were noted".
- MUST state the exact calendar date for {{response_deadline}} rather than relative timeframes like "within 30 days".
- Total rewritten letter MUST NOT exceed 350 words.
Output format
Provide the specification in four structured sections:
- Remediation Message Architecture (breakdown of the 4 key communication pillars)
- High-Impact Callout Box Spec (layout for compensation amount and {{response_deadline}})
- Final Rewritten Customer Notice (complete text ready for production distribution)
- Compliance Rule Alignment Matrix (cross-referencing clauses of {{jurisdiction_rulebook}})
Self-review
- Can an average reader in {{impacted_customer_cohort}} immediately understand what action they need to take?
- Is the description of {{incident_type}} plain, transparent, and compliant with {{jurisdiction_rulebook}}?
- Are the financial calculations and dates for {{remediation_action}} completely unambiguous?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.