In this guide
A successor can read every date on a project schedule and still miss the one decision that will determine whether the next milestone happens.
Start at the next commitment that crosses the departure
Identify the next approved milestone, review or promised update after the outgoing person changes roles. Ask what decisions are needed before it and who can make them. This focuses the transition on continuity rather than trying to reconstruct the whole project in one meeting.
Phoenix Water Services publicly describes infrastructure projects and planning alongside ongoing operations. A staff change in such a context could affect coordination even when the project itself continues. The example here is about the person’s handover, not engineering instructions or a reported City project.
Separate decisions, proposals and assumptions
A project file can contain all three. Have the departing person identify which decisions were authorized, which proposals remain open and which assumptions need validation. Preserve the relevant source and approval history in the authorized project environment.
Do not turn a meeting note into a formal decision merely because the original coordinator is leaving. Likewise, do not reopen every settled choice without a reason. The successor needs to understand the basis and scope of the existing decision before deciding what requires further review.
Worked hypothetical: a technology project changes coordinator
Phoenix ITS describes large technology project management among its functions. Imagine a coordinator moving to another assignment shortly before a planned internal readiness review. The date is on the schedule, but one contributing team has not confirmed a prerequisite.
The outgoing coordinator identifies the prerequisite, its owner and the decision route if it remains unresolved. The incoming coordinator accepts responsibility for following up from the agreed handover point. The person authorized to decide whether the review proceeds remains explicitly identified; the coordinator’s replacement does not silently inherit every approval power.
The handover output contains the next milestone, the unresolved prerequisite and the approved route for a decision. It does not reproduce system diagrams, credentials or confidential project information. This is a fictional example, not a description of a Phoenix deployment or project-control method.
Use a short successor walkthrough
Ask the incoming person to explain the next decision and where its supporting evidence lives. This is a useful way to discover missing context. A folder tour shows where files are; a decision walkthrough shows whether the successor can use the relevant record for the next authorized step.
Where knowledge is incomplete, record the gap instead of replacing it with certainty. The supervisor or project authority can decide whether more overlap, a different owner or a changed plan is needed. An employee should not make that consequential choice simply to declare the handover finished.
Make the former lead’s exit observable
Confirm when routine requests should stop going to the outgoing person and how any approved final assistance will end. Update contact references through the authorized process. A successor cannot fully own the assignment if other teams still treat the departed lead as the only decision route.
Your output is a transition brief centered on the next decision: evidence, authority, owner and acceptance point. Reporting-line changes covers the wider team context. The old-role handoff helps keep a short overlap from becoming permanent dual ownership.
Sources and limits
Public sources checked October 5, 2026. Editorial examples are hypothetical; official instructions and case-specific decisions remain with the responsible City service.
- City of Phoenix About Water Services
Public description of water, wastewater, infrastructure maintenance and capital planning; no technical operating procedure or employee authorization is reproduced.
- City of Phoenix Information Technology Services
Public description of City technology, identity management, employee IT assistance and project functions; no private access workflow was tested.