You hand off the client welcome process on a Monday. You explain it clearly, share the files and feel a small rush of relief. By Wednesday there are three messages that start with “quick question”. By Friday you are sending the welcome emails yourself again, because it is faster than answering the questions.
If that sounds familiar, there is a reason, and it can be fixed. A task handed off without the structure around it always finds its way home.
I call this the bounce-back: work that was handed off and returned to the founder. It happens in law practices, coaching businesses, consultancies and studios, and it happens to capable people on both sides. The person taking on the work wants to get it right. The founder wants to let go. The work still comes back, because something it needed stayed behind.
A handoff that holds is a small system with four parts. Leave one out and the work returns to you, usually as a question.
1. The owner
Every handed-off piece of work needs one named person who owns the outcome. “The team” is not an owner. Neither is “whoever is free”.
Owning the outcome goes further than doing the steps. The owner is the person who moves the work forward when something is unclear, who notices when it stalls, and who answers for it in the weekly review.
Consider new-matter intake in a small law practice. If the honest answer to “who owns intake?” is “me, until it reaches the paralegal”, then the paralegal owns a fragment. Every gap between the fragments defaults back to the founding attorney, and that is where her afternoons go.
Try this
Pick one recurring process. Can you name its owner in under three seconds? If you hesitate, or the answer is you, that process has no owner yet.
2. The context
Context is everything someone needs to do the work without asking you. It covers what done looks like, the standard you expect, where the files live and why the work matters to the client.
Most handoffs pass on the steps and keep the context in the founder's head. That is where the quick questions come from. Each one is reasonable. Together they turn a handed-off task into a running conversation with you.
Picture a coach who hands her welcome pack to a contractor. The contractor sends it on time, every time. What the contractor doesn't know is that clients who arrive by referral always receive a short personal voice note first. Clients notice the difference, the founder steps back in, and the handoff quietly reverses.
The fastest way to share context is a finished example. One completed version, annotated with why each part is there, teaches more than a page of instructions.
- Definition of done: what the finished work looks like when it is right.
- The standard: tone, timing and the details clients notice.
- The reference example: one real, completed version to copy from.
- The why: what this piece of work does for the client.
Try this
Could someone do this work on a Monday morning without messaging you? If the answer is no, the missing piece is almost always context.
3. The decision rights
Capable people play it safe when they don't know where the line is. They ask about everything, because asking feels more respectful than guessing.
Decision rights give them the line. For each handoff, write three short lists:
- Decide: choices the owner makes alone.
- Decide and tell me: choices they make, then mention in the weekly review.
- Ask first: choices that need your approval before anything happens.
Take a client asking to move a session at short notice. Can your assistant agree on the spot, offer two alternatives, or does it come to you? Each answer is fine. Having no answer is what sends the message to your phone.
Keep the “ask first” list as short as you can comfortably live with. Every item on it is a moment where work waits for you.
4. The blocked path
Every process gets stuck sometimes. A client goes quiet, a document is missing, a supplier is late. The question is where the stuck work goes, and in most businesses the answer is the founder's inbox.
The blocked path decides this in advance. It covers how long to wait before acting, who to ask other than you, what to tell the client in the meantime, and the point at which it really does need you.
Say a new client hasn't returned their intake form after four days. A written blocked path might read: send a friendly reminder on day three, a second on day five with a direct link, and raise it in the weekly review if there is still nothing. Nobody needs to interrupt you, and the client still feels followed up.
How to tell if a handoff holds
For the next two weeks, keep a short note every time a handed-off task comes back to you. Next to each one, write which of the four parts was missing: the owner, the context, the decision rights or the blocked path.
Within a fortnight a pattern appears, and it usually points to a single part. That is the one to build first.
What changes when handoffs hold
You still lead. You still set the standard, make the important calls and stay close to your clients. What changes is that you stop being the only place the information lives, so the people around you can carry the work all the way to done.
Start with one recurring task, the one that comes back to you most often, and build its four parts this week.
