A postmortem is the document you write after an incident is resolved, capturing what happened, what caused it, and what you’ll do to prevent the next one. In Warrn, every postmortem belongs to exactly one incident and lives in its Post-Mortem tab.Documentation Index
Fetch the complete documentation index at: https://docs.warrn.io/llms.txt
Use this file to discover all available pages before exploring further.
Starting one
Open the resolved (or in-progress) incident, go to the Post-Mortem tab, and click Create postmortem. You’ll be asked whether to start blank or seed from a template. Templates are defined org-wide at/settings/incident-policies → Postmortem Templates. Most orgs have one or two: a short version for low-severity incidents and a longer one for sev1s.
Writing it
The postmortem editor is the same rich editor as the rest of Knowledge:- Auto-save on every keystroke.
- Slash commands (
/) for headings, lists, tables, code, embeds. - Live collaboration with multiple cursors.
- @mentions for teammates.
- Version history with restore.
- Table of contents in the side panel.
- Writeagen AI assist for first drafts of root cause, impact summary, and timeline narration.
Status
A postmortem moves through three states:| Status | Meaning |
|---|---|
| Draft | You’re still writing. |
| Ready for Review | Done writing, asking teammates to read. |
| Published | Approved and final. Posted to the timeline as postmortem_published. |
Exporting to Confluence
If the org has Confluence connected, an Export to Confluence button copies the published postmortem into the default Confluence space (configured at/settings/incident-policies → Integrations). The status bar at the bottom of the editor shows where the copy went.
When to write one
Most teams write a postmortem for any sev1 or sev2, and skip it for sev3/sev4 unless something interesting happened. You can configure deadline reminders per severity at/settings/incident-policies → SLA Policy (the RCA deadline schedule).