In this guide
“Call me if anything comes up” sounds generous. During a role change, it can also leave the old assignment attached to you long after someone else is supposed to own it.
Hand over responsibilities, not your entire memory
Start with recurring duties, unfinished decisions and known upcoming obligations. For each, identify the authorized record location and the person or role accepting it. You are making work findable, not exporting the contents of your mailbox or producing a private instruction manual.
The Phoenix City Clerk Department manages functions including meeting notices, agendas, records and licenses. An employee leaving an administrative assignment connected with those functions may need to surface obligations tied to future meetings or unresolved records work. Actual handling and retention requirements come from the employer, not this checklist.
Make an approved overlap small enough to end
If both teams want a period of assistance, ask them to define its purpose, permitted work, priority and endpoint. A final walkthrough is different from continuing to own an old inbox. Do not assume that helping the successor authorizes you to approve old work or retain access after it should change.
Ask how requests arriving after the transition will be routed. The answer might involve an approved reassignment, contact update or managed access change. Let the responsible people choose the mechanism. Do not set up forwarding to a personal account or give a successor your credentials.
Worked hypothetical: a meeting-support assignment changes hands
Imagine an administrative employee moving away from a meeting-support assignment. A forthcoming meeting has two outstanding preparation questions. The successor can find the official materials, but one approval remains unresolved. The departing employee identifies the approval role and the most recent authorized status; they do not turn an informal conversation into an approved outcome.
The supervisor accepts that the successor owns follow-up from the agreed transition point. One scheduled walkthrough is approved for the departing employee. After that walkthrough, new questions go to the successor or supervisor. The former owner is no longer the default destination merely because they remember the history. No actual Phoenix meeting schedule or handoff policy is asserted.
Check the access boundary separately
Phoenix Information Technology Services publicly describes identity management and employee IT assistance among its responsibilities. That public description supports asking about authorized access changes. It does not provide a do-it-yourself account-transfer process.
Make a list of access questions, not passwords: which shared resources the successor needs, which old permissions require review and which device or equipment return instructions apply. Ask the authorized channel to act. A file being technically visible does not mean your new role still permits every use of it.
Use a teach-back to reveal missing context
Where the supervisor considers it appropriate, invite the successor to describe the next step on one representative assignment. A missing reference or misunderstood approval becomes visible immediately. Keep this within approved work and training arrangements; it is not a test you impose on a colleague.
Close with a short record of what was accepted, what remains unresolved and who owns each exception. The cleanest handoff may still contain open work. Its success is that the work has a destination and an understood decision route. The internal-move plan connects that endpoint to the new assignment. If you are leaving the employer, the departure sequence adds personal employment and benefit questions that a task handoff cannot answer.
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 City Clerk Department
Public scope includes Council agendas, meeting notices, records and licenses; no records-retention rule or employee authority is inferred.
- 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.