A handover fails the same way every time: it's a Slack scroll. The outgoing engineer types three paragraphs at 5:58pm, the incoming engineer skims them at 6:20pm between meetings, and the one thing that matters at 2am sits in paragraph two, unbolded, unread.
I've been shipping small-team ops templates over at the HIVE80lab ops-notes site, and the handover is the one people ask for most after incident comms. So here's the version that fits on one screen and takes ten minutes to fill.
The six sections
1. Status line. One sentence, traffic-light: GREEN (nothing on fire), AMBER (watching X), RED (incident #N open, link). If the next person reads nothing else, this sentence carries the shift.
2. Alerts handled today. Bullets only: what fired, what it was, what you did. This is how the incoming engineer recognizes the same alert in ninety seconds instead of rediscovering it at 2am.
3. Alerts still open / watchlist. Anything that fired twice, anything suppressed, anything with a ticket. Ticket number and owner, or it doesn't count. "Watch it" is not an owner.
4. Deployments and freezes. What shipped today, what ships tomorrow, what's frozen and why. The 2am pager should never meet a surprise deploy.
5. Pending follow-ups. Every promise made today — the customer awaiting an update, the metric someone asked about — each with an owner and a date. Otherwise it's not a follow-up, it's a hope.
6. Escalation notes. Who's out, who covers whom, which stakeholder is upset or waiting. People context never lives in the monitoring dashboard.
The one rule
If it lives only in your head, it doesn't exist. Handovers fail on the quiet stuff: "I was watching that retry queue," "the vendor has an outage window tonight." Ten minutes of writing beats one page with zero context.
Why small teams pay for skipping it
On a team of 2–10, on-call rotates between two or three people. Every gap in the handover comes back with interest within one rotation, because the person reading your vague notes two weeks later is you — and by then the memory is gone too. The handover isn't a courtesy to the next engineer. It's a message to your future self at 2am.
Full template
The fill-in version (with the status-line shorthand and a worked example) is live on the ops-notes site: On-Call Handover Template — part of a free library of small-team incident templates (postmortems, severity matrices, comms templates).
If you want the deeper always-on version — unattended-agent monitoring, escalation ladders, and the watchdog patterns that page a human only when a human is actually needed — that's the Agent Ops 24/7 kit. Launch week takes 30% off any paid kit with code HIVE-LAUNCH30 at checkout.
And start free: The First 30 Minutes is a one-page incident quick-start checklist, no email needed.
Top comments (0)