Procurement KPI Dashboard
- Source
- sample-data.csv · 5 rows
Realized savings (YTD)
$412k
+$38kPO cycle time
3.2 days
-0.5 daysMaverick spend
8.6%
-1.1ppSupplier defect rate
1.8%
-0.3ppRealized savings by category
Sample data — year to date
Procurement dashboards must prove value in finance's language: realized savings against baseline, spend under management, and the leakage metrics — maverick spend and off-contract buying — that erode both.
Realized savings (YTD)
$412k
+$38kPO cycle time
3.2 days
-0.5 daysMaverick spend
8.6%
-1.1ppSupplier defect rate
1.8%
-0.3ppRealized savings by category
Sample data — year to date
Live render with sample data — upload your own export and this structure regenerates from your numbers, with the computation attached to every figure.
Everything you need to know about using AnalyzeData.
Realized savings by category, PO cycle time, maverick spend, supplier defect rate, and contract compliance — value delivered plus the leakage metrics that threaten it.
Export POs, invoices, and receipts as CSV, upload, and ask for the quarterly procurement review. Savings math runs against your baseline columns with the code attached.
Negotiated savings are what you agreed at the table; realized savings are what actually shows up in invoices versus the baseline price. The gap between them is the whole game, because deals that never translate into lower paid prices never reach the P&L. Track realized savings as baseline minus actual price times volume, and guard it with contract compliance, which measures whether contracted items are truly bought at contract terms.
When the requisition-to-PO cycle drags, buyers route around the process to get what they need, and those off-contract purchases are exactly what maverick spend measures. So a slow PO cycle time quietly manufactures the leakage that erodes your realized savings. Track the two together, since tightening cycle time is often the most direct way to pull maverick spend down and keep spend under management.
Upload the export you already have — the dashboard computes itself, verifiably.
Open the workspace