The Handover Document That Explains Nothing

The departing colleague left twelve pages. The pages are accurate, complete and of no help whatsoever with any question that has actually come up since.

Most of the job was never in words

A great deal of working knowledge is procedural rather than factual. Knowing which supplier answers the phone, which report is quietly wrong, and when to push a request.

That knowledge is built from hundreds of small experiences and is not stored in a form that can be transcribed on request.

Asked to document their role, people produce the part that is easy to write down, which is the part a newcomer could mostly have worked out anyway.

Expertise hides what is unusual

Someone who has done a job for years no longer notices its oddities. The workarounds have become the process and the exceptions have become the rules.

Documenting requires identifying what a stranger would find surprising, which is precisely the perception that expertise removes.

This is why the most useful handovers are written by someone in their first six months, when the strangeness is still visible.

It is written in the final week

Handover documents are produced at the point of departure, when the author is finishing projects, attending farewells and mentally already elsewhere.

The reward for thoroughness is zero, since the writer will never work with the consequences, and the deadline is immovable.

Organisations that get useful handovers generally start them long before anybody leaves, and treat documentation as ongoing rather than as an exit task.

What gets recorded is structure, not judgment

Lists of systems, contacts, recurring meetings and file locations are straightforward to write and genuinely necessary, so they fill the document.

What is missing is why decisions were made the way they were, which constraints are real and which are habits, and what has already been tried and failed.

Without that, a successor repeats old experiments, and the organisation pays again for lessons it has already bought once.

The knowledge lives in people who were not asked

Colleagues, counterparts in other teams and long-serving suppliers hold much of what the document omits, and generally hold it willingly.

A handover organised as introductions rather than as a file transfers considerably more, because it connects the successor to the network the role actually ran on.

Very few processes are built that way, because a document can be filed and ticked off, and a set of relationships cannot be attached to a leaver's checklist.