Write a handover someone can actually use

The person receiving a handover is usually missing the context you have accumulated over weeks. A folder of files may contain all the information and still be difficult to use. Start from the next action they must take, then organise the handover around what they need to do it safely and confidently.

Describe the state of the work

Say what is finished, what is in progress and what has not started. Mark drafts and approved versions clearly. A file called ‘final’ is not a substitute for an approval record, especially when several versions share that word. Point to the version that should be used and explain whether any checks remain.

Include the immediate next step with its context. ‘Send the draft’ is incomplete if the recipient does not know which draft, to whom or for what kind of review. Give the purpose and any constraint that changes the action. Avoid assuming they know which stakeholder prefers a call or which supplier is waiting for a specific answer.

Give access a separate check

A working link for you may be inaccessible to your colleague. Confirm that the recipient can open the required documents and use the relevant shared systems through the organisation's normal access process. Do not place passwords or other secrets in a handover document as a shortcut. Refer access requests to the appropriate administrator or established credential-sharing mechanism.

For a hypothetical content handover, the useful package might include the approved brief, current draft, image folder, publication date, review status and the name of the final approver. It would not need every discarded headline unless an earlier rejection explains an important boundary. Keep decision history where it helps, not as an unfiltered archive.

Expose the awkward details

List unresolved questions and dependencies. An uncomfortable issue hidden to make the handover look complete will reappear as a surprise. Explain what you have already tried, who has been contacted and what would trigger escalation. This prevents the next person from repeating an unsuccessful approach without knowing it.

Separate essential reading from background material. Put the short orientation first and link to detail. A recipient with twenty minutes should be able to identify the next obligation; someone taking long-term ownership should also have a route into the deeper history.

If the work is complex, walk through one real next task together. Ask the recipient to explain what they would do and where they would find the information. That is a more useful test than asking whether everything makes sense. Correct gaps while both people are available, then update the written record so the explanation does not exist only in the call.

A handover is complete when ownership and access have transferred, not when the sender presses send. Agree the point at which the recipient becomes responsible and whether any limited follow-up remains. That boundary helps both people avoid duplicate work or an assumption that the other person is still handling it.

A rehearsal reveals what the folder cannot

Consider a hypothetical handover of a monthly report. The incoming colleague can open the report template and find last month's figures, but cannot identify which source contains the current month's approved totals. A file inventory would pass; the first real task would fail. Ask them to trace one number from its source into the report and explain who confirms it. This tests the connection between documents rather than merely checking that each file exists.

Next, introduce an ordinary exception: the usual reviewer is away or a source has not arrived. The recipient should know whether to pause, use a named alternative or send an update. They do not need to solve every imaginable failure. They need the boundaries that prevent a guess from becoming an unintended public commitment. Record the route for the exceptions most likely to occur.

A temporary holiday cover arrangement can be lighter than a permanent transfer. State the tasks the covering colleague should handle and those that can wait, along with the return date. For a permanent handover, include recurring obligations and longer-term maintenance. Treating both situations identically either burdens temporary cover with irrelevant history or leaves a permanent owner without the context they need.