DEV Community

Hive80-lab
Hive80-lab

Posted on Originally published at hive80-lab.github.io

The On-Call Handoff: The Checklist That Stops Monday Surprises

#devops #sre #oncall #incidentresponse

Most on-call disasters don't start during the on-call shift — they start at the handoff.

Engineer A closed the ticket in their head, muttered something in a hallway, and went on leave. Engineer B inherited a sleeping pager with three landmines inside it. Monday morning an alert fires, and B discovers the failing replication job that A has been babysitting all week — from scratch, at 8:47am, while the pager is still screaming.

The fix costs nothing: a five-minute written handoff with five things in it. Here's the checklist we run, and the note template you can paste tonight.

The handoff note — five things, always

  1. Written, not verbal. Ever. "I told Dave about the cron job" is not a handoff — it's a rumor. If it isn't in the handoff note, the next engineer doesn't know it, and in three weeks nobody will.
  2. State of the world, in one paragraph. What's degraded, what's flapping, what was fixed this week and how. Under five lines.
  3. Open items with owners and deadlines. The paused migration, the cert expiring Thursday, the vendor ticket nobody answered since Tuesday. Name, date, next action.
  4. Known flaky alerts, with the tell. "pvc-alert flaps at 3am — it's the NFS mount, ignore unless it persists 15+ min." This single line converts 80% of night pages back into sleep.
  5. In-flight changes and their landmines. Anything deployed, flagged, or disabled this week — plus what to do if it misbehaves. Nobody should discover a feature flag during an incident.

The seven lines you can paste tonight 

ON-CALL HANDOFF — <date> — from <name> to <name>

STATE: everything up. Dashboard link. One degraded thing: <what>.
FLAKY: <alert> flaps <when> — <why> — ignore unless <condition>.
OPEN: 1) <item> — owner <who> — due <when> — next step <what>.
CHANGES: <what shipped / got disabled> — if it misbehaves: <action>.
WAITING: <vendor/team> owes us <answer> since <date>.
ESCALATE TO: <name> for <area>, <name> for <area>. If unsure: <name>.
Enter fullscreen mode Exit fullscreen mode

Two minutes to write, ten seconds to read — and it survives holidays, sick days, and people quitting. A hallway conversation survives none of those.

The rules that make it stick

  • Same time, every time. A fixed handoff slot means the note is expected, not discovered.
  • Fifteen minutes synchronous, then written. Talk is fine for tone; the note is the artifact. If only the talk happened, the handoff didn't happen.
  • The receiver asks one question: "what would you warn me about?" Whatever comes out goes in the note verbatim. Gut feelings capture what tickets don't.
  • No new on-call starts blind. First day on-call? The outgoing engineer shadows the first alert hour.
  • Review the note in the postmortem. When an incident traces back to a missed handoff item, add it to the template. The note is a living control, not a ritual.

If your rotation is held together by hallway conversations, the free On-Call Handoff Checklist (part of 40+ free ops templates at HIVE80lab ops notes) takes two minutes to adopt.

And when you're ready for the full pack — rotation schedule, escalation matrix, and the on-call runbook — the Ops Starter Kit Vol. 2 ($27) has it. Launch week: 30% off any paid kit with code HIVE-LAUNCH30.

Top comments (0)