The 2am handover that wasn't
A few years ago I was on a small team — two engineers, one shared PagerDuty rotation, zero documentation. Every Friday at 5pm one of us would mumble "you got this?" over Slack, the other would say "yeah," and by Sunday night the on-call person was usually discovering that the thing that broke at 2am Saturday was exactly the thing the other person already knew how to fix.
The fix wasn't a better tool. It was a 3-minute written handover at every shift change.
The template (copy it)
# ON-CALL HANDOVER — [date] [outgoing name] → [incoming name]
## 1. OPEN FIRES (0–3 items, else write "NONE — trust but verify")
- [what's burning, ticket link, who owns the fix, ETA]
## 2. WATCH ITEMS (things that will become fires)
- [error rate trending on X, disk at 78% and climbing, cert expires in 9 days]
## 3. RECENT CHANGES (last 72h)
- [deploys, config changes, new vendors — "if it broke, it was probably this"]
## 4. THE THING NOBODY KNOWS
- [that one cron job, that legacy auth flow, the vendor whose API breaks every Sunday]
## 5. ACCESS CHECK (one line)
- [I could reach: prod, dashboards, vendor portals. Confirm yours works NOW, not at 2am.]
Why it works when more tooling doesn't
Small teams fail at handovers for the same reason they fail at incidents: the knowledge lives in one head, and the transfer is verbal and unrecorded. A 3-minute written block forces three things:
- The outgoing person has to enumerate — which surfaces the fires they've normalized ("oh that, it's been flaky for weeks" is a fire).
- The incoming person starts with a map instead of learning by pager.
- You get a paper trail — after three months of handovers you have a free, brutally honest reliability history of your systems.
The 3-minute ritual
- Set a recurring calendar event at shift change. Non-negotiable, 3 minutes.
- The outgoing person sends the doc in chat — written, not spoken. Reading forces thinking.
- Incoming person replies with one word: "Ack." (If they can't ack in 60 seconds, the doc failed and you fix the doc, not the person.)
Steal the full kit
If this template is useful, the full Ops Starter Kit ships it as a fillable file alongside standing orders, a status-page runbook and an on-call escalation ladder — everything above, pre-formatted for a team of 1–5.
And if you want the complete set — incident checklists, after-action templates, automation packs — the Ops Mega Bundle is the whole shelf for less than the cost of one hour of downtime.
What's in your handover? Reply — I'm collecting the weird ones for a follow-up post.
Top comments (0)