A rota is more than a list of names against dates. This template covers the parts that cause real pages to go unanswered: who the secondary is, what happens when nobody acknowledges, and what the outgoing engineer must hand over.
Set the rotation length first. Weekly is the common default. Shorter rotations reduce fatigue but multiply handovers; longer ones do the reverse. Pick one and keep it stable. Predictability matters more to on-call engineers than the exact length.
Name a secondary for every shift. A rota with only a primary fails the first time someone is on a train. The secondary is not decorative; they need the same access and the same runbooks.
Define acknowledgement timeouts as well as escalation order. State how long a page waits before it escalates. An escalation ladder without timeouts is a list of names, and pages will sit unacknowledged.
Run the coverage audit each quarter. Check public holidays, planned leave, and time-zone coverage. Most gaps appear at handover boundaries and in the week between Christmas and New Year.
Here's a preview. Unlock the free download to get all 5 sections (4 more below).
One row per shift. Keep at least one full rotation cycle scheduled ahead at all times.
| Shift start | Shift end | Primary | Secondary | Escalation manager | Notes |
|---|---|---|---|---|---|
| 2026-11-03 | 2026-11-10 | R. Okafor | S. Lindqvist | H. Patel | Handover call Mon 09:30; no open incidents carried over |
| 2026-11-10 | 2026-11-17 | S. Lindqvist | A. Mehta | H. Patel | R. Okafor unavailable Thu-Fri; A. Mehta covering as primary |
More free templates IT teams use alongside this one.
Most postmortems produce a document nobody reads and actions nobody owns. This one forces the three things that actually reduce repeat incidents: a timeline built from timestamps rather than memory, contributing factors stated without naming a person, and action items with an owner and a date.
The question a skills matrix should answer is not who is good at what. It is which skills exist in exactly one person's head. That number is a continuity risk you can act on cheaply before anyone resigns.
Most severity matrices fail in the one moment they matter: at 02:00, when a tired engineer has to decide whether to wake anyone. This one is written so the level is readable off customer impact alone: no judgement call about root cause, no guessing how bad it might get.
Weekly is the most common. Shorter rotations reduce fatigue but multiply handovers, where context is most often lost; longer ones do the reverse. Consistency matters more than the exact length: on-call engineers plan their lives around a predictable rota.
Yes. A single-tier rota fails the first time the primary is driving, in a tunnel, or asleep through a page. The secondary needs the same access and runbooks, otherwise the escalation only moves the problem.
Open incidents and their next step, any suppressed alerts and when the suppression expires, deploys landing during the next shift, and known-noisy alerts. Anything deliberately left undone should be stated explicitly rather than discovered.
