Cut Purchase-Requisition Approval Delays [2026 Playbook]

A purchase requisition is a small document with an outsized ability to stall a factory. On the plant floor it is the request that says "we need this bearing, this coolant, this contract maintenance visit, and here is who is asking and why." It is not a purchase order yet — it is the internal ask that has to be approved before procurement is allowed to spend money. And in most manufacturers, that ask spends far more time waiting for a signature than it spends being evaluated. A maintenance planner submits a requisition for a $4,200 spindle motor on Monday, and the part does not get ordered until Thursday — not because anyone disagreed with buying it, but because the approval sat in a supervisor's inbox while they were on the floor, then bounced to a controller who was traveling, then waited for a plant manager to come back from a customer audit.

This guide is about closing that gap: how to route purchase-requisition approvals so the right approver signs off fast, the requisition escalates when it stalls, every dollar threshold is enforced automatically, and the whole trail is auditable. The mechanics are not exotic. The fix is a routed approval workflow that reads the requisition's amount, cost center, and category, sends it to the correct approver by spend authority, escalates after a deadline, and converts the approved requisition into a purchase order without a human re-keying anything. Below is how to build it, with the routing tiers, a worked example, the benchmarks, and an honest section on when this is the wrong project.

TL;DR

Manual requisition approval is slow because it relies on email and memory, not rules. Manual requisition approval averages 5 to 7 business days per cycle, according to APQC (2026). Replace inbox routing with amount-based rules, deadline escalation, and automatic PO creation, and you compress that to same-day for routine spend while keeping a clean audit trail. Route by amount and category, escalate on a timer, and only pull a human in for the items that genuinely need judgment.

Requisition-to-PO is the workflow where the work takes minutes and the routing takes days. That sentence is the entire problem statement, and it is why automation pays off here faster than almost anywhere else in procurement.

What "routing a purchase requisition" actually means

Routing a purchase requisition means automatically sending each request to the correct approver — or sequence of approvers — based on its dollar amount, cost center, and spend category, then advancing or escalating it until it is approved or rejected. In plain terms: the system decides who needs to see this requisition and in what order, instead of a buyer guessing and forwarding an email.

That distinction matters because the two failure modes of manual routing are opposites. Either the requisition over-routes — a $90 box of shop rags gets the same three signatures as a $90,000 CNC retrofit — or it under-routes, and a large commitment skips an approval it legally required. Good routing is conditional: small, in-budget, pre-approved-vendor spend should clear with one quick look or none at all, while large or off-contract spend should climb the authority ladder. The whole point of automating it is to make those conditions explicit and consistent instead of dependent on whoever happens to be at their desk.

Who this is for

This playbook is written for a specific reader. It fits a manufacturer with roughly 50 to 1,000 employees and $10M to $500M in annual revenue that processes anywhere from a few hundred to several thousand purchase requisitions a month across maintenance, production, and indirect spend. You probably run an ERP or MRP system — NetSuite, Epicor, SAP Business One, Infor, or similar — and your requisition approvals currently happen in email, a shared spreadsheet, or an ERP module that everyone routes around because it is clunky. The pain is real and measurable: parts arrive late, expedite fees pile up, and your buyers spend their day chasing signatures instead of negotiating with suppliers.

Red flags — skip this if: you have fewer than ~15 staff and one person approves everything in five minutes anyway; you process fewer than ~50 requisitions a month, where the automation overhead outweighs the savings; or your spend is entirely on long-term blanket contracts with no per-requisition approval step. In those cases you are automating a problem you do not have.

If you sit in that fit window, the rest of this guide is a build plan. If you want to see how routed approvals connect to broader procurement automation, our overview of agentic workflow automation covers the orchestration layer underneath.

The approval-authority ladder

Before you automate anything, write down the rules a human is supposed to follow today — because automation can only route as cleanly as your policy is defined. Most manufacturers approve by spend authority: dollar thresholds that determine how high a requisition has to climb. The table below is a representative ladder; yours will differ, but the structure is the point.

The reason this matters for automation is that every row is a rule a machine can enforce perfectly and a human enforces inconsistently. Roughly 60% of approval delay is queue time, not decision time, according to the Hackett Group (2026) — meaning the requisition is not being debated, it is just sitting. Encode the ladder once and the queue time mostly disappears.

