You've delegated the work. You just haven't delegated the decisions. So the purchase order sits until you look at Slack, the discount waits for your nod, the refund hangs in limbo while a customer gets colder by the hour. Your team isn't incapable. They simply don't know what they're allowed to decide without you, and nobody wants to be the person who guessed wrong.
That gap has a name: decision rights. And the fix isn't another org chart or a new hire. It's a one-page artifact that most mid-market companies have never written down.
Why the bottleneck survives every reorg
Owners often diagnose this as a calendar problem. Too many approvals, not enough hours. So they batch them, or push them to a weekly meeting, or hire a COO and hope the queue moves somewhere else.
It doesn't work, because the queue isn't caused by volume. It's caused by ambiguity. When the boundary is unwritten, the safest move for any employee is to escalate. Escalating costs them nothing and protects them from blame. Deciding costs them a potential conversation about why they spent $4,000 without asking.
Until you change that math, every process improvement you make will quietly route back through you.
What an approval matrix actually contains
An approval matrix is a short table that answers four questions for each recurring decision: what is the decision, who can make it, within what limits, and what happens when it exceeds those limits.
That's it. No policy manual. One readable page that a new manager could follow in their first week.
Start with the decisions that actually stall work in your business. For most operating companies, the usual suspects are:
- Purchases and vendor commitments above a certain amount
- Discounts, price exceptions, and custom terms on quotes
- Refunds, credits, and warranty calls
- Write-offs, including inventory adjustments and bad debt
- Hiring, contractor engagement, and overtime authorization
- Scope changes on active projects
- Payment terms and credit limits for new customers
Pick the five that generate the most back-and-forth in your inbox. Those are your first five rows.
Set thresholds you'd only be mildly annoyed by
The hardest part is choosing the numbers, and most owners set them far too low. A useful test: pick a limit where, if someone used the full amount on a decision you disagreed with, you'd be mildly annoyed — not furious, not indifferent.
Mild annoyance is the right calibration. It means the limit is high enough to actually remove you from the flow, and low enough that a bad call is recoverable. If your threshold is set so tight that nothing clears it, you haven't delegated anything. You've just documented your bottleneck.
Build two or three bands rather than one. A line manager approves to one level, a department head to the next, you handle what's genuinely above both. Each band should be meaningfully wider than the last, or you've created a relay race instead of a delegation.
Put it in the system, not the handbook
A matrix that lives in a shared doc is a suggestion. A matrix enforced by your ERP is infrastructure.
This is where modern platforms earn their keep. In a system like Odoo, purchase approvals, quote discount limits, expense policies, and credit holds can all be configured as rules tied to amounts and roles, with the approval trail recorded against the transaction. The person who approved it, the time they approved it, and what the record looked like at that moment are all captured without anyone maintaining a spreadsheet.
That matters for three reasons. Approvals stop depending on whether someone saw a message. The audit trail builds itself, which is exactly what a lender, insurer, or acquirer will eventually ask for. And the rule applies consistently, including on the days you're unreachable.
Configure it in a test environment first, walk a few real transactions through it, and make sure the rules don't block routine work before you turn them on for everyone.
Design the exceptions on purpose
Every matrix needs an escape hatch, or your team will build one for you — usually by routing around the system entirely.
Name a backup approver for every role, and make the backup automatic when the primary is out, not something that requires a request. Set a response expectation for anything escalated, so "waiting on approval" has a deadline. And decide what happens in a genuine emergency: who can act first and document after, and what counts as an emergency.
Then review the matrix on a schedule. Quarterly is plenty. Look at what got escalated and ask whether the threshold should move up. Look at what went wrong and ask whether it should move down. A matrix that never changes is one nobody is actually using.
The real payoff
A business that can't make decisions without the owner isn't a business yet — it's a job with employees. Decision rights are what turn the former into the latter, and they're one of the first things a serious buyer, lender, or incoming executive will probe.
If you're rolling out an ERP, or already have one that nobody trusts enough to approve inside, this is the layer worth getting right. Infraxio pairs operator experience with hands-on implementation to turn how you actually make decisions into rules your systems enforce. If approvals are still routing through your phone, let's talk about what it would take to change that.