Critical Integration Outage Client Remediation Notice
Draft an authoritative executive debugging post-mortem and remediation email for client leadership following a high-severity production outage.
Use this template when a production integration failure has impacted a professional services client and engineering leadership needs to deliver a definitive technical diagnosis alongside actionable recovery milestones.
Role: Principal Site Reliability Engineer specializing in professional services client recovery and systems debugging.
Context
- Client Account: {{client_name}}
- Incident Identifier: {{incident_id}}
- Impacted Production System: {{affected_service}}
- Diagnostic Stack & Error Payload: {{error_payload}}
- Verified Root Cause Findings: {{root_cause_analysis}}
- Remediation Schedule & Workarounds: {{remediation_timeline}}
Task
Synthesize raw telemetry, application logs, and root-cause findings into an executive-grade debugging report and technical remediation email to restore client trust and outline concrete preventative measures.
Method
- Analyze {{error_payload}} against normal operating baselines to isolate the precise failure boundary.
- Correlate stack traces and network logs with {{root_cause_analysis}} to verify state transitions during the incident.
- Segment technical debugging data into an executive summary, technical breakdown, and operational impact assessment.
- Document the exact sequence of environmental conditions, race conditions, or unhandled exceptions that triggered {{incident_id}}.
- Detail the immediate containment patch applied to {{affected_service}} and verify data integrity checks.
- Translate {{remediation_timeline}} into milestone-based engineering commitments with explicit verification gates.
- Frame communication for dual audiences: non-technical client sponsors and engineering audit teams.
Constraints
- MUST express technical failure mechanisms in precise, blameless architectural terminology.
- MUST NOT expose internal API tokens, credentials, or proprietary intellectual property outside {{client_name}}'s scope.
- Every identified bug MUST map directly to a permanent regression test or monitoring alert.
- Total email length MUST be under 750 words.
Output format
An email draft containing:
- Subject Line: Professional, structured incident identification
- Executive Summary: 3-4 sentences summarizing incident scope and resolution status
- Technical Post-Mortem: Diagnostic timeline, isolated root cause, and stack analysis
- Corrective Actions & Milestones: Bulleted table of patches, regression tests, and target deployment dates
- Governance & Sign-off: Direct contact info for escalation
Self-review
- Does the email clearly distinguish between temporary mitigations and permanent code fixes?
- Are all technical assertions supported by the supplied diagnostic data?
- Is the tone professional, accountable, and free of vague generalizations?
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.