DEV Community

Hive80-lab
Hive80-lab

Posted on

The on-call handover doc that gave me my weekends back (steal the template)

#devops #oncall #productivity #operations

Handovers are where small teams bleed

If you've ever come back from a weekend to find production was degraded on Saturday and nobody wrote down what happened, you already know the cost. It's not the incident — it's re-deriving it from logs at 9 a.m. Monday while the person who fixed it is unreachable.

The fix is boring and free: a handover doc with a fixed shape, filled in every Friday, read every Monday. The shape matters more than the tool.

The four sections (nothing else)

  1. What's on fire right now — one line per open incident, with the ticket/runbook link. If a line has no link, it's not a real incident, it's a rumor.
  2. What changed this week — deploys, config changes, DNS/cert renewals. This is the section that saves you: 80% of "mysterious" Monday failures trace to an unremarked Friday change.
  3. What will break soon — expiring certs, disk trending toward full, licenses renewing, that cron job nobody has tested since the migration. Dates, owners.
  4. Who owes whom what — cross-team promises with due dates. On-call people get blamed for other teams' debts; write them down and the blame evaporates.

Keep it in one file, newest on top. Fifteen minutes on Friday afternoon, thirty seconds on Monday morning. That's the whole system.

Why it compounds

After a quarter of these you have an incident history that no dashboard gives you: patterns repeat, and patterns are preventable. It's also the single most useful artifact in a team health review — "what changed" lists expose the noisy service nobody wants to admit is fragile.

Steal it, or take it pre-built

I've run this format across a handful of small IT teams and packaged the working version — templates plus the checks that populate sections 2 and 3 automatically:

Even if you never buy anything, run the four sections for one month. The Monday-morning silence is the review.

I write about the boring automations that keep small IT teams out of trouble. More at https://hive80lab.gumroad.com

Top comments (0)