Get Out of the Approval Chair: How to Stop Being the Bottleneck on Every Decision

The short version

• A ~$2M electrical contractor approves every quote over $0, so a $400 service-panel job waits in the same queue as a $40,000 rewire.
• He has not failed at delegating. He has never set a threshold, so every decision arrives at his phone with equal priority.
• The fix is a decision-rights table: for each recurring decision, name the owner, set the limit, and define what escalates.
• Routing decisions away from you is the core of your Business Independence Score, and the spread between a 1.65x and a 3.5x exit is $555,000 on a $300,000-SDE business.
• Below: the table that empties your approval queue, the limit that keeps you in control of what matters, and the score it moves.

The $400 job waiting like a $40,000 one

A ~$2M electrical contractor approves every quote over $0, so a $400 service-panel swap sits in the same queue as a $40,000 full rewire. Both wait on the same callback, and the business moves at the speed of his voicemail.

To stop being the bottleneck in your business, you name who owns each recurring decision, set a dollar or scope limit on their authority, and define exactly what escalates back to you. Most decisions stop reaching you because the routing is written down, not because you finally relaxed.

You keep the genuine exceptions and shed the routine. The $400 job clears below the line while the $40,000 job rises to you by rule.

The contractor does not have a delegation problem in the way the advice posts mean it. He has 30 quotes a week routing to one phone with no rule sorting the trivial from the real.

So the controlling question is not "why won't my team step up." It is narrower and more useful: why does every decision still come back to me, and how do I route most of them away without losing control.

Delegation is advice; decision rights is a system

"Delegate more" and "trust your team" is the answer every competing article gives, and it is a feeling, not a mechanism. Decision rights is a written assignment: who decides what, up to what limit, and what escalates.

The difference is testable. Tell a manager to "use their judgment on refunds" and every nonstandard one still comes to you, because nothing told them where their authority ends.

Write the rule instead: "approve refunds up to $500, escalate anything above." Now the $480 refund clears without you, and only the $900 one reaches your desk.

Consider where this discipline came from. In operations where waiting on one approver is itself a failure mode, authority is defined in advance, so the system keeps moving without a single person in the loop.

Defining who decides what, up to what limit, and what escalates is not a consultant invention. It is how reliability is engineered in aerospace and defense work, where getting it wrong is not an option.

Now bring that back to the contractor. A real delegation framework is not a pep talk about letting go.

It is the routing table underneath the talk, and the table is what actually empties his queue.

The reframe for the owner is simple. You are not delegating a task and hoping; you are assigning a decision and bounding it.

Decision routing is one method inside a larger whole. It belongs to the operator's reliability playbook, the system that runs the business whether or not you are in the building.

