How to Write a Handoff Email When You Change Roles

When you move to a new role, leave a project, or go on extended leave, someone inherits what you were doing. The handoff email is what stands between them picking it up smoothly and spending your first two weeks away answering “where is the X” messages. It is also, quietly, a reputation document: a clear handoff is the last impression you leave on a team, and a vague one undoes a lot of good work.

Most handoffs fail by being either a data dump nobody can navigate or a cheerful summary that omits the things that actually matter: the in-flight items, the landmines, and the people to talk to. A good one is organized around what the successor needs to do next, not around everything you happen to know.

Organize By What They Need To Do, Not What You Know

The temptation is to write down everything, which produces a wall of text the reader cannot prioritize. Instead, lead with what is live and time-sensitive, then what is stable, then reference material. Your successor’s first question is “what needs my attention this week,” so answer that first.

Before:

Here is everything about the project. We started it last year and there have been many phases and stakeholders and I have learned a lot along the way that I want to pass on to you.

After:

Three things need attention in the next two weeks: the vendor contract renews on 20 October (draft is in the shared folder, Legal has questions), the Q4 report is due to Dana on the 31st, and the API migration is paused pending a decision from Platform. Everything else is stable and documented below.

The second version tells the successor exactly where to point their attention. The first tells them a project exists. This is the same prioritization that makes a status update executives actually read work: lead with what is live.

Name The Landmines

The most valuable thing in a handoff is the knowledge that is not written down anywhere: the client who needs careful handling, the process that looks optional but is not, the system that breaks in a specific way. This is exactly what gets lost when you leave, and exactly what your successor will step on if you do not warn them.

Be honest and specific about these, without being indiscreet. “The Acme account is sensitive after the March billing issue, keep their account manager copied on everything” is a genuine gift. Omitting it to keep the handoff tidy is how your successor inherits an avoidable crisis. A handoff shares the operational reality the way a shift handover report does: the exceptions matter more than the routine.

Give Names, Not Just Tasks

For each live item, name the person who knows more, so your successor has somewhere to go when a question arises after you are gone. A task with a contact is resumable; a task with no contact is a dead end. List the two or three people who matter for each area, and, if you can, tell those people who is taking over so the introduction is not cold. Write it in plain, direct language a stressed successor can act on fast, which is the point of the plain language guidelines.

A Wrivio Context for a role handoff could say:

Rewrite this handoff into a clear, prioritized summary. Keep every date, name, deadline, and system reference exactly as written. Lead with the time-sensitive live items, then stable areas, then reference material. For each live item, include the key contact. Preserve any warnings or sensitivities, and do not flatten a specific risk into a vague reassurance.

Press Ctrl+Shift+Space, paste your draft, and check the diff. Confirm the dates and contact names stayed exact and that it did not drop a landmine warning in the name of sounding positive.

Close The Loop Before You Go

Send the handoff while you are still reachable, not on your last hour, so your successor can ask the questions the document raised while you can still answer them. A handoff email plus a short overlap conversation beats a perfect document sent as you walk out. This is the practical companion to a farewell email when leaving a job: the farewell is for the relationships, the handoff is for the work, and both deserve to be done before you are gone rather than after.

Common Questions

What should a role or project handoff email include?

The live, time-sensitive items first with their deadlines and key contacts, then the stable areas, then reference material, plus honest warnings about any sensitivities or landmines. Organize it around what the successor needs to do next, not around everything you know.

How do I keep a handoff from being an overwhelming data dump?

Prioritize ruthlessly. Lead with what needs attention in the next week or two, mark what is stable, and push background material to the end or a linked document. The successor’s first need is knowing where to focus, so answer that before documenting everything.

Should I write down the informal knowledge?

Yes, that is the most valuable part. The sensitive client, the fragile process, the system that breaks a certain way: this undocumented knowledge is what your successor will otherwise step on. Share it specifically and discreetly rather than omitting it to keep the handoff tidy.

When should I send the handoff?

While you are still reachable, not on your final hour, so your successor can ask follow-up questions while you can still answer. Pair the written handoff with a short overlap conversation for the best transfer; a perfect document sent as you leave helps far less.

How do I make each item resumable?

Attach a contact to it. For every live item, name the person who knows more, so a question after you are gone has somewhere to go. A task with a named contact can be picked up; a task with no one to ask becomes a dead end.

Download Wrivio for Windows to turn a sprawling brain-dump into a prioritized, resumable handoff before you move on.