To write a useful handover note, give the next person enough context to continue the work safely: what the task is, where it stands, what happens next, who owns each action, and where the working files are. Keep it focused on continuity. A handover is not a full project history or a list of everything you did; it is a map from the present state to the next decision.
Start with the work that is changing hands
Name the project or responsibility and state why the handover is happening, if that affects timing. Add the date the note was written and the period it covers. Identify the incoming owner and the person to contact for questions. Those details prevent an old note from looking current and help a colleague know whether they are the intended reader.
Put the current status near the top. Use a direct label such as “Ready for review,” “Waiting for the supplier,” or “Blocked by an unresolved date.” Then explain what that status means. “The draft is almost done” is hard to act on; “The draft is complete, but the legal review is still open” gives the next person a concrete picture. Plain language guidance emphasizes writing for a specific audience so readers can understand what they need to do [1].
Separate facts, actions, and decisions
A strong handover distinguishes what has happened from what someone must do. A brief history may explain why the work reached its current state, but next actions should be easy to scan. For each action, name an owner, a due date or trigger, and the expected result. If no date is agreed, say that rather than inventing one.
For example: “Mina sent the revised poster to the printer on Tuesday. Lee: confirm the proof by 3 p.m. Thursday. If the color is still wrong, ask for a corrected proof before approving production.” This gives the new owner a sequence and a decision point. “The proof should be checked” leaves the doer and timing unstated. Active sentences often make the person taking action clearer [4].
Build a small, usable example
Imagine you are handing over a community reading event. A compact note might begin: “Event page: Reading Room, 18 May. Status: room booked; access details still need confirmation. Next: Jo checks the step-free entrance with the venue by 12 May. After confirmation, update the event page and send the access note to registered readers. Files: shared folder, Events/Reading Room.” This example is invented to show the format.
Continue with open questions and risks: “The venue has not confirmed whether the side door will be open. If it is not, ask about the ramp entrance before publishing directions.” A risk should include its likely effect and a response, not just a label like “access issue.” Avoid burying this information in a long paragraph. Short sections and descriptive headings help readers navigate longer documents [2].
Include links, definitions, and boundaries
Point to the exact folder, document, form, or conversation the next owner needs. Use a descriptive name rather than “here,” and check that the intended reader can access it. Spell out unfamiliar abbreviations the first time or avoid them. If a decision is still pending, name who can make it and what information they need.
State what is outside the handover when that prevents mistaken assumptions. For instance, “The room booking is confirmed; catering is not included in this task.” Avoid an exhaustive diary. A reader needs enough background to understand a choice, not every message exchanged. When sentences become crowded with qualifications, split them so the main action stays visible [3].
Review it from the receiver’s position
Before sending, imagine opening the note with no access to your memory of the task. Can you identify the next action, its owner, and when it should happen? Are unresolved questions marked as unresolved? Can the reader find the right file without asking you to translate a folder name? Fix any unclear pronouns such as “they” or “it” when the reference could point to more than one thing [3].
A practical final check is to ask the incoming owner to name the first action they would take after reading. If they cannot tell, revise the sequence or supply missing context. Keep the note in a place the team can find later, and update it if ownership or status changes before the handoff.
