Ask most procurement teams “what’s the delivery date on this PO?” and you’ll get a single answer. In reality, a healthy purchase order carries at least three distinct dates, and the gap between them is often the earliest, clearest signal that something needs attention — long before the PO is technically “late.”
The three dates, defined
Contractual (original) ready date
The date the vendor is contractually committed to. This is fixed at the point the PO is issued and doesn’t move unless the contract itself is formally amended.
Current forecast ready date
The vendor’s latest, realistic estimate of when the goods will actually be ready. Unlike the contractual date, this is expected to move — vendors revise forecasts as manufacturing progresses, and a moving forecast isn’t inherently a problem. What matters is how far it moves from the contractual commitment.
Actual ready date
The date the goods are genuinely, verifiably ready — confirmed, not estimated. This is a fact, recorded once, not a moving target.
These three are sometimes confused with two other dates that describe a different part of the process entirely: ETA (the estimated site-arrival date, most reliable once the shipment is in transit) and actual arrival (when it physically shows up). Readiness and arrival are separate milestones — a PO can be “ready” at the vendor’s facility for weeks before it ships, and shipping delays are a distinct risk from manufacturing delays.
A worked example
Consider a purchase order with these dates on record:
| Date type | Value |
|---|---|
| Contractual ready date | 30 September |
| Current forecast ready date | 21 October |
| Actual ready date | (not yet recorded) |
At a glance, this PO looks fine if you’re only checking whether today’s date has passed the contractual commitment — it hasn’t yet. But the forecast already shows a 21-day variance against the contract. That’s real information, available right now, that a contractual-date-only view completely misses.
Why the PO is not technically completed
Until an actual ready date is recorded, the PO is not complete — regardless of what the forecast says. A forecast is the vendor’s best current estimate, not a confirmed fact. Treating a forecast date as if it were the actual date is how “on track” purchase orders turn into surprise delays: the forecast was trusted as fact, and when it slipped again, there was no visibility into the pattern because nothing was being compared against the original commitment.
Why early visibility matters
A 21-day gap between contractual and forecast dates, spotted the week it happens, gives you options: escalate to the vendor, adjust downstream planning, or investigate whether the delay affects a critical path. The same 21-day gap, discovered only when the contractual date arrives and nothing has shipped, gives you none of those options — only a scramble.
This is the core argument for tracking forecast variance continuously, not just checking whether a single delivery date has been missed. The variance itself is the early-warning signal; waiting for the contractual date to actually pass throws that warning away. Beyond the forecast date itself, there are other early warning signs of supplier delivery risk worth watching, such as unconfirmed inspections and unresolved NCRs.
A fourth date worth distinguishing: required delivery
There’s one more date that often gets conflated with the three above: the required site or final delivery date — the date your own project actually needs the goods, as distinct from anything the vendor has committed to. In a straightforward case, the required delivery date sits comfortably after the vendor’s contractual ready date, with enough buffer for shipping and receipt. But it’s worth tracking as its own field rather than assuming the buffer is always adequate — a vendor holding to their contractual date doesn’t guarantee the goods arrive in time for a required delivery date that didn’t account for a longer-than-expected transit route, for instance. Keeping required delivery separate from contractual ready makes that buffer visible and checkable, rather than assumed.
A common recording mistake worth avoiding
A frequent, understandable error is overwriting the contractual date field each time a vendor gives a new estimate — effectively using one field to track whatever the vendor currently says, rather than keeping the original commitment fixed and recording the new estimate separately. Once this happens, the variance calculation becomes meaningless, because there’s no longer a stable reference point to measure drift against. The contractual date should change only if the underlying contract itself is formally amended — not every time a vendor’s forecast shifts. Protecting that field from casual overwrites, even when it feels redundant to keep re-entering an unchanged value, is what keeps the whole variance-tracking approach honest.
How actual ready differs from ETA and site arrival
It’s worth being precise about what “ready” actually means, since the terms get used loosely:
- Actual ready means the goods have passed final inspection (where applicable) and are physically prepared for shipment at the vendor’s facility. It does not mean shipped.
- ETA is an estimate of the site-arrival milestone — when the shipment is expected to reach the buyer’s location. It’s most reliable once the shipment has left the vendor and a carrier has provided a timeline, but an earlier, less certain estimate can exist before that.
- Site arrival is the physical receipt event — when the goods reach the buyer’s location, before any condition check or formal acceptance.
Collapsing these into a single “delivery date” hides exactly where in the process a PO actually is. A PO stuck at “ready but not shipped” for three weeks has a very different problem — and a different fix — than one that’s shipped but delayed in transit.
Keeping all three (or five) dates connected
The practical takeaway isn’t that you need more paperwork. It’s that a single delivery date field, however carefully maintained, structurally cannot show you a forecast slipping against a contract. Recording contractual, forecast, and actual dates as three separate fields — and checking the variance between them on a regular cadence — is what turns delivery tracking from a pass/fail check on one date into an early-warning system that gives you weeks of notice instead of none.
The PO Delivery Tracker keeps contractual, forecast and actual ready dates separate on every PO. When the supplier’s updated forecast is recorded, the tracker calculates the variance against the contractual date so slippage can be reviewed before the commitment itself becomes overdue.