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

Here's what it looks like before that. A $400 service-panel swap is sitting in the same queue as a $40,000 full rewire, both waiting on the same callback, and the business is moving at the speed of one guy's voicemail. It's April at an electrical contractor, when the new-construction calls start stacking up, and the owner approves every quote over $0. So 30 quotes a week route to one phone, with no rule sorting the trivial ones from the real ones.

Everybody will tell him to delegate more. That isn't his problem.

Why it all comes back to you

Every decision lands on your phone with equal priority because nobody ever set a threshold. With no limit written down, the $400 job and the $40,000 job carry the same urgency, and your team escalates by default to stay safe.

Owners miss that last part. A team with no written authority does the rational thing when it's unsure: it asks. Asking is cheaper than guessing wrong and getting blamed.

So the full queue is a sign nobody knows where their authority ends. From the approval chair, that looks exactly like a weak team.

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

"Delegate more" is a feeling

That's the answer every other article gives, along with "trust your team." Neither one tells anybody what to do on Monday morning. Decision rights does: who decides what, up to what limit, and what comes back to you.

You can test the difference. Tell a manager to "use their judgment on refunds" and every odd refund still lands on your desk, because nothing told them where their authority stops. Write the rule instead, "approve refunds up to $500, escalate anything above," and the $480 refund clears without you while the $900 one comes to you.

This isn't something a consultant dreamed up. In aerospace and defense work, where waiting on one approver is itself a failure, authority gets defined in advance so the system keeps moving without one person in the loop.

So a real delegation framework isn't a pep talk about letting go. It's the routing table underneath the talk. You assign a decision and put a fence around it. And it's one piece of a bigger whole, the operator's reliability playbook, which is the system that runs the place whether you're in the building or not.

The table

Four columns. For each decision that keeps coming up: the decision, who owns it, their limit, and what escalates.

This is item H7-DRT in The Operator's Reliability Toolkit. Here's what two rows look like for the contractor (call it a ~$2M shop):

Now read the first row against how things used to work. The $400 panel job clears with the estimator and never touches the owner. The $40,000 rewire comes up to him by rule.

Each row sits on top of a process, and the limit is only as good as the written process the decision-owner works from. The table says who decides. The SOP says how it gets decided the same way every time.

The limit column is where owners slip. They fill in the decision and the owner and leave the limit blank. Which sends the decision straight back to the chair, because an estimator with no number next to their name will still call before quoting the $400 job.

Start with the five decisions that interrupted you most this week. Name the owner, set one number or one clear scope, write the escaltaion rule in plain words. Five rows that work beat 30 rows nobody trusts, and the queue drops the day the first five go live.

Keeping control of what matters

The fear is losing control. The escalation column is the answer to that fear.

Set the estimator's limit at $5,000 and roughly 90% of weekly quotes clear without the owner. The 10% that come up are the jobs that actually deserve his eyes, which is where he wanted his attention to begin with.

Usually the person holding that authority is a manager. That's the work of hiring or building a general manager who actually holds the decision rights once they're written and stops asking before every call.

Treat the number like a dial. Raise it as you build trust, lower it for anyone who's misjudged twice.

And watch what escalates, because that's data. If the same kind of job comes up three weeks running, you're missing a row, so write one. Over a few months the pile of decisions that need you shrinks. The contractor who started with 30 quotes a week on his phone can get down to the three or four that really need him.

What it does to your score, and your price

Routing decisions away from you is the core of business independence, the BIS the Keystone diagnostic measures. Every decision you move off your phone removes one point of owner-dependence, and once it opens, the diagnostic will show exactly where the business still runs through you.

It shows up in the sale price too. Most owners never see that cost, though, because they've never seen 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 nobody has measured.

As item H7-DRT, the decision-rights table lives and grows inside your Keystone operating record, tied to the Keystone Decision Routing Engine that keeps the routing going after a Full Operations Modernization installs it.

Want to see the far side before you start? What changes after a modernization walks the operation station by station once the systems are in.

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.

The goal is simple: the next $400 job clears without you and only the $40,000 one reaches your desk.

Keystone is closed while the build wraps up. When the diagnostic opens, it will give you three scores and your value range with the most likely figure locked, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records, and your Business Independence Score will read how much of the business still depends on you.

Sign up for the waitlist at https://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 bigger version of this is a Full Operations Modernization, where the decision routing, documented procedures, manager structure and owner dashboard get built into a live system your team runs.

It's available now, selectively, and it's scoped before anything is sold. Start with the Full Operations Modernization page.