Note · June 2026

The supply card

A single lead-time field, entered once and never refreshed, sets a date the whole chain then spends itself defending.

A quote goes out with a delivery date on it. The rep reads the lead time off the standing supply card, adds it to the order, and sends it. The number in the field is the number it has always been.

Nobody pulls the field up to check it, because it is the number. It is where the lead time has always lived, in the record everyone reads when they need a date, and the rep reaches for it the way the rep reaches for the price.

The supplier this card is for stopped running to that lead time a while ago. An allocation tightened, the line got longer, a plant moved, the relationship is not the one the field was entered against. The supplier behaves differently now. The field still reads what it read the day someone typed it in.

By now the date that field produces is the date everyone keeps. The rep quotes it, because it is the standing number for that supplier and there is nowhere else to read the lead time from. Planning builds the schedule around it, because the quoted date is the date the customer was promised and the schedule has to land on it. The branch carries stock against it, enough to cover the date if the supplier comes in late, because the date is the promise and the promise has to be held whether or not the supplier cooperates. And when the supplier comes in late anyway, purchasing is the seat that has to make the date real. That is the expedite, the call to the supplier, the freight moved at the company’s cost, the stock pulled from a sister branch to cover what the field promised the customer.

Four functions, four different acts, one number. None of them is doing anything wrong. The rep quotes the only lead time on file. The planner schedules to the date the business committed to. The branch holds the stock because it has learned the date is not always good and the customer’s schedule does not bend. Purchasing scrambles because the date has to be met and the supplier did not make it easy. Each one is the correct response to a date the seat cannot independently verify and is accountable to. The safety stock is not slack. It is the planner’s correct response to a date the business does not fully trust.

No one refreshes the field because refreshing it was never anyone’s task. It sits in a record many functions read and no function owns as a job. Ask when it was last reviewed and there is no clean answer, because the review was never a task that belonged to a seat. The field was entered once, against conditions that have since changed, and nothing in how the chain runs makes it track the change. This is not anyone being careless. The number simply has no owner, and a number with no owner does not move when the supplier does.

So the obvious fix, retype it, set a reminder, get someone to keep it current, changes today’s number and not the condition. Tomorrow the field still belongs to no one, and the deeper fact is not that the number is wrong but that four functions have organized themselves to defend whatever the field says. Update it and the four defenses are still pointed at it. And reading it as a data-hygiene item, one stale field among many, a clean-up line for a master-data project, is exactly what keeps it from getting an owner, because a hygiene item is a backlog item nobody escalates while this field is quietly setting the date the branch holds stock against and purchasing expedites to meet. The least maintained record in the file is the most defended number in the chain. The work the four seats do every day is built around a date none of them owns, and none of them is positioned to question.

The date the whole chain spends itself defending is set by the one record nobody is defending.

The supply card is one record among the handful the business commits against before it can deliver, and it sets a date four functions then spend themselves keeping. Which of those records get an owner, and which keep setting dates nobody is maintaining, is the decision sitting underneath the next order. That is where the work actually starts.