📋
IT & Product
Incident Postmortem
A blameless postmortem that turns an outage into a timeline, a root cause, and owned action items — the learning artifact, not the blame artifact.
Use this template18 fields · Free · Customize before publishing
What this form looks like
Preview · not interactiveIncident Postmortem
A blameless postmortem that turns an outage into a timeline, a root cause, and owned action items — the learning artifact, not the blame artifact.
Incident summary
Incident title*
e.g. Checkout API returning 500s after cache deploy
One line a future engineer could search for and recognize.
Incident ID*
INC-2431
Severity*
Select…▾
Affected services*
Select…▾
Impact started*
Pick a date📅
When customers first felt it — not when the alert fired.
Impact ended*
Pick a date📅
Total customer impact*
Pick a date📅
Duration customers were actually affected — may be shorter than the incident itself.
What happened
Customer impact description*
How was it detected?*
Select…▾
Customer-reported incidents usually point at a monitoring gap worth an action item.
Timeline*
Root cause*
Blameless means the cause is a system condition, never an individual.
Contributing factors
Select…▾
Making it not happen again
Action items*
Lessons learned
How effective was our incident response?*
★★★★★
The response, not the incident — detection speed, coordination, communication.
Submit