On-Call & Incident Tracker
On-call rotation schedule, incident logging, postmortem templates, SLA tracking, and escalation workflow system.
Product Preview
Try the interactive reader and demo tools below, or get the full product with all content unlocked.
Interactive Reader (Free Preview) ⚙ Try Demo Tools Download Free SampleFile Structure 22 files
Documentation Preview README excerpt
On-Call & Incident Tracker — Notion Template System
By Notion Developer Pro | $19
A complete incident management system for engineering teams, built entirely in Notion. Track on-call rotations, log incidents with full timelines, write structured postmortems, monitor SLA compliance, and define escalation workflows — all without leaving your workspace.
What's Inside
This template system includes 5 linked databases, 3 reference pages, and 3 reusable templates that form a complete incident management lifecycle:
Databases (CSV → Notion Import)
| Database | Purpose |
|---|---|
| On-Call Schedule | Rotation schedule with primary/secondary on-call, shift types, and handoff notes |
| Incidents | Incident log with severity, timeline, affected services, and resolution status |
| Postmortems | Structured postmortem records linked to incidents with action items |
| SLA Targets | Service-level objectives per service with compliance tracking |
| Escalation Contacts | Team contact directory with escalation tiers and notification preferences |
Pages & Dashboards
| Page | Purpose |
|---|---|
| Incident Dashboard | Current on-call, open incidents, recent postmortems, and SLA health at a glance |
| Incident Response Runbook | Step-by-step guide for responding to incidents by severity level |
| Escalation Policy | When and how to escalate, notification channels, and management contacts |
Reusable Templates
| Template | Purpose |
|---|---|
| Postmortem Template | Blameless postmortem structure with timeline, root cause, and action items |
| Incident Report Template | Quick-fill incident report for stakeholder communication |
| Handoff Note Template | End-of-rotation handoff document for the next on-call engineer |
Formulas Reference
All Notion formulas are documented in formulas/FORMULAS.md with exact text and explanations.
Features
- On-Call Rotation Management — Weekly/biweekly rotation schedule with primary and secondary on-call. Includes swap tracking and coverage gaps detection
- Severity-Based Incident Logging — SEV1 (critical) through SEV4 (low) with appropriate response times and escalation rules
- Blameless Postmortem System — Structured template covering timeline, root cause analysis, contributing factors, action items, and follow-up tracking
- SLA Compliance Dashboard — Define SLA targets per service and track monthly uptime, MTTR, and incident counts against goals
- Escalation Workflow — Three-tier escalation matrix with automatic escalation timing suggestions
- Timeline Tracking — Log detection time, acknowledgment time, mitigation time, and resolution time for MTTR calculations
- Affected Service Tagging — Multi-select service tags for tracking incident patterns across your infrastructure
- Action Item Follow-Through — Postmortem action items with owners, due dates, and completion tracking
Quick Start
Step 1: Import the Databases
Import each CSV from databases/ into Notion. See docs/IMPORT-GUIDE.md for detailed steps.
Import order:
1. escalation_contacts.csv — Import first (referenced by incidents)
... continues with setup instructions, usage examples, and more.
Content Sample templates/handoff-note-template.md
On-Call Handoff Note Template
Complete this at the end of your on-call rotation and share it with the incoming on-call engineer. Good handoffs prevent repeat incidents and reduce cognitive load for the next person.
Rotation Handoff: [Week of YYYY-MM-DD]
Outgoing Primary: [Your Name]
Outgoing Secondary: [Secondary Name]
Incoming Primary: [Next Person]
Incoming Secondary: [Next Secondary]
Rotation Summary
Total alerts received: [Number]
Incidents declared: [Number]
False positives: [Number]
Overall Assessment
[One paragraph summarizing how the rotation went. Was it quiet? Busy? Any patterns?]
Active Issues Carrying Over
[List any ongoing issues the next on-call needs to be aware of]
Issue 1: [Brief title]
- Status: [Investigating / Mitigated / Monitoring]
- Context: [What's happening and what's been done so far]
- What to watch: [Specific metrics, logs, or dashboards to monitor]
- Escalation contact: [Who to reach out to if this gets worse]
Issue 2: [Brief title]
- Status: [Investigating / Mitigated / Monitoring]
- Context: [What's happening]
- What to watch: [What to monitor]
- Escalation contact: [Who to call]
Upcoming Risks
[Anything scheduled or known that might cause issues during the next rotation]
... and much more in the full download.