DEV Community

Gavren
Gavren

Posted on

Thirty-Five Days Was Promised, Forty-Eight Was Shipped

The order confirmation said thirty-five days. The goods sailed on the forty-eighth. Nobody was idle; the shop floor worked the whole time. The thirteen days went missing at the finishing stage, which happens outside the plant, which means it never appears on the scheduling board, which means nobody folded it into the promised date.
Why does the lead time break at the subcontracted stage?
Because the schedule describes internal operations. Cutting, bending, welding, assembly and packing all sit on a board on the wall where somebody watches them and somebody chases them. Powder coating, plating, moulding and heat treatment happen in another company's building, and they are recalled only when the goods are ready to go there.
The problem at a subcontractor is rarely capacity. It is the queue. Your batch arrives behind somebody else's batch, and which one runs first is decided by them, not by you. During that window your factory has no lever at all.
It is also invisible from the inside. When the customer asks for progress, the factory can report on internal stages only. The answer for the outside process is usually in hand, a phrase that can mean three days or three weeks.
There is one question worth asking directly: how long the last batch waited at that subcontractor. A specific number means the stage is being measured. A general answer of usually quick means nobody has ever measured it.
Scheduling at a subcontractor follows different rules. It runs by fixture, by tonnage, by oven load, not by your order number. A batch that does not fill a fixture waits for the next batch to fill it, and that waiting time does not exist anywhere on your own schedule.
Which stages should the promise be divided into?
The table below is the only one here: the stage on the left, the hidden problem typical of that stage in the middle, and the wording worth writing into the clause on the right.
| Stage | Hidden problem | Wording to put in the clause |
|---|---|---|
| Incoming material and inspection | Shortages surface late, when half the lead time has gone | Agree how critical parts are confirmed and within what notice |
| Machining and welding | Changeover time is not counted, so small batches carry it heavily | State how changeover hours are handled by batch size |
| Subcontracted processes | Queue time is invisible and capacity is shared | Name the process, the subcontractor and a minimum queue allowance |
| Assembly and testing | Kits are incomplete, so assembly starts and waits | Agree the condition for starting with a complete kit |
| Pre-shipment inspection | Rework time after a failed inspection is unspecified | Agree the inspection method and the disposition deadline |
| Booking and loading | Space is scarce and the next sailing is passive waiting | Agree who books, and the latest booking date |
Not all six belong in the contract, but all six belong in the quotation conversation. Whatever you ask about and then leave out, you at least know where the risk sits and which stage deserves a buffer.
Every line on the right converts a duration into an action with an owner. Lead time clauses fail because they carry a single total number, while the total sits on six places that can each stop independently.
One more number deserves its own question: the round trip to the subcontractor. It is usually absorbed into processing time, when it is really two journeys plus one queue. Asked separately, the three answers rarely add up to the same week that the phrase about a week implies.
If only one stage can go into the contract, make it the subcontracted one. It is the only stage you can neither expedite, nor observe, nor perform yourself; on the other five, somebody in the building can act the same day.
Why does the start date matter more than the number?
Thirty-five days means nothing on its own; what matters is the day the count begins. Three candidates are common: order confirmation, deposit received, and drawing approval. Between them they can differ by weeks.
Order confirmation is the most generous to the seller, while most buyers read confirmation as the start of work. Deposit received is verifiable by both sides and is the easiest to execute. Drawing approval comes closest to reality, provided both sides define approval the same way — a signature, an email reply, or an approved sample.
Once the start point is fixed, the composition of the number deserves the same attention. Of the thirty-five days, only part is actual processing; the rest is queueing, waiting for a complete kit and the outside process. Negotiating the composition is easier than arguing the total, because each element can be checked on its own.
The usual failure is that each side applies a different start point while assuming the other uses the same one. If the contract never says which, the disagreement surfaces the first time somebody counts to thirty and looks at the calendar.
The workable form pairs the event with its evidence: the count runs from the day the deposit lands, evidenced by the bank record. That sentence can be executed on day one and checked years later.
How should the extension clause be written to avoid a fight?
Extension clauses usually list a series of excused events, and the argument is never about the list. It is about evidence. The buyer says the event did not affect you; the supplier says it did; neither has a record.
An executable version attaches an action to each event. A drawing change by the buyer extends the date by the written change order. A buyer-nominated material arriving late extends it by the receiving record. Force majeure extends it by the official notice or the carrier''s advice.
The record of extensions is best kept by one side and confirmed by the other every week. The expensive part of a dispute is not disagreement but reconstruction: three months later, two memories of which day the drawing changed will not match.
The scope of the impact needs separating too. One change may affect a single operation, or it may scrap semi-finished stock already built. The clause should extend by the actual impact rather than pausing the whole clock on the day the change arrived.
There is a second half that gets left out: the extension must be claimed within a stated period, or it is waived. Without that, a supplier can attribute three months of drift to a drawing change raised in the final week.
Why should the remedy not be a penalty alone?
A penalty is the easiest clause to write and the hardest to make whole. What the buyer actually loses is rarely the invoice value. It is an empty shelf, a delayed project, a promotion missed.
A layered structure works better. Minor delay attracts a daily liquidated amount. Moderate delay gives the buyer the option of a split shipment or a revised date. Severe delay gives the right to cancel the undelivered balance. Each layer has its own trigger, and triggers are easier to apply than a single compensation ratio.
The layering helps the supplier too. It turns never be late into how late, at what cost, which is a negotiation with room in it rather than a promise nobody can keep.
One last caution: a shorter lead time is not automatically a better one. Compress it to the limit and the cost reappears elsewhere — expediting fees to start early, a premium to jump the subcontractor queue, or a few inspection items quietly relaxed.
The structure costs the buyer something too: layering means making a choice when the delay happens, and a choice needs a decision-maker. A buyer who will not decide reduces three tiers back to one, and the one that remains is the penalty.
The precondition is that each tier is triggered by a date. Triggering on expected delay turns the clause into an argument about expectations. Triggering on the actual shipment date leaves a single calendar fact to disagree about, which is a much shorter argument.
FAQ
Should lead time be counted in working days or calendar days?
It must be stated. Across holidays and long shutdowns the two can differ by a full week. Calendar days are simpler, provided statutory holidays are listed explicitly.
Should subcontracted processes be named separately?
Yes. They are the least controllable part of the promise, and the buyer is entitled to know which operations happen outside the plant.
What should a supplier report when the buyer asks for progress?
Stages, not adjectives. Now at the subcontractor is information; pushing hard is not. If the queue position cannot be stated, that stage was never being managed.
When a shipment is late, negotiate the goods or the compensation first?
The goods. Compensation is a book entry until the cargo lands. Agree the split shipment and the revised schedule first, then the remedy; both sides usually accept that order.
All periods in this article are illustrations rather than figures from a standard or an industry dataset; delivery and liability terms are best agreed in the contract.

Top comments (1)

Collapse
 
hiredov profile image
Dov at HireDov •

The subcontracted-stage queue is the sneakiest one, since it never shows up on anyone's own board. The question that has worked for me is asking for the last batch's actual wait at that vendor, not their usual turnaround; as you say, a vague answer usually means nobody measures it. I'd also add a queue allowance for the specific process (plating, powder coat) straight into the quote, so the buffer is written down before the order starts instead of argued about at day 35. Sourcing would be a lot more fun if every lead time came with a footnote, but a clause like this is the next best thing.