A digital workflow with an owner, a due date and a status on every milestone, as built in Lesson 1, still treats each milestone as its own separate record. It does not yet show that a delay in one milestone changes the due dates of the milestones after it. Linking dependent milestones connects each task record to the one it feeds, so a status change in one place recalculates, or at least flags, everything downstream of it. This is chiefly an information-flow skill for both sides of an order: a buyer reading the workflow needs to see immediately what a factory delay will do to the ship date, without waiting for someone to explain it on a call.
Without this link, a late milestone sits on the page as one isolated red flag, and a busy buyer or merchandiser has to work out its downstream effect by hand, on every order, every time something slips.
You need: Lesson 1 of this course, which builds the digital workflow's owner, due-date and status fields.
By the end of this lesson you can:
Not covered here: setting alert and escalation rules on top of these links (Lesson 3), and combining approvals, materials, production and shipment in one workflow (Lesson 4).
| Term | Meaning |
|---|---|
| Dependent milestone | A milestone whose own due date cannot be met until an earlier, linked milestone is complete. |
| Downstream milestone | Any milestone that comes later on the critical path and is affected if an earlier one slips. |
| Cascading delay | The effect where a delay at one milestone pushes back every dependent milestone after it by the same amount. |
| Linked task | A task record connected in the digital workflow to the task record it depends on, so a date change carries forward. |
| Buffer | Extra days or weeks added to a timeline on purpose, to absorb a likely delay. |
| Ripple effect | The visible chain of date changes across several milestones caused by one original delay. |
A digital workflow becomes genuinely useful once its milestones are not just listed but linked: each task record names the milestone it depends on, so that a change to one due date carries forward to every milestone after it. Without this link, a merchandiser updating one milestone's status has no way to show, inside the tool itself, that three later milestones are now also at risk. With the link, moving one due date by a number of days moves every dependent milestone by the same number of days, unless a buffer absorbs some of the delay.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| Export vs. domestic order | An export order's linked chain, such as Order B's jeans, runs all the way through shipping and warehouse arrival at an overseas address; a domestic order's chain stops at a nearby local warehouse. | Applying an export order's own long shipping link to a domestic order overstates how far a domestic delay actually reaches. |
| MTO vs. MTS vs. hybrid | A Make to Order chain links every milestone back to one confirmed order, so a delay affects one ship date; a Make to Stock chain links milestones to a recurring replenishment cycle, so a delay can affect several future cycles at once; a hybrid account runs both chains for the same buyer. | Treating an MTS replenishment delay as if it only affected one shipment, the way an MTO delay does, understates its effect on the next planned cycles. |
| A milestone with a buffer vs. one without | Some factories build a buffer into a milestone, such as an extra few days before ex-factory, so a small delay upstream does not automatically reach the ship date. | A linked workflow that ignores a real buffer overstates the delay; one that ignores a missing buffer understates it. |
| A buyer-visible link vs. an internal-only link | A buyer such as Northline Apparel typically sees linked milestones from approvals to ex-factory; some factories keep internal hand-offs, such as between departments, linked but not shown to the buyer. | Sharing every internal link with a buyer can create noise; hiding a link that affects the ship date removes information the buyer actually needs. |
| Socks, terry and home-textile product families | A hosiery or towel order's linked chain uses the same dependency logic, with that family's own stage names, such as boarding depending on linking for socks. | The rule that a delay carries forward through linked milestones does not change by product family; only the stage names do. |
Order B's jeans workflow, built in Lesson 1, has seven linked task records running from approvals (due week 3) through fabric in-house (week 10), sewing complete (week 13), washing complete (week 16), ex-factory (week 17), shipping (week 21) and warehouse arrival (week 22). Sara, the buyer at Northline Apparel, has read access to Delta Garments' own digital workflow for this order.
Delta Garments reports that fabric in-house will now complete in week 12 instead of week 10, a two-week delay caused by a late delivery from Suez Denim. Because Sara's workflow view links every milestone after fabric in-house to it, she does not need to phone Karim to work out the consequence. The tool itself already shows every later milestone shifted by two weeks, unless Delta Garments confirms a buffer will absorb part of the delay.
The worked numberEvery one of these five later dates moves by exactly the same two weeks, because none of the stages between fabric in-house and warehouse arrival has a buffer built in for Order B's jeans. If Delta Garments had a one-week buffer before ex-factory, only one of the two weeks would reach the ship date, and the tool would need that buffer recorded to calculate it correctly.
A common mistake is treating a status update as complete once the delayed milestone itself shows the new date, without confirming that the linked milestones after it updated too. If Order B's jeans workflow does not actually link fabric in-house to sewing complete, Sara can see fabric in-house marked two weeks late while sewing complete still shows its original week 13 due date, unchanged and now impossible to meet. A workflow that shows unlinked, contradictory dates is worse than a plain written schedule, because it looks authoritative while quietly hiding the real risk.
A digital workflow is only half useful if it just lists milestones separately. The real value comes from linking each milestone to the one it depends on, so that a delay in one place automatically shows up in every later milestone connected to it. If fabric arrives two weeks late, and nothing absorbs that time, every stage after it, sewing, washing, shipping, arrival, moves two weeks later too. Seeing that whole chain at once, instead of hearing about it stage by stage over several phone calls, is what lets a buyer and a factory agree quickly on what to do next.
Delta Garments reports fabric in-house for Order B's jeans will now complete in week 12 instead of week 10. Sara opens the linked digital workflow before replying to Delta Garments' email.
The relevant line from Delta Garments' email:
Should Sara accept the new week 24 warehouse date, or ask Delta Garments to recover time elsewhere in the schedule? Decide before you open the decision.
Sara should ask Delta Garments whether time can be recovered in a non-critical stage before accepting a two-week-later warehouse date.
The two facts that decide this are the linked workflow's own calculation, which shows the full two-week delay reaching warehouse arrival with no buffer to absorb it, and Northline Apparel's fixed shop-floor date in week 22, which the new week 24 date would miss. Sara does not simply accept the tool's default projection as unavoidable; she uses it as the starting point for a request: can shipping be compressed, or can inspection and documents run in parallel with the last days of washing, to recover some of the two weeks before it reaches the ship date. If no time can be recovered, Sara escalates the shop-floor date change to her own planning team early, using the linked workflow's own numbers as evidence, rather than discovering the miss in week 22.
Order B's jeans total FOB value is fixed by its price and quantity:
If Sara only saw the fabric in-house milestone marked late, with no linked view of the downstream dates, she might not raise the shop-floor conflict until week 19 or 20, when almost no time remains to compress shipping or negotiate a partial air-freight solution. Discovering a two-week miss with two weeks left to fix it costs far more, in expedited freight or a missed shop-floor date across the whole USD 29,400 order, than discovering the same miss with twelve weeks left, the moment the fabric delay is first reported.
Use the T17-C03 Digital critical-path tracker. For Order B's jeans, add a "depends on" column linking each milestone to the one before it, and a buffer column recording any known slack before a milestone. When a status changes, use the linked columns to recalculate every downstream due date before reporting the change to the buyer.
[Download the Digital critical-path tracker](../../templates/T17-C03-digital-critical-path-tracker.xlsx)
1. What does linking one milestone to the milestone it depends on actually add to a digital workflow?
2. Fabric in-house for Order B's jeans moves from week 10 to week 12, and no buffer exists before ex-factory (originally week 17). What is ex-factory's new due date in the linked workflow?
3. A domestic Make to Stock order's replenishment workflow has a two-week delay at its own dyeing milestone, with no buffer before the next scheduled restock cycle. What does the linked workflow show?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| 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. |
| Downstream milestone | مرحلة لاحقة | Jalon en aval | Sonraki kilometre taşı | Any milestone that comes later on the critical path and is affected if an earlier one slips. |
| 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. |
| Linked task | مهمة مرتبطة | Tâche liée | Bağlantılı görev | A task record connected in the digital workflow to the task record it depends on, so a date change carries forward. |
| Buffer | هامش وقت احتياطي | Marge de sécurité | Tampon süre | Extra days or weeks added to a timeline on purpose, to absorb a likely delay. |
| Ripple effect | أثر التتابع | Effet d'entraînement | Domino etkisi | The visible chain of date changes across several milestones caused by one original delay. |
Next you will learn how to set alert and escalation rules on a digital workflow, so only genuine exceptions reach a manager instead of every task on the order. Back to the course map