Published September 23, 2026
Published September 23, 2026.
Delegation is not a single switch. Handing over a task can mean anything from "prepare a draft for my review" to "own this completely and tell me if something is wrong." When that distinction stays unspoken, both sides guess, and the result is either excessive checking or an avoidable mistake. Using explicit delegation levels removes the guesswork. Each task gets a level, the level is written down, and both people know what is expected before the work starts.
This guide defines a practical set of levels and explains how to move a task from one level to the next.
Why levels beat a vague handoff
A vague handoff forces the assistant to infer authority from context. They may under-act to be safe, which slows everything down, or over-act to be helpful, which creates risk. Levels make the boundary explicit and reviewable. They also give you a way to increase ownership gradually as trust builds, instead of granting full authority on day one or withholding it forever.
A five-level model
The following levels cover most delegated work. Each increases the assistant's authority and decreases the review required.
| Level | Name | Assistant does | Owner does |
|---|---|---|---|
| 1 | Prepare | Gathers information and options | Decides and executes |
| 2 | Draft | Produces a complete draft | Reviews, edits, sends |
| 3 | Execute with review | Acts, then reports before release | Approves before it goes out |
| 4 | Execute and inform | Acts and reports after the fact | Watches results and exceptions |
| 5 | Own | Owns outcome, escalates exceptions | Sets direction and checks sampling |
Most tasks start at Level 2. A new task rarely belongs at Level 5 immediately, no matter how capable the assistant is, because the process itself is still unproven.
Match the level to the risk
The right level depends on the cost of a mistake, not on how much you like the task. For each task, ask what happens if it is done wrong:
- Reversible and low-cost: a typo, a draft, a research note. These can move quickly toward Level 4 or 5.
- Reversible but disruptive: a rescheduled meeting, a revised invoice. Keep at Level 3 until the process is stable.
- Hard to reverse or high-stakes: money movement, legal language, public statements. Stay at Level 2 or 3 with named approval.
This is the same logic behind a delegation matrix, applied task by task.
Write the level into the brief
A delegation brief becomes far more useful when it names the level. Instead of "handle customer replies," write "Level 2: draft replies for approval; escalate refund requests." The assistant then knows both the action and the boundary. For tasks that recur, the level belongs in the standard operating procedure so it does not have to be re-decided every day.
Pair the level with a definition of done. The output standard describes what good work looks like, and the acceptance criteria describe when the work is finished. Level, standard, and criteria together form a complete instruction.
Use decision rights for the gray areas
Some situations fall outside the normal path: an unusual request, a sensitive client, or a conflict with a policy. A decision rights register records which choices the assistant may make alone, which need approval, and which must escalate. It complements the level by covering exceptions rather than the routine case.
Move levels deliberately
Increasing a level should be a decision, not a drift. Two conditions justify a move: the process has produced consistent quality, and the mistake cost is acceptable at the new level. When both hold, move up one level and adjust the review. Tell the assistant explicitly: "This is now Level 4; send me a weekly summary and flag anything unusual."
If quality slips, move down a level temporarily, fix the process, and try again. Lowering a level is not a punishment; it is a control that protects both people while the system is repaired.
Review levels on a schedule
Levels age. A task that was high-risk at a startup's beginning may become routine later, and a once-simple task may become sensitive as the business grows. Review the levels each quarter, or whenever a tool, a policy, or a person changes. A short list that is current is more useful than a long one nobody maintains.
Common mistakes to avoid
The first mistake is assigning a level implicitly and expecting the assistant to guess. The second is granting Level 5 for a process that has never been tested. The third is never raising a level, which keeps the owner in the loop forever. The fourth is raising a level after one good result. The fifth is leaving exceptions undefined, so the assistant must stop for every unusual case.
Your next step
List the tasks your assistant handles and assign each a level from one to five. Share the list and ask whether the boundaries match what both of you expected. Adjust the tasks where the level was unclear, and pick one safe task to test at the next level up this month. If you want help mapping levels for a new role, book a free consultation and we will build the register with you.
Frequently asked questions
How many delegation levels should I use?
Five is enough for most teams. What matters is that each level has a clear meaning and that tasks carry an explicit level.
How fast should I raise a level?
Only after the process has shown consistent quality and the cost of a mistake is acceptable. Raise one level at a time and watch the results.
Does a higher level mean less oversight?
It means less direct review, not less accountability. The owner still sets direction and samples results, and exceptions still escalate.
Sources and editorial limits
This article follows SBA guidance on delegating and managing work and draws on the NIST Cybersecurity Framework principle of matching controls to risk for the idea of scaling review to consequence. It is general guidance, not a substitute for your own operating decisions.