A structured record for understanding an incident, its impact, causes, response, and follow-up work. Complete after a significant incident to document what happened and agree on changes that reduce the chance or impact of recurrence.
Incident summarySummarize the event, severity, duration, trigger, detection, and resolution.
LeadupDescribe relevant conditions and changes before impact began.
FaultExplain what behaved incorrectly and how you know.
ImpactDescribe what customers and internal teams experienced, how many were affected, and for how long.
DetectionRecord how and when the issue was noticed, including who or what raised the alert.
ResponseList responders and key actions in order.
RecoveryExplain what restored service and how the team confirmed recovery.
TimelineRecord key events in chronological order with timestamps and time zones.
Five whysTrace the cause through successive why questions until the explanation points to a condition the organization can change.
Root causeState the underlying causes and explain how they produced the incident.
Backlog checkReview related open work for items that could have prevented or limited this incident.
RecurrenceAssess whether this failure or a similar one has happened before.
Lessons learnedCapture what helped, what slowed the team, and where the outcome depended on luck.
Corrective actionsTurn findings into specific, owned work with a due date and a way to confirm completion.