Transfer the work, not just the task list
This guide helps a role holder and successor capture recurring responsibilities, the context behind decisions, and the relationships that help work move. It is for a longer-term role change, rather than a brief shift handoff. The examples use the fictional Northstar Services regional service team; they illustrate work coordination, not a universal procedure.
Decide what needs a transfer conversation
Prioritize work that repeats, depends on context, or relies on relationships.
Transfer the cycle, the inputs, what the role holder looks for, and how the successor can prepare and lead the next review.
Explain the cues that prompted a past decision, what information was checked, and which manager or established support route can resolve an unfamiliar case.
Record the outcome and any reusable reference the team already maintains; a full walkthrough may not be useful if the task will not recur and no decision context needs to carry forward.
Introduce the successor to the relevant collaborator and explain what information each role provides, when to involve them, and what a useful handoff looks like.
Work through the transfer together
Use a real responsibility as the example, then let the successor try it.
-
1
List recurring responsibilities
Name each deliverable, its cadence or trigger, the people who depend on it, and the next time the work is expected.
-
2
Capture the judgment behind the work
For each responsibility, note the usual inputs, decisions, exceptions, and where the role holder gets reliable context. Separate observed practice from assumptions.
-
3
Walk through one completed example
Choose a recent, non-sensitive example. Explain what was noticed, what was compared, what conclusion followed, and what would have prompted a conversation.
-
4
Make the introductions useful
Tell each collaborator why the successor is joining the work, what information or decision passes between the roles, and how to raise an unresolved ownership question.
-
5
Let the successor practice
Have the successor prepare or lead the next suitable cycle while the role holder observes. Record questions that need clarification and agree who will answer them.
Worked reference: monthly service review
Fictional Northstar Services example. This authored reference is illustrative, not a live queue or universal decision rule.
| Responsibility | Cadence or trigger | Judgment to transfer | Successor practice |
|---|---|---|---|
| Prepare the regional service review | Monthly, before the review meeting | Compare the incoming trend summary with recent context; distinguish an expected fluctuation from a change that needs discussion. | Prepare the next review, state the comparison used, and identify any question for the manager. |
| Follow up on an unresolved review question | When the review leaves an owner or next step unclear | Check which role owns the decision; do not infer ownership from the report alone. | Summarize the open question and take it to the relevant manager or established support channel. |
Show how judgment travels
A worked example makes the reasoning visible without turning it into a fixed rule.
Start with the signal and context
In the fictional example, the role holder notices that a monthly trend differs from the previous review. The first question is not “Is this automatically a problem?” but “What changed, and what context helps explain it?”
- Check the same time period and measure used in the prior review.
- Note a relevant change in workload, reporting, or timing if it is known.
- Keep the source and any uncertainty visible in the review notes.
Explain the decision to discuss it
The role holder compares the trend with recent context and explains why a sustained or unexplained change merits a conversation, while a one-period fluctuation may need more context first. This is an example of reasoning—not a threshold or rule for other teams.
- Describe what evidence supports the interpretation.
- Name what remains uncertain rather than presenting a guess as fact.
- Ask the manager or established owner when the decision or responsibility is unclear.
Make responsibilities between people clear
These are role descriptions, not named employees. Use the relevant people in your actual transfer conversation and agree the ownership of any open question.
Role holder
Explains recurring work and decision context; demonstrates a representative cycle; identifies assumptions and open questions.
Successor
Asks questions, practices the work, records useful context, and identifies where ownership or access remains unclear.
Relevant collaborator
Explains the interface between roles, the information they provide or need, and how a handoff is ordinarily coordinated.
Manager
Clarifies scope or ownership questions and directs unresolved access or process issues to the established internal support route.
Agree the next practice, then close the loop
A useful transfer ends with a clear next conversation—not an assumed approval or completed system record.
Choose the next responsibility the successor will prepare or lead.
Name any open question and the role responsible for resolving it.
If ownership or access is unclear, raise it with the manager or use the established internal support channel.
The role holder, successor, and manager agree the next practice opportunity together.