The incident is over.Where does the lesson get written?
Most teams learn something from every outage and meet the same thing again months later. A structured postmortem keeps that learning in a fixed shape, attached to the incident itself.
Free plan: 3 monitors and one vantage point · 14-day Pro trial
Five fixed fields
A fixed shape means everyone writes the same way and it stays reviewable.
Summary
What happened, in a few lines.
Impact
Who and what was affected, and for how long.
Root cause
Not the symptom, but what actually caused it.
Resolution and prevention
How it was fixed, and what keeps it from happening again.
Draft, then publish
Draft first
Save it incomplete and finish it after the team has looked.
Then publish
The final version is marked as published, so it is clear the review is done.
One per incident
Each incident has exactly one postmortem, so no scattered versions appear.
Where this stops
No action-item list
Follow-up work is not tracked as assignable items; for now it is written as text.
It is internal
Postmortems are not published on the public status page.
From the Starter plan
Writing one is a Starter feature; reading what is already written is not restricted.
Related features
Keep the experience in the team
After your first real incident, fill in the five fields and see how much it is worth later.
Create a free account