Karim, the production manager at Delta Garments, runs Order A for Northline Apparel and a domestic batch for Cedar & Co. at the same time, both drawing on some of the same suppliers. This lesson mainly teaches the information flow of pulling three separate skills, naming every supplier, tracking blind milestones, and judging ship-date threats, into one shared tracker that covers more than one order line at once.
Without a single combined tracker, a factory risks running three different, disconnected records for what should be one coherent picture, missing the moment a delay at a shared supplier, such as Colorline Dyeing, threatens both the export line and the domestic line at the same time. This lesson teaches how to build that one complete tracker.
You need: lessons 27.3.1 (naming every supplier), 27.3.2 (tracking a blind milestone) and 27.3.3 (deciding a ship-date threat) 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 in detail (lesson 27.3.1), the specific method for tracking a blind milestone (lesson 27.3.2), and the specific method for judging a ship-date threat (lesson 27.3.3).
| Term | Meaning |
|---|---|
| Digital critical-path tracker | The complete tool combining owner, due-date, status, linked-milestone, alert and connected-workflow fields for a live order. |
| Cross-supplier critical path | A critical path drawn across every supplier tier an order actually depends on, not only the factory the buyer directly contracts with. |
| Blind milestone | A milestone whose progress a buying office cannot check directly, because it happens at a supplier the buying office has no line of sight into, and can only be tracked through an intermediary's own reporting. |
| 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. |
| Dependent milestone | A milestone whose own due date cannot be met until an earlier, linked milestone is complete. |
| Cascading delay | The effect where a delay at one milestone pushes back every dependent milestone after it by the same amount. |
A complete cross-supplier tracker holds every milestone, from every supplier, for every order line a factory is running at once, each tagged with its own owner, its own buffer and its own line. When two order lines share a supplier, only a combined tracker shows how the same delay affects each line differently.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| Number of order lines sharing a supplier | Order A and a Cedar & Co. batch both draw fabric from Colorline Dyeing at overlapping times; a factory running only one line at a time has no shared-supplier risk to track at all. | More shared suppliers across active lines means more places one delay can affect more than one order at once. |
| Business model mix | Order A's own Make to Order line books a fixed production slot; the Cedar & Co. batch's own Make to Stock line draws from running stock, so its blind-milestone check differs even for the same supplier. | A combined tracker must record each line's own business model, since the same supplier milestone is checked differently depending on it. |
| How tight each line's own buffer is | Order A's own buffer before its fixed sailing date can be a few days at a given point; the Cedar & Co. batch's own buffer before its cutting date can be different again, even against the identical delay. | The tracker must calculate buffer per line, not once for the shared supplier, since a single delay can be recoverable on one line and a ship-date threat on the other. |
| Who owns escalation on each line | Sara at Northline Apparel owns escalation decisions for Order A; Omar at Cedar & Co. owns them for his own batch; Karim at Delta Garments owns the factory-side milestones for both. | A combined tracker must route an alert to the correct owner for each affected line, not to a single generic contact. |
| Product family | A factory also running a hosiery order for Suez Hosiery, alongside apparel lines, tracks a different supplier chain entirely for that order, since Suez Hosiery knits directly from yarn without a separate knitting-mill tier. | A tracker built to scale across product families must allow each order line its own supplier chain, not force every line into the same fixed chain. |
Delta Garments is running Order A (15,000 pieces, export, Make to Order) and a Cedar & Co. batch (3,000 pieces, domestic, Make to Stock) at the same time. Both lines depend on Colorline Dyeing for dyed and finished fabric, though on different production slots. Karim sets up one tracker with a row for each milestone, tagged by order line, supplier, owner, due date, buffer and blind/direct status.
When Colorline Dyeing reports a 3-day delay affecting its current production run, Karim checks the tracker for every row tagged "Colorline Dyeing" and finds two: one for Order A, one for the Cedar & Co. batch. Each row's own buffer, calculated separately in lesson 27.3.3's own method, shows the delay is recoverable for Order A (about 4 days of buffer before Order A's own port cut-off) but leaves the Cedar & Co. batch with a much thinner margin (2 days of buffer before Omar's own cutting date, as calculated in lesson 27.3.2).
The worked numberThe identical 3-day delay at the same supplier is recoverable on Order A but becomes a genuine threat on the Cedar & Co. batch, whose own buffer was already thinner; only a tracker holding both lines side by side reveals this difference in one look.
A common mistake is keeping Order A's tracker and the Cedar & Co. batch's tracker as two separate spreadsheets. It costs a factory the ability to see a shared risk at all: a 3-day delay at Colorline Dyeing can look like two unrelated minor updates in two separate trackers, when in fact it is one supplier event that is recoverable on one line and a genuine ship-date threat on the other.
A factory rarely runs just one order at a time, and different orders often use some of the same outside suppliers. If you keep a separate record for every single order, you can miss the moment one supplier's delay actually hits two orders at once, in different ways. Putting every order's own milestones, from every supplier, into one shared list lets you see all of that together. The same delay can be a small problem for one order and a real threat for another, and only a combined view shows you both at the same time.
Colorline Dyeing has just reported the delay affecting its current production run, which feeds both Order A and the Cedar & Co. batch.
Should Karim update the one combined tracker and let it show each line's own status separately, or write two separate, disconnected updates, one for each buyer? Decide before opening the answer.
Karim should update the one combined tracker, entering the single 3-day delay once against Colorline Dyeing, and let the tracker calculate and display each line's own separate buffer and status.
1. Entering the delay once, in one place, avoids recording the same supplier event twice with a risk of the two records drifting out of agreement over time. 2. The combined tracker's own calculation already shows Order A as recoverable and the Cedar & Co. batch as a ship-date threat, using each line's own buffer, so Karim does not need to redo that comparison separately for each buyer. 3. Routing the alert correctly still matters: Sara receives a routine update for Order A, while Omar receives an urgent alert for his own batch, both generated from the same single tracker entry rather than two separately maintained records.
One combined tracker, correctly tagged per line, protects against exactly the kind of missed shared-supplier risk that two separate, disconnected trackers would hide.
Colorline Dyeing's 3-day delay leaves Order A with about 1 day of buffer, recoverable, but leaves the Cedar & Co. batch at about -1 day, a genuine ship-date threat. If Karim tracked each line separately and did not compare both against the same supplier event, the Cedar & Co. batch's own threat could go unnoticed until fabric simply fails to arrive on Omar's own cutting date.
The figures here are framed against each line's own buffer rather than a fixed cost from the master order data, since no per-day delay cost is fixed for either order; they show why one combined tracker, not two disconnected ones, is what actually catches a shared-supplier risk before it becomes a missed shipment.
Open the Cross-supplier critical path tracker and enter every order line's own supplier milestones, using the "Supplier milestone map", "Blind milestone log" and "Ship-date threat check" sheets together. Tag each row with its own order line, owner and business model, so the tracker calculates buffer and threat status separately for every line, even where a supplier is shared.
[Download the Cross-supplier critical path tracker workbook](../../templates/T27-C03-cross-supplier-critical-path-tracker.xlsx)
1. Why does a combined tracker covering more than one order line show something two disconnected trackers cannot?
2. Colorline Dyeing's 3-day delay leaves Order A with 1 day of buffer and the Cedar & Co. batch with -1 day. What should Karim do?
3. What is the main risk of keeping Order A's and Cedar & Co.'s trackers as two separate spreadsheets?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Digital critical-path tracker | متتبع المسار الحرج الرقمي | Suivi numérique du chemin critique | Dijital kritik yol takip listesi | The complete tool combining owner, due-date, status, linked-milestone, alert and connected-workflow fields for a live order. |
| Cross-supplier critical path | المسار الحرج عبر الموردين | Chemin critique multi-fournisseurs | Tedarikçiler arası kritik yol | A critical path drawn across every supplier tier an order actually depends on, not only the factory the buyer directly contracts with. |
| Blind milestone | مرحلة عمياء | Jalon aveugle | Kör kilometre taşı | A milestone whose progress a buying office cannot check directly, because it happens at a supplier the buying office has no line of sight into, and can only be tracked through an intermediary's own reporting. |
| 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. |
| Dependent milestone | مرحلة تابعة | Jalon dépendant | Bağımlı kilometre taşı | A milestone whose own due date cannot be met until an earlier, linked milestone is complete. |
| 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. |
This is the final lesson of Course 3. Track 27's next course continues buyer-side order and supplier management with a new set of tools and scenarios. Back to the course map