Ask an operator where the bottleneck is and you'll usually hear a department: "fulfillment is backed up," "sales ops can't keep up." Watch the work for a week and you'll often find something else. The job isn't stuck in a department. It's sitting in someone's inbox, waiting for a yes.
Approvals are the quietest form of operational drag. Nobody logs them. They don't show up on a dashboard. But a purchase order that waits two days for a signature, a discount that waits for the owner to get off a plane, a new vendor that waits for someone to confirm the terms are fine — those pauses compound across every order, every quote, every hire.
Why Approvals Accumulate
Most approval steps were created for a good reason. Someone made an expensive mistake, and a checkpoint was added to make sure it didn't happen again. That's reasonable. The problem is that checkpoints are easy to add and nearly impossible to remove. Five years later the company is ten times larger, the person who made the mistake is long gone, and the owner is still personally approving every expense over a few hundred dollars.
The second reason is trust that never got written down. The owner knows which discounts are acceptable and which aren't. That knowledge lives in their head, so every borderline case has to route through them. The team isn't incapable — they just have no stated rule to work from, and guessing wrong is worse than waiting.
Run an Approval Audit
Before you fix anything, find out what you actually have. Spend a week logging every decision that required someone else's sign-off. For each one, capture four things:
- What was being approved, and who approved it
- How long it waited before someone looked at it
- Whether the answer was ever anything other than "yes"
- What would plausibly have gone wrong without the step
That last column is the honest one. If an approval has been granted every single time for two years, it isn't a control. It's a formality with a delay attached. If it occasionally catches something real, it's worth keeping — but probably not in its current form.
Convert Judgment Into Thresholds
The fix for most approval bottlenecks isn't removal, it's conversion. Take the judgment that currently lives in one person's head and express it as a rule with boundaries.
Instead of "the owner approves discounts," write: discounts up to a set percentage are the rep's call; above that, they need the sales manager; above a higher line, they need the owner. Instead of "I approve purchases," set a spend limit per role, a higher limit for pre-approved vendors, and a clear escalation path for anything new.
What you're doing is making the easy cases automatic so the hard cases get real attention. Most approvals aren't close calls. When you stop routing the obvious ones through a person, the genuinely risky ones stop getting rubber-stamped in a batch at 11pm.
Write the thresholds down where people work, not in a policy document nobody opens. A rule that lives in a PDF is a rule the team will keep asking about.
Let the System Hold the Line
This is where software earns its keep. Modern ERP platforms — Odoo included — support approval rules natively: spend limits by role, multi-step routing based on amount or category, automatic escalation when something sits too long, and a complete audit trail of who approved what and when.
The practical benefit is that the rule gets enforced without anyone policing it. A rep can't quote outside their band. A purchase above a limit routes itself. Nobody has to remember the policy because the system won't let them break it, and nobody has to chase an approval because the approval chases them.
The audit trail matters more than people expect. When a controller, an auditor, or a prospective buyer asks how spending is controlled, "here is the rule and here is every decision it produced" is a far better answer than "the owner looks at everything."
Review the Exceptions, Not the Transactions
Once thresholds are in place, the owner's job shifts from approving work to reviewing patterns. Each week, look at what hit escalation. Are reps consistently pushing against the discount ceiling? Maybe pricing is wrong. Is one category constantly exceeding limits? Maybe the limit was set with stale numbers.
Thresholds should move. Raise them as the team proves itself, tighten them where the audit shows real risk. That's the difference between a control system and a bottleneck: one adapts, the other just waits.
The Bigger Payoff
A business where every meaningful decision routes through the owner isn't a business yet — it's a job with employees. Converting approvals into enforceable rules is one of the most direct ways to reduce that dependence. It speeds up the work, it makes the company easier to hand off, and it makes the operation legible to anyone evaluating it from the outside.
If your team is waiting on you more than you'd like, we can help you map where decisions stall and build the thresholds and system rules that unstick them. Reach out to Infraxio and let's look at your approval paths together.