Post-Incident Reviews
PagerDuty Post-Incident Reviews (formerly Jeli Post-Incident Reviews) allow you to turn incidents into learning opportunities. Post-Incident Reviews integrate with your incident lifecycle, Slack data, and generative AI to help your team uncover systemic patterns, build chronological incident narratives, and coordinate preventative follow-up actions directly within the PagerDuty platform.
User PermissionsAny user with permission to edit an incident has permission to create an associated post-incident review. This includes Limited Users, Users, Admins, and Account Owners.
Post-incident review access is determined by the access settings of the incident it is associated with. There are no additional access controls on a per-review basis.
Editing templates requires an Admin or Account Owner base role.
Create a Post-Incident Review
You can create a post-incident review in the following ways:
In the Web App
-
Navigate to the desired incident's details page and click the Post-Incident Review tab.
-
Click Generate with AI or Start from Scratch.

Start your post-incident review
Via Slack
Coming SoonCreating a post-incident review from Slack is coming soon. When an incident is resolved, a message will be sent to the incident's dedicated Slack channel with options to Generate with AI or Start from Scratch. Clicking either option opens the post-incident review in a new browser tab.
Generate with AI
When you generate a post-incident review with AI, PagerDuty pulls data from up to three sources:
- Scribe Agent
- Slack messages from the dedicated incident channel
- Incident Lifecycle Events (ILE)
The AI uses this data to write the individual sections of your review, generate narrative markers, and create follow-up actions.
Missing Data SourcesIf Scribe Agent was not active during the incident, that data source will not be available. The AI generates the review using whichever sources are present.
Edit a Post-Incident Review
The entire post-incident review is editable. The editor supports rich text formatting, inline comments, and live collaborative editing.
- Highlight text to apply formatting options.
- Click the comment icon to leave a comment.
- Tag teammates using @mention.
- Changes made by collaborators appear in real time.
- AI-generated content is labeled with an AI badge. Editing an AI-generated section removes the badge.
Import Data From Slack
If the AI output has gaps, you can supplement it with additional Slack data:
-
In the narrative section, click Import Data Custom Import Data.
-
Select the Workspace and Channel you want to pull from. This is most commonly used to add data from other channels in the same workspace.
-
Select a Date Range. You can drill down to a specific start time and end time.
-
Select Messages to import. This can be everything from a channel or only pinned messages.
-
Click Import Data.

Import data from Slack
-
Click Generate Markers. The narrative updates based on the newly imported data.
Narrative Builder
The narrative builder displays the incident narrative with supporting evidence attached to each narrative marker. Click Supporting Evidence next to a marker to expand the evidence that informed that section of the narrative.
If you started your post-incident review from scratch, or would like to rebuild the incident narrative, you can do so in two ways:
- With AI: Click on the narrative builder, and then click Generate Markers in the Narrative Builder screen.
- Manually: Click on the narrative builder, select events from the left-side panel, and attribute them to narrative markers by clicking Create New Marker.
Once a narrative is built, it automatically populates the incident's timeline.
Follow-Up Actions
Follow-up actions track tasks that help remediate the impacts of an incident, prevent similar incidents from recurring, or implement monitoring.
You can create follow-up actions in two ways:
- With AI:
- Click Generate with AI on the Post-Incident Review landing page, if you have not yet started your review.
- Click the sparkle icon on the Follow-up Actions section and select your preferred generation settings.
- Manually: Click on the Follow-up Actions section and fill out the relevant details of the follow-up action.

Follow-up actions
To view a filterable list of follow-up actions, navigate to Incidents Post-Incident Reviews and click the Follow-Up Actions tab.
Assign a Follow-Up Action
You can assign follow-up actions to teammates:
- Click next to the follow-up action and select Edit Follow-Up.
- Add a note, assign a person to the task, and set a due date.
Full Screen Mode
Click the icon to enter a focused editing view that removes surrounding UI elements and displays only the post-incident review.
Sidebar
The sidebar displays contextual information from the incident alongside the review.
Export a Review
You can export a post-incident review from the sidebar. Under Export, select one of two options:
- HTML: View a shareable link to the post-incident review.
- PDF: Download the post-incident review as a PDF.
Manage Templates
Post-incident reviews consist of predefined template sections that can be filled out by the AI or manually after an incident. The Incident Narrative and Follow-up Actions sections are built-in with every template and cannot be removed.
To add, edit, or delete sections in your templates:
- Navigate to Incidents Post-Incident Reviews and open the Template tab.
- Create, edit, or delete sections in your templates. For each section, you can set:
| Field | Description |
|---|---|
| Section Name | The name of the template section. |
| Section Description | Helps writers understand what to write in the section. |
| Required Section | Determines if the section is required or optional. |

Post-incident review template builder
Coming SoonThe ability to create multiple custom templates is in development. Admins and Account Owners will be able to define both human instructions and AI prompts for each section of a template. Additional per-section settings — an LLM prompt, a required toggle, and an AI-generation toggle — are also coming soon.
