There is a document sitting in someone's inbox right now, waiting for approval. It has been waiting for two days. Before that, it waited three days in someone else's inbox. The person who created it spent four hours preparing it. The combined review time, when it finally happens, will be fifteen minutes. This is the approval chain in action — a process that was designed for oversight but has become a mechanism for delay. Cross-functional handoffs cause 60% of process delays, and approval chains are handoffs by design. Each approver in the chain represents a handoff: the document moves from one person's responsibility to another's inbox, where it competes with every other demand on their time. Process inefficiency costs businesses 20-30% of revenue annually, and bloated approval chains are one of the most visible and correctable contributors. This article examines why approval chains grow beyond usefulness, how to identify the ones that are slowing your business, and how to redesign them to maintain genuine oversight whilst eliminating unnecessary delay.

Multi-layer approval chains slow businesses because each additional approver adds waiting time without proportionally increasing quality or risk protection. Most approval chains can be shortened by 40-60% through three changes: establishing clear decision criteria that enable pre-approved actions, reducing the number of required approvers to the genuine decision-makers, and implementing parallel rather than sequential approval for decisions requiring multiple perspectives.

Why Approval Chains Keep Growing

Approval chains grow through a ratchet effect: steps are added in response to problems but never removed when the problems are resolved. A client proposal that once required one approval now requires three because, at some point in the past, an error slipped through single-level review. A purchase that once needed one signature now needs four because a previous employee once misspent funds. Each addition was a rational response to a specific incident, but collectively they create a process where the oversight cost far exceeds the risk it mitigates. 60% of business processes are never documented, and approval chains are often among the undocumented — nobody has formally reviewed whether each approval point still serves its original purpose.

The growth is also driven by management anxiety. Adding an approval layer feels like taking action against risk. It is visible, concrete, and immediately implementable. By contrast, improving training, creating decision frameworks, or enhancing process controls — the approaches that actually reduce risk — are slower, less visible, and harder to implement. The result is that organisations accumulate approval layers as a substitute for genuine risk management, creating the illusion of control whilst actually reducing operational speed. Companies spend 27% of productive time on process debt, and unnecessary approvals are some of the most wasteful forms of that debt.

There is a cultural dimension too. In many organisations, requiring someone's approval is a signal of their importance. Removing that requirement feels like a demotion or a diminishment of their role. This political sensitivity makes approval chains extremely resistant to simplification, even when everyone acknowledges they are too slow. The Process Maturity Model describes the progression from ad hoc through optimised, and approval chain reform is often one of the most challenging steps in that progression because it requires addressing political dynamics as well as process design.

The True Cost of Sequential Approval

Sequential approval — where a document must pass through approvers one at a time, in a fixed order — is the most expensive approval architecture. Each approver adds their review time plus their queue time. If three approvers each take 15 minutes to review but the document waits an average of two days in each inbox, the total process time is six days and 45 minutes — of which 45 minutes is productive review and six days is pure waiting. The waiting is not the approvers' fault; they have competing priorities. It is a structural problem created by the sequential design.

The financial cost compounds with volume. If a business processes 20 proposals per month, each delayed by an average of four days due to approval chains, that represents 80 proposal-days of delay monthly — during which clients may engage competitors, market conditions may change, and internal resources remain committed to pending rather than confirmed work. Process inefficiency costs businesses 20-30% of revenue annually, and approval delays are a measurable component of that cost. Bottleneck elimination in the top three processes yields 80% of possible efficiency gains, and the approval bottleneck is frequently among the top three.

Standard checklists prevent 50% of errors in complex operations, and a properly designed approval checklist — a document that specifies exactly what the approver should verify — is more effective at preventing errors than multiple sequential reviews where each approver assumes the others have checked thoroughly. The diffusion of responsibility in multi-approver chains actually reduces quality because each person in the chain feels less personally accountable. A single well-documented SOP saves 2-3 hours per week per team member who uses it, and an approval SOP that clarifies each approver's specific responsibility improves both speed and quality.

Identifying Which Approvals Are Necessary

Not all approvals are unnecessary. Genuine oversight — ensuring compliance, managing financial risk, maintaining quality standards — is essential. The challenge is distinguishing between approvals that serve these functions and approvals that exist through inertia or political convention. For each approval point in your chains, ask three questions: What specific risk does this approval mitigate? Has that risk materialised in the last twelve months? Could the same protection be achieved without a human approval — through a checklist, a template, or a decision rule?

The DMAIC framework provides the analytical structure. Define the purpose of each approval point. Measure how often it catches genuine issues versus how often it simply rubber-stamps work that was already correct. Analyse whether the protection it provides could be achieved more efficiently. Improve by removing, automating, or redesigning the approval. Control by monitoring whether the change introduces any new risk. Process mapping exercises identify 25-35% waste in existing workflows, and in approval-heavy workflows, the waste percentage is typically at the higher end because waiting time dominates cycle time.

