Handover email templates for colleagues, clients and cover

A good handover email answers three questions quickly: who takes over, when the change happens, and what the reader needs to do next.

The details depend on the recipient. An internal successor needs open actions and a link to the working material. A client needs a clear introduction and the next agreed step. A colleague covering an absence needs boundaries, dates and a route for urgent decisions.

Use the three templates below as starting points. Replace every bracketed field and delete any sentence that does not apply. They are draft structures to adapt, not messages ready to send unchanged.

Confirm the owner and date before writing

Check that the incoming person has agreed to the responsibilities and that the manager has confirmed the transfer date. If nobody has accepted ownership, ask the manager to name an interim owner before announcing the change.

Prepare the underlying handover document first. The email can then point to a reviewed source rather than carrying a second, competing version of the entire handover.

Use a specific subject line such as “Reporting handover to Sam from 19 October.” Avoid “Important update” when the actual change can fit in a few words. Include the year or time zone where recipients could interpret the date differently.

1. Internal handover email to a successor

Use this when responsibility is moving to a named colleague. Send it to the successor and include the manager if they need visibility or have an action. Keep the short list of priorities consistent with the linked document.

Subject: Handover: [role or workstream] from [effective date]

Hi [successor name],

From [date], you’ll take over [specific responsibilities], as agreed with [manager]. [Responsibility outside this transfer] will remain with [owner].

The current handover document is here: [approved link]. It includes the active work, relevant contacts, source files and outstanding questions.

Please start with these items:

• [Action or deliverable], due [date]. Current status: [status].
• [Action or deliverable], due [date]. Current status: [status].
• [Question or dependency] needs a decision from [owner] by [date].

The main unresolved item is [issue]. [Named owner] is responsible for [resolution step]. If it affects [specific commitment], please raise it with [escalation contact].

Please check that you can open [essential resource] using your own account and let [permission owner] know if access is missing.

Our handover review is [agreed date, time and time zone]. Before then, please review [specific section or task] and note any gaps.

Thanks,

[sender name]

How to adapt it

If a review has not been arranged, replace the review sentence with an agreed next step.

Keep the priority list short enough to scan. Put longer explanations in the handover document. “Awaiting client approval” gives the reader more useful direction than “Almost finished.”

If the outgoing person will be unavailable after a date, route later questions to the manager or another agreed contact. Do not promise continuing support from someone who has not agreed to provide it.

2. Client introduction email

A client-facing message should make the new contact easy to identify and preserve the next agreed commitment. Resolve internal gaps before sending where possible. Do not include internal staffing commentary, reasons for a departure, or a private handover link that the client should not receive.

HubSpot’s sales handoff guidance recommends restating the customer’s goals and introducing the incoming service team. Applying those two ideas to a change of consultant is an editorial adaptation; it does not mean every sales-handoff recommendation fits an employee transition. HubSpot handoff guidance

Subject: Introducing [new contact] for [project or account]

Hi [client name],

I’m introducing [new contact name], copied here, who will be your [role or main contact for defined scope] from [date].

[New contact] will coordinate [specific responsibilities]. Our current focus is [existing client objective or agreed deliverable].

The next agreed step is [action or meeting] on [date]. [New contact] will [confirmed preparation or follow-up responsibility].

For questions about [scope], please contact [new contact] at [approved business contact details]. [Other named contact] remains responsible for [separate responsibility], if relevant.

[Optional, only if arranged: We’ll use our meeting on date and time to make the introduction and review the next steps together.]

Thank you,

[sender name]

How to adapt it

Describe the incoming person through their role in this work. There is no need to invent a biography or promise an identical service experience. Check any statement about timing or scope with the person responsible.

If the next meeting is still being scheduled, say so and name who will arrange it. Avoid presenting a proposed date as confirmed. For the work behind the introduction, use the consultant handover checklist.

3. Absence-cover handover email

Temporary cover needs a clear end date and agreed decision authority. Explain which work the colleague should handle, what can wait, and which decisions belong to someone else.

Subject: Cover for [workstream] during [start date] to [end date]

Hi [cover colleague],

Thanks for covering [defined responsibilities] from [start date] through [end date]. I expect to resume responsibility on [return date]; [manager] will confirm any change.

The cover notes are here: [approved link]. The scheduled items during this period are:

• [Task or meeting] on [date], with [required action].
• [Task or deadline] on [date], with [required action].

You can make decisions about [agreed authority]. Please refer [decision outside that authority] to [named person]. [Work that can wait] can remain pending until [date or agreed trigger].

For urgent issues involving [specific situation], contact [escalation person or approved channel]. If they are unavailable, use [agreed backup route].

Please record material updates and unresolved items in [shared location] so we can review them when I return. Our return review is [agreed date, or who will arrange it].

Please confirm the scope and flag any missing access before [date].

Thanks,

[sender name]

A useful successor acknowledgment

A reply can distinguish receipt from actual readiness. This short version gives the sender something concrete to act on:

Hi [name],

I’ve reviewed the handover and can access [resources]. My first action is [task] by [date]. I still need [missing item] from [owner]. Please confirm [unresolved responsibility], so I can complete [next step].

Thanks,

[name]

Check recipients, links and promises before sending

Read the message once from the recipient’s perspective. Is their next action clear? Are dates confirmed? Have you removed unused placeholders and checked the addresses in To and Cc?

Open linked material with the intended access level in mind. A working link for the sender does not prove the recipient has permission. CNIL’s access guidance recommends limiting access to what a person needs for their responsibilities. Apply your organization’s approved process when sharing material that contains personal data. CNIL access guidance

Finally, keep the announcement consistent with the handover document. If the owner or date changes, update the source and tell the affected recipients. A clear email gives the transfer a visible starting point; the incoming person still needs the information and access to do the work.