Your Approvals Take Two Weeks. The Decision Takes Five Minutes.
Your VP of Operations is at a conference for three days. While they are away, a vendor contract renewal sits unsigned, two new hire offers wait in a queue, and a client project cannot move to the next phase because nobody approved the revised scope. The decisions themselves would take five minutes each. The wait takes two weeks.
This is not a scheduling problem. It is a structural one. The approvals that keep your business moving were never designed as a workflow. They evolved from email threads, Slack messages, and hallway conversations into something that looks like a process but has no documentation, no backup path, and no visibility.
According to Asana's Anatomy of Work Index, which surveyed over 10,000 knowledge workers globally, 60% of work time is spent on coordination activities rather than skilled or strategic work. That includes chasing statuses, forwarding requests, and waiting for someone higher up to click 'approved.' The decision is the easy part. Getting it in front of the right person, at the right time, with the right context is where operations stall.
Why Approval Workflows Break at 50 to 200 Employees
At ten employees, approvals work fine because the founder is in the room. At 50, someone set up a shared inbox. At 100, there are three people who can approve different things, but nobody wrote down which person handles which type of request. At 200, the original approver left the company six months ago and their responsibilities were split across two people who were never told.
1. The process was never designed
Most approval workflows at mid-market companies were not planned. They emerged. Someone started forwarding purchase requests to a VP, the VP started replying with 'approved' in the subject line, and over two years that became the official process. Nobody mapped which types of requests need approval, what dollar thresholds apply, or who approves when the primary approver is unavailable. The workflow exists as institutional memory, not as a documented process.
2. Approval authority is tribal knowledge
Ask five employees who can approve a software purchase over $5,000 and you will get four different answers. The actual authority lives in someone's understanding of how things have always been done. When that person goes on leave, gets promoted, or quits, the knowledge leaves with them. New employees learn the approval chain by asking around, and what they learn depends on who they ask.
3. There is no system of record for decisions
Approved requests live in email threads. Rejected requests live in a different email thread, or sometimes in no thread at all because someone said 'no' in a hallway conversation that was never documented. When an auditor, a new manager, or a frustrated employee asks 'who approved this and when,' the answer requires searching through six months of email. If the approver used their phone, the record might not exist.
4. Exceptions became the default
Every company has an 'urgent' bypass for approvals. A client needs an answer by end of day, so someone texts the VP directly. A vendor discount expires Friday, so the purchasing manager gets verbal approval and processes it. Over time, the exception path becomes the primary path, and the official process is something people follow only when they have time. Which is never.
What Broken Approvals Actually Cost
The direct cost is time. A 2025 study by Custom Workflows AI found that 67% of knowledge workers spend more than three hours per day on manual coordination tasks including status updates, chasing responses, and re-routing requests. For a 100-person company where half the team touches approvals regularly, that is roughly 150 hours per week spent on work that produces no output.
The indirect costs are harder to measure but larger. Vendor discounts expire because a purchase order sat in a queue. New hires start two weeks late because the offer letter was waiting for a signature that nobody tracked. Client projects slip because a scope change needed three levels of internal sign-off, and the third approver did not know the request existed.
Accenture's Pulse of Change survey of 3,000 C-suite leaders in mid-2026 found that 82% are increasing their AI and automation investment, but only 23% report sustained, enterprise-wide value from those investments. One of the primary reasons: the underlying workflows were never formalized. You cannot automate an approval process that nobody has documented. You can only make the existing chaos faster.
Six Signs Your Approvals Are the Bottleneck
You do not need a consultant to spot this. Look at your own operations over the last 30 days:
- You cannot name who approves what above $1,000 without checking. If the approval authority matrix is not documented, it is tribal knowledge.
- The same person is the bottleneck for three or more approval types. One executive approving vendor contracts, hiring decisions, and budget changes means every category stalls when they are busy.
- Your team uses the words 'waiting for approval' in standups more than twice a week. If it comes up regularly, the delay is structural, not situational.
- You have no report showing average approval turnaround time. If you cannot measure it, you cannot improve it. And if nobody has asked for the report, nobody has framed it as a problem yet.
- More than half your approvals happen outside the system of record. If the real approval was a Slack message or a text, and the system entry happened after the fact, the system is a log, not a workflow.
- When a key approver is out, work stops or people guess. No documented backup authority means either a bottleneck or unauthorized decisions. Both are problems.
Four or more of these signals means the approval layer is an operational risk, not just an inconvenience.
What Most Companies Try First (and Why It Fails)
Attempt 1: Buy approval software. The company purchases a workflow tool, configures three approval types, and announces the new process. Usage starts strong. Within two months, people route urgent requests through Slack again because the tool adds steps but does not remove the bottleneck. The person who has to click 'approve' is the same person, in the same seat, with the same 200 emails.
Attempt 2: Create a shared tracker. Someone builds a spreadsheet to track pending approvals. For three weeks, the team updates it. Then the tracker itself becomes another thing to maintain, and the person who built it goes on vacation. The spreadsheet is now six days behind reality.
Attempt 3: Add a Slack channel. A #approvals channel appears. Requests are posted. The approver responds when they see it, which might be immediately or might be Thursday. There is no escalation path, no SLA, and no way to tell which requests are urgent versus routine. The channel becomes a queue with no order.
Each of these addresses the symptom without touching the cause. The problem is not that people lack a place to submit requests. The problem is that the approval structure itself was never mapped, the authority was never delegated, and the decision criteria were never written down.
Not Sure Where Your Approvals Are Stalling?
Hidden approval bottlenecks are one of the most common findings in an operations diagnostic. A 30-minute review of your approval chain, delegation rules, and decision routing can show you exactly where the delays are accumulating.
Request a complimentary diagnostic to find out how much time your team loses to approvals every week.
How to Fix the Approval Layer: A Five-Step Audit
Step 1: Map every approval type
Spend one week logging every request that required someone's sign-off. Categorize them: financial (purchases, expenses, budget changes), personnel (hiring, promotions, time off), operational (scope changes, vendor selections, process exceptions), and compliance (data access, security changes, contract terms). Most companies discover they have 15 to 25 distinct approval types. They thought they had five.
Step 2: Document the actual authority chain
For each approval type, write down who currently approves it, what threshold triggers the approval, and who handles it when the primary approver is unavailable. If there is no backup, that is a finding. If the threshold is 'it depends,' that is a finding. The goal is not to design the ideal process yet. The goal is to see what actually happens today.
Step 3: Identify the concentration points
Plot each approval type against its approver. In most mid-market companies, two or three people are responsible for 70% of all approvals. Those are your bottleneck points. Every day those individuals are in back-to-back meetings, traveling, or out sick, the company accumulates a queue that nobody else can clear.
Step 4: Set delegation thresholds and backup authorities
Decide which approvals can be delegated, to whom, and under what conditions. A purchase under $2,000 might not need VP approval at all. A scope change under 10% of contract value might only need a project manager's sign-off. A new software subscription under $500 per month might only need the department lead. Push authority down to the lowest level that can make an informed decision. Document the new matrix and share it.
Step 5: Build the audit trail, then choose the tool
Once you know the types, the thresholds, and the authorities, pick a tool that matches the process you designed. Not the other way around. The tool should enforce the rules: route to the right approver, escalate after a defined period, notify the backup when the primary is out, and log every decision with timestamp and reason. If your existing project management or ERP system can do this, you do not need a new tool. You need a configured workflow.
The Approval Problem Is a Governance Problem
When you trace approval bottlenecks to their source, you usually find a governance gap. The company grew past the point where one or two executives could review everything, but nobody redesigned the decision rights to match the new scale. The executives are not hoarding authority. They inherited it, and nobody took it away.
This is why fixing the approval layer often requires changes beyond the approval itself. It means defining which decisions are strategic (and need senior review) versus operational (and should move without it). It means writing down the criteria for each decision type so the approver is not making a judgment call every time. And it means accepting that pushing authority down is not losing control. It is building the operating model your company's current size actually requires.
Companies that treat their approval process as operations infrastructure, rather than something that just happens, consistently move faster without taking on more risk. The decisions do not change. The routing changes.
How Fill System Helps
Fill System's Process and Operations practice starts with exactly this kind of audit. We map your approval types, trace the actual routing (not what is written in a policy nobody reads), identify concentration points, and design a delegation framework that matches your risk tolerance and company size.
The output is not a software recommendation. It is a documented approval matrix, clear delegation thresholds, and the workflow design to enforce them, whether that means configuring your existing tools or selecting new ones.
Learn more about our approach: Extended Diagnostic.
Next Step
Your team makes dozens of decisions every day. The question is whether those decisions flow through a designed process or through whoever happens to be available.
Request a free diagnostic and find out where your approval chain is costing you more time than the decisions themselves.
Related Reading
Where are your approvals stalling?
Request a free diagnostic and get a clear picture of what to fix first - no commitment, no sales pitch.