A handover note is the document you leave behind when you go on leave, change roles, or finish a contract. It's the difference between a colleague stepping in with confidence and a colleague sending you ten panicked messages on your first day off. Most people write handover notes in the final hour before they leave. That's exactly when the important details get dropped.
What a handover note actually needs to do
A handover note serves one purpose: give the person covering your work enough information to act without you. That sounds obvious, but most handover documents fail because the writer defaults to listing tasks rather than explaining context. Your colleague can see the task list. What they can't see is why the client in row 3 needs to be called before 10 a.m., or why the invoice in draft is being held deliberately.
A good handover note covers three things. First, the current state of each active piece of work. Second, any decisions or actions due while you're away, including deadlines and who needs to approve them. Third, contact details and background for every key relationship the cover person will need to manage.
Structure: keep it scannable
Use a simple format with headings for each project or responsibility area. Under each heading, write two or three sentences on the current status, then note the next action, the deadline, and who owns it. Bullet points work for action items. Prose works better for context and nuance.
A basic section looks like this:
- Current status: Draft report sent to client on 19 August. Awaiting one round of feedback before final sign-off.
- Next action: Chase the client by email if no response by 25 August. Use the attached template.
- Owner: Priya Mehta (cc: Daniel Osei).
Keep the language plain. Your cover person may be from a different team and won't know every acronym. If you're writing for an international colleague, the guidance on writing in plain English for international readers applies here directly: cut jargon, shorten sentences, and spell out every abbreviation on first use.
The parts writers most often forget
Three things routinely go missing from handover notes, and all three cause real problems.
The first is pending email threads. If you've promised to reply to someone, say so. Give the cover person the sender's name, the rough content of the expected reply, and any constraints. Don't assume they'll scroll through your inbox and work it out.
The second is escalation paths. Who does the cover person call if something goes wrong? Listing one manager is not enough. Name a backup. Include a mobile number. "Reach out to the team" is not an escalation path.
The third is decisions you've parked deliberately. If you've chosen not to act on something yet, say so. A cover person who doesn't know that will either act prematurely or feel anxious about leaving it. One sentence of explanation saves everyone time.
Tone and length
Write a handover note the way you'd write a briefing for a smart colleague who's new to your work. Confident, specific, and free of hedging. Avoid padding. A handover that runs to 15 dense pages is almost as unhelpful as one that runs to 2 sparse bullet points.
Aim for one page per major project, with a summary table at the front listing all live pieces of work, their status, and who's covering them. The table gives a fast overview; the sections beneath it give the detail. This structure means the cover person can triage quickly without reading everything.
On format: a Word document or a shared Google Doc both work. Email is a poor choice for anything complex because it's harder to scan and can't easily be updated. If your organisation uses a project management tool, a pinned note in the relevant workspace is better still.
Before you send it
Walk through the document with the person covering you, not just email it to them. Even ten minutes on a call catches the gaps you didn't know were there. Ask them to flag anything that feels incomplete. That conversation will surface the one thing you forgot.
Check dates, names, and contact numbers carefully. A handover note with a wrong phone number is worse than no number at all because it creates false confidence. For anything you're attaching, cite enclosures clearly so the reader knows exactly what's included and where to find it.
Finally, if you're sending the handover note by email, write a subject line the cover person can find later. "Handover - Priya covering 25 Aug to 5 Sep" is useful. "Handover notes" is not. Your cover person may need to search for it in a hurry. Make it findable. For more on getting subject lines right, the principles in writing subject lines that get your email opened apply equally to internal documents that need to be found under pressure.
A well-written handover note protects your work, protects your relationships, and protects the person covering you. It's a short document with a disproportionately large impact. Write it before the last hour if you can.