Writing a Handover Someone Can Actually Use
A useful handover explains the current state, next action, key decisions, and location of the working files in plain language.
A handover is often written when time is already short: a holiday is approaching, a colleague is changing roles, or a project must move to another team. The temptation is to provide every document and hope that the recipient can reconstruct the story. A useful handover does more than transfer files. It explains where the work stands and what happens next.
Begin from the recipient's point of view. They may understand the general task but know little about the decisions, delays, or informal agreements surrounding it. Your job is to make the essential context visible without requiring them to read an entire message history first.
Explain the current state and next action
Open with a short statement of the project's purpose and present status. Say what is complete, what is in progress, and what remains unresolved. Use concrete language: a draft awaiting review is different from a document ready to send. Avoid labels such as nearly done when they hide the actual remaining work.
Identify the next action and the person responsible for it. Include the relevant deadline and explain whether it is fixed or an internal target. If progress depends on another person, state what is needed from them. This turns a general summary into something the recipient can act on.
List the locations of the authoritative files. A direct link to the current working document is more useful than several attachments with similar names. Check that the recipient has the appropriate access through the usual process, and keep sensitive material in the approved location rather than copying it into a widely shared note.
Preserve decisions without reproducing every conversation
Record the important choices already made and the reasons they matter. For example, an option may have been rejected because it exceeded the agreed scope, not because anyone considered it technically impossible. Keeping that distinction prevents the new owner from repeating the same discussion or misunderstanding the constraints.
Include open questions separately from established facts. A suspected problem, a proposed solution, and an approved change should not appear as equivalent statements. If you are uncertain, say so and identify where the recipient can obtain clarification. Clear uncertainty is more useful than confident wording that disguises a gap.
Keep contact information focused on the work. Explain which colleague handles which issue and where routine questions should go. There is no need to include a large directory of people who have no role in the next stage. A short, relevant list makes the handover easier to navigate.
Finally, ask the recipient to walk through the note when possible. Their questions show which assumptions still need explanation. Update the handover accordingly, then leave it as a concise guide to the current work. A successful handover gives someone enough context to continue responsibly, with a clear path to the details they need.
