Incident communication template
Ready-to-use messages for every stage of an IT incident, from first alert to postmortem, so users and management always know what’s happening.
During an outage, silence creates more pressure than the outage itself. Use these templates so the right people hear from you early, regularly and in plain language.
1. Initial notice (within 15 minutes)
[Investigating] [Service name] is unavailable / degraded
We’re aware that [service] is [unavailable / slow / showing errors] for [who is affected] since [time]. Our team is investigating.
Workaround: [if any, otherwise "None at this time"]
Next update: [time, e.g. in 30 minutes]
2. Progress update (every 30–60 minutes)
[Identified / Monitoring] [Service name]
Status: [what we know now, in one or two sentences]
Impact: [who and what is still affected]
What we’re doing: [current action]
Next update: [time]
3. Resolution notice
[Resolved] [Service name] is back to normal
[Service] has been working normally since [time]. Total impact: [duration] for [who].
Cause (short): [one sentence, no blame]
Next: We’ll share a summary of what happened and what we’re changing by [date].
4. Postmortem summary (within 5 working days)
| Section | What to write |
|---|---|
| Summary | What happened, in three sentences |
| Impact | Who was affected, for how long, and any business impact |
| Timeline | Key times: detected, escalated, mitigated, resolved |
| Root cause | The underlying cause, not just the trigger |
| What went well | Detection, teamwork, tools that helped |
| What we’re changing | Actions with an owner and a due date |
Who to inform
- Users affected: initial notice, updates and resolution
- Management: the same, plus business impact and expected cost
- Service desk: everything first, so they can answer calls
- Vendors: if they’re involved in the fix, with a clear owner on each side