Transfer an open workflow when a staff member leaves

Where the extra work starts

Transfer decisions, evidence and commitments together so the replacement can continue without rebuilding each case.

For invoice preparation, ParseMill combines PDF extraction, source review and Excel export in one workspace. Test whether the downloaded workbook gives the receiving colleague what they need. The plan has one account owner; shared team seats and automatic posting to accounting systems are not included.

This is a work-continuity checklist. Account access, retention and offboarding should follow the firm's established administrator and employment processes; the handover should not depend on sharing the departing person's credentials.

A practical way to get it right

Inventory active tasks, client promises, pending reviews and scheduled future work within the person's role. Reconcile the task tracker with permitted mailbox and document records so work outside the obvious queue is considered. Record source locations and unresolved questions without copying unnecessary sensitive content into a broad handover document.

Assign each outcome to a named replacement with the appropriate authority. Ask the receiver to open the evidence, understand the latest commitment and accept the transfer. Split work among owners where necessary instead of sending everything to one person merely because a bulk reassignment is convenient.

Review recurring templates and schedules separately from current cases. A current task can be transferred while next month's work still points to the departing colleague. Record who will maintain those settings and verify the next generated instance when it appears.

Karbon: Managing colleagues on leave distinguishes visibility through shared views from reassignment. For a permanent departure, confirm actual ownership rather than treating a shared view as a completed transfer.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

The table separates current actions from future generation rules. Copy the categories and add an accepted-at field for each receiving owner. A row is not transferred merely because a replacement name is typed into the handover sheet; the operational record and source access must support the same assignment.

Catch the cases that create rework

If the departing colleague is unavailable, reconstruct commitments from reliable records and label uncertainty. Do not present an inferred promise as confirmed. Prioritize cases with imminent agreed actions and unreviewed decisions, while assigning someone to investigate the rest.

Check copied tasks for missing comments or inaccessible linked files. Keep the original reference so a replacement can distinguish transferred evidence from a newly created summary.

Microsoft: Copy and move Planner tasks warns that in basic plans, task-copy context and linked-file access can differ. Test the replacement’s evidence and retain key decisions outside omitted comments.

Decide whether the change is worth keeping

Have the lead reconcile the inventory against accepted transfers and remaining unknowns. Confirm no active task or recurring role still depends on the departing person unintentionally. During the first subsequent cycle, inspect newly created work and client replies for missed routing. The handover is complete when ordinary staff can continue the work using approved access and documented commitments.

The workflow audit checklist can help record the observed friction before considering a change.