Delegation: What to Delegate 

A practical UK manager’s guide to freeing up time, building capability and avoiding rework

Delegation sounds simple: give someone a task and get it off your plate. Yet most delegation fails for predictable reasons. Managers delegate the wrong things, delegate too late or delegate without enough clarity. The work then comes back half-finished, quality drops, the manager feels they would have been quicker doing it themselves, and the team feels dumped on. After a few cycles, everyone becomes reluctant: the manager hoards work, and the team stops stretching.

Done well, delegation is one of the most powerful leadership skills you can develop. It frees up time for higher-value work, reduces burnout and creates a team that can deliver without you becoming the bottleneck. It also improves retention, because people grow faster when they are trusted with meaningful work and supported to succeed. In UK workplaces, effective delegation also supports fairness and wellbeing by balancing workload and giving people clear ownership, reducing the stress caused by ambiguity and constant firefighting.

This guide is designed for UK managers, team leaders and business owners who want a repeatable framework for delegation. You will learn what to delegate, what not to delegate, how to assess risk and complexity, how to match work to skill level, how to set outcomes and boundaries, and how to follow up without micromanaging. You will also get checklists, examples and copy-and-use templates so you can put these ideas into practice immediately – even when you are under pressure.

What to Delegate as a Manager

The easiest way to decide what to delegate is to stop thinking in terms of ‘tasks I do’ and start thinking in terms of ‘value only I can add’.

As the manager or business owner, you should keep work that genuinely requires your authority, judgement or relationships. Everything else is a candidate for delegation, automation or removal. Delegation is not just about reducing your workload. It is also about moving decisions and ownership closer to the work so that delivery becomes faster and more effective.

A practical framework is to sort your work into four buckets:

1. High value, only you can do it (Keep)
2. High value, someone else could do it with support (Delegate to develop)
3. Low value, someone else can do it (Delegate to deliver)
4. Low value, nobody should do it (Stop or automate)

Here are some common examples of tasks to delegate as a manager:

• Routine reporting that follows a template and can be reviewed quickly.
• First drafts of documents, slides, policies, meeting agendas and communications.
• Data gathering, preparation for analysis, and extracting insights from dashboards.
• Project coordination, including chasing actions and maintaining a plan.
• Customer or stakeholder updates that are structured and repeatable.
• Admin-heavy tasks that support a core decision you will make later.
• Quality checks using a checklist, where the criteria are clear.
• Process improvements owned by the people who work with the process every day.

A useful question is: “If I was off sick for two weeks, what would still need to happen?” Those activities are often the best delegation candidates, because they are both essential and repeatable.

Another strong prompt: “What am I doing that a capable person could do at 80% quality with the right brief?” If the answer is “a lot”, the issue is usually not capability. It is clarity, support and coaching.

You may find it helpful to align your delegation mindset with established management guidance such as the CIPD resources on people management and practical leadership tips like Harvard Business Review’s delegation articles.

What Not to Delegate

Some things should stay with you, at least until you intentionally transfer them. Not because you are indispensable, but because the risk, ethical considerations, legal responsibility or strategic judgement must remain with the role holder.

What not to delegate usually falls into a few categories:

1) Work that requires your formal authority

For example, final sign-off on budgets, pay decisions, disciplinary outcomes, contractual commitments or high-stakes risk acceptance. You can delegate preparation and recommendations, but the final decision should remain with you.

2) Sensitive people decisions and duty of care

You should not delegate the human responsibility of handling grievances, safeguarding issues, serious wellbeing concerns or protected disclosures to someone who lacks the appropriate training and authority. You can involve HR and specialists, but do not ‘hand off’ accountability.

3) Core leadership responsibilities

You cannot delegate your role as leader. That includes setting direction, building culture, removing systemic blockers, and ensuring the team has clear priorities and sufficient resources. You can share elements of the work, but you cannot outsource ownership.

4) Work where the relationship is the value

Certain stakeholder conversations need your credibility and trust. You can delegate follow-ups, preparation and delivery of agreed messages. However, key relationship-building conversations may need to remain with you.

