Planning the Handover
Mia and Jack go through her current projects, deadlines, and key contacts to create a practical handover plan. They identify what can be finished before her last day and what needs a new owner.
Dialogue10

Thanks for making time, Jack. I’ve put together a handover plan for my projects, but I’d like to check the priorities and make sure nothing falls through the cracks.
Good call. Let’s start with the product launch. The draft is nearly done, but the client still needs to approve the final copy. When’s your last day?
The 28th. I can send the copy over by Friday and follow up with the client early next week. If they request major changes after that, someone else will need to take over.
I can take that on. I’ve worked with them before, so the transition should be fairly smooth. Could you add their preferences and the approval process to the project notes?
Absolutely. I’ll include the key contacts, past feedback, and a brief timeline. The quarterly report is less straightforward, though; I’m waiting on two departments for their figures.
Could you draft the sections we already have data for, then flag the gaps? I’ll check who can follow up with those departments and own the final report.
That works. I can finish a solid first draft before I leave, but I wouldn’t want to promise the whole report will be ready without those numbers.
Fair enough. What about the weekly client dashboard? It’s mostly routine, but there are a few steps that aren’t documented anywhere.
I’ll record a short walkthrough and write up the steps, including the checks I run before sending it out. We should also decide who’ll own it going forward.
I can own the dashboard for now, and we can revisit the workload next month. Let’s put the handover dates and new owners in the shared tracker so the team has one clear source of truth.
Vocabulary7
- take that on
To accept responsibility for a task. You can use this when offering to handle work that someone else can no longer do.
- follow up with
To contact someone again to check progress or get a response. In this dialogue, Jack will contact the departments about their figures.
- flag the gaps
To clearly point out missing information or unfinished parts. Use this when you want others to notice what still needs attention.
- own the final report
To take responsibility for completing and managing the final report. At work, “own” a task means you are accountable for it.
- walkthrough
A step-by-step explanation or demonstration of how to do something. Mia plans to record one so the dashboard process is easier to learn.
- revisit the workload
To look at the amount of work again later and consider whether it needs to change. This phrase is useful when a decision is temporary.
- source of truth
The one place everyone should check for the most accurate information. Here, the shared tracker will keep handover dates and owners clear.
Key Sentences7
- 1
I’ve put together a handover plan for my projects, but I’d like to check the priorities and make sure nothing falls through the cracks.
This is a polite way to introduce a plan and ask others to review it. You can reuse the structure to check priorities and avoid missing important details.
- 2
If they request major changes after that, someone else will need to take over.
This sentence uses a conditional to explain what may happen and who will need to act. Use “If…, someone will need to…” to set expectations about a possible situation.
- 3
Could you add their preferences and the approval process to the project notes?
This is a courteous way to ask a colleague to document useful information. Replace the details with the preferences or procedures someone else needs to know.
- 4
Could you draft the sections we already have data for, then flag the gaps?
This practical request separates work that can be completed now from information that is still missing. You can use the same structure when coordinating a report or project.
- 5
I can finish a solid first draft before I leave, but I wouldn’t want to promise the whole report will be ready without those numbers.
This sentence makes a realistic commitment while politely explaining a limitation. “I wouldn’t want to promise…” is useful for managing expectations without sounding abrupt.
- 6
I’ll record a short walkthrough and write up the steps, including the checks I run before sending it out.
This explains exactly how someone will document a routine process for a new owner. You can reuse it when offering to create instructions or training materials.
- 7
Let’s put the handover dates and new owners in the shared tracker so the team has one clear source of truth.
This suggests a concrete next step and explains why it will help the team. Use “Let’s put… in…” to propose recording important information in a shared place.