A missed milestone is not automatically a shipping problem. Meridian Sourcing, the agent coordinating a hybrid order for Delta Garments, learns that Colorline Dyeing released fabric 3 days late. This lesson mainly teaches a decision: given a specific delay and the buffer remaining before the fixed sailing day, does this particular miss actually threaten the ship date, or does the order's own buffer absorb it without any change to the plan.
Without a method for making that decision, an agent either raises an alarm over every minor delay, wasting management's attention, or ignores every delay equally, missing the one that genuinely threatens the ship date. This lesson teaches how to tell the two apart using the order's own fixed dates.
You need: lessons 27.3.1 (naming every supplier on the critical path) and 27.3.2 (tracking a milestone you cannot see directly) as background are useful but not required.
By the end of this lesson you can:
Not covered here: naming every supplier on a critical path (lesson 27.3.1), tracking a milestone you cannot see directly (lesson 27.3.2), and building the complete tracker across every supplier (lesson 27.3.4).
| Term | Meaning |
|---|---|
| Critical path | The chain of sequential stages that sets the shortest possible total time for the order. |
| Recoverable delay | A stage finishes late, but a buffer later in the timeline absorbs it without moving the final date. |
| Non-recoverable delay | A stage finishes late with no buffer left, so the final date must move or a costlier recovery option must be used. |
| Cascading delay | The effect where a delay at one milestone pushes back every dependent milestone after it by the same amount. |
| Ship-date threat | A missed critical path date whose delay is large enough, with no downstream buffer left to absorb it, that it actually pushes back the order's own ship date. |
| Buffer | Extra days or weeks added to a timeline on purpose, to absorb a likely delay. |
Deciding whether a missed date is a ship-date threat means comparing two numbers: the size of the delay itself, and the buffer still available before the order's fixed cut-off. A 3-day delay early in a 16-week timeline, with weeks of buffer still ahead, is a different event from the same 3-day delay discovered the week before the port cut-off.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| Where the milestone sits on the timeline | A delay at Colorline Dyeing, early in Order A's 5-week fabric stage, still has the sewing, inspection and shipping stages ahead of it to potentially absorb it. A delay discovered at the port cut-off itself has no later stage left to absorb anything. | The same number of delay days is far more dangerous the closer it sits to the fixed sailing date. |
| Business model | The confirmed line of a hybrid order has a fixed sailing date the buyer has already booked; the forecast line often has more flexibility on its own final date. | A missed milestone on the confirmed line is more likely to be a genuine ship-date threat than the identical miss on the forecast line. |
| Whether the delay cascades | A delay at Colorline Dyeing pushes back Delta Garments' own cutting start by the same amount, which can then push back sewing, which can then push back inspection, unless buffer exists at each stage to absorb it. | A cascading delay can consume buffer at several stages at once, so the true remaining buffer must be checked at every downstream stage, not just the first one. |
| Who owns the fixed date being protected | Northline Apparel's own letter of credit and Bluewater Line's own sailing schedule fix Order A's day-16 sailing date; Meridian Sourcing cannot move it unilaterally. | An agent coordinating the order must protect a date it does not itself control, which is why an early, accurate threat decision matters more than a late one. |
| Market | An export order like Order A has one fixed overseas sailing date; a domestic order moving by road to Cedar & Co.'s own shops can sometimes rebook a delivery slot with more flexibility. | A domestic order's own buffer decisions can sometimes absorb a larger delay than an export order's fixed sailing schedule allows. |
Order A's fabric stage runs weeks 3 to 7 of its 16-week timeline, with Colorline Dyeing's own dyeing and finishing milestone due at the end of week 7. Meridian Sourcing learns the milestone actually finished 3 days late, partway into week 8. The agent must now decide whether this reaches Sara at Northline Apparel as a routine update or an urgent one.
Order A's port cut-off falls on day 13 of week 13, and sailing is fixed for day 16 of week 16. Between the end of week 7 (when fabric was due) and the port cut-off in week 13, the timeline holds 6 weeks for sewing, inspection, packing, documents and part of shipping, several days of which are ordinary schedule buffer rather than bare minimum time.
The worked numberThe 3-day delay is smaller than the roughly 4 days of ordinary buffer already built into the schedule between fabric completion and the port cut-off, leaving about 1 day of buffer still in hand; this specific miss is recoverable and does not, on its own, threaten the day-16 sailing date.
A common mistake is escalating every missed date to management as urgent, without first checking the buffer that remains. It costs an agent's own credibility: escalating a recoverable 3-day delay as if it were a ship-date threat wastes management's attention, and can make a genuine future threat harder to get taken seriously once it actually arrives.
Not every late date is an emergency, and not every late date is fine to ignore. What matters is how much spare time was already built into the schedule between that date and the fixed day the ship actually sails. If the delay is smaller than the spare time left, the order is still fine. If the delay is the same size as the spare time, or bigger, the sailing date itself is now genuinely at risk. The only way to know which situation you are in is to do the comparison, not to guess from how the delay feels.
Meridian Sourcing has just confirmed the size and timing of the delay.
Should Meridian Sourcing report this delay to Sara as an urgent ship-date threat, or as a routine update that the order's own buffer already absorbs? Decide before opening the answer.
Meridian Sourcing should report this delay as a routine update, not an urgent ship-date threat, while still recording that the buffer has shrunk to about 1 day.
1. The 3-day delay is smaller than the roughly 4-day buffer already built into the schedule between fabric completion and the port cut-off, so the day-16 sailing date is not currently at risk from this specific miss. 2. Reporting it as urgent would consume Sara's management review time on an issue the schedule's own buffer already handles, weakening the impact of a genuinely urgent report later if one becomes necessary. 3. Recording the reduced buffer, even in a routine update, keeps Sara informed that only about 1 day of slack remains, so a further delay of even 1 more day at any downstream stage would need to be reported as urgent.
Meridian Sourcing's own credibility depends on reserving "urgent" for delays the buffer cannot absorb, not for every delay that occurs.
The schedule holds about 4 days of buffer between fabric completion and Order A's port cut-off; the actual 3-day delay leaves about 1 day of that buffer still in hand. Reporting this as urgent would spend management review time disproportionate to the actual risk, while leaving less credibility available if a later delay genuinely does threaten the fixed sailing date.
The figure here is framed against the schedule's own buffer rather than a fixed cost from the master order data, since no per-day delay cost is fixed for Order A; it shows why an accurate threat decision, not an automatic escalation, protects both the schedule and the agent's own credibility with management.
Open the Cross-supplier critical path tracker, "Ship-date threat check" sheet. For each missed milestone, enter its due date, its actual completion date and the order's own fixed protected date; the sheet calculates the delay, the buffer that existed, and flags whether the miss is recoverable or a genuine ship-date threat. Start with Colorline Dyeing's 3-day delay above, then log one delay of your own.
[Download the Cross-supplier critical path tracker workbook](../../templates/T27-C03-cross-supplier-critical-path-tracker.xlsx)
1. What determines whether a missed milestone counts as a ship-date threat rather than a recoverable delay?
2. Colorline Dyeing's fabric is 3 days late, and about 4 days of buffer existed before Order A's port cut-off. What should Meridian Sourcing conclude?
3. Why might reporting every missed milestone as equally urgent actually make Meridian Sourcing's future reports less effective?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Critical path | المسار الحرج | Chemin critique | Kritik yol | The chain of sequential stages that sets the shortest possible total time for the order. |
| Recoverable delay | تأخير قابل للتعويض | Retard rattrapable | Telafi edilebilir gecikme | A stage finishes late, but a buffer later in the timeline absorbs it without moving the final date. |
| Non-recoverable delay | تأخير غير قابل للتعويض | Retard non rattrapable | Telafi edilemeyen gecikme | A stage finishes late with no buffer left, so the final date must move or a costlier recovery option must be used. |
| Cascading delay | تأخر متسلسل | Retard en cascade | Zincirleme gecikme | The effect where a delay at one milestone pushes back every dependent milestone after it by the same amount. |
| Ship-date threat | تهديد لتاريخ الشحن | Menace sur la date d'expédition | Sevkiyat tarihi tehdidi | A missed critical path date whose delay is large enough, with no downstream buffer left to absorb it, that it actually pushes back the order's own ship date. |
| Buffer | هامش وقت احتياطي | Marge de sécurité | Tampon süre | Extra days or weeks added to a timeline on purpose, to absorb a likely delay. |
Next you will learn how to combine every supplier milestone, blind milestone and ship-date threat check into one complete tracker covering an entire order, or several order lines at once. Back to the course map