In this article
A role transition needs two plans: who will own the work, and who will authorize the access and employment-related changes. A handoff document cannot perform both jobs. Begin with your supervisor and established departmental personnel and technology contacts. The City’s public employee-benefits overview notes that benefits vary with employment context and points current employees to SFHSS; do not infer the effect of a transition from a job title alone. This guide concerns coordination, not an entitlement or account-access decision.
Describe the transition before building the checklist
A temporary assignment, a move between teams and a departure can have different operational needs. State which kind of change is being planned and which dates are confirmed. Separate a proposed date from a communicated decision. If the scope is not settled, label it as a question rather than writing a definitive handoff around an assumption.
Then identify the people authorized to decide each part. Your supervisor may coordinate work ownership, a system owner may approve permissions, and a personnel contact may explain an employment record. One friendly colleague should not be expected to resolve all three. The purpose of the plan is to expose those responsibilities, not quietly transfer them.
Inventory work at the level another person can use
A useful task entry explains the outcome, not just the file name. “Monthly report” is less informative than “prepare the report from the approved source, obtain the required review and place the final version in the designated location.” Include the current owner, the next expected action and the location of the approved instructions. Keep sensitive operational details within the authorized workplace environment.
Distinguish a recurring task from a one-time open issue. A recurring task needs a schedule or trigger and a new owner. An unresolved issue needs its current status, the unanswered question and the person expected to respond. Combining them in a long narrative makes it easy for an open decision to disappear among routine steps.
- Work: what result is needed next?
- Owner: who has agreed to take responsibility?
- Authority: who can approve the relevant decision or access?
- Evidence: where is the current, approved source of information?
- Open point: what still needs an answer?
Transfer knowledge without transferring an identity
Never make a password, verification code or personal sign-in session part of a handoff. The receiving person needs whatever access the authorized system owner approves for their own role. A document saying “use my account until yours works” does not become safe because it is temporary or convenient.
Instead, describe the business task and the permission question to the established technology route. Ask what access the new owner needs and how the transition should be confirmed. Keep the handoff of work moving where it can proceed without unauthorized access, but do not bypass the approval step to meet an informal deadline.
Also review temporary arrangements at the end of the transition. A temporary delegate, a shared queue owner or an added reviewer may need a new decision once the handoff is complete. Record who will check that arrangement. Do not assume that adding a successor automatically removes earlier access or responsibility.
A hypothetical handoff that exposes an unfinished decision
Hypothetical example: an employee changes assignments after preparing a draft for an upcoming meeting. The draft is stored in the approved team location, but a decision about its final audience remains unanswered. A weak handoff says, “The file is in the folder.” A useful one explains that the draft exists, who has reviewed it, which decision is pending and who is authorized to make it.
The successor can then continue the work without mistaking a draft for an approved publication. The outgoing employee does not copy the material to a personal drive in case someone asks later. Instead, the team confirms the approved location and the new owner. The point is continuity within the workplace, not personal possession of every record.
Keep personal administrative questions separate
A transition can leave personal questions about records, pay, benefits or later correspondence. Put those through the appropriate personnel or payroll route rather than embedding them in a broad team handoff. Colleagues taking over an operational task usually do not need the details of your individual employment situation.
Ask which records you are permitted to retain and how to request information later through an official channel. Do not assume continued access after a departure, promise that a particular portal will remain available or download whole workplace folders as a precaution. The authorized administrator should explain the route that applies to your circumstances.
If you have an unresolved pay entry, use a focused pay-statement question. If a transition raises a benefits issue, prepare it using the benefits-routing guide. Those two questions may need different contacts and different evidence even when they arise from the same change.
Test the handoff by asking for a read-back
Instead of asking only, “Did you get the document?”, invite the receiving owner to name the next action and any missing dependency. A person can receive a file without understanding what remains. The read-back is an opportunity to clarify the plan, not an examination or a substitute for training.
Check the small things that interrupt continuity: a link that points to a personal location, an instruction that names a person who has left, or a recurring task with no agreed owner. Fix what you are authorized to fix and route the rest. Avoid rewriting departmental policy inside the handoff simply because the current instructions are inconvenient.
Close the transition with evidence, not optimism
Completion should be visible. The work owner has acknowledged the next action; the responsible administrator has addressed the access request; the remaining questions have named owners. Some items may legitimately remain open. Labeling them accurately is better than declaring the whole transition finished to produce a tidy checklist.
Keep a concise record of the change in the approved location, including the outstanding items and the route for later questions. A good handoff reduces dependence on the outgoing person without erasing the context that the next person needs. It is a record of coordinated responsibility, not a promise that every system or administrative process has already caught up.
Sources & scope
Public sources checked October 27, 2026. Sources establish only the limited public facts described above. The working methods and labeled hypothetical examples are original editorial analysis, not official City procedures or individual advice.