What is a Threshold-Based Authority Map?
A Threshold-Based Authority Map is a one-page governance document that defines who may make which class of decision, up to what financial value, without escalation. It is the difference between delegation as a hope and delegation as a system — and it is the fastest structural fix for a business where every decision still routes through the founder.
The anatomy
Decision classes
The five to eight kinds of decision that actually recur — operational spend, pricing variance, hiring, client concessions, supplier commitments.
Roles with thresholds
Each role carries an explicit financial threshold per decision class — a number, not a judgement call.
Under threshold: decide
Anything below threshold is decided without the founder — and without guilt or double-checking. Above it, a defined escalation rule applies.
Its place in the framework
Installed after Financial Visibility, before Leadership Rhythm — thresholds need real cash and margin data underneath them.
The problem it solves
In most founder-led businesses, authority was never designed — it accumulated. The founder decided everything at $500k, and at $5M still decides most things, because nobody knows precisely what they are allowed to decide alone. Capable managers escalate to be safe. The founder becomes the bottleneck, and the bottleneck reads as a delegation failure or a trust failure when it is an architecture failure: the boundaries were never written down. The full mechanics are covered in why most founders become the bottleneck and how to clarify decision rights.
What one looks like
The format matters less than the explicitness. A working example for a $3M services firm:
| Decision class | Team lead | Department head | Second-in-command | Founder |
|---|---|---|---|---|
| Operational spend | to $500 | to $2,500 | to $10,000 | above $10,000 |
| Client concessions / credits | to $250 | to $1,000 | to $5,000 | above $5,000 |
| Pricing variance from rate card | none | to 5% | to 15% | above 15% |
| Hiring | — | within approved plan | new roles to $70k | above $70k / exec roles |
| Supplier commitments | — | to $5,000/yr | to $25,000/yr | above $25,000/yr |
Five rows, four columns, one page. The thresholds are examples — yours come from your own numbers. What is not optional is the property the table creates: every person in the business can look at a decision and know, without asking, whether it is theirs.
How to build one
List the decision classes that actually recur
Pull 90 days of decisions that reached the founder. Cluster them — spend, concessions, pricing, hiring, suppliers. Five to eight classes cover most businesses.
Set thresholds from the financial data, not from comfort
This is why Financial Visibility installs first: thresholds set without forward cash and margin visibility default to caution, and the founder sets them near zero.
Write the escalation rule per class
Above threshold, who decides, and what information must accompany the escalation — so escalation is a handover, not a conversation restart.
Publish it and honour it
The founder’s discipline is the hard part: an under-threshold decision made without you must stand, even when you would have decided differently. Overrule one and the map dies — everyone resumes escalating.
Review thresholds quarterly
Raise them as trust and visibility compound. The map should loosen over time; that is what structural independence looks like.
Why authority maps fail without the other pillars
An authority map alone is a document. It becomes an operating fact when the surrounding structure enforces it: Financial Visibility so thresholds rest on real margin and cash data; Leadership Rhythm so decisions made under authority are reported — not re-approved — in the weekly cadence via Decision-First Cadences; and Accountability Design so the person holding authority also owns the outcome. Install order matters: Visibility → Authority → Rhythm → Accountability.
The test of a working authority map is silence. When the founder stops hearing about a class of decision — and the outcomes hold — that class has been structurally delegated. Delegation you can still hear is not delegation yet.
Frequently asked questions
What is a threshold-based authority map?
A one-page governance document that defines which roles may make which classes of decision — operational spend, client concessions, pricing variance, hiring, supplier commitments — up to explicit financial thresholds, without escalation to the founder. Above threshold, a defined escalation rule applies.
How is it different from a delegation-of-authority matrix?
Same family, different design intent. Corporate DoA matrices are compliance documents, often dozens of pages nobody reads. A Threshold-Based Authority Map is an operating tool for founder-led businesses: five to eight recurring decision classes, thresholds set from live financial visibility, reviewed quarterly, and enforced through the leadership rhythm.
What thresholds should a growing business set?
Set them from your own margin and cash-flow data — that is why financial visibility installs first. A practical starting point: thresholds low enough that a wrong decision is affordable, high enough that at least 80% of recurring decisions in each class clear without the founder. Then raise them quarterly as outcomes prove out.
Still the decision bottleneck in your own business?
The Operational Clarity Call is a focused 30-minute structural assessment — where decisions actually route today, and what an authority map would move off your desk first.
Book an Operational Clarity Call
