> For the complete documentation index, see [llms.txt](https://docs.pagerly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pagerly.io/incident-response/postmortems.md).

# Postmortems

Pagerly generates a postmortem for you the moment an incident is resolved, drafts it with AI from the incident's own history, and lets your team review, edit and publish it — all without leaving Pagerly. When you're ready, export a copy to Confluence or Notion.

## Generating a postmortem

A postmortem can be created once an incident is **Resolved**.

* **From Slack** — when an incident is resolved, Pagerly posts a **📝 Generate Postmortem** button into the incident thread. Click it and Pagerly drafts the document, then replies with a link to open it.
* **From the dashboard** — open the incident and click **Generate Postmortem** in the right-hand panel.

The draft is written by AI from everything Pagerly already knows about the incident:

* Title, description, severity, team and trigger source
* The full update timeline (status changes, severity changes, role assignments, comments)
* Time to resolve
* Any AI investigation findings gathered during the incident

If AI is unavailable, Pagerly still creates the postmortem with a pre-filled timeline and empty sections for you to complete — you're never blocked.

## Sections

Every postmortem is organised into editable sections:

* **Summary**
* **Impact**
* **Root Cause**
* **What Went Well**
* **What Went Wrong**
* **Timeline** — a chronological record compiled from the incident's lifecycle events and comments
* **Suggested Action Items** — AI-proposed follow-ups you can turn into tracked action items in one click

An **AI-generated draft — please review** note is shown on fresh drafts so nobody mistakes them for a reviewed document.

## Editing & publishing

Each section is editable inline (Markdown supported and rendered). A postmortem moves through two states:

* **Draft** — work in progress, freely editable
* **Published** — the reviewed, final version

Click **Publish** when the review is complete. Suggested action items each have an **Add as action item** button that creates a tracked [action item](/incident-response/action-items.md) linked to the incident.

## The Postmortems page

A dedicated **Postmortems** page (under **Incidents & Paging** in the dashboard) lists every postmortem in your workspace with its status (Draft / Published), whether it was AI-generated, and when it was created and last updated. Filter by status, and click any row to open the full postmortem on its own page.

## Export to Confluence or Notion

Pagerly is the source of truth for the postmortem; export publishes a copy to your documentation tool and stores the link back on the postmortem.

* **Confluence** — uses your existing Confluence connection. Set the destination **space key** in the incident settings (defaults to `P`).
* **Notion** — paste a Notion internal-integration token and the parent page id in the incident settings.

Use the **Export** dropdown on the postmortem and pick Confluence or Notion. Once exported, a link to the external copy is shown on the postmortem.

{% hint style="info" %}
Export destinations are configured per team under **Incident Settings → Postmortem Export & Issue Tracking**.
{% endhint %}