Approval bottlenecks: why documents wait weeks for approval

Approval bottlenecks are the choke points in approval processes – the places where documents, requests or decisions stall for days or weeks even though the actual review takes only minutes. In practice it is every situation where process speed depends not on its complexity, but on whether a specific person gets around to opening an email or a shared folder.

Operationally, a bottleneck appears wherever three things coincide: no clear approval path, no SLA for each step and no tool that knows where the document currently sits. Each is tolerable on its own. Together they create friction that multiplies with organisational scale.

A classic example: a supplier invoice arrives, an assistant routes it to a shared inbox, someone notices it two days later, sends it to budget approval, the manager is on holiday, the second authoriser does not reply, finance chases up a week later. A decision that should take 30 minutes ends up taking 12 working days. That is not a people failure – it is a missing workflow.

The first and most common reason is approvals over email. The message reaches a manager, who forwards it for budget approval, the next person adds a question to legal, legal replies „I need to check this”. A week later nobody remembers the original request, who said yes and who said no. Email is a great communication tool and a poor process tool.

The second reason is the absence of SLAs. Operationally mature organisations know that every stage should have an explicit time: manager approval within 24 hours, finance within 48, legal within 72. Without that, even the most motivated people defer decisions to „later”, because everyone has more important things on their desk than approving someone else's documents.

The third reason is the absence of reminders. A workflow without automated nudges relies entirely on participant memory. One forgotten email on a Friday afternoon is five days of delay. Five forgotten emails a month inside one team is a quarter of an FTE that the organisation does not even book as a cost.

The fourth reason is missing ownership. When nobody owns a specific approval process, the document becomes a matter „between departments” – which in practice means nobody's matter. This is one of the reasons we recommend that document automation starts with organising the document workflow. Without ownership, every technology rollout ends in the same chaos in a new skin.

The fifth reason is too many approval layers. In many organisations every invoice above a modest threshold must pass through four to six approvals, including at least two that add no actual business decision. These layers are usually leftovers from older policies nobody dared to revise. Each extra layer adds 24–48 hours of delay. The sixth reason is tool sprawl – some approvals run by email, some in Teams, some in SharePoint, some in an Excel macro. Without a single workflow, the organisation loses visibility into where the case actually is.

The strongest argument for approval workflow automation is the scale of hidden costs that rarely show up in spreadsheets. The most visible is project delay. Every project depends on decisions – supplier contracts, advance invoices, change requests, security policies. A weekly delay on each of these stacks into 4–8 weeks of overall delay, which in many organisations is a meaningful time-to-market cost.

The second cost is lost margin. In procurement, an invoice not processed in time means a missed early-payment discount or a late-payment penalty. In sales, a slow quote approval means the customer moves to a competitor. In capital projects, every week of delay pushes back the moment of revenue from the asset. These costs are real but rarely measured because they do not fit into a traditional cost line.

The third cost is compliance risk. Documents waiting in inboxes outside the system are documents without an audit trail. In case of a regulator inspection or internal audit, the organisation cannot answer who approved the contract, when and on what basis. In regulated areas (medtech, fintech, energy, public sector) the lack of auditability can lead to financial penalties and loss of certifications.

The fourth cost is employee frustration. Operations, finance, legal and project managers spend a significant share of the day chasing other people's approvals – sending „pings”, escalating to managers, explaining to customers that „we are waiting for sign-off”. This is work that creates no value but burns out back-office teams. Engagement surveys regularly list it as a top reason for turnover in support functions.

The fifth cost is the lack of scalability. In organisations growing faster than their hiring capacity, manual workflows become a rigid brake on scale. Every new customer, project or product adds more decisions to be handled by the same team. At some point hiring more people stops scaling efficiency – it just multiplies the number of people writing approval emails.

The sixth cost is slower business decisions. The board does not see backlogged approvals because there is no dashboard showing process state. Operations directors do not see team load because nobody logs time spent on „chasing approvals”. Without workflow, there is no data to make priority decisions. The seventh cost is lost productivity – conservative industry estimates put 10–30% of operational team time on approval coordination. At an annual scale this is six- or seven-figure money that nobody books but everyone feels.

A modern approval workflow is not „email but electronic”. It is a structured process with four layers: the document layer (where the file lives and how versions work), the decision layer (who approves, in what order, on what basis), the communication layer (notifications, escalations, comments) and the audit layer (what trace every decision leaves behind). Each of these can be designed deliberately or improvised – and improvising is what costs organisations the most.

The starting point is a digital workflow where the document lives in one place (typically SharePoint or Teams) and approvers receive their tasks in the tool they use every day. There is no „forwarding the file by email” – there is a Teams notification, an Outlook task or a Power Automate mobile alert, and approval is a 10-second action.

