How to Write a Postmortem with AI (2026): The Timeline You Already Have

A postmortem written with AI is your timeline, your impact, and your action items, rewritten so a reader who was not in the incident can follow them. The model can order sentences. It cannot decide the root cause, the customer impact, or who owns the fix. Paste the ticket and the notes. Delete any cause you cannot point to.

This is not the weekly note. That workflow is how to write a status update with AI. A changelog is what shipped on purpose. That workflow is how to write a changelog with AI. The people who will reuse this doc are the audience of best AI tools for SRE teams.

Prices are US list prices excluding tax from directory pages checked October 16, 2026. Published October 24, 2026. We did not score write-ups.

What the model may touch

Section	Who owns it	The model may
Summary	You, in two or three sentences	Shorten it. It may not add drama
Impact	You, from the metric or the ticket count you checked	Format it. It may not estimate users affected
Timeline	The log, the chat, the ticket	Order the timestamps you pasted. It may not fill gaps
What worked	The people who were there	Phrase it. It may not invent a hero
What we will change	A named owner and a ticket	Make the owner visible. It may not assign a stranger
Root cause	You, if you actually know it	State it plainly. If you do not know, it must say that

flowchart TD
  src["You paste the ticket, the timeline, and the numbers you checked"] --> draft["Claude, ChatGPT, or Notion drafts the sections"]
  draft --> gap["You delete causes, times, and impacts that were not in the source"]
  gap --> owner["Every action has a name and a ticket"]
  owner --> send["You publish the write-up"]

If the notes say “database CPU was high,” the model will often upgrade that to “the outage was caused by a missing index.” That upgrade is a hallucination in a document people will trust later. Keep the observation. Put the cause in only when the evidence is in the paste.

Where the draft happens

A long incident channel plus a ticket. Claude Pro is $20 a month, or $17 billed annually. Put the last postmortem in a Project so the headings stay stable. The container is Claude Projects vs ChatGPT Projects.

The on-call engineer’s default chat. ChatGPT Plus is $20. Go at $8 is enough for a short draft. The ladder is ChatGPT Go vs Plus vs Pro.

The page the wiki already uses. Notion AI Business is $20 a seat. If the postmortem template lives in Notion, generate there or paste the approved text in. The card is Notion AI pricing explained. The seat math against a chatbot is Notion AI vs ChatGPT Plus cost.

The prose, after the facts are frozen. Grammarly Free covers grammar. Pro is $12 a member a month billed annually. It will not find a missing timestamp. The card is Grammarly pricing explained.

The bridge call, if you recorded it. Fathom Free includes unlimited recordings and summaries, if a bot was allowed. The summary is not the timeline. You still pull the lines you will stand behind. Team, when the notes must be shared, is $15 a user a month annually with a two-user minimum, from the pricing page read October 24, 2026. The card is Fathom pricing explained.

A prompt that holds the line:

“Here is our template: summary, impact, timeline, what worked, action items. Use only the notes below. If the root cause is not stated, write ‘Not established’ and list the evidence we do have. Do not name a person as at fault. Do not invent times, customer counts, or follow-up tickets.”

Blameless means the doc talks about the system and the next change. It does not mean the model should sand the impact down. A real outage stays a real outage. The fact pass is how to fact-check AI writing. The person who publishes is what human-in-the-loop AI is.

After it is published

Link the action items to tickets. A postmortem with no owners is a diary. The pipeline change those tickets imply is a different shelf: best AI tools for DevOps teams. The habit of keeping the same checks next time is what an AI eval harness is, if the failure was in a model, and a normal test suite if it was not.

Do not let an agent file the postmortem into the ticket system unattended. The ticket is the record. The distinction is what a system of record for AI is.

FAQ

Can AI write the postmortem from Slack alone?

It can misread jokes, guesses, and reverted theories as facts. Paste a timeline a human already cleaned, or be ready to delete most of the draft. The channel is evidence. The doc is a decision about which lines were true.

How long should it be?

Long enough to show impact, timeline, and owners. A one-page version for executives can be a second draft from the same notes. Do not let the short version invent a cleaner cause than the long one.

What if we do not know the root cause yet?

Say so. Ship the timeline and the next investigation step. A false cause is worse than a gap, because the next incident will quote it.

Should customers see this doc?

Only a version you wrote for them, with internal names and guesses removed. Generate that version from the approved internal doc, not from the raw channel.

Last verified

October 16, 2026 for Claude, ChatGPT, Notion, and Grammarly. October 24, 2026 for Fathom Team’s annual price. Published October 24, 2026.

Sources: Claude pricing, ChatGPT pricing, Notion pricing.

Published by Andrew for AI Tools Optimizer.

Claude is in the chatbots and assistants directory. Directory pages may use affiliate links. A purchase through them may earn us a commission at no extra cost to you.