The first four lessons of this course built one control at a time: an owner, date and status for every milestone; links so a delay carries forward; alert and escalation rules so exceptions reach the right person; and one connected workflow across approvals, materials, production and shipment. A live order needs all four working together, not as separate exercises but as one finished tracker a merchandiser opens every day. This is chiefly a decision-flow skill: turning a course's worth of separate controls into one working tool for a real order in front of you.
Without bringing these controls together, a merchandiser can know each technique individually and still fail to apply them consistently to the one order that actually needs watching this week.
You need: Lessons 1 through 4 of this course, which build the digital workflow's owner, due-date, status, linked-milestone, alert and connected-workflow fields, all combined in this lesson.
By the end of this lesson you can:
Not covered here: this is the last lesson of the course; further tracks apply these same principles to other tools.
| 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. |
| Live order | An order currently in progress, being actively tracked, as opposed to a finished or a purely hypothetical one. |
| Hybrid account | A buyer relationship that combines Make to Order and Make to Stock business with the same factory. |
| True current status | The order's real position right now, based on the tracker's actual data, not on the last verbal update someone remembers. |
| Milestone owner | The named person or department accountable for getting one specific milestone done on time. |
| Escalation rule | A rule that sends a specific kind of alert straight to a named manager instead of leaving it in a merchandiser's own queue. |
Each earlier lesson in this course added one control to a digital workflow. A finished digital critical-path tracker is not those controls kept in four separate places; it is one tool where every milestone already carries its owner, due date and status (Lesson 1), is linked to the milestones it affects (Lesson 2), is covered by an alert and escalation rule appropriate to its own urgency (Lesson 3), and sits inside one connected record spanning approvals, materials, production and shipment (Lesson 4). Reading this one tracker should answer, without a phone call, exactly where an order stands and what needs attention.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| A single MTO run vs. a recurring MTS programme | A single MTO seasonal run has one confirmed set of milestones, tracked once from confirmation to arrival; a recurring MTS reorder programme repeats the same tracker structure every cycle, with alert and escalation rules doing more of the daily work across several cycles at once. | A merchandiser reading only the MTO structure into an MTS programme misses that several cycles' worth of the same tracker are live at the same time. |
| A hybrid account's two sides | Cedar & Co.'s hybrid account runs one MTO seasonal jeans style and separate, recurring MTS reorders side by side; each needs its own tracker instance, sharing the same structure but not the same task records. | Merging an MTO run's one-time milestones with an MTS programme's repeating ones into a single undifferentiated tracker hides which milestones repeat and which do not. |
| Export order vs. domestic order | An export order's finished tracker, such as Order B's jeans, spans all four stages to an overseas warehouse; a domestic order's tracker covers the same structure with a shorter final shipment leg. | The tracker's structure, owner, date, status, link, alert, connected stage, does not change by market; only the shipment stage's length and detail do. |
| A tracker read once a day vs. one relied on for a live decision | A routine daily read confirms nothing urgent has changed; a live decision, such as whether to accept a new ship date, requires opening the full tracker's linked and connected view, not just the day's alert summary. | Treating every read of the tracker the same way, whether routine or decision-critical, either wastes time on full detail daily or misses detail when a real decision is needed. |
| Socks, terry and home-textile product families | A hosiery or bedding order's finished tracker uses the same four combined controls, with that family's own stage names and material sources. | The combined tracker structure does not change by product family; only the milestone names and thresholds inside it do. |
Cedar & Co., the domestic brand with 12 shops, runs a hybrid account with Delta Garments: one Make to Order seasonal denim run, an illustrative 1,000-piece batch modelled on Order B's own construction, sold on 60-day open account, plus separate, recurring Make to Stock reorder cycles against Cedar & Co.'s own sales forecast, as introduced in Lesson 3. Mona builds one tracker instance for the live MTO seasonal run, and a separate, repeating tracker structure for the MTS reorder cycles, sharing the same owner, date, status, link, alert and connected-stage fields across both.
For the live MTO seasonal run, every milestone already has an owner and due date (Lesson 1), is linked so a delay carries forward (Lesson 2), is covered by an escalation rule matched to its own urgency (Lesson 3), and sits inside one connected record spanning approvals, materials, production and shipment (Lesson 4). When Mona opens this one tracker each morning, she can state the order's true current status, and the one milestone that most needs attention, without checking four separate files or calling Karim first.
The worked numberThis single read combines every control from the course: the owner and status of each milestone, the linked recalculation of ex-factory from the sewing slip, the escalation rule confirming this specific slip does not yet need Karim's immediate attention, and the connected view across all four stages in one place.
A common mistake, after learning owners and dates, links, alerts and connected stages as separate techniques, is applying each one to a different order or a different exercise rather than combining all four on the one live order that actually needs them together. A merchandiser who can explain linking perfectly, but still keeps materials in one spreadsheet and shipment in another, has not actually built a tracker; they have four separate skills applied nowhere at once. The value of this course is not in knowing four techniques individually, but in having one tool where they all operate on the same order at the same time.
This course taught four things one at a time: give every milestone an owner and a date, link milestones so a delay shows its full effect, set alert rules so only real problems reach a manager, and combine approvals, materials, production and shipment into one workflow instead of four separate files. A finished tracker is simply all four of those things, built on the same live order, at the same time. Reading it once should tell a merchandiser exactly where the order stands and what, if anything, needs their attention today, without four separate files and without a phone call.
Cedar & Co.'s live MTO seasonal run shows sewing complete at a half-week slip, already linked forward to ex-factory, now due week 17.5 instead of week 17. Mona is deciding, using only the tracker, whether this needs escalating to Karim today.
The relevant line from the tracker's own status summary:
Should Mona escalate this to Karim today, or let the tracker's own alert rule continue to monitor it? Decide before you open the decision.
Mona should let the tracker's own alert rule continue to monitor it, without escalating to Karim today.
The two facts that decide this are the escalation rule's own one-week threshold, which this half-week slip sits well outside of at more than three weeks from delivery, and the tracker's own confirmation that no downstream milestone has yet moved into an at-risk status because of it. This is exactly the situation the earlier lessons in this course built the tracker to handle without a merchandiser's manual judgement call each time: the linked recalculation already shows the effect, the connected view already shows no other stage is affected, and the escalation rule already confirms this does not yet meet its own threshold. Mona notes it for her next routine review and moves on, trusting the tracker rather than re-deciding a question its own rules were built to answer.
Cedar & Co.'s illustrative live MTO run's own value, at Order B's own jeans per-piece price applied to this batch, gives a sense of scale:
Without a complete tracker, answering "is this order on track" for the roughly USD 9,800 order above would require checking four separate files, then manually working out whether the sewing slip threatens the ex-factory date, then deciding whether to call Karim. With the complete tracker, the same answer takes one read: status known, effect calculated, escalation already decided. The saved time on one order is modest; across every live order and reorder cycle a merchandiser manages, it is the difference between managing exceptions and re-solving the same questions daily.
Use the T17-C03 Digital critical-path tracker. Build one complete instance for Cedar & Co.'s live MTO seasonal run, combining every column built across this course: milestone, stage, owner, due date, status, depends-on link, buffer, alert condition and escalation threshold. Build a separate, repeating instance for its MTS reorder cycles, sharing the same structure.
[Download the Digital critical-path tracker](../../templates/T17-C03-digital-critical-path-tracker.xlsx)
1. What makes a digital critical-path tracker complete, rather than just a collection of separate techniques?
2. Cedar & Co.'s live MTO run shows a half-week sewing slip, linked forward to ex-factory, more than three weeks from delivery, with the escalation threshold set at one week. What should happen?
3. Cedar & Co.'s hybrid account runs one MTO seasonal run and several recurring MTS reorder cycles at once. How should the tracker handle this?
| 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. |
| Live order | طلبية حية | Commande en cours | Canlı sipariş | An order currently in progress, being actively tracked, as opposed to a finished or a purely hypothetical one. |
| Hybrid account | حساب مختلط | Compte hybride | Hibrit hesap | A buyer relationship that combines Make to Order and Make to Stock business with the same factory. |
| True current status | الحالة الحالية الحقيقية | Statut réel actuel | Gerçek güncel durum | The order's real position right now, based on the tracker's actual data, not on the last verbal update someone remembers. |
| Milestone owner | مالك المرحلة | Responsable du jalon | Kilometre taşı sorumlusu | The named person or department accountable for getting one specific milestone done on time. |
| Escalation rule | قاعدة تصعيد | Règle d'escalade | Yükseltme kuralı | A rule that sends a specific kind of alert straight to a named manager instead of leaving it in a merchandiser's own queue. |
This is the last lesson of Course 3. Course 4 builds on the tracker you have just built, turning its own milestone and status data into KPIs that support real management decisions. Back to the course map