TL;DR:
A good handoff gives the new person a context summary, says who does what next, and tells the other side what is happening.
Introduce the colleague in the same thread so the other side knows the change is real.
Stay available briefly after the handoff, then step back.
You are going on a project, changing roles, or simply the wrong person for a thread that has been running for weeks. You forward the whole thing to a colleague with "can you take this?" and they spend the afternoon reading it. Meanwhile the person on the other end wonders whether anyone is still answering them.
A handoff has two audiences: your colleague, who needs context, and the other party, who needs to know who to talk to now. Serving both takes one short email, written once.
Decide what you are handing over
The whole conversation, or one part of it?
Is the colleague now the contact, or an extra pair of hands?
Will you still be involved, and for how long?
Does the other party need to agree to the change? Usually they only need to be told.
Write down the answers in a line or two before drafting. If you cannot say it in two lines, the handoff is not yet clear to you either.
What a colleague needs to see
A colleague stepping into a thread needs the context summary, the current state and the next step. The context summary is a few lines: who the other party is, what they want, and what has been agreed so far. For the current state, state what is waiting and on whom. Then give the next step with a name and a date: who does what next.
If the thread is long, write the summary yourself instead of pointing at the thread. See summarizing a long email thread for someone new for how to mark decisions, open questions, owners and dates.
Steps for the handoff
Check with your colleague first: Ask if they can take it and by when. A surprise handoff is not a handoff.
Write the context summary: Three to five lines or bullets. Include any promises you have made to the other party.
Reply in the existing thread: Add your colleague to the recipients. Keeping the same thread keeps the history attached for both people.
Address the other party first: Tell them who is taking over, why, and what they can expect. Then address your colleague with the details.
Say who does what next: Name the action, the person and the date.
Offer a short window: Say you are available for questions until a specific date. Then step back.
Worked example: introducing a colleague into a thread
You have been talking with Lena at a supplier about a delayed order. You are going on leave, and your colleague Omar will take over. Here is the email, sent as a reply to the thread, with Omar added.
Subject: Re: Order 7731 delivery date
Hi Lena, hi Omar,
Lena, I am on leave from 18 November, so I am handing this thread to my colleague Omar, who is copied. He knows the order and will be your contact from now on.
Omar, here is where things stand:
- Lena's team confirmed the order will ship late, with a new date expected by 20 November.
- We agreed that if the new date is after 5 December, we will ask for a partial shipment.
- Next: Lena sends the confirmed date. Omar then decides on the partial shipment and tells the warehouse.
I am reachable for questions until 17 November. Thank you both.
SamCheck it. The other party gets the key facts: who is taking over, from when, and that Omar knows the order. Omar gets a context summary in three lines and a clear next step with owners (Lena sends the date, Omar decides). The dates are written out, and the window for questions ends before the leave starts, since 17 November is the day before 18 November.
Notice what is missing: no apology, no history lesson, no request that Omar read all of the earlier messages. If he wants more, the thread is below.
Writing the context summary well
The summary is the part your colleague will read twice, so spend your effort there. Write it as if the colleague will never open the old messages. Name the other party, say in one line what they want, and list anything you promised. Promises are the most dangerous thing to lose in a handoff, because the other party remembers them even when you do not.
Keep opinions separate from facts. If you think the other party is difficult, or that a deadline is unrealistic, say it in a private message to your colleague, not in a thread the other side can read. In the shared email, stick to what was said and agreed.
Finish with the first thing your colleague should do. A handoff that ends with a clear action is much more likely to be picked up on the same day than one that ends with "let me know if you have questions".
Mistakes to avoid
Forwarding with no explanation. The recipient has no idea what to do.
Moving the conversation to a new thread. The other side loses history and may think it is a new topic.
Leaving the other party unsure who to contact.
Forgetting promises. If you told someone you would send a document by Friday, include it in the summary.
Staying in the thread forever. Say when you step out, and do.
After the handoff
Check in once the next step is due, ask whether anything was unclear, and then leave it. If the thread was a customer problem, share the tone you used and what the customer cares about. For a complaint, the guide on replying to a customer complaint shows a calm structure your colleague can reuse. If you are away for a stretch, also set an out-of-office that helps so new senders know who to contact.
Frequently asked questions
Should I ask the other party for permission?
Usually you inform them rather than ask. If the person is a senior contact or the change is sensitive, a line of warning helps.
What if my colleague wants the full history?
Point to the thread below your message and offer a call. The summary is for speed, not a replacement.
Get started
