Operations Analysis

How to Hand Over Work Without It Coming Back

D
Author
DOMS Global LLP
Published
December 24, 2025
Read Time
6 min read
How to Hand Over Work Without It Coming Back

You handed it over in January. By March you were back to reviewing it, and by June you had taken it back entirely, telling yourself it was faster to do it yourself.

Which is true, on any given day, and completely false across a year. But the daily version is the one that decides, because the daily version is the one under pressure.

Delegation fails at handover, not at execution

When work comes back, the assumption is that the person could not do it. Usually the handover was incomplete in a specific and predictable way.

Handing over a task means transferring four separate things, and most handovers transfer only the first:

  1. 1.The task. What needs doing. Almost always communicated.
  2. 2.The standard. What good looks like, specifically enough to be checked. Rarely stated.
  3. 3.The authority. What they may decide alone, and what needs you. Almost never stated.
  4. 4.The context. Why it matters and what happens downstream if it slips. Almost never stated.

Without the standard, they cannot tell whether they have succeeded. Without the authority, they must check with you constantly, which feels to you like they cannot do it. Without the context, they cannot make sensible judgement calls when reality deviates from the instruction.

You did not delegate a task. You lent it, with the conditions unstated, and then judged the result against a standard the other person could not see.

Write the handover down, once

It does not need to be long. Half a page per task, covering:

  • The outcome, in a measurable form.
  • What good looks like, with an example of an acceptable result and an unacceptable one.
  • The decisions they own outright.
  • The decisions that need you, and how quickly you will respond.
  • What to do when something unexpected happens.
  • When you will review it, and what you will look at.

The example pair does more work than any description. People calibrate from examples far more reliably than from adjectives.

Then let it be done worse than you would do it

This is the actual barrier, and it is emotional rather than operational.

A competent person doing a task for the first month will produce something noticeably worse than you would. If your threshold for intervention is anything below your own standard, you will take back every task you ever delegate, permanently, and conclude that you cannot find good people.

Set the bar at good enough rather than at your level, and hold it there for a defined period. Most tasks reach your standard by month three if you allow the gap to exist in month one.

Review the process, not the output

The instinct is to check the work. Checking the work teaches them that you will check the work, so they stop checking it themselves.

Review the process instead. Ask what they did, what they decided, where they hesitated, and what they would change. That conversation improves capability. Correcting the output only improves the output, and only once.

When it genuinely does come back

Sometimes work returns because it was the wrong handover, not a failed one. Before trying again, ask honestly:

  • Did they have the authority to do it without me?
  • Did they have the time, or was it added to a full workload?
  • Did they have the information, or is it in my head?
  • Was the standard stated, or assumed?
  • Did I intervene early enough that they never actually owned it?

That last one is the most common. Work handed over and then supervised closely was never handed over. It was supervised, and the person knew it.

Why this is the highest-return thing you will do

A business where the owner is the routing layer for decisions cannot scale, cannot be valued properly and cannot function during a holiday. Every task successfully transferred raises the ceiling.

It is also the direct route out of the pattern described in the business that cannot run without you, and it works alongside the SOP thinking in why your SOPs get ignored.

If you want to see how concentrated your business currently is around one person, the free operations diagnostic measures ownership and handoffs directly, and gives you a score in about four minutes.

Frequently asked questions

Why does delegated work keep coming back?

Because handover usually transfers only the task itself and omits three other things: the standard, so the person cannot tell whether they have succeeded; the authority, so they must keep checking with you; and the context, so they cannot make sensible judgements when reality deviates from the instruction.

What should a written handover contain?

The outcome in measurable form, what good looks like with an example of an acceptable and an unacceptable result, the decisions the person owns outright, the decisions that need you and how fast you will respond, what to do when something unexpected happens, and when you will review it.

How good should delegated work be at the start?

Noticeably worse than you would do it. If your threshold for intervention is anything below your own standard, you will take back every task you delegate and conclude you cannot find good people. Set the bar at good enough for a defined period; most tasks reach your standard by month three.

Should you review the work or the process?

The process. Checking the output teaches people that you will check it, so they stop checking it themselves. Asking what they did, what they decided, where they hesitated and what they would change builds capability, whereas correcting the output improves only that one piece of work.

delegation for foundershandover processbusiness owner time managementaccountability systemsoperations consulting

Recognise any of this
in your business?

Most of what we write about started as a problem someone brought to us. If something here sounded familiar, a conversation costs nothing and usually makes the constraint obvious.