Questions to Ask When Taking Over a Project
Handover questions for anyone inheriting a project already in flight, covering what it is meant to deliver, where the real status differs from the reported one, which commitments and deadlines are already made, who disagrees with the plan, and what the outgoing owner never got to.
20 questions, each with the reason to ask it · includes a conversation guide
The questions
Open any question to see why it works.
- 1
In one sentence, what is this project supposed to deliver?
Ask the outgoing owner, the sponsor, and two people doing the work. If the sentences do not match, you have found the actual problem before you have read a single document, and it explains most of the delays already on record.
- 2
Who signs off that it is finished?
Projects without a named acceptor never end, they only get quieter. You want a person, not a committee, and you want to know whether that person has ever seen the current plan.
- 3
What is the reported status, and what is the real one?
Ask them separately and in that order. The gap between the two is the debt you are taking on, and the outgoing owner is the last person who will ever describe it honestly, because after today it stops being their problem.
- 4
Where did the deadline come from?
Dates come from an estimate, a contract, an event, or somebody's guess in a meeting two years ago. Only the first two are worth defending, and the difference determines whether the date can be moved at all.
- 5
What has already slipped, and what reason was given at the time?
Look for whether the same cause appears twice. A single bad quarter is noise. The same dependency slipping three times is the thing that will slip again the week before your first review.
- 6
What has been quietly cut from the scope already?
Descoping usually happens in a meeting and never reaches the people expecting the original thing. Find out what was dropped and, more importantly, whether the customer or sponsor was ever told.
- 7
What decisions are still open, and who is sitting on them?
An open decision is different from an unfinished task: it is idle time you are paying for. Ask what each one is blocking, and how long it has been waiting, because these are the fastest wins available to a new owner.
- 8
What commitments have been made to customers or other teams?
Verbal promises about dates, features, and access outlive the person who made them. You need the list now, because renegotiating in week one reads as prudence and renegotiating in month three reads as failure.
- 9
Where does the documentation that people actually use live?
There is the official project space and there is the folder, chat thread, or spreadsheet where the real decisions are recorded. Ask for the second one specifically, and ask who else has access to it.
- 10
Who is on this team full time, and who is borrowed?
Borrowed people get recalled without warning, usually by a manager who never agreed to the loan in writing. Get names, percentages, and whose budget each person sits on.
- 11
Is anyone here leaving, or wanting to?
Handovers are a common moment for people to move on, and the outgoing owner often knows who is looking. Losing the one person who understands a component is the risk most likely to break your first month.
- 12
What is the budget, how much is spent, and what is committed but not yet invoiced?
The third number is the one that catches new owners. Purchase orders and contractor time already agreed will land against your remaining budget, and they rarely appear in the project's own reporting.
- 13
Which vendors or contracts are involved, and when do they renew or expire?
A licence or contractor agreement expiring mid-project creates a hard stop with a long lead time to fix. Ask who holds the relationship, because if it is the person leaving, the introduction has to happen this week.
- 14
Which dependencies rely on another team, and do they know we are relying on them?
Roughly half the time, the other team has no idea, or agreed to it under a different set of dates. Confirm each one directly rather than trusting the plan, and confirm it with the person who does the work, not their manager.
- 15
What is the part most likely to go wrong, and what happens if it does?
Ask the engineers or practitioners, not the previous manager. The riskiest piece is usually well known on the ground and softened in every upward summary, and the mitigation is often something nobody has been given time to do.
- 16
Who disagrees with the direction of this project?
There is always someone, and they are frequently right about something specific. If you do not find them now, you will meet them at the review where they explain, in front of the sponsor, what nobody listened to.
- 17
What do you report, to whom, and how often?
Inheriting a reporting cadence blind means either you miss the first one or you send a status you cannot yet defend. Ask what format they expect and which single question the audience keeps asking.
- 18
If the date has to move, who has to agree to that?
Establish the escalation path before you need it, while it is a hypothetical question. Asking for the first time under pressure makes the request look like an excuse rather than a plan.
- 19
What did you never get to?
This is the most generous version of what is broken, and people answer it far more honestly. Expect testing, documentation, a stakeholder never brought along, or a decision deferred so many times it stopped being tracked.
- 20
Six weeks from now, what will I wish I had asked you today?
Ask it at the end, when the formal handover is done and the outgoing owner has relaxed. It reliably produces the one thing they knew mattered but had no obvious place to mention.
Inheriting a project already in flight
Practical guidance for the conversation itself.
Running the handover itself
Running the handover itself
Book more than one session
A single handover meeting produces the tidy version. The useful details arrive in the second and third conversation, once the outgoing owner has stopped presenting and started remembering. Schedule them before their last day, not after.
Ask for status twice, worded differently
Once as what is the status, once as what would you be worried about if you were staying. The second phrasing removes the need to defend past reporting, and it is usually where the real risks appear.
Take the introductions, not just the documents
Ask the outgoing owner to introduce you personally to the sponsor, the difficult stakeholder, and each vendor contact. A warm handoff of a relationship is worth more than the folder of files, and it expires the day they leave.
Write your own summary and send it back
One page: what it delivers, when, who signs off, top three risks, open decisions. Send it to the outgoing owner and the sponsor and ask them to correct it. Their corrections are the handover.
The first two weeks as owner
The first two weeks as owner
- Talk to the people doing the work individually before you accept any plan as accurate. Group settings produce the reported status, not the real one.
- Clear the open decisions first. They cost nothing to resolve and they are the visible proof that something changed when you arrived.
- Confirm every cross-team dependency directly with the team that owes it, and get a date from them in writing.
- Resist reorganizing the plan in week one. You do not yet know which awkward parts of it are load bearing.
- If the date is already unachievable, say so early. New owners get exactly one window in which bad news is diagnosis rather than failure.
- Find out what the sponsor cares about most, and make sure your first status report answers that before anything else.
Warning signs during a handover
Warning signs during a handover
- The outgoing owner cannot name who signs off on completion.
- Status has been green every week for months, including the weeks something slipped.
- The plan has no named owner for a large piece of work, only a team name.
- Key people are borrowed from another manager with no written agreement about how long.
- There is a customer commitment nobody can produce in writing, but everyone remembers differently.
- You are told not to worry about a particular stakeholder because the previous owner handled them.