Incident Postmortem
Post-incident reviews produce lengthy narratives that need to be distilled into structured records for tracking and learning. This template captures the incident summary, timeline, root cause, customer impact, detection method, resolution steps, and follow-up action items, creating a consistent postmortem format across your engineering organisation.
See it in action
What users type
What you get
Owen Park
Checkout Outage - Stripe Webhook Handler Crash Loop
2026-04-02
47 minutes
Unhandled Stripe webhook event type (payment_method.automatically_updated) from API 2026-03-15 caused webhook processor crash-loop, backing up queue and starving checkout flow
~340 customers experienced failed checkouts
SEV2
1. Add webhook event type validation/catch-all. 2. Set up Stripe API changelog monitor. 3. Load test webhook queue under backpressure.
Extracted fields
| Field | Type | Required |
|---|---|---|
| Author | text | Required |
| Incident Title | text | Required |
| Incident Date | date | Required |
| Duration | text | Required |
| Root Cause | text | Required |
| Customer Impact | text | Required |
| Severity | select | Required |
| Action Items | text | Required |
Use this template
Sign up and select “Incident Postmortem” from the template gallery. Customise any field before going live.
Start with this template — freeRelated
Templates
Parse bug reports from users or QA into structured tickets with reproduction steps and severity.
Change RequestStructure change requests with scope, justification, risk assessment, and rollback plan.
Deployment RequestParse deployment requests capturing version, environment, dependencies, and approval status.