Support & Ops

Incident Postmortem

Structured PIR template. Fill fields, preview the markdown, export or print.

SEV2INC-2026-001Blameless
Major degradation, partial outage
UsersRevenueDuration
0%
Completion
0 / 7
TTR
TL;DR · leadership summary
Template format
Pick a company's postmortem style
Strict blameless format. Heavy on timeline fidelity, action-item ownership, and 'what went well' vs 'what went wrong'.Summary (1 paragraph)Impact (users, revenue, duration, SLO burn)Root causesTriggerResolutionDetectionAction items (who, what, when, link to bug)Lessons learned — what went well / what went wrong / where we got luckyTimeline (UTC timestamps)Supporting information (graphs, chat logs)
Timeline
on-budget over 60m
DetectRespondMitigateResolve
add times to plot
1
2
3
4
Impact
Users affected
Revenue impact
Duration
Paper preview
Letter · blameless · SEV2
Postmortem / INC-2026-001

Untitled incident

2026-05-13 · SEV2 Major degradation, partial outage
Blameless · In review

1TL;DR

No summary yet.

2Impact

Users
Revenue
Duration

3Timeline

  1. --:--Alert fired
  2. --:--Engineer acknowledged
  3. --:--Mitigation deployed
  4. --:--All clear

4Root cause

5What went well · lessons

6Action items

  • (task)@ownerdue TBD
— end of postmortem · blameless by policy —
Raw markdowntoggle
# Incident Postmortem: (untitled)

**Severity:** SEV2 — Major degradation, partial outage  
**Date:** 2026-05-13

## Summary
_No summary yet._

## Timeline
- **--:--** — Alert fired
- **--:--** — Engineer acknowledged
- **--:--** — Mitigation deployed
- **--:--** — All clear

## Impact
- Users affected: —
- Revenue impact: —
- Duration: —

## Root Cause
—

## Contributing Factors
—

## Resolution
—

## Action Items
- [ ] (task) — @owner — due TBD

## Lessons Learned
—