5) Work that will create confusion if split

Some tasks require one person to hold the context. If dividing the work creates more coordination effort than the task itself, keep it, simplify it or redesign the process before delegating.

A simple ‘do not delegate’ test is: “If this goes wrong, would it be unfair to the person I delegated it to?” If the answer is yes, keep it or redesign it.

Delegation vs Dumping Work

Delegation and dumping can look identical from the outside. Both involve giving work to someone else. The difference lies in what happens next.

Delegation transfers ownership with clear expectations, appropriate support and authority matched to responsibility.
Dumping transfers tasks without context, support and often the authority needed to succeed.

People can tell the difference instantly. Dumping feels like someone is offloading a problem. Delegation feels like being trusted with meaningful ownership and an opportunity to grow.

Here are the signals:

Signs you are delegating (the good kind)

• You explain why it matters and how it connects to outcomes.
• You define what ‘done’ looks like and set clear quality standards.
• You clarify boundaries, risks and decision-making authority.
• You check capacity and agree priorities.
• You schedule support and feedback loops.

Signs you are dumping (the kind that creates rework)

• You send a vague message such as “Can you sort this?”
• You delegate work only when it is already late, urgent or disorganised.
• You do not share the relevant context, stakeholders or constraints.
• You give responsibility without authority.
• You disappear and then criticise the outcome.

If you want a quick way to self-check, ask yourself: “Would I feel set up to succeed if I received this task?” If not, rewrite the brief.

For practical guidance on healthy workloads and avoiding burnout patterns, resources such as Acas advice on workplace wellbeing can support your wider management approach.

Delegation Levels: Tell, Sell, Consult

One reason delegation fails is that managers use the same approach for every task. In reality, different types of work require different levels of direction. A useful model is to choose your delegation level intentionally.

Here is a simple three-level structure that works well in busy teams:

Tell

You decide the approach and the outcome. The other person carries out the work.
Use this when: risk is high, time is tight or the person is new to the task.
What you provide: step-by-step guidance, a checklist and regular review points.
Your mindset: “I am building confidence and preventing avoidable mistakes.”

Sell

You decide the outcome and propose the approach, but you invite questions and adjustments.
Use this when: you want buy-in, or the person has some experience but still needs alignment.
What you provide: the why, the constraints and room for the person to refine the plan.
Your mindset: “I am creating ownership while protecting quality.”

Consult

You define the outcome and constraints, then ask the other person to propose the approach. You agree the plan together before work begins.
Use this when: the person has relevant expertise or the work would benefit from their perspective.
What you provide: success criteria, boundaries and stakeholder context.
Your mindset: “I want their best thinking, and I will support them to deliver.”

A key point is that delegation levels are not determined by seniority. They are determined by the level of risk, the novelty of the task and the person’s experience with that type of work. The same person might be at the ‘consult’ level for a technical problem and the ‘tell’ level for a new compliance process.

If you want to go deeper into decision-making styles and empowerment, CIPD guidance on leadership and management can be a useful reference.

How to Choose the Right Person

Choosing the right person is less about who is ‘free’ and more about who is the best match for the work right now. In UK teams, capacity is often tight, so you need a realistic approach that balances delivery with development.

Use these five factors:

1) Skills and experience

Do they have the core skills needed? If not, can the gap be covered by training, pairing or clearer templates?

2) Interest and motivation

People deliver better work when they care. Interest is not the only factor, but it can improve quality and speed.

3) Capacity and competing priorities

Delegation that ignores capacity can quickly create frustration and resentment. Check workloads honestly and, where necessary, renegotiate priorities before assigning additional work.

4) Risk tolerance and impact

High-risk tasks should be assigned to someone with either relevant experience or the support, guidance and review points needed to succeed.

5) Development value

Ask yourself: “Will this task build a skill they need for the next step in their role?” If yes, it may be worth investing additional time in more support.

A practical way to match tasks to people is to use a simple risk-and-complexity rating:

• Low risk, low complexity: delegate widely and focus on speed and confidence.
• High risk, low complexity: delegate with clear standards and regular review.
• Low risk, high complexity: delegate to develop and provide coaching.
• High risk, high complexity: delegate carefully, often with consultation, pairing and staged sign-off.

