1. IMR Help
  2.    
  3. AI in Xurrent IMR
  4.    
  5. AI Postmortem

AI Postmortem

Draft a postmortem report with Sera AI

Writing a postmortem means reassembling the incident: when it was detected, who was paged, what each responder did, and in what order. Sera AI drafts that record for you from the incident's own history.

Where several incidents share a cause, attach them to one postmortem and Sera drafts a single report across all of them — one timeline, one root cause narrative, one set of corrective measures.

You review the draft, attach it to the postmortem, and turn the recommended actions into tracked post-incident tasks.

Before you begin

Requirements

  • The incident must have a history to draw on. Sera reads the incident record, so an incident with no recorded activity produces a thin draft.
  • A postmortem can be created at any point in an incident's lifecycle, but a draft generated before resolution will report the incident as unresolved.

Important

  • Verify the timeline before saving. Sera reconstructs events from the incident record, and attribution or sequence can need correcting.
  • Timeline entries are rendered in a single timezone. Confirm it matches what your reviewers expect, particularly for incidents spanning regions.
  • The depth of the draft tracks the depth of the record. A postmortem covering one sparse incident returns a summary and timeline; one covering several well-documented incidents returns root cause, recovery, and corrective measures as well.

Create a postmortem

  1. Open the incident and select Postmortem in the left panel.
  2. Click Create Postmortem.

To add this incident to a postmortem that already exists, click Attach To Postmortem instead.

On the Postmortem Details page, set the Title and Status. The postmortem records who created it, and can be reached from any of its attached incidents.

Attach incidents and post-incident tasks

The Postmortem Details page holds both sides of the postmortem: the incidents it covers, and the work that comes out of it. Attach the incidents before generating the report, and add the tasks after reviewing it.

Attach related incidents

A cluster failure rarely produces one incident. It produces a CPU alert, a latency alert, a duplicate of each, and an escalation. One postmortem covering all of them is more useful than six covering fragments.

  1. Under Attached Incidents, click Add Incidents.
  2. Search by incident number or title in the Attach Incidents dialog.
  3. Click Add beside each incident to attach it.
  4. Close the dialog. Attached incidents are listed under Attached Incidents, and can be removed with Unlink.

Tip: Attach every related incident, including duplicates, before generating with Sera. Duplicates are evidence: a run of near-identical incidents inside a few minutes is itself a finding, and Sera reports it in the corrective measures.

Add post-incident tasks

A postmortem that ends in recommendations changes nothing. Post-incident tasks turn them into assigned, tracked work on the postmortem itself.

Under Attached Post Incident Tasks:

  • Create Task — add a task, with an assignee and status
  • Import Tasks — bring in tasks already defined elsewhere

Tip: Work through the corrective measures Sera drafted and create a task for each one your team accepts. The draft gives you the candidate list; the tasks are what make it accountable.

Generate the report with Sera AI

  1. In the Postmortem Report section, click Write with Sera AI.
  2. Sera returns a draft for review, marked as generated by AI.
  3. Rate the draft using the feedback controls. This signal improves future output.
  4. Click Attach Postmortem to insert the draft into the Postmortem Report editor, or Go back to discard it.
  5. Edit the report, complete the remaining fields, and click Save Postmortem.

Once a draft has been attached, View Generated Postmortem replaces the generate control, so you can refer back to the original.

What the draft contains

Section Description
Issue summary What failed, which service was affected, and the impact
Timeline Events across every attached incident, in sequence with timestamps — creation, assignment, escalation, acknowledgement, resolution, and status changes
Root cause What the incident data indicates about the underlying cause
Resolution and recovery How the incident was brought under control, and who was involved
Corrective and preventative measures Recommended immediate actions, process improvements, and monitoring changes

Sera draws all of this from the attached incidents. Detail your responders did not record will not appear in the draft, and the recommended measures are suggestions for your team to accept, reject, or replace.

Use a postmortem template

A template gives every postmortem the same structure, so reviewers know where to look and responders are not deciding what to include at the end of a long incident.

In the Postmortem Report section, click Use Postmortem Templates and select a template. The report is populated with its structure, ready to write into.

Templates and Sera can be combined: generate a draft first and edit it into your template's structure, or start from the template and use the generated draft as the source for its timeline and summary sections.