Why everything routes back to you (it's not your team)

Every decision arrives at your phone with equal priority because no one ever set a threshold. With no limit defined, a $400 job and a $40,000 job carry the same urgency, and your team escalates by default to stay safe.

That last part is the piece owners miss. A team with no written authority does the rational thing under uncertainty: it asks. Asking is cheaper than guessing wrong and getting blamed.

So the queue is not evidence of a weak team. It is evidence of undefined authority, and the two look identical from the approval chair.

The contrast is sharp once you name it:

• Owner decides everything: no limits exist, so all 30 quotes a week escalate, and the business stalls at the owner's response time.
• Authority defined: a written limit clears the routine 90% below the line, and only the real exceptions reach the owner.

The team did not change between those two states. The rule did.

Build the decision-rights table

The core artifact is a four-column table. For each recurring decision, you write the decision, the owner, the authority limit, and what escalates.

This is item H7-DRT in The Operator's Reliability Toolkit, and here is the structure with two worked rows from the contractor's business:

Recurring decision	Owner	Authority limit	What escalates
Approve a service quote	Lead estimator	Up to $5,000	Any quote above $5,000, or any custom-fabrication job
Issue a customer refund	Office manager	Up to $500	Any refund above $500, or a repeat complaint from one account

Read the first row against the old reality. The $400 service-panel job now clears with the estimator and never reaches the owner, while the $40,000 rewire escalates by rule, not by accident.

Each row encodes a process, and the limit is only as good as the documented process a decision-owner runs from. The table says who decides; the SOP says how the decision is made the same way every time.

The authority limit is the column owners get wrong. They write the owner and the decision, then leave the limit blank, which routes the decision straight back to the approval chair.

A blank limit is the same as no limit. The estimator who has no number above their name will still call before quoting the $400 job, because nothing told them they were allowed not to.

Fill in your own rows starting with the five decisions that interrupt you most this week. Name the owner, set one number or one defined scope, and write the escalation rule in plain language.

Keep the first table short. Five well-bounded decisions that clear without you beat 30 rows nobody trusts, and the contractor's queue drops the day the first five are live.

Set the limit so the right things still reach you

The "without losing control" fear is the real objection on this keyword, and the escalation column is the answer to it. A limit is not abdication; it is the rule that routes the genuine exceptions up while the routine clears below.

Set the contractor's estimator limit at $5,000 and roughly 90% of weekly quotes clear without him. The 10% that escalate are the jobs that actually warrant an owner's eyes, which is exactly where he wanted his attention in the first place.

The person who carries that authority is usually a manager. This is the work of hiring or building a general manager who holds the decision rights once they are defined, rather than a loyal employee who still asks before every call.

Raise the limit as the owner builds trust, and lower it for one person who has misjudged twice. The number is a dial, not a one-time setting.

There is a second control most owners miss: the escalation rule itself is data. When the same kind of job escalates three weeks running, that is a missing row, and you write a new limit for it.

Over a few months the set of decisions that require you shrinks instead of holding steady. The contractor who started at 30 quotes a week on his phone can be down to the three or four that actually need him.

The control you keep is the exception, not the routine. You stopped approving the $400 job; you did not stop seeing the $40,000 one.

This is the work that moves your independence score, and your price

Routing decisions away from the owner is the core of business independence, which is the BIS the free diagnostic measures. Every decision you move off your phone is a point of owner-dependence you remove, and the diagnostic reads exactly where the business still runs through you.

The same work shows up in the sale price. An owner-dependent service business sells near 1.65x its earnings; an owner-light one sells near 3.5x.

On a $300,000-SDE business, that spread is $555,000. Same revenue, same industry, same year, half a million dollars apart on decision design alone.

Most owners never see this cost because they never see their number. 86% of small business owners have no professional valuation or only a rough estimate, so the approval-chair habit quietly discounts a price they have never measured.

The decision-rights table is not a one-time download. As item H7-DRT, it lives in and accumulates inside your Keystone operating record, tied to the Keystone Decision Routing Engine that sustains the routing after the Sprint installs it.

FAQ

How do I stop being the bottleneck in my business?

You stop being the bottleneck by naming who owns each recurring decision, setting a dollar or scope limit on their authority, and defining exactly what escalates back to you. Most decisions then stop reaching you because the routing is written down, while the escalation rule keeps the genuine exceptions in your hands.

Why does every decision in my business go through me?

Every decision routes to you because no threshold was ever set, so a $400 job and a $40,000 job arrive with equal priority. A team with no written authority escalates by default to stay safe, which looks like a weak team but is actually undefined authority.

How do I delegate decisions without losing control?

You keep control through the escalation column, not by approving everything. Set a limit so the routine 90% of decisions clear below the line, then write a rule that routes the genuine exceptions up to you.

How much authority should I give my employees?

Start with a limit that clears the routine majority of a recurring decision, such as quotes up to $5,000 for a lead estimator. Raise it as the person proves their judgment, and lower it for anyone who has misjudged twice.

---

You cannot route a decision away from yourself until you can see which ones still run through you.

The free Keystone diagnostic gives you three scores and an estimated sale price, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records. Your Business Independence Score reads exactly how much of the business still depends on you, and routing decisions away raises it.

Get your three scores and an estimated sale price, free, at app.trykeystone.io.

Knowing the gap is one thing. Installing the table is another, and most owners do not have the months it takes to build the routing alone.

The Systems Sprint installs the Decision Routing Framework: the decision-rights table, the limits, and the escalation rules, built for your business in 30 days. The table then lives in the Keystone Decision Routing Engine, where it accumulates as your operating record instead of sitting in a drawer.