Handover Documentation: Never Lose Knowledge When Someone Leaves
Every business has roles where one person is the only one who knows how something works. While they are employed, that feels like reliability. The day they resign, it is revealed as risk. Handover documentation is how you convert personal knowledge into business property — and the trick is that it must be built before anyone resigns.
The two kinds of handover
The planned handover happens across a notice period, with the outgoing person available to explain. The sudden handover happens with no notice at all — illness, emergency, or a resignation that goes badly. A business that only prepares for the first kind is unprepared. The standing handover document is your insurance for the second.
What a standing handover document captures
| Section | Contents |
|---|---|
| Role snapshot | Purpose, outcomes, current priorities |
| Recurring tasks | Daily, weekly, monthly — each linked to its procedure |
| Systems and access | Every account the role uses, and who administers it |
| Key contacts | Suppliers, clients, internal — with context on each relationship |
| In-flight work | What is currently mid-stream and its next step |
| Where things live | Files, folders, records — locations, not descriptions |
Running the planned handover
- Freeze and list. On resignation, update the standing document immediately and list every in-flight item.
- Prioritise transfer time. Notice periods evaporate. Spend the outgoing person's remaining time on the things only they know, not on finishing routine work someone else can pick up.
- Shadow forward, not backward. Where possible, the incoming person does the tasks while the outgoing person watches — not the reverse. Watching teaches little; doing reveals every gap.
- Close access on the last day. Every account in the systems list gets disabled or transferred, same day, from the list — not from memory. Employers also have obligations around final pay and entitlements; the Fair Work Ombudsman sets out current requirements.
Run a sudden-absence drill
Once a year, pick a role and pretend its holder is unreachable for a fortnight, starting tomorrow. Sit someone else down with only the standing handover document and have them walk through: what runs this week, what would they do first, which accounts can they actually get into, who would they call. Every stumble is a gap in the document, found for the price of an hour instead of a crisis. It is also the fastest way to convince a sceptical team that the quarterly updates are not busywork — nothing sells the standing handover like watching someone try to use a stale one.
What not to include
The handover document indexes knowledge; it does not duplicate it. Procedures live in the operations manual and get linked, not pasted — a pasted copy is stale the first time the original changes. Credentials live in the password manager, never here. And opinions about people do not belong in it at all: relationship context is useful, personal commentary is a liability. If a section starts growing beyond a page, it is probably absorbing content that belongs in another document — link to it instead and keep this one lean enough that someone in a crisis can read it end to end in twenty minutes.
Where the handover lives
Keep every role's handover document in one predictable place — the same folder structure for every role, named the same way, findable by someone who has never looked for it before. A perfect document nobody can locate during an emergency is worth exactly nothing. Access to the folder should sit one level above the roles it describes: the owner and one other trusted person at minimum, so the document survives the exact absence it exists to cover.
If you have nothing today, start with your most irreplaceable person and the systems-and-access table — it is the section whose absence hurts fastest, and it takes an hour.