Skip to main content
Writing post-mortems is one thing. Making sure they actually get written, reviewed, and completed across your organization is another. This is especially true as your team grows and the number of incidents increases. You need visibility into what’s been done and what’s outstanding, and you need a way to enforce standards without chasing people around.

​
Post-mortem list view

The post-mortem list view gives you a single place to see every post-mortem across your organization. You can filter by status, severity, incident type, team, incident lead, participants, custom fields, and more, so you can quickly find the post-mortems that need attention. Each row shows the post-mortem’s status, the incident it belongs to, and how many follow-ups have been completed. This is the view you want if you’re a manager or process owner who needs to keep track of how your team is doing with post-incident work. Each team also has its own post-mortem list on their team page, pre-filtered to show only post-mortems for that team’s incidents.

​
Custom columns

By default, the list shows status, severity, incident duration, follow-ups, and last updated. You can customize which columns are visible by clicking the Display button in the toolbar. From there, you can add columns for any of your custom fields or incident roles, so the list shows exactly the information you care about.

​
Saved views

If you find yourself applying the same filters and column configuration repeatedly, you can save it as a view. Saved views capture your current filters, sorting, and column selection, and are available to everyone in your organization. This is useful for things like “Critical incidents missing post-mortems” or “My team’s in-review documents.” You can switch between views, rename them, or delete them from the view dropdown.

​
Post-incident flow

The post-incident flow is a guided sequence of tasks that kicks in after an incident is closed. You can include post-mortem related tasks in this flow, such as:
  • Export the post-mortem: creates or exports the post-mortem document.
  • Draft the post-mortem: prompts the responder to write the post-mortem and move it to review.
  • Mark post-mortem as complete: a reminder to finish the review and mark the document as complete.
  • Share the post-mortem: a prompt to share the completed document.
These tasks can have default assignees, so the right person is automatically responsible. You can use expressions to assign tasks conditionally. For example, the incident lead always gets the “Create post-mortem” task, but a specific team lead gets the “Review” task for critical incidents. Tasks can also have due dates and reminders. You can set these up as expressions too, so critical incidents get a shorter deadline than minor ones. Reminders are sent automatically when tasks are overdue. If a post-mortem isn’t needed for a particular incident, the responder can opt out of the post-incident flow with a reason. This gives you visibility into why post-mortems were skipped without forcing people through a process that doesn’t apply.

​
Policies

Policies let you enforce post-mortem completion SLAs across your organization. You configure them in Settings > Policies, where you can create rules that define which incidents require a post-mortem (based on severity, type, or other properties) and set deadlines for completion. When a post-mortem is overdue, the responsible people are notified via Slack and email. You can also set up recurring reports — daily, weekly, or monthly — that summarize outstanding post-mortems and deliver them to Slack channels or email. Reports can be suppressed if there are no current violations. Policies are available on Pro and Enterprise plans.

​
Settings

Post-mortem settings are managed in Settings > Post-mortems. Here you can configure:
  • Default timezone for timestamps in exported post-mortems.
  • Custom terminology to rename “post-mortem” across the product.
  • Template expression for dynamic template selection based on incident properties.
  • Export destinations for Google Docs, Notion, Confluence, and SharePoint.
  • Share templates for Slack announcements.
  • Auto-sync follow-ups from external documents back into incident.io.