An order's critical path is a fixed sequence of stages, but a list of stage names and week numbers on a page is not yet a workflow. A workflow is that same sequence, turned into records a digital workflow tool can hold: one row per milestone, a person or department named as its owner, a date the milestone is due, and a status that tells anyone opening the tool whether that milestone is on track, at risk or late. This is chiefly an information-flow skill: turning a schedule that lives in one merchandiser's head, or in a static document, into a shared, always-current record that the factory floor, planning and the buyer's own office can all check without asking someone else first.
Without this step, a factory can have a correct critical path and still lose control of it, because nobody can see, on any given day, who is responsible for the next milestone or whether it is still on schedule.
You need: a basic sense of what a critical path is and how its milestones are sequenced. Track 11, Course 1 (Order to Ship: the Critical Path) is useful preparation, though not required.
By the end of this lesson you can:
Not covered here: linking one milestone's delay to the milestones it will push back (Lesson 2), setting alert and escalation rules (Lesson 3), and combining approvals, materials, production and shipment in one workflow (Lesson 4).
| Term | Meaning |
|---|---|
| Digital workflow | An order's stages and milestones recorded in a shared digital tool instead of a private document, so anyone with access sees the same current record. |
| Milestone owner | The named person or department accountable for getting one specific milestone done on time. |
| Due date | The date a milestone must be completed for the rest of the critical path to hold. |
| Status field | A record, updated as work happens, that shows whether a milestone is on track, at risk or late. |
| Task record | One row in the digital workflow, holding a single milestone's own name, owner, due date and status together. |
| Critical path | The chain of sequential stages that sets the shortest possible total time for the order. |
A critical path names the stages an order must pass through and the order they happen in. A digital workflow takes that same sequence and gives every milestone a task record: who owns it, when it is due, and what its status is right now. A schedule without these three fields can still be correct on paper, yet nobody can act on it, because nobody can see, without asking around, who is responsible today or whether a milestone is already slipping.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| Export vs. domestic order | An export order's workflow, such as Order B's jeans, runs task records all the way to an overseas ship date and warehouse arrival; a domestic order's workflow stops at a local warehouse, a shorter final stretch. | Copying an export order's own shipping and customs task records onto a domestic order adds stages that do not exist for it. |
| MTO vs. MTS vs. hybrid | A Make to Order workflow opens only once a buyer confirms, one row set per confirmed order; a Make to Stock workflow can open recurring task records against a forecast, before any single confirmed order exists; a hybrid account runs both kinds of workflow side by side for the same buyer. | Building only one workflow shape for every order type forces an MTS reorder to wait for a confirmation event that, for that business model, never happens in the same way. |
| Who owns a milestone | Fabric in-house and sewing complete are usually owned inside the factory; sample approval is owned by the buyer's own office, since the factory cannot approve its own sample. | A workflow that names the factory as owner of a buyer-controlled milestone hides who the next action actually depends on. |
| A short critical path vs. a longer one | Order A's T-shirt workflow holds 16 weeks of task records; Order B's jeans workflow, with its extra washing stage, holds 22 weeks of task records across one more stage. | Reusing a shorter order's own set of task records for a longer, more complex order leaves whole stages, and their owners, missing from the digital record. |
| Socks, terry and home-textile product families | A hosiery or towel workflow uses the same owner/date/status fields, with that family's own stage names, such as linking and boarding for socks in place of cutting and sewing. | The task-record structure does not change by product family; only the stage names inside it change. |
Northline Apparel confirms Order B with Delta Garments: 3,000 five-pocket jeans, 12 oz denim with 2% elastane, on a 22-week critical path from confirmation to shipment. Mona, the merchandiser at Delta Garments, does not wait for the first milestone to be late before opening a digital record. On the day of confirmation, she opens Order B in the digital workflow tool and creates one task record per milestone, with an owner and a due date already filled in before any work has started.
She names Karim, the production manager, as owner of fabric in-house, sewing complete and washing complete, since those stages happen inside Delta Garments. She names Northline Apparel's own office as owner of the approvals milestone, since sample approval is the buyer's decision. Every task record starts with the status "on track," a value the tool will only change once actual progress is reported against the due date.
The worked numberEach due date is not an independent guess; it is the running total of every stage before it. Mona records all seven due dates in the digital workflow on day one, so the tool can already show, for any date in the future, which milestone should be underway and which owner is responsible for it.
A common mistake is treating the digital workflow as a reporting tool used once a problem appears, rather than a record opened on the day of confirmation. If Mona waits until fabric in-house is already overdue to create Order B's jeans task records, the tool has no on-track baseline to compare against, and nobody can say from the record alone whether the delay started in week 4 or week 9. Opening every task record on day one, with its owner and due date already fixed, is what lets a status change later mean something specific rather than a guess made after the fact.
A critical path is a list of stages an order must pass through in order. A digital workflow takes that same list and turns each stage into a record: who is responsible, when it must be done, and how it is going right now. Without an owner, nobody knows who to ask. Without a due date, nobody knows if something is late. Without a status, everyone has to check by phone or email instead of by looking at one shared record. Building all three into the workflow on the day an order is confirmed is what makes the tool worth using later.
Delta Garments has confirmed Order B, the jeans order, with Northline Apparel. Mona is finalising the digital workflow's seven task records before sending the file to Karim for review.
The relevant note from the production plan:
Who should the washing-complete task record name as owner? Decide before you open the decision.
Karim, as the internal owner who tracks the hand-off to and from Cairo Wash Works, not Cairo Wash Works itself.
The two facts that decide this are that the digital workflow is Delta Garments' own tool, which Cairo Wash Works has no access to, and that Karim is the person who can actually update the record's status from what he sees: goods dispatched, goods returned, ready for ex-factory inspection. Naming a company with no access to the tool as owner leaves the status field permanently unmanaged, since nobody with a login is accountable for updating it. Karim owns the milestone inside the workflow; his own coordination with Cairo Wash Works happens outside the tool, by phone or email, and its result is what he then records.
Order B's jeans total FOB value is fixed by its price and quantity:
If the washing-complete task record has no accountable internal owner, a delay at Cairo Wash Works can go unrecorded until the ex-factory date, due week 17, is already missed. Since shipping (4 weeks) and warehouse arrival (1 week) both run after ex-factory, a missed ex-factory date pushes the same number of weeks onto every milestone after it, risking the sea freight booking for the whole USD 29,400 order. Naming Karim as the internal owner on day one, before any delay occurs, is what lets the tool flag a slip while there is still time to act on it.
Use the T17-C03 Digital critical-path tracker. For Order B's jeans, record each milestone's name, its stage, its owner, its due date counted from confirmation, and its starting status. Start every task record as on track on the day the order is confirmed, and leave the status field open for later lessons to update.
[Download the Digital critical-path tracker](../../templates/T17-C03-digital-critical-path-tracker.xlsx)
1. What are the three fields a digital workflow adds to a milestone that a written critical path alone does not have?
2. Order B's jeans washing-complete milestone is due week 16. Cairo Wash Works, an outside laundry, performs the actual wash cycle. Who should the task record name as owner?
3. Order A's T-shirt workflow has 16 weeks of task records. A different, longer order runs a 30-week critical path with an extra dyeing stage. What should its digital workflow do?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Digital workflow | سير العمل الرقمي | Flux de travail numérique | Dijital iş akışı | An order's stages and milestones recorded in a shared digital tool instead of a private document, so anyone with access sees the same current record. |
| Milestone owner | مالك المرحلة | Responsable du jalon | Kilometre taşı sorumlusu | The named person or department accountable for getting one specific milestone done on time. |
| Due date | تاريخ الاستحقاق | Date d'échéance | Vade tarihi | The date a milestone must be completed for the rest of the critical path to hold. |
| Status field | حقل الحالة | Champ de statut | Durum alanı | A record, updated as work happens, that shows whether a milestone is on track, at risk or late. |
| Task record | سجل المهمة | Fiche de tâche | Görev kaydı | One row in the digital workflow, holding a single milestone's own name, owner, due date and status together. |
| Critical path | المسار الحرج | Chemin critique | Kritik yol | The chain of sequential stages that sets the shortest possible total time for the order. |
Next you will learn how to link one milestone to the milestones that depend on it, so a single late task shows its full downstream effect instead of sitting on the page as an isolated red flag. Back to the course map