How automated routing works, step by step

Here is the workflow that replaces the inbox. Each step is a rule, not a person's habit.

1. Capture and validate. The requisition enters from your ERP, a form, or an email parse. The system checks the required fields — amount, cost center, category, vendor, need-by date — and rejects or flags anything incomplete before it ever reaches an approver.

2. Classify and route. It reads the amount and category, matches them to the authority ladder, and assigns the approver chain. A $3,800 maintenance part for an approved vendor goes straight to the department manager; a $48,000 new-tooling request gets the controller-then-plant-manager chain plus a capex tag.

3. Notify and track. The first approver gets a notification with a one-click approve/reject and the full context — no digging through email threads. The clock starts.

4. Escalate on deadline. If the approver does not act within the target turnaround, the requisition escalates — a reminder, then a re-route to a delegate, then up the ladder. Nothing sits silently.

5. Convert to PO. Once fully approved, the requisition becomes a purchase order in the ERP automatically, with the approval trail attached, and procurement is notified to send it to the supplier.

The leverage is in steps 2 and 4. Automated escalation cuts stalled approvals by about 70%, according to Ardent Partners (2026), because the most common cause of a late requisition is simply that nobody nudged the person sitting on it.

This is the layer where US Tech Automations reads each requisition's amount and category, applies the authority ladder to assign the approver chain, and fires the escalation timer the moment the first notification goes out. For teams whose requisition data already lives in the ERP, our data-extraction agent handles parsing inbound requisition emails and POs into the structured fields the router needs.

Worked example: the $4,200 spindle motor

Picture a 380-employee metal-fabrication plant running NetSuite, processing about 820 purchase requisitions a month, where the maintenance team alone submits roughly 240 of them. A maintenance planner submits requisition PR-20614 for a $4,200 spindle motor from an approved vendor with a need-by date 6 days out. Under the old process, that requisition emailed to a supervisor who was on the floor, then forwarded to a department manager who was in a 2-hour production meeting, and the PO did not cut until day 3 — by which point the only way to hit the need-by date was a $340 expedite fee. With routed approvals, the system reads the $4,200 amount and the approved-vendor flag, sends it directly to the department manager (the supervisor tier auto-clears under the in-budget rule), and when the manager does not act in 4 hours it escalates with a reminder. The manager approves at hour 5, the approval fires NetSuite's purchaserequisition.afterSubmit event, the system writes the record back where the purchaseorder record is created automatically, and the supplier has the PO the same afternoon — no expedite fee, and a complete approval trail attached to the requisition. Across 240 maintenance requisitions a month, eliminating even half the expedite fees at ~$300 each is roughly $36,000 a year recovered.

Benchmarks: manual vs. routed approvals

Numbers make the case more cleanly than adjectives. The table below contrasts a typical manual requisition process against a routed one, using mid-market manufacturing figures.

Each manual requisition costs $35 to $60 to process, according to APQC (2026), counting labor, error correction, and expedite fees — which is why the per-requisition processing cost is where finance usually first notices the savings. Off-contract "maverick" spend runs 8% to 15% in manual processes, according to the Hackett Group (2026), and routed approvals attack it directly by refusing to advance requisitions that point at unapproved vendors.

A second benchmarking lens — what changes operationally when you switch — is below.

Common mistakes when automating requisition approvals

Teams that struggle with this project usually trip on the same few things, none of which are about the technology.

• Automating a broken policy. If your authority ladder is contradictory or undocumented, automation just enforces the contradiction faster. Fix the rules on paper first.

• Over-routing everything. Sending every $80 requisition through three approvers because the $80,000 ones need it. Conditional routing exists precisely so small, in-budget spend can clear in one step or zero.

• No escalation path. Building the routing but not the deadline timer. Approvers act 3x faster when a deadline timer is visible, according to Gartner (2026). Without escalation, you have moved the bottleneck, not removed it.

• Ignoring delegation. Approvers go on vacation. If there is no out-of-office delegate rule, every absence becomes a stalled queue.

• Skipping the writeback. If the approved requisition does not flow into the ERP as a PO automatically, your buyers are still re-keying, and you have automated the front half of a two-part problem.

Decision checklist: is your process ready to automate?

Run through this before you scope a build. The more boxes you can check, the smoother the project.

