Spending Hours You Haven't Got: A Framework for Handing Work Over Without Losing Control

The standard advice is to delegate more. It is offered to managers who are already working a fifty-hour week, in organisations where nobody is sitting idle, and it is heard — correctly — as a suggestion to create time by spending time. What is missing is any account of the cost.

Handover is not free. A task given to someone else typically consumes between a fifth and a third of its original duration in explanation, checking and correction before it runs independently. For a manager with no slack, that upfront cost arrives in the same week as everything else. Which is why the useful question is not 'what should I delegate?' but 'what can I afford to hand over this month, and what is the cheapest safe way to do it?'

Delegation as a budget line

Treat delegation the way you would treat any other finite resource. Each week has a fixed number of working hours. Some are committed to meetings, some to work only you can do, and a residual amount is available for handover. That residual is the delegation budget. It is usually smaller than managers assume, and it is almost never written down.

Writing it down changes the conversation. Instead of a vague intention to be better at letting go, you get an allocation decision with a visible cost — and an obvious reason to be selective.

Step one: calculate the delegable hours

Start with the tasks, not the people. List everything you did last week that someone else could, in principle, do. Be strict about 'in principle': if it requires your signature, your relationships or your judgement in a regulatory sense, it is not delegable this quarter.

Then estimate the weekly hours each item consumes. Most managers find that the genuinely delegable total is between eight and fifteen hours — larger than expected, and considerably more than they could hand over at once.

The gap between the two figures is the point. You have identified a reservoir, not a plan. The reservoir is what you draw from over months, at a rate the budget can bear.

Step two: sort the work into risk tiers

Not all handovers carry the same exposure. A three-tier sort is usually sufficient.

• Tier one — reversible. If it goes wrong, it can be corrected within a day and nobody outside the team notices. Formatting, scheduling, routine drafting, standard reporting.
• Tier two — costly but recoverable. An error costs money, time or a client relationship, but can be repaired. Supplier correspondence, first-draft client documents, data reconciliation.
• Tier three — irreversible or reputationally exposed. Statutory filings, contractual commitments, anything said to a regulator, anything that cannot be unsaid.

The tiers determine the pace. Tier one work can be handed over with a written note and a single review. Tier two needs a short shadowing period and a checkpoint. Tier three is usually not delegated at all — it is shared, escalated or retained, and pretending otherwise is how small organisations get into difficulty.

Step three: price the handover

For each task you intend to move, estimate the handover cost in hours: explanation, first attempt review, second attempt review, plus a margin for the questions that arrive in between. A reasonable rule of thumb is 25 per cent of the task's monthly hours, spent in the first month only.

A task consuming four hours a week therefore costs roughly four hours to hand over in month one, then returns three to four hours a week thereafter. That is a good trade — but only if the budget exists in the month you make it.

The hand-back rule

This is the mechanism that keeps delegation from quietly reversing itself. It is short and it should be stated to the team in advance.

If the same question comes back twice, it is not a delegation failure. It is a gap in the brief.

On the third occurrence, the answer is not to take the task back. It is to write the answer down — one page, added to the handover note — and point the person to it. Taking work back on the second or third interruption feels efficient and is the single most common reason delegation does not stick. The task returns, the manager concludes that delegation does not work here, and nothing changes.

There is a parallel rule for genuine tier-three escalations, which must always be answered immediately and without penalty. The distinction has to be explicit, or the hand-back rule reads as a refusal to help.

A worked example

A team leader in a twelve-person business oversees four staff and a weekly reporting cycle. Of a fifty-hour week, roughly eleven hours are delegable: two hours of routine reporting, three hours of scheduling and coordination, four hours of first-draft correspondence and two hours of data checking.

The budget allows around six hours of handover time in any given month. In month one, they move the scheduling and the reporting — seven weekly hours — at a cost of about seven hours of explanation and review. Month two is spent consolidating rather than adding. Month three takes the correspondence. The data checking stays with them until the quarter closes.

By the end of the quarter, roughly nine hours a week have moved. That is not a transformation; it is a durable reallocation achieved without a crisis.

The trade-offs, stated plainly

This framework has real costs and it is dishonest to present it otherwise.

First, the first month is worse before it is better. Errors made by someone learning will land on your desk, and they will arrive at inconvenient times.

Second, the standard of a delegated task will initially be lower than yours. If the work is client-facing, that may be unacceptable for a period, which is an argument for starting with tier one rather than against the approach.

Third, some of what you hand over you will do better. That is not a reason to keep it. The relevant test is whether it is good enough and repeatable, not whether it is best-in-class.

Finally, in organisations with no cover, illness and resignation will occasionally undo a handover overnight. That risk exists whether or not you delegate; the difference is that a documented handover is recoverable and an undocumented one is not.

Reviewing the budget

Put twenty minutes in the diary at the end of each month. Three questions: what moved, what came back, and what is the budget for next month. A task that has come back twice without a documented answer is a signal to rewrite the brief rather than to reclaim the work.

Delegation done this way is unglamorous and slow. It is also the only version that survives contact with a busy November in a business where nobody has spare capacity to lend.