The short version
- A handover deck covers the shape of the project. The questions that follow it are the other sixty percent of the transfer.
- Mid-flight is harder than a fresh start, because the successor inherits commitments and constraints they did not choose.
- Use a checklist for the transferable facts, then plan for the questions rather than hoping the deck prevented them.
- Scope the answerable record to the project, so the successor is not dependent on one person's availability.
Handing over a live project is one of the most reliably underestimated tasks in delivery. The visible part is a document or a deck, and it gets built well. The invisible part is everything the new owner will need to ask over the following two months, and that is where projects lose their momentum.
"The handover deck is 40 slides; the questions are the other 60%."
Why mid-flight is harder
Starting a project fresh means choosing your own constraints. Inheriting one means living inside decisions you did not make, with commitments you did not give, to stakeholders whose expectations were set by someone else.
Three specific difficulties. The successor cannot tell which constraints are real and which are conventional. They do not know which commitments were firm promises and which were indicative. And they will unknowingly reopen settled questions, because the reasoning behind past decisions is the least documented part of any project.
The handover checklist
| Item | What it must say |
|---|---|
| Commitments | Who was promised what, in what words, and how firm |
| Trade-off map | What can be cut, in what order, and what already was |
| Decisions with reasoning | The five that would be most tempting to reverse |
| Stakeholder map | Who needs warning, who is unhappy, who to trust |
| Dead ends | What was tried, and why it was abandoned |
| Open risks | The three things most likely to move the date |
Six items, a few pages. Note what is absent: a description of the work itself, which is on the board, and a full history, which nobody will read.
The trade-off map is the item most often missing and the one successors most need, because without it they will offer up something in a negotiation that was already conceded elsewhere.
The sixty percent after the checklist
However good the checklist, the successor will have a stream of specific questions for two months: what exactly did we agree in July, why was the export descoped, who signed off on the data model, was this dependency ever confirmed.
Those questions go to the previous owner, who has moved on to something else and is being asked to context-switch back into a project they have left. The answers get thinner and slower, and the successor starts guessing, which is how inherited projects acquire decisions nobody can explain.
Scoping an answerable record to the project changes this. A Project StandIn answers from what the people working on it wrote down: where things stand, what was agreed, what was rejected and why, who owns each call, with a source under every answer. It never guesses, and when the answer is not in the record it says so and names who to ask, which keeps the previous owner as a narrow escalation route rather than a permanent help desk.
The handover then has a floor under it. The deck covers the shape, and the record covers the sixty percent. See StandIn for the first 30 days.
The successor's first two weeks
Three things worth doing deliberately.
Meet every significant stakeholder, individually, in week one. Not to gather information but to be introduced, because a stakeholder who has not met the new owner will keep routing to the old one.
Do not change anything in the first two weeks, unless it is on fire. New owners have a strong temptation to demonstrate value by reversing a decision, and it is the fastest way to lose the team's confidence.
And write down, at the end of week two, the five things that were unclear. That list is the real handover gap, and it is both the correction to the deck and the guide for whatever you inherit next.
Common Questions
What should a project handover include?
Commitments with their firmness, a trade-off map, the reasoning behind the most reversible-looking decisions, a stakeholder map, dead ends, and the top three risks. Not a description of the work, which is already on the board.
How long should a mid-project handover take?
Two weeks of overlap where the successor leads and the previous owner reviews, if you can get it. A single handover meeting transfers facts but not the judgement about what is negotiable.
Should the previous owner stay available?
As a narrow escalation route, yes, and with a time limit, because open-ended availability means the successor is never fully the owner and the stakeholders keep routing around them.
What is the most common handover failure?
Not recording which commitments were firm. The successor then either over-delivers on something indicative or breaks a promise that mattered, and both damage trust with stakeholders they have only just met.
Log off like you mean it.
Your StandIn answers the questions that come up while you're out, from what you actually wrote down, so the return pile stays small.