Handover Document Template for Leaving a Job (1 Page)

Here's the short answer: a handover document that actually gets used is one page, written in the first week of your notice period, and organized into five short sections — a paragraph of context, a three-line status of the work, the two or three decisions your successor will face in month one, the ten people who matter most, and the two or three fragile things nobody ever wrote down.

The forty-page wiki you were told to build is not a handover document. It is a reassurance object. Your successor opens it once on their first Tuesday, scrolls three screens, closes it, and asks a coworker instead.

That is not a failure of effort. It is a failure of format. The person taking over your job needs a single page they can print, read in six minutes, and keep next to their laptop for the first month. Everything else lives in the wiki they already have.

The one-page template

Copy this into a fresh doc and fill it in. Keep the whole thing to one printed page, roughly 350 to 500 words total. If a section runs long, it belongs in a linked appendix, not the doc itself.

Section 1 — Context (one paragraph, about 60 words)

What the role actually does, in plain language your successor's manager would recognize. Not the job description. The real thing. Two sentences on what you own, one on who you serve, one on what "good" looks like at the end of a quarter. Skip acronyms unless they are unavoidable — a successor from another team may not know them.

Section 2 — Status (three lines)

Line one: what is in flight this quarter, in one sentence per active workstream. Aim for three or four workstreams, not eleven. Line two: what is blocked and by whom. Line three: what is done but not yet announced. Your successor's first status meeting will be a question from someone senior about "where things stand"; these three lines are the answer.

Section 3 — Next decisions (two or three items)

The one to three real decisions coming in month one that only the role owner will be asked to make. Name each one, name who will bring it, and name the timeframe. This is the section your successor will read three times. Do it well.

Section 4 — The ten people (one line each)

Ten names, not thirty. Role, one line on how they work best ("prefers Slack, not email"; "will push back once and then agree"), and one line on the piece of shared context that would take your successor six months to earn otherwise. This is where a real read of your last twelve months of calendar matters — memory over-weights whoever pinged you most recently.

Section 5 — Fragile things (two or three items)

The two or three things that will break if nobody knows about them, and that are not written down anywhere. The vendor contract that renews on the 14th of every month. The report that runs from your personal laptop. The stakeholder who needs a heads-up email before every all-hands. Write these plainly, no jargon. This section, more than any other, is what your name will be attached to a year from now.

The section that quietly fails

Section four is where most handover docs collapse. Everyone remembers the noisy people. Nobody remembers the quiet partner from Q1 who covered on-call when you were out, or the cross-functional PM from a project that shipped in March, or the person who inherited half your seam when someone else left.

If you write section four from memory, you will list the seven people who pinged you last week and miss three who mattered more. That is not carelessness. It is how memory works. Your last twelve months of calendar is the only honest record of who worked closely with you — the recurring 1:1s, the standing meetings, the project rooms that ran for eight weeks and then stopped.

Write it in week one, not the last Friday

Two weeks feels like plenty of time. It is not. If you wait until your final Friday afternoon, you will write a rushed, incomplete version that creates problems for months. Draft the whole page in the first week of your notice period, then leave it alone for four days. On day nine or ten, come back and cut a third of what you wrote. That second pass is what makes it usable. This is the same reason the first week of notice matters more than most people plan for.

The 45-minute handover meeting

Book one 45-minute meeting with your successor in the middle of your final week, Wednesday morning if you can. Not four one-hour sessions spread across two weeks — nobody remembers that much. One clean pass, in order:

• Five minutes: read section one aloud together. Answer questions.
• Ten minutes: walk section two, workstream by workstream. Note anything they push back on.
• Ten minutes: section three. Ask them who they think will bring each decision. If they name the wrong person, correct it now.
• Ten minutes: section four. Warm-intro three names in real time, right from the meeting.
• Ten minutes: section five. Fragile things. Slow down here.

If your successor has not been named yet, run the same 45 minutes with your manager. The doc is still worth writing — someone will read it in month one. More on which meetings to book (and which to cut) in the final-week meeting calendar.

Three edge cases

You are the only person who does this work. Section three doubles in length and section five triples. Add a "how I made these decisions" paragraph at the bottom that gives your successor the reasoning framework, not just the tasks. That paragraph is what protects the work after you are gone.

You were laid off with same-day access cut. Write the one page from home from what you remember, send it as a plain-text email to your former manager within 48 hours, and stop there. You do not owe more. The company owes you an honest exit; the doc is a courtesy, not a debt. The five-day plan in training your replacement compresses into one afternoon in this scenario.

You have four or more weeks of notice. Write the one-pager in week one, run three 45-minute meetings across weeks two, three, and four, and use the extra time to make warm introductions rather than expand the doc. Longer notice does not mean a longer document. It means a better-known successor.

Three mistakes that make the doc useless

Writing forty pages instead of one. If your successor cannot read the whole thing in six minutes, they will read none of it.

Skipping section four because "everyone already knows everyone." They do not. Six weeks after you leave, your successor will be in a meeting with someone whose name they will not know, on a project they thought was done. Section four is the answer to that meeting.

Sending the doc without a real walkthrough. A doc without a meeting is a wiki page. A doc with a meeting is a handover.

The final line

Your handover document is the last artifact of your working relationship with a job that mattered. Write it on one page. Deliver it in one meeting. Make sure section four names the people who actually shaped your time, not the ones your inbox surfaced this week. If you want help building that list from your calendar, It Was Great Working With You reads the last twelve months and hands you back the ten names in about three minutes.