In this guide
Receiving a list is not the same as accepting responsibility for everything people believe that list represents. Review the promises attached to the work before you become its only contact.
Ask for the position at a particular time
When you enter an assignment, ask for an authorized snapshot of work as of the handover time. It should distinguish completed work, open work and work waiting on a decision. The snapshot belongs in the employer’s approved environment. Do not create a personal archive of cases to make the takeover easier.
Phoenix Planning and Development publicly identifies plan intake, routing, reviews, inspections and customer inquiries among its functions. These are useful examples of work that can continue while an employee changes roles. The public page does not expose the department’s internal queue or tell a new employee which cases they may decide.
Look for a promise outside the status label
For each item assigned to you, ask whether someone has promised an update, requested an exception or agreed to a next step. A status such as “pending” may be accurate and still omit the important fact that a response is expected tomorrow. Confirm where that history is recorded and who may alter the commitment.
Do not equate an old target with a deadline you are authorized to change. Ask for its basis. It could be a formal requirement, an approved schedule, a customer expectation or an estimate. Those distinctions determine whom to involve if the work cannot proceed as expected.
Worked hypothetical: a reassigned plan-support employee
An employee hypothetically takes over six plan-support inquiries from a colleague moving to another assignment. Five have an identifiable next step. The sixth says only “waiting,” but the colleague explains that a customer was promised an update after an internal review. The incoming employee asks that the actual record and approved communication history be identified.
The new owner then confirms whether they may provide that update or must obtain a reviewer’s decision first. Their acceptance note states that five items have been reviewed and that the sixth remains dependent on a named decision role. It does not label all six “resolved” to make the transition look tidy. This is an editorial example, not a Phoenix service standard.
Use an exception list instead of rereading everything
A focused acceptance review should identify what prevents confident ownership. Common questions include a missing current record, an unclear next decision or a commitment known only to the departing person. Prioritize these exceptions with the supervisor rather than treating every historical document as equally urgent.
The same method fits a hypothetical Public Works employee inheriting fleet-administration inquiries. Public Works describes fleet maintenance and administrative support as distinct functions. A new coordinator can clarify responsibility for the inquiry without assuming authority to make a technical maintenance decision.
Define the end of the takeover
Ask for an acceptance point that means something: assigned items reviewed, important commitments located, unresolved exceptions assigned, and the next review route understood. The employee receiving work and the person authorized to assign it should share that understanding. A farewell message alone does not establish it.
Your output is a brief acceptance statement with a date, scope and exceptions. For example: “The assigned items have been reviewed; these two questions still require the designated reviewer.” Use the employer’s terminology and records. The outgoing handoff guide shows the other side of this conversation; the authority check helps prevent a takeover from becoming an accidental expansion of your decision rights.
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 Planning and Development
Public description of planning, permitting, inspections, counters and supporting functions; not an internal delegation or approval matrix.
- City of Phoenix About Public Works
Public scope of solid waste, fleet and facilities functions. Used to ground hypothetical workforce transitions, not to describe a verified internal handoff process.