Begin with the receiving person’s task
A handover is not simply a list of files you have accumulated. Identify what the next person must be able to continue, decide or check. Explain the purpose of the work and the boundaries of responsibility. Do not assume that a colleague has the same background you acquired over months. At the same time, avoid repeating every detail indiscriminately. Select the context that makes the next action understandable and direct the reader to authorised supporting records.
Separate status from history
State what is complete, what is provisional and what is waiting for another action. A long chronology can conceal the current state. Include history where it explains an important decision or constraint, not merely because it happened. Use clear dates and references according to the organisation’s rules. Do not label an item approved when it has only been discussed, or closed when a necessary response remains outstanding. Accurate status is more useful than a reassuring tone.
Record the reason for a choice
Explain a significant decision, the alternatives considered and the condition that might require reconsideration. The receiving colleague should not have to rediscover a limitation you already know. Distinguish facts from estimates and informal assumptions. If the work involves a formal approval, point to the approved record rather than reconstructing authority from memory. A handover should make the decision trail accessible without creating a new unofficial source that conflicts with the organisation’s actual records.
Make ownership and access explicit
Name the appropriate role or authorised contact for each unresolved item and identify the expected next step. Check that the recipient can access the necessary material through approved systems. Never include passwords in a handover document or widen access merely for convenience. Questions about permission should go through the organisation’s process. A clear explanation of where access must be arranged is better than transferring restricted information into an easier but inappropriate location.
Test continuity with a reader
Ask the intended recipient, where appropriate, to identify the next action and the main unresolved risk without your verbal explanation. If they cannot, revise the context or status labels. Do not treat a signature or acknowledgement as proof that every detail is understood. Clarify any formal acceptance requirements separately. The purpose of the test is operational understanding, not shifting blame or creating a private record of another person’s supposed failure.
Create a compact handover note
Use a fictional project to practise four headings: purpose, current state, decisions and next actions. Link each action to an appropriate owner and a required input. Add one unresolved question and show where its answer should be recorded. Ask a reader to continue the scenario without inventing missing context. If they need to guess, improve the note. For real work, use the organisation’s approved templates and confidentiality rules. The exercise develops a transferable communication skill; it does not authorise disclosure, delegation or a change in anyone’s formal responsibilities.