When NOT to use US Tech Automations

Honesty serves you better than a sales pitch here. If you process only a handful of requisitions a month, or one trusted person approves everything within minutes, a routed-approval system is overhead you do not need — a shared spreadsheet and a phone call will outperform any workflow engine at that volume. The same is true if your spend is locked into long-term blanket purchase agreements with no per-requisition approval step, since there is no routing decision to automate. And if your underlying policy is genuinely undecided — if nobody can tell you who is supposed to approve a $20,000 requisition — then automation is premature; you have a governance problem to solve before you have a workflow problem. Bringing in US Tech Automations to enforce rules you have not written yet will only produce fast, consistent enforcement of the wrong thing. Solve the policy first, then automate it.

Glossary

A few terms that come up constantly in procurement workflow conversations, defined plainly.

Key Takeaways

The core argument of this playbook compresses into a few points.

• Requisition approval is slow because of queue time, not decision time — and queue time is exactly what rules-based routing eliminates.

• Route by amount, category, and cost center against a documented authority ladder so small spend clears fast and large spend climbs the chain.

• Add a deadline timer with escalation and delegation, or you have only relocated the bottleneck.

• Write the approved requisition back into your ERP as a PO automatically, or your buyers are still re-keying.

• Automate the policy, not the chaos — if the rules are not written, fix them before you build.

To map your authority ladder into a routed workflow and see what it costs, compare options on our pricing page. If your broader procurement stack also struggles with engineering-change routing, the same pattern applies — see routing engineering-change orders for approval and routing quality nonconformance reports for disposition. The upstream input quality matters too — keeping requisition data clean depends on disciplined cycle-count adjustments reconciled to inventory.

Frequently asked questions

How long does it take to automate purchase-requisition approvals?

Most mid-market manufacturers reach a working routed approval flow in 4 to 8 weeks. The technical configuration — mapping your authority ladder, connecting your ERP, and setting escalation timers — is usually 2 to 3 weeks. The rest is the part teams underestimate: documenting and aligning on the approval policy itself. If your authority ladder is already written and your requisition data is structured in an ERP, the build is faster; if you are deciding approval rules as you go, expect the longer end.

Will automated routing replace our buyers or approvers?

No — it removes the chasing, not the judgment. Approvers still approve; they just do it from a notification with full context and a deadline, instead of digging through email. Buyers stop spending their day forwarding requisitions and start spending it on supplier negotiation and sourcing. The work that automation removes is queue management and re-keying, which is exactly the low-value work most procurement teams want gone.

What happens to a requisition if the approver is out of office?

A well-built routing flow handles this with delegation and escalation rules. Each approver should have a designated delegate, and the deadline timer should re-route the requisition to that delegate or up the authority ladder if no one acts in time. Automated escalation cuts stalled approvals by about 70%, according to Ardent Partners (2026), precisely because absences stop creating silent dead-ends. Without these rules, a single vacation can stall a queue for a week.

How does routing prevent off-policy or "maverick" spend?

By refusing to advance a requisition that violates policy. If a requisition names a vendor that is not on the approved list, exceeds a budget threshold, or skips a required approval tier, the workflow flags or blocks it rather than letting it slip through. According to the Hackett Group (2026), maverick spend runs 8% to 15% of total spend in manual processes, and rules-based routing is the most direct lever against it because the policy is enforced at the moment of approval, not discovered in a later audit.

Do we need to replace our ERP to do this?

No. Routed approval workflows sit on top of your existing ERP or MRP rather than replacing it. The automation reads requisition data from the system you already run — NetSuite, Epicor, SAP Business One, Infor, and others all expose the requisition and PO objects an integration needs — applies the routing rules, and writes the approved PO back. Ripping out an ERP to fix approval routing would be a far larger and riskier project than the one this playbook describes.

What is the realistic ROI on this kind of automation?

For a manufacturer processing several hundred to a few thousand requisitions a month, the savings come from three places: reduced expedite fees from faster cycles, lower per-requisition processing cost, and reclaimed maverick spend. According to APQC (2026), each manual requisition costs $35 to $60 to process versus $8 to $15 automated — so even at 500 requisitions a month, the processing-cost savings alone often exceed the build cost within the first year, before counting expedite-fee and maverick-spend recovery.