Annual Leave Coverage Checklist: The Thirty-Minute Ritual That Stops One Holiday Breaking the Whole Rota

The quick version: in a small team, every holiday is a reorganisation pretending to be a calendar entry. One person away means their decisions, their inbox, their clients, and their half-finished work all need somewhere to live — and when that placement is improvised the week before the flight, it lives in whoever answered the phone that day. This page gives the thirty-minute coverage ritual that runs a fortnight before every leave: five decisions, one handover sheet, the client-facing message, and the boundary rules that keep the holiday a holiday instead of remote work with worse internet.

Why one holiday breaks the rota

Small teams run on informal memory. The person going away holds a map nobody wrote down: which client needs prodding, which invoice is disputed, which supplier goes quiet in month-end. The leave request is approved in five seconds; the coverage — the actual transfer of that map — is scheduled never. Then the absence starts and the team discovers it in real time: a client emails the person on a beach, a deadline quietly passes, a decision waits because "only she knows."

The failure isn't the holiday. It's that coverage was treated as a name on a rota instead of a set of transfers. A rota says Tom covers. A transfer says Tom owns these four decisions, has this sheet, can reach this person, and knows what may wait. The first fails in a week; the second survives a fortnight.

The five decisions (thirty minutes, fortnight before)

1. Decision 1 — what they own. List everything the leaver holds: named clients, recurring tasks, approvals, logins, in-flight projects. Fifteen minutes with their calendar and task list is enough. Anything unlisted now is a fire later.
2. Decision 2 — who covers what. Assign an owner per item, not "Tom covers." One person covering eight things covers none. If a task genuinely has no sensible owner, that is not a coverage problem — it is a signal the task should be paused or killed. Say so out loud.
3. Decision 3 — what the clients see. Send the short note: who to contact, that nothing changes, and the date normal service resumes. One email beats ten apologies. (Template: see the related pages below.)
4. Decision 4 — what can wait. Mark the work that is allowed to sit for a fortnight. Everything else gets a due date inside the absence window or a pause. A leave that has no "allowed to wait" list becomes a leave that nothing survives.
5. Decision 5 — the one emergency line. One named person, one channel, for genuine fires only. Not "call anyone, we'll figure it out" — that line is how a holiday becomes a shift.

The handover sheet (one page, five columns)

A handover that lives in conversation dies the day the person flies. Write one page with five columns:

• Item — the client, task, or approval, in the owner's own words.
• Cover owner — one name. Never two.
• State — where it actually stands: "invoice sent, client disputes line 4," not "in progress."
• Next action + date — what the cover owner does and when it's due during the absence.
• Escalate to — the one person for genuine surprises, plus the emergency line from Decision 5. This sheet is the fortnight-long version of the daily shift handover log — same three states, longer clock.

Fill it with the leaver, not about them — fifteen minutes side by side, reading their calendar row by row. Then test it: cover owners walk their rows and say what they'd do first. Anything that gets a shrug is a hole in the sheet, and a hole found on the Tuesday before leave costs five minutes; the same hole found on the Friday after costs a client.

The boundary rules (so leave is leave)

Coverage fails in two directions: not enough, and the leaver keeps working. Both need rules, set before the out-of-office goes on:

• Channel cut-off. The leaver's inbox gets an auto-reply naming the cover owner, not a promise to "reply when I can." If it matters, it routes; if it doesn't, it waits. No "I'll just check my email" — checking is answering, and answering is working.
• The emergency line is for emergencies. Define one: money moving, a client walking, something broken that stops the business. Not questions. Not opinions. Not "quick one."
• The leaver writes, the covers decide. The handover sheet records judgement, not instructions for every case. A sheet that scripts everything is read once and abandoned; a sheet that records state and next actions is used daily.
• Re-entry buffer. First day back has no client meetings and no decisions scheduled — it's for reading the sheet's outcome column and re-owning their items. A person who lands from leave straight into a nine-o'clock pitch was never on leave.

Worked example: the bookkeeper's fortnight

A three-person accounting practice lost the same week twice. First time: the senior bookkeeper went on leave with a rota name and no sheet. Two client payrolls slid, a BAS query sat unanswered for nine days, and she answered emails from an airport on the way back — "just to clear the backlog." The holiday cost more hours than a working fortnight.

Second time, the same leave went through the ritual. Thirty minutes a fortnight out: eleven items listed, each with one cover owner. The disputed BAS invoice got a state line ("client disputes late-fee line; we have the sent-receipt") and a next action ("cover owner calls Tuesday, outcome logged in the sheet"). Clients got the standard note. The emergency line was the practice manager, and in fourteen days it rang once — a genuine payroll error, fixed in twenty minutes with the sheet in front of the cover.

The bookkeeper came back to a page of outcomes instead of an inbox of archaeology. Total cost of the ritual: thirty minutes plus one page. Total cost of the improvisation: the whole week, twice.

The four traps

• The name-on-a-rota. "Tom covers" without items, states, or next actions. It fails exactly one day after the plane leaves.
• The absentee stand-in. The leaver keeps answering "just this once." Once is daily. The out-of-office that names a cover owner is the boundary's first line — set it before the taxi arrives.
• The everything-pause. Pausing all their work "while they're away" trades a fortnight of coverage for a fortnight of backlog on return. Decide what waits; don't let the default decide.
• The return-day ambush. Scheduling the quarter's biggest pitch for day one back. Re-entry buffer, every time.

From the HIVE80lab kit

Every page ships with a kit block — the paid tools behind the free advice:

• The First 30 Minutes — free incident quick-start checklist
• Ops Starter Kit — incident response for small teams — $14
• Ops Starter Kit Vol. 2 — advanced incident response & communications — $27
• Ops Mega Bundle — all 5 kits in one download — $49

Related: the delegation of authority template sets what the cover owner may decide without asking — the coverage sheet tells them the state, the DoA tells them the limits; the on-call handover template is the same ritual for the technical rota, where the handover is between shifts instead of holidays; the employee offboarding checklist covers the leave that never ends — the same five decisions, run once, permanently; and the outage email templates are the customer-facing message if what breaks during the absence is bigger than a rota.