Your Admin Lead Is Going on Leave: How to Keep the Work Moving
In short
Losing your admin lead to leave? Capture processes from live work, not a rushed handover document, and keep a lean team running.
The leave date has been in the calendar for months. Everyone agrees there'll be a handover. Then, in the final week, a long document appears, written late in the afternoon between everything else.
On the first Monday without them, the questions start. Is that report monthly or quarterly? Which client was waiting on a reply? Where does the current version of the template live? Who signs off before it goes out? The document has a section on most of these. It just doesn't answer them.
If you run a lean professional services business, this is one of the most common ways work quietly stalls. Nothing breaks on day one. Things simply take longer, deadlines get closer than anyone likes, and the person on leave starts getting "quick questions".
What it usually looks like
- The handover document gets written in the last few days, from memory
- Recurring reports are listed, but not where the source information comes from
- Nobody is sure which tasks belong to the new person and which stay with the team
- Templates exist in three versions, and only one is current
- Finished work sits waiting because nobody knows who approves it
None of this means the outgoing person did a bad job. It means the knowledge was never captured while the work was happening.
Why handover documents don't work
A handover document is written from memory, and memory edits out the parts people do on autopilot. The login that only works from one browser. The client who needs a phone call, not an email. The report that needs a nil return when there's nothing to declare. Those are exactly the details the next person needs.
It's also written at the worst possible time: when the person leaving is busiest, finishing their own work and thinking about what comes next. And it describes what the process is meant to be, not what actually happens.
The fix isn't a better template. It's changing when and how the knowledge gets captured.
What to do instead
This sits in the Capability Building phase of our Operational Excellence Framework: making sure knowledge lives in the system, not in one person's head. Here's the cut-down version you can start on your own.
- 1
Learn through live work, not a briefing. Start the incoming person on real tasks as early as you can, with the outgoing person available for questions. A two-hour walkthrough feels productive, but doing the work once teaches more.
- 2
Write the SOP the first time the task is done. Every time a recurring task is done for the first time, write it up straight away: the steps, the tools, the templates, who approves it and when it's due. Keep it short and update it as questions come up.
- 3
Confirm the source before you submit. Inherited work is full of assumptions. Before anything goes to a funder, regulator or client, check the original email, contract or portal for the period, deadline and format.
- 4
Build data sources you can reuse. If the same details go into many documents, put them in one checked list and let the documents pull from it. Retyping is where errors creep in.
- 5
Keep the action and the sensitive detail apart. Task tools are built to be shared. Use the task for what needs doing, by when, and a link. Keep health, performance and other confidential detail in the restricted file.
- 6
Make sign-off a visible step. Most work isn't slowed by preparation. It's slowed waiting for a yes. Give approvals their own status, so everyone can see what's ready and who it's waiting on.
What this looks like in practice
In October, BVIRTUAL stepped into an Australian HR consultancy as their long-standing administrator prepared for leave. The team was lean, workload came in peaks, and a lot of the program administration relied on experience rather than written steps.
We didn't wait for a handover document. Each recurring task was written up as an SOP the first time we did it for real, then updated as handover notes came in. Within three weeks the team had seven working SOPs, covering weekly program administration, shared inbox triage, monthly government reporting, recruitment campaigns, job and time recording, social content scheduling and a weekly regional update.
The other steps showed up in the live work too. One reporting obligation was confirmed as quarterly rather than monthly by going back to the source email, and the check was written into the process so nobody sends a duplicate return. When a time-critical set of nine personalised letters was needed by the next morning, one checked source spreadsheet and a mail merge did the heavy lifting, and the list is ready for the next stage. Sensitive employee matters stayed in the secure client file, with the tasks tracking only the actions.
The result: the work kept moving, and the knowledge now sits in the system rather than with one person.
The handover self-check
Run this before anyone in a key admin role takes leave, and get your readiness score in a minute:
Checklist
- Could someone else find every recurring task, with its due date, without asking?
- Is each recurring process written down from a time it was actually done?
- Are reporting periods and deadlines confirmed against the source, not memory?
- Do repeated documents pull from one checked data source?
- Is sensitive information kept out of shared task records?
- Can you see at a glance which items are waiting on approval, and from whom?
If you answer "no" to more than one question, the handover risk is already there, whether or not a leave date is booked.
Your task for this week
Pick the next recurring task on the calendar and write it up as it's being done. One task a week adds up faster than you'd expect, and it's the first piece of the handover you won't have to write in a rush.
If a leave date or resignation is coming up and the process still lives in someone's head, book a Capability Call. We'll help you map what needs capturing first.
Book a Capability Call