The Approval Matrix Is Where Your Cycle Time Goes

Procurement delays are rarely caused by slow buyers. They are caused by a sequence of approvals that each seemed reasonable when it was added and that nobody has reviewed since.

A typical pattern: a request needs a manager, then a department head, then finance above a threshold, then an executive above a higher threshold, then procurement for vendor setup. Each approval is defensible in isolation. Together they create a process where a routine purchase waits on five calendars.

Measure queue time, not work time

Take a sample of recent purchase orders and record, for each step, when the document arrived and when it left. Total the time spent waiting versus the time spent working.

Almost every organization that does this finds that eighty to ninety-five percent of cycle time is queue time. That single number changes the conversation. You are not trying to make people work faster. You are trying to remove steps and shorten waits.

Redesign around risk, not hierarchy

Approval thresholds should reflect financial exposure and reversibility, not organizational seniority.

• Low-value, routine, contracted spend should not require multiple approvals. If the vendor is approved and the price is on contract, the control already exists at the contract level.
• Mid-value spend needs one accountable approver with budget authority, and a clear statement of what they are approving.
• High-value or non-standard spend warrants real review — competitive documentation, scope definition, and a second set of eyes.

The test for any approval step: what specific risk does this person catch that no earlier step catches? If the answer is unclear, the step is a delay, not a control.

Configure the system to match

Once the matrix is right, make the system enforce it. Delegation rules for absences, automatic escalation after a defined number of days, catalog purchasing for recurring items, and pre-approved vendor lists remove entire categories of waiting.

Two configuration details matter more than most: automatic reminders at defined intervals, and a visible aging report that shows every request currently in the queue with the number of days it has been sitting. Visibility alone tends to shorten queues, because the delay becomes attributable.

What good looks like

A well-designed process usually lands here: routine contracted purchases in one to two days, mid-value purchases in three to five days, and exceptions handled as exceptions — quickly, with documentation, and with a named owner.

The point is not speed for its own sake. It is that every day a purchase sits in a queue is a day the business is waiting on something it has already decided to buy.