How to Write a Handover Email to Your Team (With Templates)

A handover email to your team is the short, written version of everything you want colleagues to know before you go: what you were working on, who is taking it over, and how to reach you if something breaks. Done right, it answers the questions people would otherwise ask in your last week. Here is exactly what to write.

What a handover email to your team is for

Your handover document covers the operational detail. The handover email is the announcement that points people to it. Two different artefacts, two different jobs.

The email has three goals: tell the team you are leaving (if they do not already know), tell them who is now responsible for what, and tell them where to find the longer handover document. That is it. Anything else is optional.

When to send it

Send the handover email two to three working days before your last day. Earlier than that and people forget. Later than that and there is no time to respond to questions while you can still answer them.

Send it after you have already briefed your manager and your direct successor in person. The email should confirm what they have already heard, not surprise anyone with the news.

What to include

A handover email to your team has five parts. Each one earns its place. Cut anything that does not fit one of these:

• The fact that you are leaving, and your last day
• Who is taking over what, broken down by area or project
• Where the handover document lives, with a working link
• How to reach the right person for the most common questions
• One short thank you, kept brief

Do not include your reasons for leaving. Do not include grievances. Do not include speculation about what the team should do differently in future. The handover email is not the place.

Structure: the parts of the email

Subject line

Be direct. People scan inboxes. Aim for clarity over creativity.

Handover: my last day is Friday 30 May
Moving on: handover and who to contact
My last week: handover details inside

Opening

State the fact in the first sentence. Date, then context. Do not bury it under three lines of throat-clearing.

Who is taking over what

This is the section that gets read. Make it scannable. Use a short list mapping each area of your work to the person now responsible. If responsibilities are being split, say so explicitly: vague handovers create gaps.

Where the handover document lives

Include the link. Confirm access has been shared with the relevant people. If you do not have the document ready yet, you are not ready to send the email.

Closing

One sentence of thanks. Optionally, share how to stay in touch (LinkedIn is enough). Keep the personal email address off a team-wide message unless you genuinely want everyone to have it.

A template you can copy

This is the version most people should send. Replace the names and projects, keep the structure.

Subject: Handover: my last day is Friday 30 May

Hi team,

A quick note to confirm that Friday 30 May is my last day. It has been a real pleasure working with you all.

To make the transition as smooth as possible, here is who is now picking up what:

- Client accounts (Acme, Northwind): Priya
- Quarterly reporting and the QBR process: Tom
- The internal tooling project: Sarah, with Daniel as backup
- Anything ad hoc that does not fall into the above: please go to Priya in the first instance

Full handover document is here: [LINK]. It covers active projects, key contacts, recurring meetings, system access, and the things that only live in my head. Access has been shared with Priya, Tom, Sarah and Daniel, and with the wider team in read-only.

If anything is unclear in the next two days, please reach out before EOD Thursday and I'll do my best to answer.

Thanks again. You can find me on LinkedIn if you want to stay in touch.

[Your name]

A short version (when the team already knows)

If your departure has been public for weeks, you do not need to re-announce it. Strip the email down to the operational part.

Subject: Final handover: who to contact after Friday

Hi all,

As you know, Friday is my last day. Quick recap of who is taking over what:

- Client work: Priya
- Reporting: Tom
- Tooling project: Sarah

Handover document: [LINK]. Worth a skim if any of the above affects you.

Catch me on Slack or email before Thursday EOD if anything needs clarifying.

Thanks for everything,
[Your name]

Common mistakes

• Sending it too late. An email on your last day at 4pm helps no one. People need time to ask questions.
• Vague ownership. "The team will pick this up" is not a handover. Name a person for each area.
• Linking to a document that does not exist yet. Write the handover document first. Send the email second.
• Mixing the handover email with the goodbye email. They are different things and they should be different messages.
• Including grievances. Even one sentence of frustration becomes the only sentence anyone remembers.
• CC'ing the entire company. Send it to your team. The wider goodbye goes out on Friday, separately.

After you send it

Expect a small wave of replies in the next 24 hours. Most will be one-line thanks. Some will be questions about edge cases you forgot. Answer them in writing, then add the answer to the handover document so the next person who asks has it already.

On your last day, send a separate, shorter goodbye email. For the structure and timing of that one, see what to do in your last week at work.

The handover email is only as good as the document it points to. If you are working in Google Workspace, OneLast.Day reads your Gmail, Drive and Calendar and drafts the handover document from your actual work data, so the link in your email goes somewhere worth opening.