How do I decide what work to finish before changing roles and what to transfer?

Start with a list, not a promise to finish it all. For each item, write down: the next meaningful milestone, when it is due, what it depends on, who needs to act next, and what would happen if it remains open when you move. Then ask two questions: Can I realistically complete the useful milestone before my transition? And is completing it more helpful than preparing someone else to continue it?

Treat these as separate decisions: finishing a whole project may not be possible, but you might complete a review or deliver a usable draft. Conversely, a task that looks nearly done may still need ongoing ownership. Agree on priorities and transition timing with your manager or the appropriate decision-maker; your list helps make that discussion concrete.

Transfer an item when it will continue after you leave, another person must make a decision, a dependency is outside your control, or the remaining time is too short for a responsible finish. Also flag work whose next action is not obvious. A task can be small and still need an explicit owner.

For each transfer, capture the current state, the next action, the relevant date or decision point, known dependencies, and where the working materials are kept. Describe uncertainty honestly: for example, “Waiting for [team] to confirm [item]; follow up by [date]” is more useful than presenting an unresolved assumption as settled. Use the team’s approved workspace and avoid copying sensitive information into places where it does not belong.

Here is a hypothetical example; the dates, roles, and work are placeholders, not a recommendation about your particular transition.

1. Draft a project update — A review-ready draft is feasible before [transition date], and the team needs it for its next discussion. Decision: finish the draft; note any open questions rather than implying they are resolved.
2. Vendor decision — The decision depends on input expected after [transition date]. Decision: transfer. Record what input is pending, who is expected to provide it, and who should decide what happens next.
3. Recurring weekly report — The next report is manageable, but the work continues afterward. Decision: complete it only if it fits the agreed priorities, and transfer the recurring responsibility with the location of the template and the next due date.

The point is not to score tasks mechanically. It is to make the trade-offs visible, then confirm who owns each next step.

Use a short worksheet and ask for corrections before treating it as final:

Transition date: [date]

Work item: [name] Current state: [one-sentence status] Next milestone or action: [specific step] Due date or decision point: [date, or “not set”] Dependency or open question: [person/team or “none known”] Proposed plan: [finish milestone / transfer / pause by agreement] Proposed next owner: [name or role] Materials location: [approved workspace or reference] Confirmation needed from: [manager, receiving owner, or other relevant person]

For example, “Proposed plan: transfer; next action: review [draft] after [input] arrives; proposed owner: [role].” Ask the receiving person to confirm that the next action and timing make sense. If no owner is available, mark that as an unresolved decision and raise it promptly rather than silently retaining or abandoning the work. Keep the final list aligned with what your manager and receiving owners actually agree to.