Supplier Intelligence as a System, Not a Spreadsheet

Ask a procurement team which of their three qualified suppliers for a critical casting has the tightest on-time delivery over the last eighteen months, and you'll usually get a fast, confident answer. Ask them to show the number behind it, and the confidence thins out — into a spreadsheet somebody maintains on the side, a recollection of "they've been solid lately," or an answer that turns out to describe a different supplier once you check the purchase order history. This isn't a knowledge problem in the sense of the knowledge not existing. The buyer genuinely knows. The problem is where that knowledge lives, and what happens to decision quality the day the buyer who holds it takes a different job.

The knowledge is real; the storage is the risk

A buyer who's managed the same supplier relationships for six years carries something genuinely valuable — not just lead times, but the texture underneath them: which supplier ships on time on paper but pads the quoted lead time to do it, which one is reliable on standard runs but slips on anything expedited, which quality issue eighteen months ago was a one-off versus the start of a pattern later confirmed. That's real expertise, earned the slow way, and it's exactly what a spreadsheet can't hold, because most of it was never written down — it lives as pattern-matching in one head, not transferable to whoever picks up the supplier list next. The risk isn't that the knowledge is wrong. It's that it's a single point of failure, and plants tend not to notice until the person leaves, at which point the successor inherits a supplier list and none of the judgment that made it useful.

We've watched this play out the same way more than once: a buyer leaves, their replacement inherits a spreadsheet with lead times six months stale and a qualification note that just says "approved," and the plant's first real signal that something's wrong is a late shipment on a supplier everyone assumed was dependable — because the person who knew otherwise isn't there to say so anymore.

Why a shared spreadsheet doesn't fix this

The obvious fix — get the buyer to document everything in a shared tracker — helps for a quarter, then decays: a spreadsheet has no mechanism that keeps it current, and updating it always loses to whatever's more urgent that week. It also has no way to reconcile against what actually happened. A lead time entered as "14 days" in January doesn't get checked against the receiving records that would show it drifted to 19, because nothing in a spreadsheet forces that reconciliation. The result looks like a system of record but functions as a snapshot of whatever got typed in — a fair description of most "supplier intelligence" we find when we start a project, spreadsheet or not.

What turning this into a system actually requires

The difference between a spreadsheet and a system isn't the interface. It's whether the numbers are derived from source transactions or typed in by hand.

Lead time and on-time performance computed from the transaction record, not entered manually. If purchase order dates, promised dates, and actual receipt dates already exist in the ERP, a supplier's real on-time percentage and lead-time distribution — the distribution, not a single average, since the variance often matters more — should be a query against that data, continuously current, not a figure someone updates when they remember to.

Quality history tied to the lot and the defect, not a subjective score. "Supplier quality: good" isn't information anyone can act on. A queryable link between a non-conformance, the lot it came from, and the supplier that shipped that lot — the same traceability chain a plant already needs for FMEA and audit purposes — turns quality history into something a system surfaces automatically when a new PO against that supplier gets cut, instead of something a buyer has to remember to mention.

Qualification status as a structured, queryable record with an audit trail, not a folder of certificates. Which suppliers are qualified for which parts, under what conditions, approved by whom, expiring when — exactly the kind of record a spreadsheet handles badly, with no enforcement or expiration alerts, and a proper system handles as a first-class object with the same rigor a plant already applies to equipment calibration records.

The tacit judgment captured as structured annotation, not lost. The genuinely hard part to systematize is the buyer's texture — "reliable on standard runs, slips on expedited." A system can't compute that from transactions alone; some of it has to be captured, not derived. It can be captured as a structured, attributed, timestamped note tied to the supplier record — visible to whoever inherits the relationship, instead of existing only as long as the person who wrote it stays in the role.

What changes when it's a system

The payoff isn't that procurement decisions become fundamentally different — a good buyer with a good spreadsheet often reaches the same call a good buyer with a proper system would. The payoff is what survives turnover, what's auditable when a quality event forces you to explain why a supplier was qualified, and what a new buyer can trust on day one instead of rebuilding the knowledge their predecessor spent six years accumulating and took with them when they left.