Postmortem Report Template
A postmortem template is a standard structure for documenting an incident: summary, impact, timeline, root cause, what went well and poorly, and action items.
Why it exists
Without a shared structure, postmortems vary wildly in depth, skip key analysis, devolve into blame, or end without concrete follow-up. A template helps reviewers cover the same essential ground and record follow-up work, but the team must still investigate and track the actions.
The mental model
Think of the template as a checklist that shapes the conversation. By prompting for specific sections, it forces the team past the immediate fix into impact, true root cause, and systemic improvement, and it deliberately frames the whole exercise as blameless learning rather than fault-finding.
How it works
A common template includes a concise summary of what happened, the impact in user and business terms including duration and scope, a timestamped timeline, root cause and contributing factors often explored with techniques like the five whys, an honest assessment of what went well and what went poorly, and a list of action items each with a clear owner and tracking link. Many teams add severity classification and detection and resolution durations. The filled report is reviewed, often in a meeting, then shared widely so others learn.
When it matters
A template matters most in organizations running many incidents across many teams, where consistency lets you spot recurring themes and measure whether reliability is improving. It also matters culturally: a blameless template signals that the goal is system improvement, which encourages honest disclosure of mistakes. Its weakest point is when action items are listed but never tracked, so the action-item section with owners is the part that delivers durable value.
A concrete example
After a checkout outage, the team fills the template: summary, impact of 22 minutes of failed checkouts affecting a percentage of users, the reconstructed timeline, a root cause of an unbounded retry storm, what went well such as fast rollback, what went poorly such as an eight-minute detection gap, and three action items each assigned to a named owner with linked tickets, ensuring the fixes actually happen.
Interview question
Which section of a postmortem template most directly determines whether the incident actually leads to lasting improvement?
- a.The summary paragraph describing what happened
- b.The severity label assigned to the incident
- c.The list of attendees at the review meeting
- d.Action items with named owners and tracking linksCorrect
Why? this is the answer
Improvement depends on follow-up work being tracked and owned, so action items with owners and links are what convert lessons into durable change. A summary or severity label documents the incident but does not by itself drive remediation.
Just read this? Test yourself on what you have been reading.
Read the original → sre.google
- #postmortem
- #template
- #blameless
- #incident-response
- #sre
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles