General writing
AuraScore 81/100

Digital Banking Incident Impact Report

Author a structured incident review report detailing digital service disruption and remediation.

Use this template after an unexpected banking platform outage or payment gateway failure. It produces a clear, transparent customer and stakeholder report explaining cause, resolution, and restitution.

Template

Role: Financial Services Crisis Communications Lead specializing in consumer transparency and operational risk disclosures.

Context

  • Financial Institution: {{financial_institution}}
  • Incident Classification: {{incident_type}}
  • Outage Duration: {{incident_duration}}
  • Impacted Systems: {{affected_services}}
  • Corrective Actions: {{remediation_actions}}
  • Client Restitution Policy: {{client_compensation_policy}}

Task

Draft a formal post-incident impact and transparency report detailing the root cause, operational timeline, client impacts, and remediation measures taken by {{financial_institution}} following the {{incident_type}}.

Method

  1. Chronicle the incident timeline from initial detection through full recovery across {{incident_duration}}.
  2. Catalog user impacts across {{affected_services}}, distinguishing between transaction failures and display latency.
  3. Explain the underlying technical failure in accessible, non-jargon language suitable for all account holders.
  4. Describe the immediate containment measures and long-term infrastructure fixes in {{remediation_actions}}.
  5. Detail the financial recourse, fee waivers, or credit adjustments defined in {{client_compensation_policy}}.
  6. Address data integrity and security posture, explicitly confirming whether customer funds and credentials remained secure.
  7. Summarize institutional governance safeguards implemented to prevent recurring vulnerabilities.

Constraints

  • MUST clearly state that customer data and core balances remained secure.
  • MUST NOT use defensive, evasive, or overly dense technical jargon.
  • MUST explicitly provide exact instructions for customers seeking claims under {{client_compensation_policy}}.
  • Keep document length between 500 and 800 words.

Output format

Format as a markdown business report structured as follows:

Incident Review Report: {{incident_type}}

1. Executive Summary & Status Overview

2. Event Timeline & Affected Services

3. Root Cause Analysis & Security Verification

4. Remediation & Preventive Measures

5. Account Holder Recourse & Compensation Details

Self-review

  1. Ensure the distinction between service unavailability and data security is crystal clear.
  2. Confirm that all affected channels from {{affected_services}} are explicitly addressed.
  3. Verify that compensation steps from {{client_compensation_policy}} are clear and actionable.
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 engineering10/12 · Adequate

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 efficiency7/10 · Adequate

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
financial-services
incident-report
retail-banking
crisis-communications