How do I plan a transition when a project’s sponsor or decision-maker changes?
Quick answer
Create a short sponsor-transition brief before the handoff. List decisions in progress, what has already been agreed, commitments and deadlines, and the people affected. Mark what needs confirmation rather than treating it as settled. Ask the outgoing and incoming sponsors to review the same brief, clarify who decides what, and record next steps, owners, and dates. This keeps the transition focused without assuming the incoming sponsor will approve existing plans.
The question, the details, the next step.
Our project sponsor is changing, and several decisions are still open. What should I do first so the handoff doesn’t turn into a long history lesson?
Start with a decision-focused snapshot, not a chronological account of everything the project has done. Give the incoming sponsor enough context to act, while making clear what is agreed and what is not.
Use four headings:
- Purpose and current position: the project’s intended outcome, current phase, and the next meaningful milestone.
- Decisions in progress: the question, options under consideration, who has input, and when a decision is needed.
- Commitments: promises, approvals, deadlines, or dependencies that people may be relying on.
- Open questions and risks: anything that could change the plan or needs sponsor attention.
For each item, label its status: confirmed, proposed, pending, or needs reconfirmation. Don’t infer approval from silence or present a proposal as a commitment. The brief should help the new sponsor see where their attention is needed, not force them to endorse the previous sponsor’s choices.
How do I handle commitments that were made by the outgoing sponsor? I don’t want to undo something important, but I can’t speak for the new person.
Separate the fact that a commitment was made from whether it remains approved. Record who made it, what was promised, to whom, and any deadline or dependency you know. Then mark it needs reconfirmation unless the incoming sponsor has explicitly accepted it.
For example, assuming a project team promised a partner a draft by a particular date, write: “Draft promised to [partner/team] by [date] by [outgoing sponsor]; delivery plan and date need reconfirmation with [incoming sponsor].” This makes the expectation visible without silently changing it or claiming the new sponsor has agreed.
If the commitment is time-sensitive, raise it early and ask what to communicate while approval is pending. Avoid making a new promise on the incoming sponsor’s behalf. Record the decision, who will communicate it, and by when.
What context does the incoming sponsor actually need? The project has a lot of history, and I’m worried the short version will leave out something important.
Include context that changes a decision or the next action; keep background available separately if it may be useful later. For each pending decision, note why it is open, the realistic options, the consequences the team has identified, and the people who need to be consulted. Distinguish known information from assumptions and unresolved questions.
A compact worked example, with hypothetical details:
Decision: Choose between [option A] and [option B] for [project component]. Needed by: [date], because [milestone or dependency]. Current status: Pending; no final approval recorded. Relevant context: [constraint or prior discussion that affects the choice]. Input needed from: [roles or teams]. Next step: Incoming sponsor to confirm decision owner and review options by [date].
This gives the sponsor a starting point without burying the decision in a meeting-by-meeting recap. If a key detail is uncertain, label it as uncertain and identify who can verify it.
Can you give me a usable outline and a way to run the actual handoff meeting?
Use this as a one-page briefing outline, adjusting it to the project:
Sponsor transition — [project name]
- Purpose and current position: [outcome, phase, next milestone]
- Decisions in progress: [question; options; status; decision needed by; input needed]
- Commitments to review: [commitment; made by; recipient; deadline; reconfirmation status]
- Agreements to preserve: [what is confirmed and where it is recorded]
- Open questions or dependencies: [issue; effect; person who can clarify]
- Proposed next steps: [action; owner; date]
- Decision roles: [who recommends, who provides input, who approves—confirm at handoff]
In the meeting, first check that the summary is accurate. Then ask the incoming sponsor which pending decisions they will take, what needs more context, and which commitments they want reconfirmed or communicated. Close by reading back decisions, owners, and dates. Send the updated brief to the participants and keep a note of anything still unresolved. If the transition is rushed, prioritize deadlines and decisions that could affect other people’s plans.
A practical checklist
Separate confirmed agreements from proposals, pending decisions, and items needing reconfirmation.
For each open decision, record the question, options, decision date, and relevant input.
List commitments with their source, recipient, deadline, and current confirmation status.
Flag uncertain context and identify who can verify it.
Confirm decision roles, next actions, owners, and dates with the incoming sponsor.
A few more useful answers
Should the outgoing sponsor attend the handoff?
If available, their participation can help clarify the reasoning behind open decisions and commitments. Still, record what the incoming sponsor confirms rather than treating the outgoing sponsor’s account as automatic approval.
What if the incoming sponsor cannot review the brief before a deadline?
Highlight the deadline and the consequence of waiting, then ask who can authorize an interim response. Do not make or imply a commitment on the new sponsor’s behalf.
How much project history belongs in the transition brief?
Include the history needed to understand a current decision, commitment, or dependency. Keep other background separate and offer it if the incoming sponsor asks.