--- title: Incident post-mortems with tracked action items description: Post-mortems written in a wiki nobody revisits are where action items go to die. The new Post-mortems section lets you write a structured retrospective on any… canonical: https://watchfor.io/changelog/2026-08-21-incident-postmortems --- [All updates](/changelog/page/7#2026-08-21-incident-postmortems) ✨ New Aug 21, 2026 · v 5.7.1 # Incident post-mortems with tracked action items Post-mortems written in a wiki nobody revisits are where action items go to die. The new Post-mortems section lets you write a structured retrospective on any incident in a rich editor (no markup to learn; Markdown stays available as an advanced mode), with severity and root-cause classification, an extendable timeline, and action items with assignees and due dates. The list view keeps drafts and open follow-ups visible, and completed post-mortems can be published to your status page. Available on higher plans. Severity, root cause and the write-up sit right next to the incident. ## Write it next to the evidence A post-mortem is attached to its incident, so the timeline, the confirming checks and your internal notes are one click away. Start one from Post-mortems → New post-mortem or from the incident page. The draft opens with a template covering what every good review answers: summary, impact, root cause, detection, resolution, what went well and what could have gone better. - Rich editor: headings, bold, code and lists from a toolbar. A Markdown tab and a preview are there if you prefer. - Severity and root-cause category (deploy, configuration change, third-party dependency, capacity and so on), so reviews can be compared across incidents. - Timeline: the incident's own start and end, plus your entries, such as when the rollback finished. - Action items with an assignee and a due date. Overdue items are flagged, and the open count stays visible in the list. ## An example Checkout was down for 24 minutes after a configuration change. You open the incident, start a post-mortem, set severity Major and category Configuration change , and add two action items: "Add config validation to CI" for Jordan, due Friday, and "Alert on checkout error rate" for Priya. A week later the Post-mortems list still shows one item open, so it can't quietly slip. ## Share it, if you choose Mark it completed and, as an owner or admin, publish it. It then appears on your status page's incident, without assignee names. Internal notes always stay private. Post-mortems are included on higher plans; see [pricing](/pricing). Details in [Post-mortems](/docs/alerting/postmortems). Share this update --- Canonical page: https://watchfor.io/changelog/2026-08-21-incident-postmortems · Site guide: https://watchfor.io/llms.txt