The Decision Routing Framework: Who Decides When You're Not There

The short version

• A decision routing framework is a written table of decision categories, dollar limits, and named owners, where anything not covered defaults to the manager and never to you.
• Most owners find three or four recurring decisions a week routing back through one phone. The framework is what ends that.
• The same independence work is the difference between a 1.65x and a 3.5x sale: $555,000 on a $300,000-SDE business.
• The Sprint builds the framework once, and it lives on inside the Keystone Decision Routing Engine, which keeps the rules current instead of letting the table go stale. Here is how it works.

The decisions that route back through your phone

Keep a one-line log for five business days of every time someone on your team asked you a question or needed a decision. Most owners in this revenue band fill that page with three or four recurring decisions that come back week after week.

A quote that ran long and needs re-pricing. A discount a customer is pushing for. A slow-paying account someone wants to put on hold.

None of these are hard for you. They are hard for the team only because nobody wrote down who is allowed to decide them and on what terms.

So the decision waits. It waits on your phone, in your truck, on your day off, and the business runs at the speed of one person's attention.

The owner reads that pile of interruptions as proof the team needs them. A buyer reads the same pile as risk and prices it down.

The interruption log is not a complaint list. It is the raw material for the fix, because every recurring item on it is a decision that could have a rule.

What a decision routing framework actually is

A decision routing framework is a written table that sorts your recurring decisions into categories, assigns each one a dollar limit and a named owner, and sets a default rule so that anything not explicitly covered goes to the manager, never to the owner. It replaces "ask the owner" with "look up the category, follow the rule," so the normal case runs without you and only the true exception escalates.

This is the opposite of motivational delegation. Nobody is told to trust their team or let go.

The team is handed a specific instruction: under $300, approve it; over $300, bring it to the manager; this exact situation, here is the outcome.

The framework is built from your actual interruption log, not a generic template. The categories are your categories, and the dollar thresholds are the ones that fit your margins.

A good routing rule is specific enough that two different team members reading it reach the same outcome. "Use your judgment on small amounts" is not a rule; "approve any warranty replacement under $300 without calling" is.

The four categories every decision falls into

In the Sprint, the decision audit walks your interruption log line by line and sorts each item into one of four categories. The sort is what tells you which decisions get a rule and which stay yours.

1. Decisions that should have a rule are the routine calls with an obvious right answer once the condition is written down, like "approve any refund under $200." They move straight into the routing table.

2. Decisions the team can make but lacks the confidence to are ones the team can handle but feels it should run by you first. A written authority limit removes the hesitation and these leave your phone too.

3. Decisions only you can make are the few that legitimately stay with the owner, like a major customer relationship or a pricing exception that sets a precedent. The framework names these honestly rather than pretending everything can be delegated.

4. Decisions that reveal a missing process are not decision problems at all; the team did not know the steps for handling a situation. These flag a process to document rather than a rule to write.

Categories one and two are what fill the routing table. Category three is the short list that stays with you on purpose, and category four points to the documentation work.

The honest version of this exercise usually surprises the owner. Far more of the interruption log belongs in categories one and two than they expected, which means far more of their week is recoverable than they thought.

Where the framework lives after the Sprint: the Keystone Decision Routing Engine

A routing table printed once and taped to a wall starts dying the day the business changes. A new service line appears, a threshold needs raising, a manager changes, and the paper version is already wrong.

This is where the Sprint deliverable stops being a document and becomes an operating layer. The Decision Routing Framework the Sprint builds pre-provisions the Keystone Decision Routing Engine, and the framework lives on inside that surface after the engagement ends.

Inside the Decision Routing Engine, the rules are not a static PDF. They are editable as the business changes, the thresholds update in one place, and the engine routes the real decisions instead of leaving them to a forgotten printout.

That is the hand-off that makes this different from every delegation post you have read. The Sprint installs the framework; it lives on in the Decision Routing Engine afterward, which keeps the table current rather than letting it decay into a binder nobody opens.

The work the Sprint does in 30 days is the same work that closes the independence discount on your sale price. An owner-dependent business sells near 1.65x earnings; an owner-light one sells near 3.5x.

On a $300,000-SDE business, that spread is $555,000, set by operational design rather than revenue. The valuation behind those numbers is calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records, so the gap is the pattern in real closed transactions.

This deliverable is one of four the Sprint installs. It is the start of everything the Systems Sprint installs, the operating layer that takes the owner out of the daily path.

It is also the concrete form of a horizontal discipline. Getting recurring calls off your phone is how you get out of the approval chair for good, and the routing table is the artifact that does it.

If you want the broader version of handing decisions to named owners, the delegation framework sits underneath the same idea: route the decision to a person and a limit, not back to yourself.

What changes in the first week

The decision routing framework is the deliverable Sprint clients use most, and the one that produces the fastest visible result. The reason is simple: it works in week one.

Your team gets the table, looks up the category when a situation comes up, and follows the outcome. The calls that used to land on your phone start landing on the rule instead.

The first week is usually where the owner feels it. The interruptions that filled the old log thin out, because the decisions they represented now have a written home.

That early win is what carries the rest of the work. Fewer interruptions in week one is the proof the team needed that they are allowed to decide, and the momentum makes the harder documentation and manager work stick.

You will still get the genuine exceptions, the calls that belong in category three. That is the point: you are left with the few decisions that actually require the owner, not the forty that never did.

FAQ

What is a decision routing framework?

A decision routing framework is a written table that sorts your recurring decisions into categories, gives each one a dollar limit and a named owner, and defaults anything uncovered to the manager rather than the owner. It replaces "ask the owner" with "look up the category, follow the rule," so the team decides the normal case without you.

What decisions should a business owner keep?

A business owner should keep only the decisions that truly require them: major customer relationships, pricing exceptions that set a precedent, and calls that rest on expertise nobody else has yet. Everything routine, like standard approvals and ordinary discounts, belongs in a written rule with a dollar limit and a named owner.

How do you let employees make decisions without you?

You let employees make decisions without you by writing down the rule, not by telling them to use their judgment. Give each recurring decision a specific condition and dollar limit so two team members reading it reach the same outcome, and the calls stop routing back to your phone.

Does the framework go away after the Sprint?

The framework does not go away. The Sprint builds it once, and it pre-provisions the Keystone Decision Routing Engine, where the rules live on, stay editable as the business changes, and route the real decisions rather than decaying into a forgotten printout.

---

You cannot fix the decisions routing through you until you measure how many still do.

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. It shows exactly how much of the business still waits on you and what that costs your number.

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

The diagnostic names the gap. The Systems Sprint installs the routing framework that closes it, and three more deliverables alongside it.

The Sprint is a 30-day engagement that asks under five hours of your time, delivered once with no retainer. Pricing is $1,500 Beta for the first engagements, $1,900 Standard, and $4,500+ for the Portfolio Edition.