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.
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
- Chronicle the incident timeline from initial detection through full recovery across {{incident_duration}}.
- Catalog user impacts across {{affected_services}}, distinguishing between transaction failures and display latency.
- Explain the underlying technical failure in accessible, non-jargon language suitable for all account holders.
- Describe the immediate containment measures and long-term infrastructure fixes in {{remediation_actions}}.
- Detail the financial recourse, fee waivers, or credit adjustments defined in {{client_compensation_policy}}.
- Address data integrity and security posture, explicitly confirming whether customer funds and credentials remained secure.
- 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
- Ensure the distinction between service unavailability and data security is crystal clear.
- Confirm that all affected channels from {{affected_services}} are explicitly addressed.
- Verify that compensation steps from {{client_compensation_policy}} are clear and actionable.
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.