How do I take over an in-progress project after its lead changes?
Quick answer
Arrange a focused handoff with the outgoing lead and, where useful, key collaborators. Review the project’s goal, current status, commitments and dates, open decisions, dependencies, and next milestones. For each item, record an owner and next action. Separate confirmed information from estimates and questions that still need checking, then share a concise draft so the right people can correct gaps.
The question, the details, the next step.
I’m taking over a project already underway because its lead is changing. What should I do first? I don’t want to rely on old notes and miss something important.
Start with a handoff conversation rather than trying to absorb every document at once. Ask the outgoing lead to explain the project’s purpose, current state, commitments, unresolved decisions, collaborators, and next milestone. Treat existing notes as information to verify, not proof that everything is current.
Before the meeting, request the latest plan, status update, decision notes, and collaborator list, if available. A focused agenda might be:
- What outcome is the project meant to deliver?
- What is complete, in progress, blocked, or not started?
- What has been promised, to whom, and by when?
- Which decisions remain open, and who can make them?
- What happens next, and who owns each action?
The aim is a shared understanding, not a review of the previous lead’s performance.
How do I distinguish commitments from ideas being discussed? What should I do with dates that sound uncertain?
Ask about each important deliverable: Is it agreed, proposed, or still under discussion? Who agreed to it, with whom, and what does it include? Classify each date as a confirmed commitment, a working estimate, or an unconfirmed target. If no one can verify it, record that uncertainty instead of turning it into a promise.
For example: “Review draft — in progress; owner: [name]; recipient: [team or stakeholder]; date: Friday [confirmed / estimate / needs confirmation]; next step: check scope and date with [decision owner].” The bracketed details are placeholders, not project facts.
If a commitment is unclear, identify who can confirm it and by when. Don’t change scope or dates on someone else’s behalf. Update the shared summary once the relevant people have checked the details.
There are several collaborators and unresolved decisions. What should I capture without turning the handoff into a huge meeting?
You don’t need everyone at the first meeting. Ask who contributes to the work, who depends on it, who needs updates, and who has authority to resolve each open decision. Invite only people needed to clarify the handoff; request specific input from others separately.
For each unresolved decision, note the question, information or input needed, decision owner, and when the decision matters. For example: “Decision: [question]; owner: [role or name]; input needed from: [roles]; needed by: [date or milestone]; next step: [action].” If ownership is unclear, make assigning an owner a follow-up rather than guessing.
Also record dependencies—work, approvals, or information needed from others—and who to contact. This gives you a practical map of whom to involve and why, without expecting the first meeting to solve everything.
What should I send afterward, and how do I avoid presenting unverified details as fact?
Send a concise draft status summary after the handoff. Mark details still being checked, and separate confirmed information from estimates and open questions. Give each next action an owner and, when known, a date or milestone. Ask the outgoing lead and relevant collaborators to correct specific gaps; don’t imply they approved details they haven’t reviewed.
Copyable template:
Project: [name] Purpose / intended outcome: [confirmed description] Current status: [state and brief supporting detail] Committed work: [deliverable — owner — recipient — confirmed date] Dates or scope to confirm: [item — who will confirm — by when] Open decisions: [question — decision owner — input needed — needed by] Collaborators and dependencies: [person or role — contribution or dependency] Next milestones and actions: [action — owner — date or milestone] Unknowns to revisit: [item — next check]
Update the note when a commitment or decision is confirmed, and tell affected people what changed. For a large project, separate near-term priorities from issues to investigate later.
A practical checklist
Request the latest plan, status, decision notes, and collaborator list, if available.
Confirm the intended outcome and distinguish completed, ongoing, blocked, and unstarted work.
For each deliverable, record agreement status, owner, recipient, scope, and date certainty.
Capture open decisions with an owner, needed input, and next action.
List collaborators and dependencies by their role in the work or decision.
Share a draft summary, label uncertainties, and ask relevant people to correct gaps.
A few more useful answers
Should I change a project commitment during the handoff?
Record the concern and identify who must confirm a change. Don’t present a changed scope or date as agreed until the relevant decision-maker and affected collaborators have confirmed it.
What if the outgoing lead cannot answer a question?
Record it as an open question, identify who or what might clarify it, and assign a next step. A clear unknown is more useful than an unsupported assumption.
How detailed should my first status summary be?
Include enough to clarify next actions, owners, commitments, and unresolved decisions. Put background that does not affect near-term work in supporting notes.