On this page2 sections
Preview or copy each section below. Paste into Notion, Confluence, or your wiki.
Schedule spec
On-call: [Team name]
Overview
| Field | Value |
|---|---|
| Schedule | [Name in Incido] |
| Timezone | [Europe/Zurich] |
| Escalation policy | [Policy name] |
| Shift verification | On / Off |
| Last reviewed | YYYY-MM-DD |
Rotation layers
| Layer | Length | Handoff | Rotation order |
|---|---|---|---|
| Primary | 1 week | Mon 09:00 | A → B → C → D |
| Secondary | 1 week | Mon 09:00 | E → F → G |
Coverage snapshot
| Week of | Primary | Secondary |
|---|---|---|
| YYYY-MM-DD | [Name] | [Name] |
Handoff (5 min)
Outgoing: Open incidents · Upcoming maintenance · Contact methods verified
Incoming: Acknowledge shift · Test push/SMS/email · Know escalation policy name
Overrides
| Dates | Covering | Reason |
|---|---|---|
| YYYY-MM-DD – YYYY-MM-DD | [Name] | Vacation |
Scope
Covers: [Services / components]
Does not cover: [Other teams’ components: link their schedule]
Incident sources
| Source | How it reaches Incido |
|---|---|
| Monitors | API / webhook |
| Manual | Dashboard |
| Support | [Triage process] |
# On-call: [Team name]
## Overview
| Field | Value |
|-------|-------|
| Schedule | [Name in Incido] |
| Timezone | [Europe/Zurich] |
| Escalation policy | [Policy name] |
| Shift verification | On / Off |
| Last reviewed | YYYY-MM-DD |
## Rotation layers
| Layer | Length | Handoff | Rotation order |
|-------|--------|---------|----------------|
| Primary | 1 week | Mon 09:00 | A → B → C → D |
| Secondary | 1 week | Mon 09:00 | E → F → G |
## Coverage snapshot
| Week of | Primary | Secondary |
|---------|---------|-----------|
| YYYY-MM-DD | [Name] | [Name] |
## Handoff (5 min)
**Outgoing:** Open incidents · Upcoming maintenance · Contact methods verified
**Incoming:** Acknowledge shift · Test push/SMS/email · Know escalation policy name
## Overrides
| Dates | Covering | Reason |
|-------|----------|--------|
| YYYY-MM-DD – YYYY-MM-DD | [Name] | Vacation |
## Scope
**Covers:** [Services / components]
**Does not cover:** [Other teams’ components: link their schedule]
## Incident sources
| Source | How it reaches Incido |
|--------|----------------------|
| Monitors | API / webhook |
| Manual | Dashboard |
| Support | [Triage process] |
How to use this template
- Target ≤ 33% on-call load per engineer. Adjust rotation length to team size.
- Keep overrides visible; surprise handoffs cause missed pages.
- Enable shift verification to catch bad contact methods early.
Incido builds shifts from rotation layers, supports overrides and shift verification, and links schedules as escalation-policy targets.