A Notion template for managing on-call rotations, logging incidents in real time, running structured postmortems, and tracking SLA compliance. Built by engineers who've been paged at 3 AM and wished they had a better system.
Key Features
On-call rotation schedule with weekly assignments and swap tracking
Incident log with severity classification and real-time timeline
Postmortem templates with blameless 5-Whys root cause analysis
SLA tracking with uptime calculations and breach alerts
Escalation workflow — clear paths from L1 to L2 to management
Runbook library linked to specific incident types
On-call handoff notes for smooth rotation transitions
Database Schema
Incidents (Primary Database)
Property
Type
Description
Incident Title
Title
Brief description of what happened
Incident ID
Unique ID
Auto-generated (INC-0001)
Severity
Select
SEV1 - Critical · SEV2 - Major · SEV3 - Minor · SEV4 - Informational
P0 - Immediate · P1 - This Sprint · P2 - Next Sprint · P3 - Backlog
Status
Select
Open · In Progress · Done · Won't Do
Due Date
Date
Target completion
Source Incident
Relation → Incidents
Which incident generated this
Type
Select
Prevention · Detection · Response · Process
Quick Start
Duplicate the template into your Notion workspace
Set up your on-call rotation — add team members and assign weekly slots
Review the incident template — familiarize yourself with the fields before an incident hits
Customize severity definitions — adjust SEV levels to match your organization's SLAs
Run a practice postmortem — use a past incident to test the workflow
Usage Guide
Incident Response Workflow
1. Alert fires → Create incident (Status: Detected, log Detected At)
2. Assign commander → Start timeline logging
3. Investigate → Update Status to "Investigating", add timeline entries
4. Mitigate → Apply fix, Status to "Mitigating"
5. Resolve → Confirm recovery, log Resolved At, Status to "Resolved"
6. Postmortem → Schedule within 48h for SEV1/SEV2, create postmortem record
SLA Reference
Severity
Response Time
Resolution Target
Postmortem Required
SEV1
5 minutes
1 hour
Yes (within 48h)
SEV2
15 minutes
4 hours
Yes (within 1 week)
SEV3
1 hour
24 hours
Optional
SEV4
Next business day
1 week
No
Recommended Views
View
Type
Filter / Group
Use Case
Active Incidents
Board
Status ≠ Postmortem Complete
Real-time incident tracking
This Week's On-Call
Table
Current week
Who to page
Open Action Items
Table
Status = Open, sorted by Priority
Sprint planning
Incident History
Timeline
By Detected At
Trend analysis
Needs Postmortem
Table
Status = Resolved, no linked postmortem
Accountability
Template Examples
Example: SEV1 Incident
Field
Value
Incident Title
Database primary unreachable — full API outage
Severity
SEV1 - Critical
Status
Resolved
Detected At
2025-11-20 02:34
Resolved At
2025-11-20 03:12
Duration
38 minutes
Affected Service
Database, API, Web App
Customer Impact
Full Outage
Root Cause
Infrastructure (disk full on primary)
Example: On-Call Handoff
Field
Value
Week
2025-W48
Incident Count
3
Handoff Notes
Flaky alerts on search-service — known issue, ignore unless sustained >5min. Deployment freeze Thursday for maintenance window.
Customization Tips
Add a "Cost" number property to incidents to track business impact in dollars
Create a "MTTR Trend" dashboard using rollup formulas across monthly incident counts
Add a "Communication Log" text field for tracking status page updates sent during incidents
Build a "Repeat Offenders" view grouping incidents by Affected Service to find reliability gaps
Add PagerDuty/Opsgenie incident IDs as a text property for cross-referencing
This is 1 of 11 resources in the Notion Developer Pro toolkit. Get the complete [On-Call & Incident Tracker] with all files, templates, and documentation for $19.
Top comments (0)