Lead Time Has a Clock

“Ten to twelve weeks” sounds like a fact until somebody asks: ten to twelve weeks from what?

From the quote date? From deposit? From a signed approval? From receipt of COM? From final field dimensions? From shop-drawing approval? From the day the factory decides the order is complete enough to enter production?

Lead time is useful only when the clock has a start condition.

This is one of the reasons procurement can look much more certain than it is. A schedule has a number. The number becomes a date in somebody’s head. That imagined date begins steering installation, temporary solutions, substitute conversations and client expectations even though the record never established when production actually begins.

Keep the source with the duration

A lead-time number should be accompanied by its source and the date of that source. A vendor quote dated this week is different evidence from a product page last updated nobody knows when. A manufacturer statement is different from a salesperson’s estimate. A confirmed production window is different from the number that appeared before the order was placed.

Practice keeps the duration, the lead-time source and the clock trigger as separate fields for a reason. “8–10 weeks” is one fact. “Vendor quote dated September 10” is another. “Clock starts after approved COM is received” is the part that makes the first fact usable.

When any of those changes, the sourcing history should show the change instead of silently overwriting the old expectation.

Selected is still early

Room for Drama now treats procurement as a decision trail rather than a binary purchased/not-purchased flag.

An item can be considered, selected, quoted, approved, ordered, confirmed, shipped, received and installed. The record can also preserve an issue, return or replacement, along with real-world exceptions such as backorder, damage, discontinuation or hold.

These states exist because each one answers a different question. A selected item can still have no price. A quoted item can still have no approval. An ordered item can still have no factory confirmation. A shipped item can still arrive damaged. A received item can still fail the specification when unpacked.

Compressing all of that into “ordered” makes the interface look simpler by making the evidence worse.

The decision deadline is different from the delivery date

Procurement becomes a design problem when delay changes what remains possible.

If a custom upholstery order must be released by Friday to make an installation window, Friday is a decision deadline. If a tile has a six-week lead time but the installer cannot start until waterproofing is verified, the project may have more decision time than the raw lead-time number suggests. If a fixture has a substitute available locally, the decision may remain open longer than an item with no credible alternative.

The useful date is often the last date a decision can move without creating a consequence.

That is why the Practice sourcing record carries a decision deadline separately from the lead-time duration. It makes urgency explainable. “Decide now” is weak project language. “Release by September 18 or the current installation week is no longer supported by the vendor’s quoted lead time” is a defensible reason.

Receiving belongs in the decision chain

Procurement does not end when a tracking number appears.

Somebody has to know where the item is going, who can receive it, what happens if the carton is damaged, how quickly a freight claim has to be made, whether the return window begins at delivery and whether the object can physically travel from the loading point to the room.

Those facts become especially important for custom, oversized, fragile or finish-sensitive pieces. A product that fits the design and misses the receiving reality is still a bad project outcome.

The Room Record therefore keeps a receiving owner, return or damage terms and installation dependencies. They are not warehouse fields. They are conditions that can change whether the selected design is still a responsible choice.

Do not let a changed date erase the old one

A useful procurement history is append-only in spirit. The current state should be easy to see, but the route to that state should remain available.

If the original quote said eight weeks, the confirmation moved to twelve, the order then backordered and a replacement was approved, that sequence explains later decisions. Without it, the project ends up with one current date and no record of why the installation plan changed three times.

Practice logs dated sourcing events with an evidence source. The point is not to produce a heroic timeline. The point is to make changes legible enough that nobody has to reverse-engineer them from an inbox.

Cost certainty changes too

Time is not the only sourcing fact that gets promoted too early. Money does the same thing.

An allowance, an estimate, a quote and a purchased cost are different states of certainty. A $4,000 allowance is not evidence that an item costs $4,000. A quote may expire. Freight may be excluded. Tax may be missing. A purchased cost is firmer, but installation or receiving costs may still sit elsewhere.

The sourcing record should say which kind of number it has and when that number was current. The allowance record exists for exactly this reason.

Procurement should explain pressure, not manufacture panic

Professional project systems can become very good at showing red badges. The harder question is whether the badge represents a real dependency.

A missing vendor on an item merely being considered may be harmless. A missing receiving owner on an item already shipped is different. An unresolved lead-time clock on a selected custom item can matter. A substitution request that changes a governing performance condition should push the design back toward review.

The Practice layer is built around those distinctions. It names what is still owed and lets cross-record evidence raise a hold or check when a recorded dependency makes the next step indefensible. It does not award a completion percentage for filling boxes.

Keep the procurement fact attached to the design reason

A sourcing decision should remain connected to the specification it is sourcing. That is what prevents a replacement from being evaluated as a freestanding shopping choice.

When the selected item changes, return to the specification: performance, material, dimensions, quantity, clearance, maintenance, substitution rule and design reason. Then ask whether the sourcing event changed any of them.

If it did, the design decision may need to reopen. If it did not, the project can move without pretending the product name itself was sacred.

Use the Room Record in Practice mode to keep sourcing state, lead-time evidence and cost confidence with the room. Then read Selected Is Not Ordered for the underlying distinction between selection and actual procurement state.