Incident Postmortems
Engineering and operations teams
Engineering and ops teams: log incidents, write blameless postmortems, track the fixes.
Use this templateIncident Postmortems
Reliability dashboard
Severity guide
Weekly review
On-call roster
Incidents
Open any incident to find the full postmortem outline (timeline, impact, causes, fixes) ready to fill in.
| Incident | Incident number | Severity | Status | Started | Resolved | Commander |
|---|---|---|---|---|---|---|
| Login errors after a certificate renewal | — | Mitigated | Nov 17, 2:15 PM | — | Sigrid Halvorsen | |
| Database failover did not promote a replica | — | Resolved | Nov 10, 5:10 AM | Nov 10, 6:50 AM | Keiko Tanaka-Ruiz | |
| Payout emails delayed by six hours | — | Postmortem done | Oct 22, 12:30 PM | Oct 22, 7:00 PM | Amara Nwachukwu | |
| Dashboard slow for all customers | — | Postmortem done | Oct 8, 3:40 PM | Oct 8, 5:15 PM | Amara Nwachukwu | |
| Card payments failing for one region | — | Postmortem done | Sep 17, 8:05 PM | Sep 17, 10:20 PM | Sigrid Halvorsen |
Action items
| Action | Incident | Type | Owner | Due | Completed on | Status |
|---|---|---|---|---|---|---|
| Add a regional health check to the payment router | Card payments failing for one region | Bruno Castellanos | Oct 4, 2026 | Oct 4, 2026 | Done | |
| Add an index to the transactions table | Dashboard slow for all customers | Keiko Tanaka-Ruiz | Oct 14, 2026 | Oct 14, 2026 | Done | |
| Fail over card traffic automatically when errors pass 5% | Card payments failing for one region | Amara Nwachukwu | Oct 19, 2026 | Oct 19, 2026 | Done | |
| Alert when dashboard p95 passes 3 seconds | Dashboard slow for all customers | Amara Nwachukwu | Oct 21, 2026 | Oct 21, 2026 | Done | |
| Move email sending to its own worker pool | Payout emails delayed by six hours | Bruno Castellanos | Nov 9, 2026 | — | In progress | |
| Retry queue alert when depth passes 1000 | Payout emails delayed by six hours | Patrick Osei | Nov 14, 2026 | — | In progress | |
| Run a monthly region-loss drill | Card payments failing for one region | Sigrid Halvorsen | Nov 18, 2026 | — | In progress | |
| Write the manual promotion steps into a runbook | Database failover did not promote a replica | Keiko Tanaka-Ruiz | Nov 20, 2026 | — | In progress |
| Incident | Incident number | Severity | Status | Started | Resolved | Commander |
|---|---|---|---|---|---|---|
| Login errors after a certificate renewal | — | Mitigated | Nov 17, 2:15 PM | — | Sigrid Halvorsen | |
| Database failover did not promote a replica | — | Resolved | Nov 10, 5:10 AM | Nov 10, 6:50 AM | Keiko Tanaka-Ruiz | |
| Payout emails delayed by six hours | — | Postmortem done | Oct 22, 12:30 PM | Oct 22, 7:00 PM | Amara Nwachukwu |
| Incident | Incident number | Severity | Status | Started | Resolved | Commander |
|---|---|---|---|---|---|---|
| Login errors after a certificate renewal | — | Mitigated | Nov 17, 2:15 PM | — | Sigrid Halvorsen | |
| Database failover did not promote a replica | — | Resolved | Nov 10, 5:10 AM | Nov 10, 6:50 AM | Keiko Tanaka-Ruiz | |
| Payout emails delayed by six hours | — | Postmortem done | Oct 22, 12:30 PM | Oct 22, 7:00 PM | Amara Nwachukwu |
| Action | Incident | Type | Owner | Due | Completed on | Status |
|---|---|---|---|---|---|---|
| Add a regional health check to the payment router | Card payments failing for one region | Bruno Castellanos | Oct 4, 2026 | Oct 4, 2026 | Done | |
| Add an index to the transactions table | Dashboard slow for all customers | Keiko Tanaka-Ruiz | Oct 14, 2026 | Oct 14, 2026 | Done | |
| Fail over card traffic automatically when errors pass 5% | Card payments failing for one region | Amara Nwachukwu | Oct 19, 2026 | Oct 19, 2026 | Done |
Open actions
| Action | Incident | Type | Owner | Due | Completed on | Status |
|---|---|---|---|---|---|---|
| Add a regional health check to the payment router | Card payments failing for one region | Bruno Castellanos | Oct 4, 2026 | Oct 4, 2026 | Done | |
| Add an index to the transactions table | Dashboard slow for all customers | Keiko Tanaka-Ruiz | Oct 14, 2026 | Oct 14, 2026 | Done | |
| Fail over card traffic automatically when errors pass 5% | Card payments failing for one region | Amara Nwachukwu | Oct 19, 2026 | Oct 19, 2026 | Done |
Incidents without a finished postmortem
| Incident | Incident number | Severity | Status | Started | Resolved | Commander |
|---|---|---|---|---|---|---|
| Login errors after a certificate renewal | — | Mitigated | Nov 17, 2:15 PM | — | Sigrid Halvorsen | |
| Database failover did not promote a replica | — | Resolved | Nov 10, 5:10 AM | Nov 10, 6:50 AM | Keiko Tanaka-Ruiz | |
| Payout emails delayed by six hours | — | Postmortem done | Oct 22, 12:30 PM | Oct 22, 7:00 PM | Amara Nwachukwu |
Choosing a severity
Decide on the customer impact you can see right now, not on how the fix is going. Raise or lower it as you learn more, and say so in the incident channel.
Who is the commander
The first on-call person to declare the incident, unless they ask to hand over. The commander coordinates and does not debug.
When to stop an incident
When the customer impact is gone and the cause is understood well enough to prevent a repeat tonight.
Thirty minutes every Thursday with the head of reliability and the action owners.
| Action | Incident | Type | Owner | Due | Completed on | Status |
|---|---|---|---|---|---|---|
| Add a regional health check to the payment router | Card payments failing for one region | Bruno Castellanos | Oct 4, 2026 | Oct 4, 2026 | Done | |
| Add an index to the transactions table | Dashboard slow for all customers | Keiko Tanaka-Ruiz | Oct 14, 2026 | Oct 14, 2026 | Done | |
| Fail over card traffic automatically when errors pass 5% | Card payments failing for one region | Amara Nwachukwu | Oct 19, 2026 | Oct 19, 2026 | Done |
What's inside
3 tables · 14 views · 1 form · 2 row actions · 1 agent5 pages
- Incident Postmortems
- Reliability dashboard
- Severity guide
- Weekly review
- On-call roster
2 tables
- Action items7 views · 11 sample rows
- Incidents6 views · 5 sample rows
Questions
- What is included in the Incident Postmortems template?
- 5 pages (Incident Postmortems, Reliability dashboard, Severity guide, Weekly review and On-call roster) and 2 tables (Action items and Incidents), filled with 16 sample rows so every view opens with realistic data.
- Who is the Incident Postmortems template for?
- Engineering and operations teams.
- Is the Incident Postmortems template free?
- Yes. Sign up free, press Use this template, and a full copy is added to your workspace.
- Can I change the template after I use it?
- Yes. Every page, table, column and view in your copy is yours to rename, edit or delete, and the sample rows can be cleared.
Related workspaces
Agency OSSmall agencies: clients, retainers, projects, capacity and proposals in one place.
Runbooks & On-callInfrastructure and support engineers: runbooks per service plus a weekly on-call schedule.
Small Business OSOwners of 1 to 15 person businesses: sales, projects, money, team and goals in one.
Event PlannerEvent organisers: guests and RSVPs, vendors, tasks, budget and run of show.
Inventory TrackerSmall shops and makers: track stock, suppliers and orders so you reorder in time.
Support and Feedback TrackerSmall support teams: triage tickets, track feature requests, link help articles.