Incident report (postmortem) template.
For the postmortem doc written after the page is mitigated. Pair with the on-call recording (Screendog captures it during triage) for evidence of what actually happened.
The template
### Summary
[One paragraph for an executive: what happened, who was affected, for how long, what we did]
### Timeline (UTC)
- HH:MM — first signal (alert / customer report)
- HH:MM — on-call engaged
- HH:MM — root cause hypothesised
- HH:MM — mitigation deployed
- HH:MM — fully resolved
### Impact
- Users affected:
- Revenue impact (rough):
- Internal teams blocked:
### Root cause
### Contributing factors
### What went well
### What did not go well
### Action items
- [ ] [Owner] — short-term mitigation
- [ ] [Owner] — long-term fix
- [ ] [Owner] — improvement to detection / response
### Evidence
- On-call recording: <link>
- Dashboard snapshots: <link>
Frequently asked
Blameless?
Yes. Name systems and decisions, not people, in the contributing-factors section.
Try Screendog free.
5 recordings on the free trial. Real Linear, GitHub, Notion, Slack, and Jira filing. No credit card.
Start a workspace — free