Approvals and permissions: how can we simplify while maintaining control?

Two office colleagues examine a docking station and purchasing documents during a procurement review.

Reviewing the business need behind a purchase request takes just a few minutes, yet the request sits in managers’ inboxes for days. The first approver checks whether it is necessary, the second repeats the same check, and the third is involved only because all requests used to be routed to them. Meanwhile, it is not always clear who checks the budget and who is responsible for supplier risk.

The simplification of the approval process does not mean abandoning checks across the board. The aim is for every decision to be made where relevant information and appropriate authority are available. At this stage of business process optimization, we fine-tune operations that have already been mapped: reducing unnecessary waiting, clarifying responsibilities and ensuring demonstrable control.

1. First, clarify what approvers actually check

During the assessment, do not simply ask how many signatures are required. Assign a specific control objective to every approval step. Whether the equipment is needed, whether the budget is available, whether the supplier is suitable and whether the contractual terms are acceptable are separate questions. If these are blurred together, more signatures will not guarantee a more thorough review.

It is worth tracing a few completed purchases from submission through to ordering. Alongside the process diagram, record waiting times, requests sent back for correction and decisions made by email outside the system. This reveals where genuine control is exercised and where requests are merely forwarded.

  • Decision objective: what risk does this approval reduce?
  • Information: does the approver have data that no one else has reviewed yet?
  • Authority: can they actually make a decision, or do they simply forward the request?
  • Consequence: what would happen if this step were replaced by a predefined rule or another check?

A signature used solely to keep someone informed can often be replaced with a notification. Mandatory checks, however, must not be removed simply to speed things up: their legal, contractual and internal policy basis must first be clarified.

Charcoal technical schematic separates a non-blocking notification branch from a mandatory control gate on the main approval route.

2. Simplify with risk-based routing

Applying the same decision chain to every case can easily overload managers. A regularly ordered item from an approved catalog does not require the same checks as an agreement with a new supplier containing unusual terms. Value is an important consideration, but it is not sufficient on its own.

When designing decision routes, factors beyond value may include the procurement category, budget availability, supplier rating and any departure from standard contractual terms. In IT procurement, for example, data processing or access risks may justify a separate specialist review even for lower-value purchases.

Three illustrative decision routes

  • Standard case: approved supplier, familiar item, available budget. Depending on internal policy, a decision by one accountable person or automatic forwarding within a pre-approved budget may be sufficient.
  • Higher-risk case: new supplier, higher value or unplanned expenditure. Additional financial, procurement or management controls are required.
  • Exceptional case: bespoke contract, sensitive data processing or a flagged conflict of interest. A targeted specialist review and documented justification are needed.

These are design patterns, not universally applicable corporate rules. Specific thresholds and exceptions must be tailored to the organization’s own risks. If several rules apply simultaneously, their order of precedence must be clear. Missing risk data should not automatically trigger the most permissive route.

3. Link permissions to roles, case data and status

Shortening the decision chain is safe only when precise access rules are in place. The “manager” role alone is too broad: it does not specify which organizational unit’s cases the person can handle, up to what value or which actions they are authorized to perform. Permission design must therefore account for several conditions together.

  • Role: the requester enters the request, the budget owner makes the decision and the buyer prepares the order.
  • Case data: decision-making authority may depend on the cost center, company, category and amount.
  • Status: a draft can be edited, but key details of a request that has already been decided on may only be amended through a controlled change procedure.

Viewing, editing, approval and administration should each have separate permissions. An employee tracking progress is not necessarily authorized to view quotations or contract attachments. Access should be restricted to the data needed for the task at hand.

Establish separate rules for self-approval and segregation of duties. If the requester is also the budget owner, the process should assign another decision-maker where necessary. Delegation should be limited in duration and scope, logged and revocable. Absence should neither halt work nor create unrestricted authority.

Split view contrasts a cluttered paper approval desk with an abstract digital workflow separating requester, approver and limited delegation.

4. Procurement example: targeted checks instead of waiting in line

Consider an illustrative business scenario: every equipment request goes first to the line manager, then to the department head, finance and finally procurement. The assessment reveals that the first two managers often review the same business need, while missing information is not identified until the final step.

Redesign does not start by simply removing a signatory. First, clarify the submission requirements and who is responsible for each check:

  1. A complete request is submitted. The required information includes the item, justification, cost center, estimated value and relevant attachment.
  2. Rules determine the route. Standard requests go to the appropriate budget owner; exceptions trigger additional review.
  3. Independent checks run in parallel. If financial and technical reviews do not depend on each other's findings, they can be performed simultaneously.
  4. The order proceeds only when all conditions are met. Managers who need to be informed receive a notification, not another mandatory decision task.

When introducing parallel processing, you must also define what happens if a request is rejected: are the other tasks canceled, suspended or continued? Handling subsequent changes is equally important. If the amount or supplier changes after approval, the system must initiate a new review in accordance with policy.

When planning xFLOWer-based process optimization, these decision criteria, access permissions and exception paths should be consolidated into a shared set of requirements. During implementation, verify separately whether the specific configuration and connected systems actually support the expected functionality, such as providing up-to-date budget data.

5. Measure speed and control together

It is advisable to start implementation with a clearly defined procurement category. Record the baseline before making changes, then assess the results using a comparable mix of cases. If more straightforward requests arrive in the new period, this alone may improve the average, so evaluate results by risk category as well.

  • Turnaround and waiting time: how much time elapses between submission and decision, and how much of that is spent waiting in a queue?
  • Approval rounds: how many substantive approvals take place per case?
  • Requests for missing information: how often are requests returned, and for what reasons?
  • Exceptions: how many cases require manual intervention or a different procedure?
  • Control failures: do unauthorized decisions, self-approvals or changes without review occur?

Testing should also cover cases at approval thresholds, missing budget data, delegation and revoked permissions. The decision log must make it possible to trace who made a decision, when, based on which data and under which version of the rules. Rule changes require a designated owner, approval and documented deployment to production.

The pilot can be considered successful if, alongside faster processing, the predefined control requirements are also met. Shorter turnaround times alone are not a success if they result in more incorrect or improperly authorized orders.

Unlabeled abstract line, bar, donut and audit graphics give equal emphasis to processing speed and control checks.

6. Summary: fewer signatures, clearer accountability

Simplifying the approval process is sustainable when every remaining check has a clear purpose. Risk-based routing, precise permissions, controlled delegation and traceable decisions work together to ensure that faster operations do not mean weaker control.

Would you like to identify which approval rounds could be simplified at your company? Consult xFLOWer experts about reviewing a selected procurement process. A joint assessment of decision objectives, permissions and waiting points can provide a concrete basis for a measurable, controlled optimization pilot.

This article is part of our comprehensive guide: Business process optimization: a comprehensive guide to improving existing workflows

xFLOWer.ai

Design the process behind this article – for free!

AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.

Contact us

Let's talk about your processes

Tell us briefly which process you'd like to automate – we'll get back to you within 1 business day.