The second layer is approvals automation. The workflow knows who owns each step based on document metadata (amount, department, contract type). Reminders go out automatically after 24 hours. After 72 hours the case escalates to a manager. The audit trail builds itself – who, when, what they approved and with what comment.

The third layer is visibility. Everyone in the process sees in one dashboard where each case stands, who has held an approval longer than the SLA and where the most frequent bottlenecks are. Operations use this for day-to-day management, leadership for monthly and quarterly process reviews. The fourth layer is mobile approvals – a sales director can approve from a phone on the way to a meeting, shortening the decision cycle from days to minutes. The fifth and most modern layer is AI-assisted workflow, where a language model summarises the document before approval and classifies it automatically – we cover that in the Copilot section below.

For organisations in the Microsoft ecosystem, SharePoint and Power Platform are the natural foundation for approval workflows. SharePoint provides a document library with versioning, metadata, access control and a full audit trail – everything the approval process needs as a document layer. Every document has one canonical version, a change history and clearly assigned permissions.

Metadata is the underappreciated element. A well-designed SharePoint library carries not only the file but also: document type (contract, invoice, policy), amount, department, customer, approval status, required decision date. These metadata feed every automation – the workflow knows who to route an approval to because it reads the „department” and „amount” fields.

Power Automate is the process layer. It defines that a document tagged „invoice” with „amount > 50 000” goes to finance approval with a 48-hour SLA, and above 200 000 also to board approval with a 72-hour SLA. The workflow handles escalations, reminders, parallel approvals and conditional approvals. In practice, most organisations need 10–20 workflow variants to cover 80% of cases.

Teams integration is now standard. Approval notifications land in Teams as adaptive cards – with a document summary, „Approve / Reject / Return with a comment” buttons and a direct link to the file. The employee never leaves Teams or logs into a separate workflow system. Approval takes 15 seconds instead of five minutes.

All of this requires governance. SharePoint without governance quickly turns into an archive where nobody finds the current version. That is why deployment does not end with workflow configuration – it includes naming standards, versioning rules, retention policies and a change process for the workflow itself. The same principle we describe for implementing monday.com as a central process management system applies here: without governance, any platform becomes chaos.

A Power Automate workflow solves the process layer – who approves, when, in what order. It does not solve the decision layer: the employee still has to read the document, understand it and decide. This is where Microsoft Copilot and AI in approval processes come in – a layer that shortens the time needed for an informed decision, not just the time needed to click.

The first use case is AI summaries. Copilot analyses the document and generates a 3–5 sentence summary of key elements: parties, amount, deadlines, non-standard clauses, risks. The approver sees this summary together with a link to the full document. In practice this shortens decision time from 15–20 minutes to 2–3 minutes – not at the cost of quality, but at the cost of routine skim-reading of repeatable sections.

The second use case is intelligent routing. The model classifies the document from its content: it recognises an NDA, a licensing agreement, a cost invoice or a project document and automatically sets the metadata the workflow needs. The employee no longer chooses the document type manually – the system does it with accuracy above 95% in stable domains.

The third use case is document classification and data extraction. For an invoice, Copilot recognises supplier, tax ID, amounts, dates and PO numbers. These values land as metadata in SharePoint and as workflow inputs. This eliminates manual transcription from file to system – one of the biggest hidden costs in accounts payable.

The fourth use case is AI notifications and recommendations. The system not only flags pending documents – it analyses approval history in the organisation and suggests typical decisions („similar contracts in the last 12 months were approved without changes”) or flags anomalies („this clause deviates from the company template”). This turns the approver's role from administrative into substantive.

The fifth use case is AI copilots for documents. The approver can ask Copilot: „show clauses that deviate from our template”, „find similar contracts from the last year”, „summarise the financial obligations in this document”. Copilot answers in seconds and the employee makes the decision with full context. All of this requires a governance layer – AI models in approval processes are an area where AI governance for enterprise should be designed up front to keep control over sensitive data and decision auditability.

Not every process needs the same level of workflow automation. The highest ROI is in processes with high volume, repeatable decision structure and a visible cost of delay. The first group is contracts – NDAs, customer contracts, service agreements, supplier agreements, project contracts. Each shares a similar skeleton and requires legal, business and finance approval. Workflow shortens cycles here from weeks to days.

The second group is cost invoices (accounts payable). It is the highest-volume process in most organisations and the most repeatable. A well-designed workflow with OCR and AI data extraction handles 70–80% of invoices without human input – the employee sees only exceptions. For companies with hundreds of invoices a month this is hundreds of hours saved monthly.