Also consider equity. If the same person always gets the admin, they will not develop. Rotate opportunities where possible. Make the invisible work visible, and distribute it fairly across the team.

For a helpful mindset shift on matching tasks to growth, you may like MindTools guidance on delegation as a practical reference point.

Delegation Checklist for Managers

Use this checklist before you delegate anything that matters. It takes two minutes, and it prevents the most common failure modes.

• Purpose: Why does this work matter now?
• Outcome: What does ‘done’ look like in one sentence?
• Quality bar: What standards must be met?
• Scope: What is included and what is not included?
• Constraints: Budget, tools, approvals, legal or policy limits.
• Stakeholders: Who needs to be informed or consulted?
• Decision rights: What can they decide without you?
• Timeline: When is it due, and what are the key milestones?
• Resources: What templates, examples, data or access do they need?
• Check-ins: When will you review progress and unblock?
• Risks: What could go wrong and how will you catch it early?

If you can’t answer these quickly, you are not ready to delegate that task yet. That does not mean you must keep it. It means you need to do a clearer brief first.

Setting Clear Outcomes and Deadlines

Clarity is the difference between delegation that saves time and delegation that creates rework. The goal is to define outcomes without prescribing every step.

Start with an outcome statement:

• “By Friday 4pm, produce a one-page summary of X with three options and your recommendation.”

That sentence gives a deadline, a deliverable and a decision shape. It also makes it easier to review.

Then add two more elements:

1) Definition of done

What does success look like? For example:

• “Includes key risks, cost estimate and implementation steps.”
• “Written for a non-technical audience.”
• “Uses the attached template and is under 600 words.”

2) Boundaries

What should they not do? For example:

• “Do not contact the client directly without me.”
• “Do not commit to a vendor, but you can request quotes.”
• “Do not change the timeline without flagging it.”

Deadlines should also be realistic. If you delegate something late, you force shortcuts. A better approach is to delegate earlier and set milestone check-ins:

• Draft by Tuesday
• Review on Wednesday
• Final by Friday

Milestones reduce risk without micromanaging. They also help the person plan their week.

If you want a recognised approach to defining deliverables and scope, you might find PRINCE2 project principles useful for thinking about outputs, tolerances and governance, even outside formal project roles.

Delegating Without Micromanaging

Micromanagement usually starts with fear: fear of mistakes, fear of being judged, fear of deadlines slipping. The solution is not to let go completely. The solution is to build a smart control system that protects quality while protecting autonomy.

Here are practical ways to do that:

Agree the ‘how’ at the right level

You do not need to control every step. You need to control risk points. So agree:

• The first step.
• The milestone check-ins.
• The final review.

Use ‘show me early’ check-ins

Ask for an early draft or outline. It is easier to course-correct at 20% than at 90%. This also reduces anxiety for both of you.

Focus on principles, not personal style

If the output meets the standard, let it be done their way. People need room to develop their own approach.

Ask questions instead of rewriting

When you see issues, try:

• “What options did you consider?”
• “What evidence supports this?”
• “What would you do if the deadline moved forward?”

This builds capability rather than dependency.

Separate coaching from control

Coaching sounds like: “Here is what I would improve and why.”
Control sounds like: “Do it exactly like me.”
If you want people to grow, coach.

A useful target: if you are rewriting more than 20% of delegated work regularly, the issue is usually briefing, training or mismatched delegation level, not the person.

How to Delegate When You’re Busy

The irony of delegation is that it takes time upfront. When you are busy, you feel you do not have time to delegate. Then you stay busy forever. The way out is to delegate in a lighter, faster format while still protecting clarity.

Try these approaches when you are under pressure:

Use a 5-minute delegation brief

Send a short message that covers:

• Outcome
• Deadline
• First step
• Check-in time
• Where the resources are

Delegate ‘drafts’ not ‘finals’

When time is tight, delegate the first draft. Then you do a quick review. This saves time without handing over full risk.

Delegate decision prep

