14 Approvals Stuck. $1,200 Per Day in Overhead.
Your procurement team submitted 14 purchase requests in the last two weeks. Three have been approved. Eleven are in review. Two have been sitting in the same inbox for 11 days. The crew needed those materials 6 days ago. Your software does not track any of this.
Your Approval Backlog — Named, Timed, Costed
14 items. One bottleneck. Watch the overhead cost tick while approvals wait.
The Cost of Approval Gridlock
Three ways your own approval process is costing you more than the materials it is meant to protect.
Your software only tracks issued POs
Eleven purchase requests are currently in review. Three have been there for more than 10 days. Your procurement software does not track any of this — it only counts POs that have already been issued. The backlog is invisible until materials are late.
Every day of approval delay is $1,200 in overhead
Your overhead meter runs at $1,200 per day regardless of whether materials are moving. When 14 approvals are stuck and the crew is waiting, that overhead accumulates against zero productive output. After 14 days, that is $16,800 in overhead accrued against no work.
The bottleneck is named — but invisible without data
Your director reviews and approves every PO. That is a policy decision with a cost. At 8.4 days average at that stage, it is responsible for 73% of your total PO cycle time. You have never measured this. POD does — and names the stage, the approver, and the cost.
Your Approval Backlog — Named, Timed, Costed
ApprovalPipeline names the bottleneck. OverheadBurnRate shows what every day of delay costs.
Approval Pipeline
PODOverhead Burn Rate
What POD Gives You Back
Every approval mapped to its owner
ApprovalPipeline shows every in-flight purchase request, its current stage, who owns it, how long it has been there, and which activities it is blocking. The bottleneck becomes undeniable — and attributable to a specific stage.
Named, timed, costedOverhead burning against every stuck approval
OverheadBurnRate tracks overhead spend per day against budget. Combined with ApprovalPipeline, you see the exact overhead cost of every day of approval delay — in real time, while you can still act.
Dollar cost of delay made visibleEscalation triggers before the window closes
When an approval exceeds a configurable threshold (e.g., 3 days for critical-path items), POD triggers an escalation alert to the reviewer and their manager. The bottleneck is broken before it creates a delay.
Escalation before damageProcess data for permanent fix
Once you see that 73% of your PO delay happens at director approval, you can implement a targeted fix — a delegated threshold for routine purchases, parallel review for critical-path items. POD gives you the data to make the case and the metrics to verify the fix worked.
Data to fix the process, not just track it73% of Your Delay Happens at One Stage. Fix That Stage and Your POs Drop from 11 Days to 3.8.
ApprovalPipeline shows that Director Approval averages 6.8 days — 73% of total cycle time. Every other stage runs efficiently. One stage creates 8 days of delay. One fix — a delegated approval threshold for routine purchases — removes 60-70% of items from that bottleneck. POD gives you the data to make that case and the metrics to prove it worked.
Frequently Asked Questions
See Every Stuck Approval and What It Is Costing You
Your team is not the bottleneck. Your process is. POD shows you exactly where — and what every day of delay costs.
Related reading: