Skip to content

Post-Mortems ​

After an incident is fixed, write a blameless review: what happened, why, what helped, and what you'll follow up on. Each incident has one post-mortem.

The Flow ​

Draft → In review → Approved → Published
StageWhat it means
DraftYou're still writing
In reviewYou've asked for feedback
ApprovedReviewers are happy with it
PublishedFinished and locked — no more edits

To send for review you'll confirm the review is blameless. Publishing locks the post-mortem so it can't be changed afterward.

What to Write ​

  • What happened — short summary and timeline of key events.
  • Why — root cause and anything that contributed.
  • Impact — how long, what was affected, who felt it.
  • What helped — what went well during the response.
  • What to improve — what didn't work and lessons learned.

Follow-Up Tasks ​

Add follow-up tasks with an owner and a due date so fixes actually happen.

  • For the due date you can pick just a date (treated as end of that day) or a full date and time.
  • To clear a date, empty the field and save.
  • If a task goes overdue, its owner gets a reminder.

You can see all open follow-ups in one place, sorted with the most urgent due dates first.

Workflow in the App ​

  1. Open the incident's Post-mortem tab (a draft may already be started for you after resolving).
  2. Fill in the sections while it's a draft.
  3. Click Submit for review and confirm it's blameless.
  4. Reviewers approve, then you click Publish.
  5. Track follow-up tasks to completion.

If review sends it back, it returns to draft for more edits.

See Also ​

Released under the MIT License.