Ask someone to bring options, data and a recommendation. You keep the final decision, but you remove the heavy lifting.

Time-box your own support

Instead of being available all day, schedule a 15-minute slot for questions. This prevents constant interruptions.

Use templates and examples

Busy delegation works when you provide patterns. A good example document can save an hour of explanation.

If you struggle with constant interruptions, consider team agreements that protect focus, similar to the work practices encouraged in The UK Health and Safety Executive stress guidance which highlights how workload and demands can affect wellbeing. A meeting culture and workload culture are closely linked.

Delegating Tasks to Develop Skills

Delegation is one of the best development tools you have, if you use it intentionally. The trick is to choose tasks that stretch someone slightly beyond their comfort zone, then provide enough support so they succeed.

To delegate for development:

Pick a skill, then pick a task

For example:

• If they need stakeholder management, delegate a structured update meeting with a clear script.
• If they need planning skills, delegate ownership of a small project plan.
• If they need decision-making, delegate an options paper and recommendation.
• If they need confidence, delegate a low-risk ownership role that is visible.

Make learning part of the brief

Say it openly:

• “I’m delegating this because it will help you build X skill.”

This reframes the task from ‘extra work’ to ‘growth opportunity’.

Increase autonomy over time

Move through delegation levels:

• Tell for the first run.
• Sell for the second.
• Consult for the third.

This creates a clear progression, which also motivates people.

Use feedback loops that teach

After the task, do a short debrief:

• What went well?
• What was harder than expected?
• What would you do differently next time?
• What support would help next time?

This kind of debrief builds reflection skills and reduces repeat mistakes.

For managers building coaching habits, CIPD coaching and mentoring resources can help you structure development conversations.

Delegation Examples for Team Leaders

Examples help because delegation can feel abstract. Below are realistic scenarios team leaders and managers face, with what good delegation looks like.

Example 1: Delegating a recurring report

You currently spend two hours a week building a report.

Good delegation:

• Outcome: “Publish the weekly performance report by 10am Monday using the template.”
• Quality bar: “Data must match dashboard totals, and insights must include three key changes.”
• Support: Provide last month’s reports as examples.
• Check-in: Review together after the first two weeks, then monthly.

Why it works: repeatable task, clear standards and early quality checks.

Example 2: Delegating meeting facilitation

Meetings drift and you want the team to own structure.

Good delegation:

• Outcome: “Facilitate Tuesday’s team meeting and send notes within 2 hours.”
• Scope: Use the agenda template, focus on decisions and actions.
• Decision rights: They can time-box discussion and park topics.
• Support: You attend but do not chair. You give feedback afterwards.

Why it works: builds facilitation skills and improves team accountability.

Example 3: Delegating stakeholder updates

You are the default contact, but you want resilience.

Good delegation:

• Outcome: “Send the fortnightly stakeholder update using the agreed format.”
• Boundaries: “Do not commit to new scope. Escalate new requests to me.”
• Support: Provide key messages and a list of risks.
• Check-in: Review first two updates before they go out.

Why it works: transfers ownership while managing risk.

Example 4: Delegating process improvement

A process causes delays, and you are tempted to fix it yourself.

Good delegation:

• Outcome: “Map the current process, identify top three bottlenecks, propose fixes.”
• Timeline: “Two weeks, with a draft map by Friday.”
• Stakeholders: “Talk to X and Y. I will introduce you.”
• Decision method: “Bring options and recommendations to me.”

Why it works: the people closest to the process find the real friction, and you retain decision authority.

Common Delegation Mistakes to Avoid

Most delegation mistakes come from predictable habits. Avoid these and your delegation success rate will rise quickly.

• Delegating too late: You hand over a problem at crisis point, so there is no time to do it properly.
• Delegating without context: The person does not know why it matters, so they optimise for the wrong thing.
• Unclear quality standards: You expect ‘good’, they deliver ‘done’, and both feel frustrated.
• Giving responsibility without authority: They get blamed for outcomes they cannot control.
• Ignoring capacity: You create overload, and quality drops everywhere.
• No check-ins: You only discover issues near the deadline.
• Taking work back too early: You rescue too fast, which trains dependency.
• Criticising style instead of outcomes: You rewrite because it is not ‘your way’.
• Delegating only the dull tasks: The team does not develop, and motivation drops.

