Your Transition Document: 8 Things Your Replacement Needs

Here is the short answer. A transition document when leaving a job should capture the eight things your replacement needs on day one: your current projects and their status, the recurring meetings and what each is for, the files and where they live, the people to know and what each knows, the systems and logins, the open loops and risks, the quiet work that keeps the role running, and the first two weeks they should spend learning not doing.

You are leaving in a week or two. You want to leave the role better than you found it, and you want your replacement to not feel ambushed on Monday. This is the document that does both.

Most people write a transition doc the Friday before they leave. By then they have forgotten half of what makes the job work. The result is a long file full of links and no idea what matters. Your replacement reads it, closes it, and asks a coworker for help anyway.

Write the doc now, in short bursts, over the next week. Keep it to one page or two. Here is what belongs in it.

1. Your current projects and their real status

Not "in progress." Not "on track." Write what someone would need to know to pick it up without you. For each live project, include three lines: what it is in one sentence, where it is right now in plain words, and what the next decision point is. If a project is behind, say so. If something is quietly dead but still on the plan, say that too.

This section is the one your manager will read first. It is also the one that tells your successor what the next two weeks of their life look like.

2. The recurring meetings and what each is for

List every meeting on your calendar that repeats. For each, write why it exists, who runs it, and whether your replacement should actually keep attending. Half of them, they probably should not. The other half, they need the backstory.

Meetings are where institutional knowledge lives. A standing 30-minute call that looks pointless from outside is often the only place three teams talk to each other. Your successor will not know that unless you say so.

3. The files and where they live

Not a dump of folder links. A short map. "Project A lives in Drive, in the shared folder under Marketing. Project B lives in Notion. Weekly numbers live in that one spreadsheet nobody owns." Point to the three or four places your successor will spend most of their time, and name the file inside each.

While you are here, handing off your work email inbox is a separate exercise worth doing properly. Your transition doc does not need to replicate that work. One line pointing to it is enough.

4. The people to know, and what each one knows

This is the part people skip, and it is the most useful thing in the whole document. For every person your replacement will interact with in their first month, write one line: name, team, and what they are the expert on. Not an org chart. A living key.

"Sarah: knows the history of the pricing model better than anyone." "Marcus: owns the vendor relationship for X, and he prefers Slack over email." "Priya: do not route approvals through her on Fridays, she is in sprints." Small, specific things like this save your successor three weeks of trial and error.

Building this list is also the mental warm-up for a parallel list you need: the people you want to thank before you leave. That is what It Was Great Working With You is for. Section 4 is for your replacement; the farewell list is for you.

If you have had the last 1:1 with your manager already, you have probably already discussed who the critical people are. Pull that list into this section.

5. The systems, logins, and ownership

Not every password. Not any password, actually. Instead: which systems your role owns, who the admin contact is, and which shared accounts need to be transferred. "I am the admin on the Figma account. Need to transfer admin to Jamie by my last day." "The Zapier account is on my personal email. It needs to move to a shared mailbox."

This is the section IT and your manager will care about. Spend 20 minutes on it with a password manager open and you will catch five accounts that would have been lost in a month.

6. The open loops and quiet risks

What is not finished. What is finished but not yet announced. What is about to blow up that nobody but you knows about. You do not need to solve these. You need to name them.

"The contract with Vendor X auto-renews in March. Someone needs to decide whether to renegotiate by February." "The team keeps saying they will migrate off the old CRM. Nobody has owned that decision yet."

Write these in plain language. The goal is not to flag every risk you can think of. The goal is to make sure none of them surprise your replacement in month two.

7. The quiet work that keeps the role running

Every job has a layer of work that is not on the job description. The onboarding Slack message you send to new hires. The spreadsheet you update every Monday morning. The team birthday reminders. The vendor you check in with once a quarter because the account manager quit.

This work is invisible until you stop doing it. Name it. One line per item. Your replacement does not have to adopt all of it, but they should know it exists so they can decide.

8. The first two weeks: learn, do not do

End the doc with a short note to your successor. Not instructions. A suggestion. Something like: "If I were you, I would spend week one talking to the people in section 4 and reading section 1. Do not try to make decisions in your first week. The team is going to want to show you five problems to solve. Resist. Learn first."

Your successor will not read this when you give it to them. They will read it in week two, when they are overwhelmed, and this one paragraph will be the thing that calms them down.

Writing a transition doc is the mechanical part of leaving. The harder part is the names: the people you worked closely with, the ones you want to thank before you walk out. Your calendar already holds that pattern. The problem is pulling it out before Friday.

How long should the transition document be?

One page is ideal. Two is fine. Beyond that, your replacement will skim it and miss the signal. If a section is running long, pull it into a linked supporting doc and leave only the summary in the main file.

The number that matters is not word count. It is "how long before my replacement finds the next thing they need." Keep that under a minute and the doc is good enough.

What format should it be in?

Whatever your team already uses. If everything lives in Notion, write it in Notion. If your team is a Google Doc shop, write it there. Do not introduce a new tool for this one document. Your replacement should be able to find it in week two without asking anyone.

One other practical note: before your last day, remember to return your work laptop cleanly. If your transition doc only exists on that laptop, it is going to disappear from your replacement's view the moment you turn it in. Save a copy in the shared space before anything gets wiped.

When should you share it?

Share the doc with your manager three or four days before your last day. That gives you time to update the parts they flag and gives them time to pass it along to your replacement before onboarding. If your replacement is already hired, share it with them directly on your second-to-last day. Walk them through the first page. Let them read the rest on their own.

Do not share it earlier than that. Transition docs that circulate for two weeks collect too many edits and lose their shape. One pass is enough.

The transition doc is one half of leaving well. The other half is making sure the right people hear from you before Friday. That part is easier than it looks once you know who to look for. Start your list at It Was Great Working With You.