Delegating without losing control

Many leaders know they should delegate more and still hold on. Usually the worry is reasonable: the last time you handed something off, it came back wrong, late, or not at all. The answer is a better handoff, not doing everything yourself. Good delegation is a skill with a few specific parts, and once you have them, you can hand off real work and still sleep at night.

Why delegation goes wrong

It usually fails in one of a few predictable ways:

The outcome was unclear. You knew what you wanted; they did not.
The authority was unclear. They did not know whether they could make a call, so they either waited or guessed.
There was no check-in. You only found out about the problem at the deadline.
You took it back. At the first wobble, you jumped in and did it yourself, so they never learned.
You delegated tasks, not responsibility. You handed over steps one at a time, so you stayed the bottleneck.

Each of these has a fix.

The five parts of a good handoff

Check your handoff covers all five

0 of 5 done

The outcome. Describe the result, not just the activity. "Get the new hire set up so they can start work on Monday" is better than "Create an email account."
The context. Why does this matter? Who is it for? What happened last time? Context lets people make good choices when something unexpected comes up.
What done looks like. Be specific. A one-page summary? A booked meeting? A published page? If quality matters, show an example of good.
The deadline and check-ins. Give a real date. For anything that takes more than a few days, agree on one or two check-in points: "Show me the outline on Tuesday before you write the full thing."
The level of authority. Say clearly how much they can decide on their own. See the levels below.

Saved in this browser only.

Levels of authority

One of the most useful things you can do is name the level of authority for each piece of work. A simple scale:

Level	What it means	Good for
1. Look into it and report back	Gather information. I decide.	New, high-stakes or unfamiliar work
2. Recommend	Give me options and your recommendation. I decide.	Decisions with real cost or risk
3. Decide, but check with me first	Make the call, tell me before you act.	Building trust on medium-stakes work
4. Act, then tell me	Go ahead, and let me know what you did.	Routine work where you want visibility
5. Act on your own	Fully yours. No need to report each time.	Routine work the person has mastered

Most work should move up this scale over time. If you keep everything at levels 1 and 2 forever, you are still doing the deciding, and you will still be the bottleneck.

Staying in control without hovering

Control comes from visibility, not from doing it yourself. A few light tools:

A "waiting on" list. Every time you delegate something, write it down with the person and date. Review it weekly. See Running your week.
Agreed check-ins. Set them when you hand over, so asking for an update is expected, not a sign of distrust.
A shared task tool. If your team uses a project tool, delegated work lives there with a status, so you can see progress without asking.
Written processes. For recurring work, a short written process means you only explain it once. See the operations guide on writing SOPs.

When it comes back wrong

It will, especially at first. Before you take it back:

Check your handoff. Was the outcome, context and "done" clear? Often the gap is in the instructions.
Give specific feedback. "The summary is good. It needs a recommendation at the top, and the numbers need sources." Specific feedback is much more useful than "this isn't quite right."
Let them fix it. If you redo it yourself, they learn that you will always step in.
Update the instructions so the next handoff is clearer.

There are times to take work back: a real deadline with real consequences, or a client relationship at risk. When you do, say why, and plan how they will handle it next time.

What not to delegate

Some things should stay with you, or need a very careful approach:

Decisions that set direction for the business
Key relationships that rely on you personally
Confidential people matters, like pay or performance
Final approval on money moving out of the business

You can still delegate the preparation for most of these. Someone else can gather the data, draft the options and set up the meeting, while you make the call.

Delegating to assistants and AI

The same principles apply whether you delegate to a team member, a virtual assistant or an AI tool. AI tools need even clearer instructions and context, and their output always needs a human check. See Hiring a virtual assistant and Working with a VA and AI together.

A quick delegation template

Copy this into a message or task when you hand something off:

Outcome: [what result you want] Why it matters: [context] Done looks like: [specific deliverable] Deadline: [date] | Check-in: [date] Your authority: [level 1 to 5] Resources: [links, people, budget]

Common mistakes

Delegating only the boring bits. People grow by owning things. Give them some meaningful work.
Vague deadlines. "When you get a chance" means "never" on a busy team.
Changing the brief without saying so. If your thinking moves, tell them.
Asking for updates at random. Agree on check-ins up front instead.