The third group is HR processes: onboarding, leave requests, equipment requests, role changes, certificates. Each typically requires 3–5 approvals across departments. Without workflow they sit in HR and manager inboxes for weeks. With workflow they close in 24–48 hours.

The fourth group is procurement – RFQs, order approvals, change requests, supplier contract amendments. This area has a direct financial cost of delay (early-decision discounts, late penalties). Workflow integrated with ERP gives full control over the purchasing cycle.

The fifth group is quality documentation and CAPA (Corrective and Preventive Action) – a critical area for medtech, pharma, manufacturing and anywhere ISO/GMP regulations apply. Approval workflows for procedures, instructions, risk assessments and corrective actions are not just optimisation – they are a compliance requirement. The sixth group is project documents – scope, change requests, milestone sign-offs, final reports. Without workflow, PMI/PRINCE2 projects lose rhythm and predictability. In this area we typically combine workflow with document automation solutions at the broader operational strategy level.

The first and most common mistake is automating the wrong process. The organisation decides to improve invoice approval but keeps six approval layers, three of which add no decision value. The workflow then automates chaos – it just makes the document arrive faster at the same bottleneck. The first step should always be process simplification, not automation.

The second mistake is overengineering. A workflow handling 35 decision variants, 12 roles and 8 escalation paths looks perfect on paper and is impossible to maintain in practice. Experience shows that 5–7 workflow variants typically cover 80% of cases – the remaining 20% is better handled as manual exceptions than forced into the workflow.

The third mistake is missing governance. A workflow designed at the start of the year stops matching reality six months in – amount thresholds change, roles change, discount policies shift, the company structure evolves. Without workflow owners and regular review, configurations drift away from reality and employees start bypassing the workflow „because it does not work”.

The fourth mistake is overly complex approval chains. Each additional approval layer adds 24–48 hours to the cycle. Auditing the number of approval layers is often the cheapest improvement – in many organisations two layers replace five without loss of control, because the removed ones were a formality.

The fifth mistake is poor UX. A workflow that requires logging into a separate system, clicking through four screens and filling in fields nobody uses is destined to be ignored. The best workflows live inside tools employees use daily – Teams, Outlook, mobile apps. Approval should be one click. The sixth mistake is missing ownership – a workflow without a business owner becomes an IT matter, and IT should not decide on business processes. Without an owner, workflows stop evolving.

A successful workflow automation deployment starts with process analysis, not tool selection. In practice this means mapping the 3–5 most costly approval processes: how many documents per month, how many stages, average cycle time, most frequent stall points, cost of delay. Without these data, any automation decision is built on intuition.

The second step is a workflow audit – diagnostics involving business, operations, IT and compliance. The audit answers questions like: which approval layers are required and which are leftovers from old policies, where do the biggest bottlenecks emerge, what metadata do we need so the workflow can route automatically.

The third step is the governance design. A workflow does not exist in a vacuum – it is part of a wider process and data architecture. Decide up front: who owns each workflow, who approves configuration changes, how new variants get introduced, how we measure effectiveness. Without this layer the project becomes one-off.

The fourth step is phased deployment. Start with one process with high volume and a clear cost of delay – usually cost invoices or NDA contracts. After 4–6 weeks of piloting you have data and trust to expand into further processes. Deploying everything at once typically ends with the project shelved.

The fifth step is change management. Workflow automation changes daily work for dozens or hundreds of people. Without short, practical training, clear documentation („when do I use the workflow, when an email”) and a feedback channel to the business owner, users drift back to email within two weeks. We run these stages with clients as part of advisory and strategy and implementation and growth engagements, so the process, technology and organisational layers are built in parallel.

Approval bottlenecks are one of the most pervasive and most underestimated sources of operating cost in mid-size and large organisations. Weeks spent waiting for sign-off on contracts, invoices, policies and requests do not come from a lack of employee engagement – they come from the fact that an email workflow is the slowest possible way to run a process. Every organisation that does not see this pays for it every day in hidden operating costs, compliance risk and team frustration.

Workflow automation built on SharePoint, Power Automate and Microsoft Copilot reshapes the picture: the document lives in one place, the decision is a single click in Teams, the audit trail writes itself, and dashboards show where each case is and who has been holding an approval longer than the SLA. The AI layer further compresses decision time by summarising the document and suggesting an action – but only if the process is structured first. AI without a good process is just a faster version of chaos.

The most sensible first step for organisations considering workflow automation is not the tool choice, but an audit of the three most costly approval processes and a decision on which one to pilot first. At AlgorComp we support clients in this work as part of advisory and strategy and solution design – connecting the process, technology (SharePoint, Power Platform, Copilot) and organisational layers into one measurable system. Decisions that today take weeks can close in hours – but only if the organisation chooses to design them rather than improvise.