A quick corrective habit is to ask, every time you delegate: “What is the failure mode here, and how will we catch it early?” Then design your check-ins around that.

How to Follow Up on Delegated Work

Follow-up is where delegation becomes reliable. Without follow-up, you get surprises. With too much follow-up, you get micromanagement. The goal is a rhythm that protects quality and builds independence.

Use a three-part follow-up system:

1) Early alignment

Within the first 10-20% of the work, check:

• Are we solving the right problem?
• Is the approach sensible?
• Do you have what you need?

This is your best chance to prevent rework.

2) Midpoint check

Halfway through, check:

• What is done?
• What is blocked?
• Do priorities still hold?
• Is quality on track?

This is where you remove blockers and prevent last-minute panic.

3) Final review and debrief

At the end:

• Review output against the definition of done.
• Confirm what happens next.
• Debrief for learning, especially if it was a development task.

Keep follow-ups short and structured. Ask for evidence, not reassurance. For example:

• “Show me the outline and your recommendation.”
• “What are the top two risks?”
• “What decision do you need from me?”

If you want a simple way to document and track, a shared action list works well. For teams that prefer more structure, you can use a lightweight responsibility model such as a RACI chart. Guidance on responsibility mapping can be found in many project resources, including Project Management Institute content.

Delegation Tools and Templates

Tools and templates are useful because they reduce the mental load of delegation. You do not need a fancy system. You need repeatable patterns.

Below are practical templates you can copy into a document, email or task tool.

1) The one-page delegation brief template

Task title:
Why it matters:
Outcome (one sentence):
Deadline:
Definition of done:
Scope (in / out):
Constraints (budget, policy, approvals):
Stakeholders to consult:
Decision rights (what you can decide):
Resources (links, templates, examples):
Risks to watch:
Check-ins (dates):

This template prevents vague delegation. It also makes handover smoother if someone else needs to step in.

2) The ‘definition of done’ mini-template

Use this when quality issues keep appearing.

• Must include:
• Must not include:
• Format:
• Audience:
• Evidence required:
• Sign-off needed:

3) The milestone check-in template

• By (date): deliver (milestone)
• Review with: (name)
• Risks to confirm:
• Decisions needed:

4) The delegation agreement script

This is a short conversation format:

• “Here is what we need and why.”
• “Here is what done looks like.”
• “Here is what you can decide without me.”
• “Here are the constraints.”
• “What questions do you have?”
• “What support would help?”
• “When should we check in?”

5) A simple delegation tracker

In any spreadsheet or task board, track:

• Task
• Owner
• Deadline
• Status
• Next check-in
• Blockers
• Decision needed from manager (yes/no)

Even a basic tracker reduces the need for constant chasing.

6) Recommended tools that support delegation

The ‘best’ tool is the one your team will actually use consistently. Useful categories include:

• Task boards for visibility.
• Shared documents for briefs and notes.
• Calendar blocks for check-ins.
• Templates for recurring work.

If your team needs help writing clearer briefs and standards, you may also like the Plain English Campaign guidance to reduce ambiguity and misunderstandings in written delegation.

Conclusion

Delegation is not a single act. It is a system. When you delegate the right work, at the right level, to the right person, with clear outcomes and sensible follow-up, you reduce rework and build a team that can deliver without you becoming the bottleneck.

The practical shift is to delegate earlier, with clearer briefs, and schedule check-ins around genuine risk points rather than anxiety. That is how you avoid micromanagement while still protecting quality. Over time, delegation becomes a repeatable management skill: you free up time for higher-value work, your team develops capability and confidence, and delivery becomes smoother and less stressful.

If you take just one action this week, make it this: pick one recurring task that you do every week, write a one-page delegation brief for it, and delegate it with a first-draft milestone. Once you see the time saved and the capability built, delegation stops feeling like extra work and starts feeling like leadership.