How to Design a Purchase Order Approval Workflow People Will Actually Use

The most common approval design mistake is building the flow around the scariest purchase anyone can imagine. The result is a five-step chain applied to a box of printer paper, which trains everyone to route around it.

Start with the distribution, not the policy

Pull last year's purchases and plot them by value. In a typical mid-market company, something like eighty percent of transactions sit under a few thousand dollars and account for a small share of total spend. Those transactions should be nearly frictionless. The remaining twenty percent deserve real scrutiny.

Those numbers are a starting shape, not a recommendation. Set them where your own distribution makes them meaningful.

Route in parallel wherever you can

Sequential chains multiply delay. If finance and procurement are both reviewing the same request for different reasons, they should review it at the same time. Reserve sequential steps for cases where the second approver genuinely needs the first one's decision.

Give approvers something to decide with

An approval request that says 'Consulting — $18,000' is not a decision, it is a rubber stamp. The approver needs the budget remaining for that cost centre, whether a contract already covers it, what the alternatives were, and what happens if it is declined. Put that in the request, not in a follow-up thread.

Measure the workflow, not just the spend

• Median time from request to approval, by band.
• Percentage of requests approved with no comment (a proxy for rubber-stamping).
• Percentage sitting with an unavailable approver.
• Rejection rate — if it is near zero, the workflow is theatre.

A workflow that approves everything in four days is not a control. A workflow that approves routine spend in four minutes and genuinely argues about the large ones is. Once the bands are set, write them down in the procurement policy and watch the cycle time and bottleneck metrics for the first two quarters.

Start with the operating case, not the feature list

Context matters in approval workflow design because the visible transaction is only the final record of several earlier decisions. Consider this operating case: A $12,000 software request waits nine days because it routes serially through a manager, VP, finance, IT, security, legal, and procurement even though four reviews could occur at the same time. The useful question is not whether a form was completed. It is whether the evidence available at that moment was sufficient for a named owner to make a reversible, explainable decision. That distinction keeps the process practical: control is attached to consequence, not paperwork.

Trace one ordinary case and one awkward case from the first request to the final accounting entry. Record who knew what, which system held it, and what happened when the expected path failed. This exposes handoffs that a workshop diagram misses: the spreadsheet used to repair supplier names, the inbox where an approver asks for context, or the monthly reconciliation that makes reports believable after the fact.

Evidence to assemble before changing the process

Do not begin configuration with a blank workflow canvas. Build a small evidence pack first. It should be compact enough for the working team to challenge line by line, and representative enough that a successful pilot means something. The minimum useful pack contains the following inputs.

• Spend distribution by amount, category, department, and legal entity
• Budget ownership and delegation rules
• Risk triggers for security, privacy, legal, and supplier diligence
• Historical cycle time at every approval step

The decisions the workflow must make explicit

A dependable approval workflow design process does not ask everyone to approve everything. It identifies a small set of decisions, assigns each to the person with the authority and information to make it, and records enough context to explain the result later. If two reviewers are checking the same fact, remove one. If nobody can state what would cause rejection, the step is probably ceremonial.

• Which reviews are authority checks and which are specialist assessments
• Which steps can run in parallel
• What amount and risk thresholds justify extra control
• How absence, delegation, rejection, and resubmission should behave

Write these decisions as testable statements. For example: approve when the budget is available and the need is valid; route to security only when company data enters the service; reject when the supplier identity cannot be verified. Testable rules make demos, implementation workshops, and post-launch audits materially more useful than labels such as finance review or procurement check.

A practical implementation sequence

Sequence matters because teams otherwise automate the cleanest diagram and discover the real exceptions after launch. Keep the first release narrow, but do not make it artificially easy. Include enough volume to observe behaviour and at least one category with meaningful exceptions. A sensible sequence is:

1. 1Plot real approval paths from recent transactions
2. 2Remove approvers who cannot articulate a decision they own
3. 3Parallelise independent reviews and set response expectations
4. 4Pilot thresholds, inspect overrides, and adjust using observed distributions

At each step, preserve a manual recovery path and name the person allowed to use it. Recovery is not failure; invisible recovery is. An exception handled in a private message teaches the system nothing. An exception recorded with a reason can inform the next policy or configuration change.

Failure modes worth testing before launch

Happy-path acceptance testing proves very little. Build tests from the cases that cause delay, uncontrolled commitment, duplicate work, or misleading reporting. The following failures are common enough to deserve an explicit owner and expected response before rollout.

• Adding senior approvers to every request for visibility
• Routing by job title rather than budget accountability
• Restarting the full chain after a minor correction
• Allowing permanent delegates with no review date

Run these as tabletop exercises with the requester, approver, finance operator, and system administrator in the same room. If the answer depends on somebody remembering an unwritten convention, document it or redesign the path. If the answer requires administrator intervention for an ordinary exception, calculate that support load before declaring the workflow scalable.

Measure the control without gaming it

A metric needs a stable denominator, a reproducible source, and an owner who can change the result. Publish the definition beside the number. Show medians with a tail percentile where time is involved, and split rates by material populations rather than averaging unlike work together.

• Median and 90th-percentile approval time
• Queue age by approver and decision type
• Requests returned for missing information
• Override and escalation rate by threshold band

Review the underlying records monthly during rollout, then quarterly once behaviour stabilises. A rising exception rate can mean the process is deteriorating, but it can also mean the system has started recording exceptions that were previously invisible. Interpret the movement before rewarding or correcting anyone.

Limits and cases that need a different tool

No approval workflow design design is universal. State exclusions before estimating benefits. That protects the business case from inflated addressable volume and tells operators where a different control, specialist system, or human judgement remains necessary.

• Workflow cannot resolve disputed ownership
• Faster approval is not useful if budget data is stale
• Complex rules become impossible for requesters to predict
• Executive exceptions can undermine every configured threshold

Keep a decision record that survives the project

For each material choice, record the date, owner, evidence considered, option selected, rejected alternatives, and the condition that would trigger review. This is not meeting minutes. It is a compact explanation of why the company accepted a particular cost or risk. Six months later, a new operator should be able to distinguish an intentional compromise from an accidental omission without locating the original project team.

Use the record during monthly operations reviews. Compare the assumptions made at approval with actual volume, cycle time, exceptions, and supplier behaviour. When an assumption fails, change the rule or reopen the decision; do not quietly build manual work around it. That feedback loop is what turns a configured workflow into an operating system rather than a frozen implementation project.

The final design should be easier to explain than the process it replaces. If a requester cannot predict what information will be required and who will decide, complexity has merely moved behind the screen. Keep the common path short, make consequential exceptions visible, and revisit the rules when transaction patterns or organisational ownership change.