Skip to content

Post-mortem

Adrià Castany 2 min

What is a post-mortem?

A post-mortem is the document written after an incident to explain what happened, why, how it was resolved and what changes so that it does not happen again. It has an internal version, with the full technical detail, and a version for the customers who were affected.

Also called

postmortem, incident report, root cause analysis, RCA, incident review

Topic
Support concepts
On this page
  1. Post-mortem and root cause analysis
  2. Why it matters
  3. What a post-mortem contains
  4. The internal and the customer version
  5. Blameless
  6. When to send it
  7. How Intake handles it
  8. Frequently asked questions

Post-mortem and root cause analysis

Root cause analysis, or RCA, is the part of the report that looks for where the failure started.

The post-mortem is broader. It adds the timeline, the impact on customers, how it was communicated and the actions with an owner and a date. Many companies use both names for the same document.

Why it matters

It is what turns an incident into an improvement.

Without a report, the cause stays in two people’s heads and the same failure returns months later. For a business customer it is also the proof that the supplier understands what happened, and many contracts require one after a serious incident.

What a post-mortem contains

A post-mortem has seven sections, and the last is the one most often forgotten.

  • Summary. What happened, in three or four sentences anyone can follow.
  • Impact. Which customers were affected, for how long and in what way.
  • Timeline. The times of detection, of each notice and of resolution.
  • Cause. What failed and why it was not caught earlier.
  • Resolution. What was done to restore service.
  • Actions. What changes, who does it and by when.
  • Follow-up. When someone checks the actions were carried out.

The internal and the customer version

Two versions of the same report are written, because customers need less technical detail and more clarity on what affects them.

Internal versionCustomer version
Who reads itEngineering, support and managementAffected customers
CauseFull technical detailPlain language, no system names
TimelineMinute by minuteStart, notices and resolution
ActionsWith owner and dateWhat changes for the customer and when

Blameless

A post-mortem looks for what allowed the failure, not who caused it.

If the report points at a person, next time nobody will say what they saw. The useful question is what made the error possible and which control was missing.

When to send it

The report goes out in the days after resolution, by the date announced when the incident was closed.

If the cause is still being investigated, a provisional report is sent with what is known and the date of the final one.

How Intake handles it

Frequently asked questions

What is a post-mortem in support?

The report that explains an incident once it is resolved. It covers what happened, who was affected, the cause, how it was fixed and what actions follow. In support, the version sent to customers matters most.

Does every incident need a post-mortem?

Serious ones, always. For minor ones a short note with the cause and the action is enough. Severity decides, along with whether any contract requires a report.

Who writes the post-mortem?

Whoever led the incident, with the cause from engineering and the impact from support. The customer version is reviewed by whoever owns the relationship with the affected accounts.

Should the report apologise?

Yes, once and at the start, directly. After that the report explains and commits to actions, which is what the customer will check.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment