Covering a branch manager's absence without things quietly slipping

A branch running well under its usual manager can look noticeably different within a week or two of that manager being away, and it's rarely one dramatic failure — it's several small things nobody else knew were that manager's to watch, quietly not getting done because nobody else was explicitly covering them.

What actually tends to slip

The things that go quiet during an unplanned absence are usually the ones that don't have an obvious daily trigger — reviewing which workers are approaching the AWR 12-week threshold, following up an overdue right to work renewal, or checking that onboarding for a worker starting next week is actually complete. None of these are urgent on any single day, which is exactly why they're the first things to be missed when the person who usually owns them isn't there.

Why a job title isn't a handover plan

Most branches have some informal sense of who'd step in if a manager were away, but informal isn't the same as documented — and the gap between the two only becomes visible during the absence itself, at exactly the point it's hardest to fix. A genuine handover plan names, specifically, who covers which recurring responsibility, not just who's "in charge" in a general sense while the manager is out.

What a useful handover checklist actually contains

• –A short list of the recurring checks the manager normally runs — AWR thresholds, overdue timesheets, upcoming right to work or DBS renewals — and who covers each one specifically during an absence.
• –Where to find the relevant records, since "the manager knows where everything is" stops being useful the moment the manager isn't there to ask.
• –Any placements or hirer relationships currently mid-negotiation or otherwise not yet in a settled, routine state, so cover isn't starting from zero context.
• –A clear escalation contact for anything genuinely urgent that the covering person isn't confident handling alone.

Building this before it's needed, not during

The value of a handover checklist is almost entirely in having it ready before an absence happens — a plan drafted during the first week someone's unexpectedly off is reactive by definition and misses exactly the kind of detail a calm, planned exercise would catch. This is worth treating as a standing document reviewed periodically, not a one-off task completed once and left to go stale as the branch's client mix and processes change.

What good cover actually requires beyond a document

A checklist alone doesn't run itself — someone needs explicit authority and confidence to act on it, not just a piece of paper handed over on the manager's last day before leave. This is where being genuinely clear in advance about what a covering colleague is expected to decide independently versus escalate matters: ambiguity here is what causes things to sit untouched, because nobody wants to overstep, not because nobody noticed something needed doing.

Reviewing how cover actually went

After any period of cover, a short, honest review — what worked, what got missed, what the covering person wished they'd known in advance — turns each absence into an improvement to the handover plan rather than a one-off scramble repeated identically the next time. Branches that do this consistently tend to find cover gets noticeably smoother each time, simply because the plan keeps catching up to how the branch actually runs, in much the same way good operational KPIs only stay useful if they're revisited rather than set once and forgotten.

Absence exposes what was never written down

A branch runs on a manager's accumulated knowledge — which clients tolerate what, which candidates are reliable, which arrangements were agreed verbally, which invoices are disputed and why. None of it is documented because none of it needed to be, and it all becomes urgent the week they are unexpectedly away.

A handover checklist written during a notice period captures the formal half. The more durable protection is a branch where the informal knowledge is routinely externalised — client preferences recorded, verbal agreements confirmed in writing, decisions captured with their rationale.

Common mistakes

• –Planning for planned absence but not for sudden absence
• –Client-specific arrangements held only in a manager's memory
• –Verbal agreements with clients never confirmed in writing
• –No documented authorisation limits for whoever is covering
• –System access tied to one person's login
• –Treating handover as a document rather than as continuous documentation