This page is for a merchandiser at a domestic brand, or at the garment factory supplying it, who must set up and maintain one working tracker covering every checkpoint an order's own schedule requires. Lessons 1 to 4 taught how to name a critical path's checkpoints, set each one's own deadline backward from a fixed date, spot a slip early, and rebuild the plan once a slip has happened. This lesson brings all of that into one tool: a single critical path tracker listing every checkpoint an order needs, its planned deadline, who controls it, its actual date once known, its status, and any recovery action taken. This is chiefly an information-flow skill: keeping every checkpoint's status visible in one place, whether the schedule belongs to an export order with a fixed buyer ship date or a domestic brand's own restock run with its own internally set date. Without one tracker covering every checkpoint, a business can lose track of which dates are already confirmed, which are still at risk, and which need a decision today.
You need: the checkpoint list from Lesson 1, the backward-counting method from Lesson 2, the recoverable/non-recoverable check from Lesson 3, and the rebuilding method from Lesson 4.
By the end of this lesson you can:
Not covered here: naming checkpoints, setting deadlines, spotting slips, and rebuilding a plan, all already covered in Lessons 1 to 4.
| Term | Meaning |
|---|---|
| Order tracker | A working document that logs each stage of an order against its planned and actual date. |
| Checkpoint | A specific moment in an order's life where its progress is checked against the plan. |
| On track | A stage finishes on or before its planned date. |
| Recoverable delay | A stage finishes late, but a buffer later in the timeline absorbs it without moving the final date. |
| Escalate | Telling the people who need to know, early, that a delay may change the delivery date, instead of waiting for it to happen. |
| Critical path | The chain of sequential stages that sets the shortest possible total time for the order. |
A critical path tracker is a single working document, an application of the general order tracker to one order's own critical path, listing every checkpoint that order needs. Each row holds six fixed pieces of information: the checkpoint name, its planned deadline, who controls it (the factory or the buyer or brand), its actual date once known, its status (on track, recoverable delay, or non-recoverable delay), and any recovery action taken. A tracker is complete for an order only when every checkpoint that order's own schedule requires has its own row, whether or not that checkpoint has actually happened yet; a missing row is not the same as a checkpoint that has not started, because a missing row means nobody is tracking whether it has started at all.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| One order vs. more than one order using the same tracker file | Delta Garments' own merchandising team can keep Order A's rows and a Cedar & Co. domestic run's rows in the same tracker file, provided each order's rows are clearly labelled and kept separate. | Mixing rows from two orders without a clear order label risks reading one order's on-track checkpoint as if it also covers a different order's own schedule. |
| Export order vs. domestic order | Order A's rows close out once, at its one shipment; Cedar & Co.'s domestic restock rows repeat on every new production run of the same standing style, since each run is its own fabric lot and its own schedule. | Reusing an old completed run's rows for a new run, instead of adding fresh rows, risks missing a real slip on the new run's own fabric. |
| A checkpoint still pending vs. one with an actual date | Some rows show a planned deadline with no actual date yet, because the checkpoint has not happened; other rows show a complete actual date and status. | A tracker with blank actual-date cells long past their planned deadline flags a checkpoint that needs following up before the rest of the schedule can be trusted. |
| A recoverable row vs. a non-recoverable row | A recoverable-delay row needs no further action column entry beyond noting the buffer absorbed it; a non-recoverable row must show which of Lesson 4's three recovery options was chosen. | A non-recoverable row with a blank recovery-action column is an unresolved decision, not a completed one, even though the slip itself has already been recorded. |
| Socks, terry, and home-textile product families | A hosiery, terry, or bedding order's tracker uses the same six columns, with that product's own checkpoint names in the checkpoint-name column. | The tracker's structure does not change by product family; only which named checkpoint appears in it does. |
Cedar & Co., the domestic brand, runs a Make to Stock restock of a basic T-shirt style through Delta Garments. Its merchandiser keeps one critical path tracker file, using the same six-checkpoint shape as Order A's own reference schedule, but replacing Order A's buyer-fixed ship date with Cedar & Co.'s own internally set shop-floor date. When fabric in-house comes in four days late, as covered in Lesson 3, the merchandiser updates that row's actual date and status; when Karim confirms a separate slip on a different checkpoint is non-recoverable, as covered in Lesson 4, the merchandiser records the chosen recovery option and its cost in the same row.
The worked numberFour of the six rows are already resolved with a status recorded, and two remain open because their own planned dates have not yet arrived; the tracker is still judged complete, since every one of the six checkpoints the schedule requires has its own row, whether resolved or still pending.
The methodA common mistake, once a checkpoint is reported complete, is closing its row with no more than a tick mark, without recording its actual date against its planned deadline. A row marked only "done" cannot show whether that checkpoint was on track, absorbed a recoverable delay, or actually needed a recovery action Lesson 4 covered; the tracker then has no way to warn the next order using the same reference schedule that this particular checkpoint tends to run late. Recording the actual date and status on every row, not just a completion tick, is what turns a tracker from a simple to-do list into a genuine planning tool.
Once you know how to name a schedule's checkpoints, set each one's own deadline, spot a slip, and rebuild the plan after one, the last step is keeping all of that in one place. A critical path tracker is a single list with one row for every checkpoint an order needs. Each row holds the checkpoint's name, its planned deadline, who controls it, its actual date once known, whether it is on track or delayed, and what recovery action was taken if it slipped badly. A tracker is only complete once every checkpoint a schedule actually requires has its own row, whether it has happened yet or not, and closing a row with only a tick mark, instead of its real date and status, throws away the very information the tracker exists to keep.
Cedar & Co.'s domestic restock run has just had its fabric-in-house checkpoint reported complete, and a new colleague is updating the tracker for the first time.
The tracker's own row, exactly as the new colleague has just left it:
Is this row complete once "done" is ticked, with no actual date or buffer figure recorded? Decide before you open the decision.
No. The row must record the actual date (day 44) and the buffer remaining (1 day), not only a completion tick, so the next reviewer can judge whether cutting still has a safety margin.
The two facts that decide this are the tracker's own six required columns, which include actual date and status, not just a done/not-done flag, and the real one-day buffer remaining, information the next reviewer needs before cutting begins. A tick mark alone hides exactly the number that matters most right now. The new colleague adds the actual date and the one-day buffer figure before the row is considered complete.
Recording an actual date and status alongside a completion tick, as this lesson's decision requires, costs less than a minute more than ticking the row alone. The cost of skipping it is what the next reviewer loses: without the one-day buffer figure visible, cutting could start without anyone realising the schedule is now this thin, and a further single-day delay at cutting, easily possible on any factory floor, would then become a non-recoverable delay nobody saw coming, threatening Cedar & Co.'s own shop-floor date and the shelf availability across its 12 shops that date protects. A minute of proper recording against a threat to an entire restock run's own delivery date is not a close call.
This course's critical path tracker is the tool this whole course has built toward: one row per checkpoint, six fixed columns, and a clear order label on every row, whether the schedule is an export order's or a domestic run's. [Download the tracker](templates/T11-C01-critical-path-tracker.xlsx).
| Order | Checkpoint | Planned deadline | Controlled by | Actual date | Status | Recovery action |
|---|---|---|---|---|---|---|
| Order A (export) | Fabric in-house | Week 8 | Factory (Delta Garments) | Week 8 | On track | None required |
| Cedar & Co. (domestic) | Fabric in-house | Day 40 | Factory (Delta Garments) | Day 44 | Recoverable delay | Noted, 1 buffer day remaining |
| Cedar & Co. (domestic) | Cutting and sewing complete | Day 49 | Factory (Delta Garments) | Not yet due | Not yet due | — |
1. What are the six fixed pieces of information a complete critical path tracker row holds?
2. A checkpoint's row is marked 'done' with no actual date recorded. What is missing before this row can be judged complete?
3. A different order's cutting checkpoint finishes 3 days late, with 8 buffer days originally built in ahead of shipping. How many buffer days remain, and is this recoverable?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Order tracker | متعقّب الطلبية | Suivi de commande | Sipariş takipçisi | A working document that logs each stage of an order against its planned and actual date. |
| Checkpoint | نقطة فحص | Point de contrôle | Kontrol noktası | A specific moment in an order's life where its progress is checked against the plan. |
| On track | على المسار المخطط | Dans les temps | Zamanında | A stage finishes on or before its planned date. |
| 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. |
| Escalate | تصعيد الأمر | Alerter (faire remonter) | Üst makama bildirmek (eskalasyon) | Telling the people who need to know, early, that a delay may change the delivery date, instead of waiting for it to happen. |
| Critical path | المسار الحرج | Chemin critique | Kritik yol | The chain of sequential stages that sets the shortest possible total time for the order. |
You can now name a critical path's checkpoints, set each one's own deadline backward from the ship date, spot a slip early, rebuild the plan after a slip, and keep every checkpoint tracked in one working tool. The next course in Track 11 continues the order-to-ship sequence with sampling and approvals. Back to the course map