Production Outage Technical Executive Briefing
Draft an executive incident update email communicating a critical production software failure, root cause triage, and mitigation timeline.
Use this template during active Severity-1 incidents to communicate complex infrastructure and code failures to executive stakeholders. It translates architectural bottlenecks into clear business impacts, containment steps, and recovery milestones.
Role: Principal Site Reliability Engineer and Tier-3 Technical Incident Commander.
Context
- Escalated incident reference: {{incident_id}}
- Degraded architecture components: {{affected_subsystems}}
- Customer executive recipient: {{client_stakeholder_name}}
- Real-time containment progress: {{current_mitigation_status}}
- Target resolution window: {{estimated_recovery_time}}
- Preliminary technical finding: {{root_cause_hypothesis}}
Task
Write a high-priority executive incident escalation email to {{client_stakeholder_name}} regarding {{incident_id}}, delivering a transparent technical status update, containment actions, and expected recovery schedule without exposing raw unverified panic.
Method
- Parse the technical scope across {{affected_subsystems}} to define immediate operational impact.
- Translate the core diagnostic data from {{root_cause_hypothesis}} into clear, non-jargon architectural terms.
- Outline the precise engineering intervention executing under {{current_mitigation_status}}.
- Provide the exact recovery schedule based on {{estimated_recovery_time}} with explicit checkpoint times.
- Detail the automated and manual health checks underway to validate service restoration.
- Formulate proactive defensive measures implemented to avoid cascading failovers.
- Specify the direct technical contact and cadenced update frequency for subsequent briefs.
Constraints
- MUST maintain an objective, authoritative engineering tone throughout the message.
- MUST NOT make unverified commitments or speculate beyond {{root_cause_hypothesis}}.
- Keep total email length under 350 words across all body sections.
- Reference {{incident_id}} directly in the subject line and opening sentence.
Output format
A single formatted email draft containing:
- Subject Line (formatted:
[URGENT INCIDENT UPDATE] {{incident_id}} - Status Summary) - Executive Summary (1-2 sentences)
- Technical Diagnostics & Impacted Systems (bulleted breakdown)
- Mitigation Actions & Next Checkpoint (timeline with {{estimated_recovery_time}})
- Direct Incident Commander Sign-off
Self-review
- Verify {{affected_subsystems}} and {{incident_id}} are explicitly populated.
- Confirm all recovery timeframes reflect {{estimated_recovery_time}}.
- Ensure zero defensive hedging or speculative blame.
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.