How to hand over a workflow without it coming back to you
The short answer
A handover sticks when five things are in place before the work changes hands: a written scope with a measure of success, one named owner, the process captured from real examples, clear rules for what still comes back to you, and a weekly scorecard. Without them, the work drifts back to the founder within weeks.
Why handovers fail
- Tasks are handed over, not outcomes. “Send the invoices” leaves out who chases, when, and what counts as done.
- Nobody owns it. Shared work becomes nobody’s work, and it comes back to the founder.
- The process lives in the founder’s head. Without examples, the new owner guesses, and the founder steps back in to correct.
- Every exception comes back. With no agreed limits, every unusual case is escalated, so the founder is still in the loop.
- Nobody measures it. Without a measure, the founder checks everything by hand, which is the job they were trying to hand over.
The five things to put in place
- A written scope and a measure of success. Which steps are included, which are not, and the standard each must meet: turnaround, quality, how much less often it reaches you.
- One named owner. A person, not a team, who answers for the result.
- The process, taken from five real examples. Recent cases of the workflow, including one that went slowly. Screenshots or exports are enough. The slow one shows where it really gets stuck.
- Escalation rules. What the owner decides alone, what comes to you, and how quickly you will answer when it does.
- A weekly scorecard. On-time completion, quality, anything overdue, and how many times you had to step in. The last number is the one that tells you the handover is working.
A four-week rhythm that works
- Week 1, scope and handover. Agree the scope and success measures, gather the examples, write the process, set up access.
- Week 2, live. The new owner runs the work; you answer questions quickly.
- Week 3, stabilise. Fix what week two exposed. Tighten the escalation rules.
- Week 4, assess. Read the scorecard against the measures you agreed in week one, and decide.
This is the shape of Verth’s 30-day pilot, which takes over one workflow against success criteria agreed in writing, with a scorecard every week. It works just as well if you are handing the work to someone already on your team.
How you know it worked
The work happens on time without you asking, its quality holds, and the number of times it lands back on you has fallen against where you started. If all three are true after four weeks, the workflow is handed over.