The Handover Document That Survives a Departure
Someone hands in their notice, and the business discovers what they actually did. Not the job description version, the real one, which includes three things nobody else knows how to do and a relationship with a supplier that has never been written down.
Four weeks of notice then turns into a rushed download, most of which is forgotten within a month.
The handover document is the fix, and it works much better when it is not written during the notice period.
Write it before anyone is leaving
A handover written under notice is a summary from memory, produced by somebody whose attention has already moved on. A handover written during normal work is a description of what actually happens.
The practical version is to treat it as part of every role rather than an exit task. Each person maintains a short document covering what they own, updated when something changes. Reviewed once a year, usually alongside whatever performance conversation already happens.
That way a departure is a check and a conversation rather than an archaeology project.
What actually needs to be in it
Job descriptions are not handover documents. The useful version covers six things.
- What I own. The processes, systems, customers and relationships that are mine, plainly listed.
- The recurring rhythm. What happens daily, weekly, monthly, quarterly and annually. The annual ones are the most commonly missed, because they may not come round during the notice period.
- Where the documents are. Links, folder locations, which system holds what.
- The exceptions. The customers handled differently, the supplier who needs a phone call rather than an email, the step that fails if you do it before Tuesday.
- Who to ask. Names and contacts for the things that cannot be documented, inside and outside the business.
- What is in flight. Current work with status, and anything promised to somebody.
The job description says what the role is for. The handover says what actually happens on the days nothing goes to plan.
The exceptions are the whole value
Anyone can write down the standard process. The reason handovers fail is that the standard process is not what the person spends their time on.
The value is in the edge cases. Which two clients get a call before the invoice goes out. The thing you check before approving a payment because of what happened in 2023. The report that has to be run in a particular order. The colleague who needs to hear about a change before it happens.
Prompting for those specifically is what turns a thin document into a useful one, because people do not volunteer them. To them it is not an exception, it is just the job.
Cover the access, not just the knowledge
Handover and offboarding overlap here, and the overlap is where things get missed.
The document should list every system the person uses, including the ones nobody else knows about, any shared credential they know, any account where they are the sole administrator, and any personal device holding company information.
That list feeds straight into the leaver checklist, which is the other reason to keep it current.
Test it while they are still there
A handover document that has never been used is a hypothesis. The test is cheap and it is the only thing that tells you whether it works.
Have the person taking over run a real task from the document alone, with the outgoing person available but silent. Everywhere they stop is a gap, and it gets fixed that day.
Doing this once, for the most important recurring task, catches most of what matters.
Give the incoming person a way in
Handover is not a document transfer. Where the timing allows, a short overlap where the new person does the work and the leaving person watches is worth more than a week of meetings.
Where there is no overlap, name somebody who was adjacent to the work as the person to ask for the first month. Being told to work it out from a document is how good documents still fail.
Use it as a risk check
Reading handover documents across a team tells you something the organisation chart does not. Which tasks sit with exactly one person. Which relationships have no second contact. Which systems have a single administrator.
Those are your key person dependencies, and they are much easier to fix while everyone is still there.
Setting this up, writing the prompts that pull out the exceptions, and getting the documents to a state where they stay current is exactly the kind of process work we do with clients. It costs a few hours a year per person. The alternative cost arrives all at once, on a day you did not choose.
Want handover documents that are written before anyone gives notice? Book a consultation, or visit www.expertechsolution.com.
