The Approval Black Hole
A vendor contract sits in someone's inbox for three weeks. An investment proposal waits "for the next leadership meeting." A budget reallocation needs "one more review."
Individually, each delay seems reasonable. Collectively, they create an invisible drag on the entire organisation. Decisions that should take days take months. Opportunities expire while waiting for sign-off.
The Real Cost
A McKinsey study found that fast decision-making organisations are 2x more likely to make high-quality decisions than slow ones. Speed doesn't sacrifice quality - bureaucracy does.
Why Approvals Stall
1. Nobody Knows It's Waiting
The request went to the right person, but it's buried in their inbox with 200 other emails. They're not ignoring it - they don't know it's urgent. Or that it's there at all.
2. Unclear Ownership
"I thought finance was handling this." "We were waiting for legal." "Didn't procurement need to sign off first?" When ownership is unclear, everyone assumes someone else is responsible.
3. Missing Context
The approver receives a request but lacks the background to make a decision. They need to schedule a meeting, ask for more information, review related documents. Each step adds days.
4. Fear of Being Wrong
Saying "yes" creates accountability. Saying "no" creates conflict. Saying nothing? That's safe. Requests languish because approvers avoid the discomfort of deciding.
5. No Escalation Path
When an approval stalls, what happens? In most organisations: nothing. There's no automatic escalation, no visibility into the queue, no consequence for delay.
The Cascade Effect
Stuck approvals don't just delay one thing. They cascade:
- A delayed vendor decision blocks procurement from negotiating terms
- A stalled budget approval freezes three hiring decisions
- An unsigned contract means the project can't start, which delays the product launch
By the time the original approval finally happens, weeks of downstream work have been wasted waiting.
What Actually Works
Organisations that move fast share common practices:
Visibility
Everyone can see what's waiting for approval, who owns it, and how long it's been pending. No more "I didn't know it was stuck."
Clear SLAs
Every request type has an expected response time. Investment proposals: 5 days. Budget reallocations: 3 days. Contract renewals: 7 days. Expectations are explicit.
Automatic Escalation
If an approval exceeds its SLA, it automatically escalates. The approver's manager gets notified. Leadership sees a dashboard of overdue items. Accountability is built in.
Context Included
Requests arrive with everything needed to decide: the business case, the financial impact, the risks, the alternatives considered. No back-and-forth required.
The Mindset Shift
Fast organisations treat "no decision" as worse than "wrong decision." A wrong decision can be corrected. A non-decision just accumulates cost while everyone waits.
Measuring Approval Health
If you want to improve approval velocity, start measuring it:
- Average decision time: How long from request to resolution?
- Queue depth: How many requests are pending right now?
- Overdue rate: What percentage exceed their SLA?
- Escalation rate: How often do approvals need to be pushed up?
Most organisations have no idea what these numbers are. That blindness is the problem.
How FireBreak Helps
FireBreak workflows give you complete visibility into every pending approval. See what's waiting, who owns it, and how long it's been stuck. Automatic notifications keep things moving. Escalation rules ensure nothing falls through the cracks. And full audit trails mean every decision is documented and defensible.