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, you’re 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 — designed to help whoever comes after you get up to speed as quickly as possible.

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.

What to include

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.

Example:

I manage the relationship between the product team and our three enterprise clients. My role is to translate client requirements into actionable specs for engineering and ensure clients are kept updated on timelines. I also own the quarterly business review process.

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.

3. Active projects

For each project: what it is, where it stands, what needs to happen next, and who else is involved. Be specific about the next step — “in progress” is useless; “waiting on client approval, follow up with Sarah by Friday” is helpful.

4. Key relationships

Internal colleagues and external contacts who matter. Name, company or team, and why they’re important. One sentence each. Don’t just list names — explain the relationship.

5. Recurring commitments

Every meeting, report, or process that happens on a schedule. Weekly, monthly, quarterly. Who attends, what it covers, where the notes live. These are often the things most likely to fall through the cracks.

6. Tools and access

Every system, tool, or account used in this role. Who to contact to get access. Include anything that isn’t obvious from a job title.

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. This is the most valuable section and the one most people forget to write.

What to skip

Skip your full job history, general company information your replacement can find elsewhere, and anything that will be irrelevant to whoever is coming in. The best handover documents are concise, not comprehensive.

How long should it be?

One to three pages. If it’s longer, it’s probably capturing too much. If it’s shorter than a page, you’ve probably missed something important.

How to write it faster

The hardest part of writing a handover document isn’t the writing — it’s remembering everything. Most of what you need to capture is already in your emails, calendar, and files. If you work in Google Workspace, OneLast.Day reads those automatically and pulls out the key information for you.