A Practical Handover Note for Work That Changes Hands
A handover often becomes either a folder dump or a long narrative written too late. The receiver gets documents without knowing which ones matter, a status without the reasoning behind it, and a list of contacts without understanding the relationships that keep the work moving.
A practical handover note is a map, not an archive. It helps the next owner understand the purpose, locate the trusted material, recognise current risks, and take the first sensible actions without pretending every uncertainty has been resolved.
Open with purpose and current state
In three sentences, explain why the work exists, who should benefit, and what is true today. Link the current brief rather than retelling its whole history. State the next important milestone and whether confidence in it is high, mixed, or low—with the evidence behind that judgment.
The receiver should be able to describe the work accurately after reading the first page.
Separate active work from background
List the few items currently active, their owners, expected outcomes, and review dates. Then show blocked and waiting items separately. Archive old tasks outside the note. A handover is not improved by proving how much activity occurred in the past.
The simple states from Make Progress Visible Without Building Another Dashboard create a clear snapshot without requiring access to a complicated reporting setup.
Link decisions with their reasoning
Identify the decisions that shape present work: chosen scope, rejected route, service agreement, technical boundary, or risk accepted. Link each to the relevant entry in the decision log.
Do not force the receiver to reverse-engineer reasoning from meeting notes. A decision without context looks arbitrary and is likely to be reopened unnecessarily.
Name risks as conditions
Write each risk as a condition and consequence: “If the data agreement is not signed by 18 August, live testing moves outside the current window.” Add the owner, latest review, current mitigation, and next trigger.
A generic red status does not tell the new owner what to watch. Clear conditions make early intervention possible.
Describe the relationship map
List essential contacts with their role in the work, not only their title. Note who owns approval, who holds operational knowledge, who is affected by change, and where trust or tension requires care. Keep personal judgments respectful and factual.
Schedule live introductions for relationships that cannot be transferred through a paragraph. The outgoing owner should explain the purpose of the connection and then let the new owner establish their own working pattern.
Show where trusted material lives
Link the current brief, plan, evidence, decision log, budget, contracts, and published outputs. Mark which files are authoritative and which are historical. Remove duplicate “final” versions before transfer rather than asking the receiver to choose.
Document access requirements early. A perfect note cannot compensate for a missing account, expired permission, or private folder discovered after the previous owner leaves.
Give the first five actions
List the actions the receiver should take in sequence during the first week: confirm the brief, meet the operational owner, review the oldest blockage, attend a key session, or validate the next milestone. Include the reason behind each action.
This sequence reduces the pressure to learn everything at once and protects the most consequential knowledge first.
Use a live handover conversation
Send the note in advance. In the session, ask the receiver to explain the work back in their own words, identify the greatest uncertainty, and propose the first decision they expect to face. Correct misunderstandings and update the note together.
Agree when ownership officially changes and how long the outgoing owner remains available. Without that boundary, both people may act—or neither may.
Review after two weeks
Ask what the note made easy, what remained hidden, and which files or relationships were unnecessary. Improve the handover template with this evidence. A transition process should learn from receivers, not only reflect what outgoing owners remember to write.
The aim is not perfect continuity. It is responsible continuity: the next person can see the terrain, understand the important choices, and move without repeating avoidable discovery.
