| |
By Bill Murphy · Powered by Colony Spark |
THE OPERATIONS
BRIEF |
|
ISSUE #22 · AUGUST 21, 2026 |
|
| |
|
| |
|
Hi ${first_name},
Most planning systems store a supplier's promised date as if every commitment carries the same reliability. In reality, confidence varies by part, supplier, order condition, revision history, and recent behavior. A supplier who has moved a date twice, shipped partial three times, and taken five days to acknowledge the last purchase order is not the same risk as a supplier who has never missed.
This issue is about the shift from planning around one date to planning around the evidence behind that date. The data to build that evidence already exists in your ERP and email logs. The gap is the aggregation.
Bill
|
| |
Supplier Commit Dates Need a Confidence Score.
Every promised date carries different reliability. Most planning systems treat them as equally solid.
Supplier delivery performance is not improving. The ISM Manufacturing Supplier Deliveries Index registered 58.9 in July 2026, up from 57.4 the prior month. Readings above 50 indicate slower supplier deliveries, and the index has stayed elevated through the summer. At the same time, 70% of organizations have had between one and five critical suppliers fail in the past 12 months, and 41% say they are one supplier failure away from a supply chain crisis.
The problem is not that suppliers are becoming less reliable. The problem is that most operators discover supplier failure only after it happens. 57% admit they are reacting to supplier failure rather than anticipating it, even though 73% say they would like to spot supplier distress earlier. The evidence to see it coming already exists. It just lives in scattered form: acknowledgment timestamps, PO change logs, partial-shipment records, and informal follow-up notes that nobody aggregates into one signal.
|
Evidence already in your system
· Organizations take 25 days on average to identify and onboard a replacement supplier, and 74% are exposed to shortages or operational disruption during that window. The cost is not just the disruption. It is all the customer promises that were made on top of dates that should not have been trusted.
· 76% of organizations still rely on manual processes for supplier due diligence and risk checks, and 58% say their reliance on spreadsheets exposes them to human error. Most never extract the supplier-reliability signals that are already sitting in acknowledgment logs and PO histories.
· Reliability now outweighs speed in keeping customers. Retail delivery leaders say: "It's when you're not reliable is when we're going to lose our customers." A 2024 McKinsey consumer survey found shoppers rank arriving within the promised window above speed, with speed falling from the top delivery priority in 2022 to fifth in 2024. Industrial buyers expect the same discipline from their own suppliers.
|
The operating environment is getting less predictable. The tools to see it coming already exist in scattered form. The operators who assemble that evidence first get to act before a date slips instead of scrambling after it breaks.
|
The promised date is not a fact. It is the output of a process that has its own track record, and that track record is knowable before the date is missed.
|
|
|
| |
Every order is now a rush order.
Aaron Bradley, VP of Sales & Compliance, Terry Town, on the cost of broken delivery trust
|
"The way this industry moves now, every order is a rush order. Once someone loses trust in that communication or delivery time, the customer won't come back."
|
That is exactly the blind spot the confidence score below is built to close. The moment a customer loses trust in a delivery promise is the moment they start looking at a competitor. Seeing which promises are already at risk before the trust is spent is the difference between acting as a supplier and reacting as a vendor.
|
The takeaway
The operators winning on customer retention are not the ones with the best forecasts. They are the ones who spot which supplier commitments are already at risk before the customer discovers it through a missed shipment.
|
|
|
| |
The Supplier Commit-Confidence Board.
One score per open commitment. A weekly view of which dates deserve trust.
A ranked list that tells the planner which dates to buffer, which to monitor, and which to escalate now instead of after the date slips.
Every open purchase order carries a promised date, and every promised date gets planned against as if it were equally solid. It never is. Some suppliers move dates the moment a PO is placed. Others acknowledge late, ship partial, or have a track record that quietly degrades on exactly the part families that matter most.
The Supplier Commit-Confidence Board turns that scattered evidence into one score per open commitment. It does not replace the ERP or the supplier portal. It reads from them and produces a weekly view that tells the planner which dates to trust, which to buffer, and which to escalate now instead of after the date slips.
What goes into it
Create one row for every open PO line with a promised delivery date. Each row captures:
|
· Supplier and part. Supplier name, part number or part family, and criticality tier (single-source, long lead-time, safety-related, or readily available with backup).
· Promised date. The current committed date as it stands today, and the original date first committed at PO placement.
· Acknowledgment lag. Days between PO issuance and supplier acknowledgment. Late or missing acknowledgment is an early confidence signal, before any date has moved.
· Date-change count. How many times this line's promised date has moved since the PO was placed, and the direction and size of each change.
· Partial-shipment history. Whether this supplier has shipped partial against comparable orders in the last 6-12 months, and how often a partial shipment preceded a final delay.
· Recent on-time rate. This supplier's on-time percentage over the trailing 90 and 365 days, weighted toward the same part family when volume allows.
· Order condition flags. Rush order, first order with this supplier, order placed during a known constraint, or unusually large quantity relative to supplier's typical run size.
· Confidence score. A single 1-100 score built from the fields above, weighted by part criticality so a low score on a single-source critical part surfaces above a low score on a readily available commodity part.
· Recommended action. Hold, monitor, contact supplier, expedite alternate sourcing, or escalate to customer communication.
|
The scoring logic
Keep the scoring transparent enough that a planner can explain any score in one sentence. Start every commitment at a baseline score tied to that supplier's trailing on-time rate. Subtract points for acknowledgment lag beyond the supplier's typical response time. Subtract points for each date change, with later changes (closer to the promised date) weighted more heavily than early changes. Subtract points if a partial shipment has already occurred on this line or is a documented pattern for this supplier. Multiply the resulting score by a criticality weight so single-source and safety-related parts surface first regardless of raw score. Do not let the score replace judgment. It ranks attention, it does not auto-generate customer promises.
Supplier / Part |
Criticality |
Promised (Current / Original) |
Ack Lag |
Date Changes |
Score |
Action |
Supplier A / Single-source bearing |
Critical |
Sep 12 / Aug 28 |
6 days |
2 |
34 |
Contact supplier, begin alternate check |
Supplier B / Standard fastener |
Low |
Sep 3 / Sep 3 |
Same day |
0 |
91 |
Hold, no action |
Supplier C / Custom weldment |
High |
Sep 20 / Sep 5 |
4 days |
3, partial shipped |
41 |
Escalate, flag customer |
Supplier D / Commodity resin |
Medium |
Aug 29 / Aug 25 |
2 days |
1 |
68 |
Monitor |
What the weekly output looks like
Every Monday, the planner receives one view with four blocks: a confidence heat map with every open commitment sorted by score (lowest confidence and highest criticality at the top); a movers list showing any commitment whose score dropped since last week and the specific field that changed; customer exposure flagging which low-confidence commitments feed a specific customer promise; and recommended actions listing the three to five commitments that need a supplier call, an alternate-sourcing check, or a proactive customer conversation this week.
Operating rhythm
|
Daily: Automated fields (acknowledgment status, date changes, partial-shipment flags) update from ERP and supplier-portal data without manual entry.
Monday: Planner reviews the confidence heat map and movers list in a focused 15-20 minute session, not a full PO-by-PO review.
Midweek: Any commitment that drops below a defined threshold triggers an immediate supplier contact or customer-facing heads-up, not a wait for Friday.
Monthly: Compare predicted low-confidence commitments against what actually slipped. Use the miss rate to retune the scoring weights.
Quarterly: Review supplier-level trends. A supplier whose average confidence score is declining across multiple parts is a sourcing conversation, not just a planning adjustment.
|
Build guardrails
|
· Score the commitment, not the supplier relationship. A good supplier can still have a low-confidence line on a specific constrained part.
· Keep the scoring logic visible to the planner. A black-box score that can't be explained in one sentence will get ignored the first time it's wrong.
· Weight by criticality first. A perfect score on a commodity part matters less than a mediocre score on a single-source part.
· Do not auto-communicate to customers. The score informs a human decision about when and how to raise exposure, it does not trigger the message itself.
· Feed it from data you already have. Acknowledgment timestamps, PO change logs, and shipment records already exist in most ERPs. This is an aggregation and weighting layer, not a new data-capture burden.
· Retune quarterly. Supplier behavior changes. A scoring model that never gets checked against actual outcomes becomes another number nobody trusts.
|
What the operator gets every week
|
· A ranked view of which promised dates deserve trust and which deserve a buffer.
· Early visibility into suppliers whose reliability is quietly declining, before a single missed date makes it obvious.
· A clear reason to start an alternate-sourcing or customer conversation before the date slips, not after.
· Less time spent manually re-checking every open PO and more time spent on the handful that actually matter.
· A record of which planning assumptions were wrong, so the model gets sharper every cycle.
|
Build paths
|
Path 1. Internal build
Start with a spreadsheet or Airtable base pulling the fields above from your ERP export: promised date, original date, acknowledgment timestamp, date-change history, and partial-shipment flags. Assign a criticality tier to your top 50-100 parts by hand. Build a simple weighted score, even a basic point-deduction model, and sort by score every Monday. Track your miss rate for one quarter before trusting the score to drive customer conversations.
|
|
Path 2. ERP or partner path
Ask your ERP provider or systems integrator whether commit-date history, acknowledgment timestamps, and partial-shipment data are already captured and exportable. Most are, they're just never aggregated into a single view. The deliverable should include a per-line confidence score, a criticality weighting scheme, a weekly ranked view, and change-tracking so a planner can see exactly why a score moved. The partner should leave the operating team owning the weekly review, not another dashboard that requires a login nobody remembers.
|
|
Build the confidence layer before the next missed date tells you it was already there to see.
|
|
|
| |
|
THE OPERATIONS BRIEF
By Bill Murphy · Powered by Colony Spark
|
|
Watching supplier promises slip and scrambling to explain why, or already building a confidence layer to spot the risk early? Hit reply, I read every one. Bill
|
|
| |
|