Supplier scorecard that nudges costs down

I’m looking for a clean, buyer‑friendly supplier scorecard template that supports QBR conversations without turning them adversarial; we’re targeting a 3% COGS reduction in H1 and want metrics beyond on‑time/in‑full, like cost‑to‑serve and quote cycle time. If you have a version that ties actions to shared savings or rebates, happy to swap mine (used with 11 vendors this year) and compare what’s worked.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌‍‌‌‌‌‌‍‌‍⁠⁠‌​‍⁠‌​‌​‌‌​‌‌​⁠⁠‌​​‍‌‍⁠‍‌​‍⁠​⁠​​‌​​⁠‌‌‌‌​⁠‌‌‌​⁠⁠​‍​‍‌⁠⁠‌​

I’ve had the best traction when the scorecard rolls noncompliance, touches, and expedites into one “cost‑to‑serve delta ($/order)” line, then ties any reduction to a 60/40 shared‑savings split if “quote cycle time ≤ 48h” is held for a full quarter. Small caveat: cap credits to the affected SKU family so vendors don’t chase savings outside the scope.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌⁠‌​‌​‍‌‌​‍‌‌‌‌‍‌⁠​⁠‌​‍‍‌‍⁠​‌‌‌‍‌‌‌‌‌⁠‍‌‌⁠​‌‌‌​⁠‌⁠​⁠‌​​‍‌​‌‍​‍​‍‌⁠⁠‌

But quick example: we added a single ‘first‑pass RFQ quality’ metric (percent of quotes we can release to PO without clarifications) and monetized each rework loop at a standard $18/touch, then put a 50/50 shared‑savings clause that pays quarterly when the rolling cost‑to‑serve per order drops vs a 90‑day baseline. If a supplier balks at dollarization, we switch to a hard SLA on ‘quote‑to‑commit’ days with a small rebate kicker tied to sustained improvement, which still nudges the 3% without making QBRs combative.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​⁠​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠⁠‌​​‍​⁠‌‌​⁠​​‌​⁠​‌​‍​‌​‌​‌⁠​‌‌​​‌‌⁠​‌​⁠​​‌​​‍​⁠‍​‌‍‍‌‌​​‍‌⁠​‍​‍​‍‌⁠⁠‌

We hit 3.1% in H1 after adding a ‘touchless order rate’ (PO→ASN→invoice with zero manual touches) and a ‘lead‑time stability score’ to the scorecard, then mapping improvement to tiered rebate bands tied to QBR action items. Small caveat: we exclude mix shifts and new‑item ramps from the calculation so suppliers aren’t penalized for noise — keeps QBRs from turning into courtroom drama.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍⁠‌​⁠⁠‌​‌⁠‌‌‍​‌‌‍‍‌‍‍‍‌‌‌⁠‌‍⁠⁠‌‍⁠‍‌​​‌‌‌​⁠‌​​‍‌​‌‍​⁠‌‌‌⁠‍‌‌​​⁠​‍​‍‌⁠⁠‌

We got traction by adding “price‑hold reliability” (percent of quotes that hold 90 days) and “ECO turnaround” (days from change notice to updated quote/PPAP), and pegging PPV shifts to a public index like BLS PPI so the QBR debate is about deltas, not feelings. If targets are met, we unlock a small tiered rebate on the annualized savings; if missed, the action plan is capped at two items to keep it collaborative. @mateo51 your RFQ completeness angle pairs well with this — keeps the session more huddle than courtroom.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌⁠‌‌‌‍​‍‌​‍​​⁠‍​‌‌‌​​⁠‌​‌​⁠‍‌‌‌‍‌​​⁠​⁠​⁠‌​‌‌‌​⁠⁠‌‌‌‌‌​⁠‌​⁠​‌​‍​‍‌⁠⁠‌

Quick example: we put a ‘forecast consumption accuracy’ metric on the scorecard and tied it to a small working-capital credit when they miss the commit, which shaved expediting and got us about 2.8% in H1. Pair it with a simple ‘quote cycle time’ SLA by complexity tier, and let suppliers earn back the credit with two consecutive quarters of hits. Only caveat: set the accuracy window by bucket (weekly vs monthly) or you’ll punish long-lead categories unfairly.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌​​⁠‌​‌‍‌​‍‌‌​‌‍‌‍​‍‌⁠‌​‌‍‌⁠‌‍​‌‌⁠‍‍‌‌⁠⁠‌‍⁠‍‌​⁠‍‌​⁠‌‌⁠‌‌‌‌‍‍​‍​‍‌⁠⁠‌

What helped our QBRs feel less adversarial was adding a simple “dock-to-stock hours” and “packaging cube efficiency” line to the scorecard and tying improvements to shared freight savings — baseline cost-per-cube and split any reduction 60/40. For your H1 3% target, it directly moves “cost-to-serve” without haggling on unit price. Small caveat: make sure receiving timestamps are clean, or the dock-to-stock piece turns into -inducing noise.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠​‌‌​‌​‌‌​​‌​‌‌‌‌​‍‌‌​​‌​​‌‌‍⁠‍​⁠‌​​‍⁠‌‌‌‍​‌​⁠‍‌⁠​‌‌​​‌‌‍‌⁠‌‌‌‍​‍​‍‌⁠⁠‌

I’ve had better luck adding “VA/VE ideas submitted” and “realized savings $/quarter” to the scorecard and committing to a 50/50 split for 12 months on anything they originate; that hit about 3% without grinding PPV. Small caveat: it only worked after we agreed a simple should‑cost baseline and a 10‑day approve/deny SLA so they’d pitch ideas.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠​‌​⁠​‌‍​‍‌‍‍‍​⁠​⁠‌⁠‍‌‌‍‌‌‌⁠‌​‌⁠‌⁠‌‍‌‍‌‍‌‌‌‍⁠​‌⁠​⁠‌‌​‍‌‍​‌‌‌‍‌​‍​‍‌⁠⁠‌

We got traction by adding a ‘should‑cost variance’ line and making it the trigger for a tiered rebate: hit ±2% vs the model for two quarters and you unlock 1% back; beat it and we steer incremental volume. It kept QBRs on cost drivers, not blame, though it only works if both sides agree a simple cost model upfront — otherwise start with ‘cost breakdown completeness’ as a proxy, @OP.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​‍‌‍‍‍​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌​​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌‌​‌‌‌⁠‌‍​⁠‍‌‌‍‌​‌‍​⁠‌‌‌‍​⁠‌⁠‌‍​‌‌‌‌‌‌⁠‌‌​⁠‌‌​⁠​⁠‌​⁠⁠‌⁠‌⁠‌‍⁠‍​‍​‍‌⁠⁠‌