Table of Contents

    Giving the Right Level of Authority

    Levels of Delegated Authority

    Introduction

    Delegation does not always mean giving full authority to another person immediately. Authority can be given in levels. A leader may ask someone only to collect information, or to analyze and recommend, or to decide after approval, or to decide independently within limits. In some cases, the person may receive full ownership with periodic review.

    Understanding the levels of delegated authority helps leaders delegate more safely and effectively. It allows the leader to match authority with the person's readiness, the risk level of the task, and the importance of the outcome. A beginner may need limited authority and close review. A competent person may receive authority to decide within boundaries. An expert may receive broad ownership with review at key milestones.

    If leaders do not define authority levels clearly, delegation can become confusing. The person may not know whether they can make a decision, whether they need approval, whether they can contact stakeholders, or whether they should only provide information. This uncertainty slows work and increases dependency on the leader.

    In this section, we will discuss five practical levels of delegated authority:

    • Level 1: Informing
    • Level 2: Recommending
    • Level 3: Deciding with approval
    • Level 4: Deciding independently within limits
    • Level 5: Full ownership with review

    These levels help leaders delegate with clarity, confidence, and control without micromanaging.

    What Are Levels of Delegated Authority?

    Levels of delegated authority describe how much decision-making power a person has when they receive a delegated task. Authority can be small, moderate, or broad depending on the situation. The leader should clearly explain the authority level before the person begins the task.

    For example, if a leader says, “Please review the options and tell me what you find,” the person has limited authority. They are only informing. If the leader says, “Review the options and recommend the best one,” the person has more authority because they are expected to use judgment. If the leader says, “Choose the best option as long as it stays within the budget,” the person has decision authority within limits.

    Delegated authority is not all-or-nothing. It can be adjusted based on task risk, person readiness, and leadership accountability.

    Why Authority Levels Matter

    Authority levels matter because they prevent confusion. They help the person understand what they are allowed to do and what must be checked with the leader. Clear authority levels also help the leader maintain the right balance between empowerment and control.

    Without authority levels, the person may either ask for approval too often or make decisions beyond their role. Both situations can create problems. Too little authority creates dependency. Too much authority without boundaries creates risk.

    Benefits of Defining Authority Levels

    • It clarifies what the person can and cannot decide.
    • It reduces unnecessary approvals.
    • It prevents risky decisions beyond boundaries.
    • It builds confidence in the person receiving the task.
    • It helps leaders delegate according to readiness level.
    • It improves speed because the person knows when they can act.
    • It supports accountability because decision rights are clear.
    • It reduces micromanagement by creating structured freedom.

    Level 1: Informing

    At the informing level, the person is responsible for collecting information and sharing it with the leader. They do not analyze deeply, make recommendations, or make decisions. Their role is to gather facts, updates, status, data, or observations.

    This level is useful when the person is new to the task, when the task is low-risk, or when the leader needs information before making a decision. It is also a good starting point for beginners because it helps them understand the work without carrying full decision responsibility.

    When to Use Informing Authority

    • The person is new or still learning.
    • The leader needs basic information before deciding.
    • The task is mainly data collection or update collection.
    • The risk of wrong judgment is high, so decision remains with the leader.
    • The person does not yet have enough context to recommend or decide.

    Examples of Informing Authority

    • Collecting status updates from team members.
    • Listing open action items after a meeting.
    • Gathering defect counts from testing reports.
    • Collecting availability information for a training session.
    • Sharing a summary of current blockers without recommending action.

    Sample Delegation Statement

    “Please collect the latest updates from all module owners and share them with me by Thursday evening. At this stage, you do not need to analyze or recommend anything. Just collect accurate updates in the tracker so I can review them before the project meeting.”

    Leader's Role at Level 1

    • Explain exactly what information is needed.
    • Provide the format for collecting information.
    • Clarify who the person can contact.
    • Review the collected information.
    • Help the person understand the meaning of the information over time.

    Informing authority is a safe starting level for learning because it builds awareness without requiring decision-making.

    Level 2: Recommending

    At the recommending level, the person does more than collect information. They analyze the information and suggest a possible action, option, or decision. However, the final decision remains with the leader.

    This level is useful for developing analytical thinking, judgment, and ownership. It helps team members move from simply reporting facts to interpreting information and forming reasoned suggestions.

    When to Use Recommending Authority

    • The person has enough understanding to analyze information.
    • The leader wants to develop decision-support skills.
    • The task requires comparison, evaluation, or problem-solving.
    • The final decision is important and should remain with the leader.
    • The person is ready for more responsibility but not full decision authority.

    Examples of Recommending Authority

    • Comparing three tools and recommending one.
    • Analyzing repeated defects and suggesting improvement actions.
    • Reviewing risks and recommending which ones need escalation.
    • Preparing pros and cons of two process options.
    • Suggesting agenda items for a stakeholder meeting.

    Sample Delegation Statement

    “Please review the last three weeks of defect data and identify the top repeated categories. Prepare a short recommendation on which issue area we should focus on first and explain your reasoning. I will review your recommendation before we decide the next action.”

    Leader's Role at Level 2

    • Define the decision or problem clearly.
    • Explain evaluation criteria.
    • Ask the person to include reasons for recommendations.
    • Review the recommendation and provide feedback.
    • Help the person improve judgment over time.

    Recommending authority develops judgment because the person learns to move from facts to reasoned choices.

    Level 3: Deciding With Approval

    At this level, the person can prepare a decision or choose a preferred action, but the decision must be approved by the leader before it is implemented. This gives the person meaningful ownership while still protecting the leader’s final accountability.

    Deciding with approval is useful when the task has moderate risk, when the person is developing decision-making ability, or when the final output affects stakeholders and should be reviewed before action.

    When to Use Deciding With Approval

    • The person can make a reasonable decision but still needs review.
    • The decision has moderate risk or stakeholder impact.
    • The task is developmental and helps the person build confidence.
    • The leader wants to give decision practice without giving full independence yet.
    • The output should be checked before final communication or implementation.

    Examples of Deciding With Approval

    • Choosing a draft format for a report, subject to leader approval.
    • Selecting proposed action items for a project review before finalizing.
    • Preparing a client update draft that requires leader approval before sending.
    • Choosing a recommended training topic before confirming with participants.
    • Proposing a revised process step before implementation.

    Sample Delegation Statement

    “Please prepare the client update draft and decide the best structure for the message. You can choose the order of sections, but do not send it directly. Share the draft with me first so I can review and approve it before it goes to the client.”

    Leader's Role at Level 3

    • Define what must be approved before action.
    • Explain what the person can decide independently.
    • Review the decision or draft promptly.
    • Give feedback on judgment and decision quality.
    • Gradually reduce approval needs as readiness improves.

    Deciding with approval is a useful bridge between recommendation and independent decision-making.

    Level 4: Deciding Independently Within Limits

    At this level, the person can make decisions independently, but only within clearly defined boundaries. The leader sets limits around scope, budget, timeline, quality, stakeholder communication, or risk. Within those limits, the person has freedom to act.

    This level is useful for competent team members who have enough skill and judgment to manage a task without constant approval. It increases speed and ownership because the person does not need to check every small decision with the leader.

    When to Use Independent Decision Authority Within Limits

    • The person is competent and reliable.
    • The task is repeatable or well understood.
    • The leader can define clear decision boundaries.
    • The risk is manageable.
    • Faster execution is needed without unnecessary approvals.

    Examples of Deciding Independently Within Limits

    • Choosing meeting timing based on participant availability.
    • Updating action item status based on confirmed owner responses.
    • Selecting report layout within an approved template.
    • Prioritizing follow-ups based on due dates and blockers.
    • Coordinating with internal teams within agreed scope.

    Sample Delegation Statement

    “You can manage the weekly action tracker independently. You can contact owners directly, update status based on confirmed responses, and highlight delayed items. Please do not close any action unless the owner confirms completion. Escalate any item that is delayed by more than two working days.”

    Types of Boundaries to Define

    Boundary Type Meaning Example
    Scope Boundary What is included and excluded. “You can coordinate internal updates, but client communication stays with me.”
    Time Boundary When decisions must be made or escalated. “If no response comes by Wednesday noon, escalate.”
    Quality Boundary Standards that must be followed. “Use the approved template and include all mandatory sections.”
    Risk Boundary When the person should not decide alone. “Escalate any high-impact risk before changing priority.”
    Communication Boundary Who the person can communicate with and what they can share. “You can contact internal owners, but do not send external updates without review.”

    Independent authority works best when boundaries are clear enough to protect quality and flexible enough to allow ownership.

    Level 5: Full Ownership With Review

    At the highest level, the person receives full ownership of the task, process, deliverable, or initiative. They can plan, decide, coordinate, execute, and improve the work. The leader does not control daily actions but remains informed through periodic reviews or milestone check-ins.

    Full ownership with review is appropriate for experienced, reliable, and capable people. It is also useful when the goal is to develop future leaders or create independent process owners.

    When to Use Full Ownership With Review

    • The person is experienced and reliable.
    • The person understands the task deeply.
    • The task can be owned as a process or outcome.
    • The leader wants to reduce dependency.
    • The person is ready for leadership preparation.
    • The risk can be managed through periodic review.

    Examples of Full Ownership With Review

    • Owning a monthly dashboard process.
    • Managing the weekly action tracker independently.
    • Coordinating a recurring knowledge-sharing program.
    • Leading a small process improvement initiative.
    • Owning documentation updates for a project area.
    • Managing internal status collection and reporting.

    Sample Delegation Statement

    “I would like you to fully own the monthly dashboard process starting this month. You can collect inputs, update the dashboard, coordinate with contributors, and suggest improvements to the format. Please share the dashboard before the monthly review and highlight any major data gaps or risks. We will review the process after the first two cycles to identify improvements.”

    Leader's Role at Level 5

    • Provide strategic direction and expected outcomes.
    • Remove blockers when needed.
    • Review milestones or final outcomes.
    • Give feedback and coaching after completion.
    • Avoid unnecessary interference.
    • Recognize ownership and improvement.

    Full ownership with review gives strong autonomy while still keeping leader visibility and accountability.

    Authority Level Comparison Table

    The table below summarizes the five levels of delegated authority.

    Level Authority Type Person Can... Leader Still... Best For
    Level 1 Informing Collect and share information. Analyzes and decides. Beginners, low-risk information collection.
    Level 2 Recommending Analyze and suggest options. Makes final decision. Developing judgment and analysis skills.
    Level 3 Deciding with approval Choose a proposed action but seek approval. Approves before implementation. Moderate-risk tasks and developmental decisions.
    Level 4 Deciding within limits Make decisions independently within boundaries. Sets limits and reviews exceptions. Competent and reliable team members.
    Level 5 Full ownership with review Own and manage the process or outcome. Reviews milestones and supports as needed. Experts, process owners, leadership development.

    How to Choose the Right Authority Level

    The leader should choose the authority level based on the task and the person. Giving too little authority can slow work. Giving too much authority too early can create risk. The goal is to give enough authority for the person to succeed safely.

    Factors to Consider

    • Task risk: High-risk tasks need tighter authority boundaries.
    • Person readiness: Beginners need limited authority; experts can handle more.
    • Experience: Has the person handled similar decisions before?
    • Impact: Does the task affect customers, stakeholders, quality, or delivery?
    • Time pressure: Urgent tasks may require faster decision rights or closer leader ownership.
    • Development goal: Is the task intended to build judgment and decision-making?

    Authority Selection Guide

    Situation Recommended Authority Level Reason
    New person learning a process Level 1: Informing Builds understanding with low risk.
    Developing person practicing judgment Level 2: Recommending Builds analysis and reasoning.
    Moderate-risk stakeholder draft Level 3: Deciding with approval Allows ownership while protecting final quality.
    Competent person managing routine process Level 4: Deciding within limits Improves speed and ownership with boundaries.
    Expert managing established process Level 5: Full ownership with review Supports autonomy and leadership development.

    Moving People Up the Authority Levels

    Authority should increase as the person becomes more capable, reliable, and confident. A leader should not keep someone at the same authority level forever if they are ready for more. Gradually increasing authority is one of the best ways to develop ownership and leadership capability.

    Authority Growth Path

    1. Start with informing: The person collects information and learns the process.
    2. Move to recommending: The person begins analyzing and suggesting.
    3. Move to deciding with approval: The person practices decisions safely.
    4. Move to deciding within limits: The person acts independently within boundaries.
    5. Move to full ownership: The person owns the process or outcome with review.

    Example Growth Path

    Stage Task Example Authority Level
    Month 1 Collect status updates from team members. Informing
    Month 2 Analyze updates and recommend key risks to highlight. Recommending
    Month 3 Prepare draft report and decide structure with leader approval. Deciding with approval
    Month 4 Manage report independently within standard template. Deciding within limits
    Month 5 Own the reporting process and suggest improvements. Full ownership with review

    Delegation develops people when authority grows with capability.

    Common Mistakes With Authority Levels

    Leaders should avoid the following mistakes when assigning authority:

    • Not telling the person what authority level they have.
    • Giving only information-gathering tasks forever and not developing decision-making.
    • Expecting recommendations without explaining decision criteria.
    • Letting people decide independently without boundaries.
    • Requiring approval for every small decision from a competent person.
    • Giving full ownership before the person is ready.
    • Not increasing authority when the person has proven capability.
    • Changing authority level without communicating clearly.
    • Blaming the person for decisions when authority boundaries were unclear.

    Practical Framework: AUTHORITY Ladder

    The AUTHORITY Ladder helps leaders decide how much authority to delegate.

    Step Authority Level Leader Question
    Step 1 Inform Should the person only collect and share information?
    Step 2 Recommend Can the person analyze and suggest options?
    Step 3 Decide with approval Can the person choose an option but get approval before acting?
    Step 4 Decide within limits Can the person decide independently inside clear boundaries?
    Step 5 Own with review Can the person fully own the process while keeping review visibility?

    This ladder helps leaders avoid both under-delegating and over-delegating authority.

    Practical Activity

    Activity Name: Choose the Right Authority Level

    Choose five tasks from your work or learning environment. Decide which authority level is appropriate for each task.

    No. Task Person's Readiness Risk Level Recommended Authority Level Reason
    1 Example: Collect team updates Beginner Low Level 1: Informing Safe information-gathering task for learning.
    2 Example: Analyze repeated defects Developing Medium Level 2: Recommending Builds analysis and judgment.
    3 Example: Prepare client update draft Competent High Level 3: Decide with approval Person can draft, but leader must approve before sending.
    4 Example: Manage action tracker Competent Medium Level 4: Decide within limits Person can update status within clear rules.
    5 Example: Own monthly reporting process Expert Medium Level 5: Full ownership with review Person has experience and can manage independently.

    Sample Authority-Level Conversation

    “For this task, I want to be clear about your authority level. You can collect updates from all action owners and update the tracker based on confirmed information. You can also highlight delayed items and follow up directly with owners. However, please do not close an item unless the owner confirms completion. If someone does not respond after two follow-ups, escalate it to me. So, you have authority to coordinate and update within these boundaries, and I will review the first two cycles with you.”

    This conversation makes authority clear. The person knows what they can do, what they cannot do, and when review will happen.

    Self-Assessment: Do I Define Authority Levels Clearly?

    Mark each statement as Yes, No, or Sometimes.

    No. Statement Yes / No / Sometimes
    1 I clearly explain what authority level the person has.
    2 I distinguish between informing, recommending, and deciding.
    3 I explain what requires my approval.
    4 I give competent people decision authority within limits.
    5 I avoid giving full ownership before a person is ready.
    6 I increase authority gradually as people grow.
    7 I set boundaries around risk, quality, scope, and communication.
    8 I avoid requiring unnecessary approval for every small decision.
    9 I use authority levels to develop decision-making ability.
    10 I review authority levels after the person gains experience.

    Reflection Questions

    1. Do I clearly tell people what decisions they can make?
    2. Do I sometimes give too little authority to capable people?
    3. Do I sometimes give too much authority before someone is ready?
    4. Which tasks in my work require only informing authority?
    5. Which tasks can help someone practice recommending?
    6. Which tasks require deciding with approval?
    7. Which tasks can be handled independently within limits?
    8. Who in my team is ready for full ownership with review?
    9. How can I gradually increase authority for a developing person?
    10. What authority boundary should I clarify in my next delegation conversation?

    Key Learning Points

    • Delegated authority can be given in levels.
    • Authority level should match task risk and person readiness.
    • Informing authority allows the person to collect and share information.
    • Recommending authority develops analysis and judgment.
    • Deciding with approval gives decision practice while protecting final accountability.
    • Deciding independently within limits improves speed and ownership.
    • Full ownership with review is suitable for experienced and reliable people.
    • Authority boundaries should be clear and explicit.
    • Authority should increase gradually as capability grows.
    • Clear authority levels reduce confusion, dependency, and risk.

    Chapter 6.2 Summary

    Levels of delegated authority help leaders decide how much decision-making power to give when assigning work. Delegation does not always require full authority immediately. Authority can range from simple information gathering to full ownership with review.

    This section explained five authority levels: informing, recommending, deciding with approval, deciding independently within limits, and full ownership with review. Each level is useful in different situations depending on task risk, person readiness, experience, and development goals.

    Leaders should clearly communicate the authority level during delegation. The person should know whether they are expected to collect information, recommend, decide after approval, decide independently within boundaries, or fully own the task. This clarity prevents confusion and supports accountability.

    The main lesson of this section is: Delegation becomes safer and more empowering when leaders choose the right level of authority and communicate it clearly before the person begins the work.

    End of Section 6.2

    In the next section, we can discuss 6.3 Decision Rights and Approval Boundaries, including what decisions the person can make, what needs approval, how to define boundaries, and how to prevent confusion.