Docs Use Relia every day

Write a postmortem

Write an incident postmortem in one click from what Relia recorded, edit it in your words, copy it as Markdown, and share a public link.

A postmortem explains what went wrong, what it cost and what you'll change. Relia writes one from what it recorded during the incident, with real numbers and a timeline, so you only review and edit.

Before you start

  • Writing a postmortem comes with Growth (10 a month) and Pro (30 a month). A postmortem written earlier can always be read.
  • Anyone on the project can write one. Owners, admins and members can edit it; viewers can read and copy it.
  • Best after the incident is resolved, ideally with a confirmed fix. See Fix it and confirm the fix worked.

Tip: watch From alert to verified fix: fix plan, apply, and "Your fix worked" (2 min).

Steps

  1. Open the incident from Home (or from the resolved incidents).
  2. Find the postmortem bar under How to fix it. Click Write the postmortem. While the incident is still open, the button says Draft the postmortem: it writes what is known so far, and you update it once the problem is resolved.
  3. When it's written, click Open.
  4. Review the sections:
    • Title and Summary.
    • Impact, with the measured numbers (people, failed requests, how long it lasted).
    • Timeline: from the first error, through alerts, "I'm on it", deploys and the fix attempt, to the confirmed fix and resolution.
    • Root cause, in numbered steps, each with the evidence behind it.
    • What was done, What we change (a checklist) and Lessons.
    • Evidence Relia wrote this from: every fact it used, folded at the bottom.
  5. To use your own words, click Edit on a section, change the text and click Save. The section is marked "(your words)". In list sections, put one item per line.

Rewrite, copy, publish

  • Use Relia's text on an edited section puts Relia's words back.
  • Rewrite writes the postmortem again. Your edited sections stay as you wrote them. If the incident changed since it was written, the page says "The incident changed since this was written." and the button says Update to the latest facts.
  • Copy as Markdown copies the whole postmortem with its headings, ready to paste into your docs or a ticket.
  • Publish a link (owners and admins) makes a public page anyone with the link can read. Unpublish takes it down again.

The public page is a masked copy. Internal details are removed before anyone outside sees it:

  • Server names become "a server".
  • Network addresses, trace ids, email addresses and raw routes are removed.
  • Your team members' names become "an engineer", and the name of whoever acknowledged the incident is dropped.

How Relia keeps it factual

Every number and time in the text must come from what Relia recorded. If Relia's prose doesn't pass that check, you get a facts-and-timeline-only version, and the page says "Facts and timeline only: Relia's prose did not pass its own evidence check." You can still edit every section yourself.

If something's wrong

  • "This month's postmortems on your plan are used up.": the monthly allowance is spent. It renews on the 1st, or upgrade in Team & plan.
  • No postmortem bar on the incident: the project is on Free, where the incident's explanation is locked. Upgrade to Growth.
  • Publish a link is missing: only owners and admins can publish.

Next

Last checked against the product: 1 Nov 2026