How to Write a Handover Document (With Examples)

Writing a handover document is one of the most dreaded tasks of leaving a job. You’re already mentally checked out, juggling your notice period, and now your manager wants a document that captures everything in your head. This guide walks you through exactly what to include, what to skip, and how to get it done without spending days on it.

What is a handover document?

A handover document — sometimes called a transition document or knowledge transfer document — is a written summary of your role, active projects, key contacts, and critical knowledge. Its purpose is to help whoever comes after you get up to speed as quickly as possible. For a complete breakdown of the sections, see what to include in a job handover.

The best handover documents don’t just describe what you do. They describe what the person reading it needs to do, and what they need to know to do it well. There’s a meaningful difference between those two things.

What to include

A complete handover document has seven sections. Not every role needs all seven equally, but you should at least consider each one before skipping it.

1. Role overview

A 2–3 sentence description of what you do and why it matters. Keep it concise. Your replacement will read dozens of documents in their first week and attention is limited.

2. Key responsibilities

A bulleted list of your core ongoing duties. Not every task — just the ones that would go wrong if nobody picked them up. If something would survive a month without attention, it probably doesn’t belong here.

3. Active projects

For each project you own or contribute to: what it is, where it stands, what the next concrete action is, and who else is involved. The most common handover failure is a project described as “in progress” with no indication of what that actually means.

Project: [Name]
Purpose: [One sentence on why this exists]
Status: [Specific current state]
Next step: [Exact action + owner + deadline]
Key contacts: [Names and roles]
Files: [Where to find relevant documents]

4. Key relationships

Internal colleagues and external contacts who matter to this role. For each: name, company or team, and why they’re important. One sentence each. Don’t just list names — explain the relationship and anything non-obvious about how to work with them.

5. Recurring commitments

Every meeting, report, or process that happens on a schedule: weekly, monthly, quarterly, annual. For each: what it is, how often it happens, who else is involved, and where the supporting materials live.

These are the things most likely to fall through the cracks. A missed weekly standup is obvious. A missed quarterly report that was due in six weeks is not.

6. Tools and access

Every system, tool, or account used in this role. What it’s used for, and who to contact to get access. Include anything that isn’t obvious from a job title. Most people remember to document Salesforce and Slack. Fewer people document the vendor portal that only gets logged into once a month.

7. Critical knowledge

The stuff that only you know. The workaround for the broken system. The client who prefers WhatsApp. The spreadsheet that runs the whole thing but looks like a personal file. The meeting that always runs over and why.

This is the most valuable section and the one most people forget to write. It’s also the hardest, because by definition this knowledge lives in your head and not in any document. The best approach is to write this section last, after completing everything else — the act of writing jogs your memory.

What to skip

Skip your full job history. Skip general company information your replacement can find in the onboarding docs. Skip detailed process documentation for things that are clearly documented elsewhere — link to those documents instead of reproducing them.

The best handover documents are concise, not comprehensive. If in doubt, apply this test: would the next person actually need to read this in their first two weeks? If not, cut it.

How long should it be?

One to three pages. If it’s longer, you’re probably capturing too much. If it’s shorter than a page, you’ve probably missed something important. The length will vary by role — a complex client-facing role might genuinely need three pages; an individual contributor role might need one.

Format matters. Use headers. Use bullet points for lists. Use short paragraphs. A document that takes five minutes to read because it’s well-structured is more useful than one that takes twenty minutes because it’s a wall of text. If you’re handing over to a junior or someone brand new, see the guide on handing over to someone who has never done the role — it changes what belongs in the document.

How to write it faster

The hardest part of writing a handover document isn’t the writing. It’s remembering everything. Start by pulling together your raw material:

• Your calendar for the past three months — surfaces recurring commitments and key relationships
• Your email sent folder — reveals active projects and external contacts
• Your task manager or to-do list — shows what’s in flight
• Any existing documentation you’ve written — link rather than reproduce

Once the document is drafted, the next step is the conversation. The handover meeting with your successor is where the document earns its keep — or shows its gaps.

If you work in Google Workspace, OneLast.Day reads your Gmail, Drive, and Calendar automatically and pulls out the key information — projects, contacts, meetings, and the knowledge buried in your emails — so you’re not starting from a blank page.