Categorise your approvals into three tiers. Strategic approvals — decisions that commit significant resources, affect client relationships, or create legal obligations — genuinely require senior review. Operational approvals — routine decisions that follow established patterns — can often be handled through pre-approved criteria or delegated to the practitioners. Administrative approvals — low-risk, high-frequency actions like minor purchases or schedule changes — should be eliminated or automated entirely. Process standardisation reduces error rates by 50-70%, and standardised decision criteria often provide better protection than individual judgement on routine matters.

Redesigning Approval Chains for Speed and Quality

Three design principles transform bloated approval chains into efficient oversight systems. First, parallel approval: when multiple perspectives are genuinely needed, have all approvers review simultaneously rather than sequentially. This collapses the waiting time from days-per-approver to the duration of the longest single review. Second, conditional approval: not every item needs every approval. A purchase under £1,000 might require one signature, while one over £10,000 requires two. The criteria should be explicit, documented, and embedded in the workflow.

Third, approval by exception: establish clear standards and templates, and allow work that meets those standards to proceed without individual approval. Only items that deviate from standards require review. This approach transforms the approver's role from routine gatekeeper to exception handler, dramatically reducing their queue whilst focusing their attention on the items that genuinely need judgement. Workflow automation delivers an average ROI of 400% within the first year, and automated routing — sending items to the appropriate approval path based on predefined criteria — is one of the most impactful forms of workflow automation.

The redesigned chain should be documented as a clear SOP that specifies: what requires approval, who approves it, what criteria they should verify, what the expected turnaround time is, and what happens if the approver does not respond within that timeframe. Companies with documented processes grow twice as fast as those without, and a documented approval process is a visible commitment to both oversight and efficiency. Process owners who review quarterly improve efficiency by 15% year-on-year, and the approval chain should be reviewed quarterly to ensure it remains appropriate as the business evolves.

Creating Decision Frameworks That Replace Approvals

The most effective way to reduce approval burden is to replace individual decisions with frameworks that enable pre-approved action. A decision framework specifies the criteria under which a particular action is automatically approved, the conditions that require escalation, and the boundaries of individual authority. For example: 'Client discounts up to 10% are approved at the account manager level. Discounts of 10-20% require sales director approval. Discounts above 20% require CEO approval.' This framework eliminates the approval step for the majority of discount decisions whilst maintaining oversight for significant ones.

The Theory of Constraints applies directly: the approval bottleneck exists because all decisions, regardless of significance, flow through the same constrained resource. Decision frameworks create multiple processing paths based on significance, reducing the volume that reaches the senior decision-maker and accelerating the routine items. A single well-documented SOP saves 2-3 hours per week per team member who uses it, and a decision framework SOP saves time for both the decision-maker (who reviews fewer items) and the practitioner (who acts without waiting).

Building effective decision frameworks requires input from the current approvers. They know which decisions are routine and which genuinely require judgement. Their involvement in framework design also addresses the political sensitivity of removing approval authority — they are defining the boundaries of delegation rather than having authority taken away. Employee turnover costs approximately twice the departing employee's salary, and documented decision frameworks reduce this cost by ensuring that decision-making authority is structural rather than personal — it survives personnel changes because it is embedded in the system rather than in any individual's role.

Implementing Changes Without Creating Chaos

Approval chain reform should be phased to manage risk. Begin with one approval chain — preferably one that is visibly frustrating and involves low-risk decisions. Redesign it, implement the change, and measure the results over four weeks. If the simplified chain maintains quality whilst reducing cycle time, use the results to build the case for reforming additional chains. Only 4% of companies have integrated their processes end-to-end, and incremental reform that demonstrates results builds the organisational confidence needed for broader change.

During the transition, implement monitoring to catch any issues that the old approval points would have caught. Standard checklists prevent 50% of errors, and a monitoring checklist that reviews a sample of decisions made under the new framework provides assurance without reintroducing the old bottleneck. If the monitoring reveals genuine issues, adjust the framework rather than reverting to the old chain. Process owners who review quarterly improve efficiency by 15% year-on-year, and the first quarterly review after implementation should specifically assess whether the reformed chain is performing as intended.

Communicate the changes transparently. Explain why the approval chain is being simplified, what oversight mechanisms replace the removed steps, and how the change benefits both the team (faster decisions) and the business (reduced cycle times and costs). Process inefficiency costs businesses 20-30% of revenue annually, and framing approval reform as a revenue-protection measure rather than a risk-taking exercise helps secure buy-in from stakeholders who might otherwise resist the simplification.