Delegation of Authority: What to Hand Over and What to Keep
Delegation of authority is about decision rights, not tasks. Here is how to set limits, avoid the two common failure modes, and build leadership evidence.
Delegation of authority is the formal transfer of decision rights from one role to another: who may approve what, up to which amount, under which conditions. It is different from delegating work. Handing someone a task while keeping every decision is not delegation, it is queueing.
For anyone moving from managing work to leading an organisation, this is the transition that decides whether the step succeeds.
Tasks, decisions and answers
Three things can move, and they move separately.
| What moves | Can be delegated | Effect if you keep it |
|---|---|---|
| The task | Yes | You stay the bottleneck on capacity |
| The decision | Yes, within limits | You stay the bottleneck on speed |
| The accountability | No | You remain answerable, correctly |
You remain answerable for outcomes in your area even after you delegate the decisions that produce them. That is not a reason to withhold authority. It is a reason to define its limits carefully.
What a delegation of authority framework contains
Companies formalise this in a schedule or matrix. A workable version answers four questions for every category of decision:
- What type of decision is this: spend, hiring, pricing, contractual commitment, technical standard, customer concession.
- What is the threshold, expressed as an amount, duration or risk level.
- Who decides at each threshold, named by role rather than person.
- What must be reported afterwards, and to whom.
A short worked example for a mid sized operations function:
| Decision | Team lead | Manager | Director |
|---|---|---|---|
| Operational spend | Up to 2,000 euro | Up to 25,000 euro | Up to 250,000 euro |
| Hiring within approved plan | Recommend | Decide | Decide |
| New role outside plan | No | Recommend | Decide |
| Customer concession | Up to 1,000 euro | Up to 10,000 euro | Above 10,000 euro |
| Supplier contract length | No | Up to 12 months | Up to 36 months |
The specific numbers matter less than the fact that they exist and everyone knows them. Ambiguous authority is slower than restrictive authority, because people wait rather than risk overstepping.
The two failure modes
Under delegation. Decision rights stay with you, so every non routine choice waits for your calendar. The visible symptoms are a growing approval queue, people who stop bringing options and start bringing questions, and a manager who is busy but cannot describe the strategy they advanced this quarter. The hidden cost is that nobody below you builds a record of decisions, which means nobody is ready to be promoted.
Abdication. Authority is transferred without limits, information or follow up. The symptom is discovering commitments after they were made. Abdication is usually mistaken for trust and is corrected with a sharp recentralisation, which damages the people who did it well.
The distinction between delegation and abdication is not how much you hand over. It is whether the limits, the reporting and the review are explicit.
How to delegate authority in practice
- Delegate by decision category, not by case. Deciding one purchase for someone teaches nothing. Giving them the purchase category up to a threshold changes how they work.
- Set the threshold where a mistake is survivable. Then raise it once you have seen three decisions you agree with.
- Ask for the reasoning, not the answer. When someone brings a decision, ask what they would do and why. If the reasoning is sound, the answer is theirs.
- Write it down. One page listing categories, thresholds and reporting removes most of the hesitation.
- Review quarterly. Thresholds that never move signal that the delegation was ceremonial.
Keep the decisions that define direction
Some decisions should not move. As a rule, keep those that set direction or are hard to reverse:
- Which problems the team works on, and in which order.
- Who joins the team and who leaves it.
- Commitments that bind the organisation beyond your planning horizon.
- Anything that changes a standard other teams rely on.
Everything else is a candidate for delegation, and the default answer should be yes.
Why this belongs on your CV
Delegation of authority is one of the clearest signals of level, and almost nobody writes it down. Stating the authority you hold, and the authority you granted, answers the scope question immediately.
Led a team of eleven and managed the department budget.
Held sign off on operational spend to 250,000 euro and supplier contracts to 36 months, and delegated purchase authority to four team leads, cutting average approval time from nine days to under two.
The second version shows a leader who both holds authority and distributes it. That combination is exactly what selection panels for director level roles are looking for.
The short version
Delegate decisions, not just tasks. Set explicit thresholds, keep the direction setting and irreversible calls, and review the limits every quarter. Then make the authority you hold visible, because it is the fastest way to show the level you operate at.
If you want to know how visible your decision rights are in your current CV, the CareerSynth Career Direction Preview reads your document and tells you what a hiring committee can and cannot see.
