The Handover Document Is Usually Too Late
Most handovers start when somebody is already leaving. Suddenly there’s a document to write, meetings to schedule and a desperate attempt to remember everything the next person might need to know. The problem is obvious: by then, you’re asking someone to reconstruct months or years of decisions from memory, usually while they’re finishing projects, clearing an inbox and mentally moving on. The handover document becomes a compressed version of what they can still remember, not a reliable record of what actually happened.
This matters because useful organisational knowledge is rarely sitting neatly in somebody’s head waiting to be exported. It’s scattered across email threads, reports, spreadsheets, meeting notes, dashboards and conversations. The National Archives explicitly treats organisational change as more than a records-transfer problem: its guidance says organisations need to transfer informal knowledge as well as files, and preserve enough context for the receiving organisation to understand the information. The Health and Safety Executive makes a similar point in a very different setting: effective handover needs preparation, communication and cross-checking, not simply passing over a document.
If you wait until the handover to capture the context, you’re asking memory to do the job the record should have been doing all along.
A better handover starts long before anybody decides to leave. Decisions are kept with their rationale. Reports remain connected to what changed afterwards. Tests keep their setup and outcome. People can correct the record while the work is still fresh. Then, when the team changes, the handover isn’t an archaeological dig. The incoming person can see not just what exists, but why it exists, what was tried, what was learned and where the evidence came from.
The handover document can still be useful. It just shouldn’t be the first time the organisation tries to remember itself.