The earlier lessons in this course built a single, linked, alerted workflow for one kind of milestone at a time. In a live order, those milestones do not sit in separate worlds: an approvals delay changes when material can be booked, a material delay changes when production can start, and a production delay changes the shipment plan. If a factory tracks approvals in one spreadsheet, materials in a second, production in a third and shipment in a fourth, the four trackers can quietly disagree about the same order's real status, and nobody notices until the disagreement becomes a missed date. This is chiefly an information-flow skill for the full order, connecting stages that different people, and sometimes different companies such as a mill, each see only their own part of.
Without one connected workflow, a factory can be confident about materials while planning is already worried about production, simply because each team is reading a different tracker with a different, unreconciled version of the truth.
You need: Lessons 1 through 3 of this course, which build the digital workflow's owner, due-date, status, linked-milestone and alert fields.
By the end of this lesson you can:
Not covered here: building the complete tracker for a live order end to end (Lesson 5).
| Term | Meaning |
|---|---|
| Connected workflow | A single digital workflow holding approvals, materials, production and shipment task records together, instead of four separate trackers. |
| Hand-off | The point where goods, and ownership of them, pass from one separate company to another. |
| Mill-side milestone | A task record whose completion depends on a supplying mill's own work, such as fabric delivery, rather than the factory's own floor. |
| Hybrid account | A buyer relationship that combines Make to Order and Make to Stock business with the same factory. |
| Single source of order truth | The one connected workflow record everyone, across stages and companies, checks instead of their own separate tracker. |
| Critical path | The chain of sequential stages that sets the shortest possible total time for the order. |
Approvals, materials, production and shipment are different kinds of work, done by different people, but they are stages of the same critical path, not four independent projects. A connected workflow puts every milestone from all four stages into one linked record, using the same owner, due-date, status and dependency fields built in earlier lessons, so that a delay in one stage is visible to everyone tracking the order, not only to the team that owns that particular stage.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| Export order vs. domestic order | An export order's connected workflow, such as Order B's jeans, spans approvals, materials, production and shipment all the way to an overseas warehouse; a domestic order's workflow covers the same four stages but a shorter final shipment leg. | The four-stage structure does not change by market; only the length and detail of the shipment stage does. |
| A stage the factory controls vs. one a mill controls | Approvals and production sit inside the factory's own systems; a material milestone such as fabric delivery depends on a supplying mill's own schedule and hand-off, which the factory does not directly control. | Treating a mill-controlled milestone as if the factory alone could move it hides where the real dependency actually sits. |
| MTO vs. MTS vs. hybrid | A single MTO export order's connected workflow tracks one confirmed order through all four stages once; an MTS reorder programme repeats the same four-stage structure every cycle; a hybrid account, such as a mill selling both against confirmed orders and its own forecasted stock, runs both patterns side by side. | Merging an MTO order's one-time workflow with an MTS programme's repeating one into a single undifferentiated record hides which milestones repeat and which do not. |
| A mill's own hand-off recorded once vs. tracked in detail | Some factories record only the mill's delivery date as one milestone; others also track the mill's own upstream milestones, such as when the mill itself received its raw material, when detail matters to the order's own risk. | Recording only the delivery date is enough when the mill is reliable; tracking the mill's own upstream milestones matters more when a specific risk, such as a raw-material shortage, is already known. |
| Socks, terry and home-textile product families | A hosiery or towel order's connected workflow uses the same four-stage structure, with that family's own material source, such as a spinning mill's yarn delivery in place of a denim mill's fabric delivery. | The four-stage connected structure does not change by product family; only which mill and which material milestone sits inside the materials stage changes. |
Order B's jeans workflow already has linked, owned, alerted task records for approvals, sewing, washing, ex-factory, shipping and warehouse arrival, built in Lessons 1 through 3. The materials stage, fabric in-house, currently depends on Suez Denim, the denim mill weaving Order B's own 12 oz denim. Suez Denim also runs its own hybrid business: it weaves specific denim orders to confirmed factory requirements, such as Order B's own fabric, and separately keeps a Make to Stock greige denim inventory it sells against forecast to other customers.
Mona does not need to track Suez Denim's own internal MTS greige-stock programme inside Delta Garments' workflow; that is Suez Denim's own separate business. What she does need is the single hand-off milestone that connects the two companies: fabric delivered, in-house, ready for cutting. She records that hand-off as one linked task record inside Order B's own connected workflow, owned internally by Karim, who confirms receipt, with its due date already linked to the downstream sewing milestone the way Lesson 2 built.
The worked numberWithout the connected workflow, these same six milestones could sit across four separate files: an approvals tracker Northline Apparel's office keeps, a materials tracker Mona keeps to watch Suez Denim, a production tracker Karim keeps on the floor, and a shipment tracker logistics keeps. Merging them into one record does not add milestones; it removes the four separate, unreconciled pictures of the same six milestones.
A common mistake is trying to bring Suez Denim's own internal weaving schedule, loom bookings and yarn deliveries into Delta Garments' connected workflow, as if the factory needed to manage the mill's business as closely as its own floor. This adds noise without adding control: Delta Garments cannot act on Suez Denim's internal loom schedule, only on the delivery date the two companies have actually agreed. The connected workflow should hold the agreed hand-off milestone, with its own due date and status, and treat everything upstream of that hand-off as the mill's own business to manage.
An order is one connected chain, even though different people, and sometimes different companies, work on different parts of it. If each part is tracked in its own separate file, everyone can be technically right about their own piece while the whole order quietly falls out of agreement. Putting approvals, materials, production and shipment into one connected workflow does not create new work; it takes milestones that already exist and gives them one shared home, so a delay anywhere is visible to everyone who needs to see it, including where a mill's own delivery hands off into the factory's own schedule.
Suez Denim reports that a yarn delivery delay to its own weaving operation may push Order B's fabric delivery back by several days, though the mill has not yet confirmed a new delivery date. Mona is updating Delta Garments' connected workflow before this uncertainty affects downstream planning.
The relevant line from Suez Denim's own notice:
Should Mona update the fabric-in-house milestone's due date now, or wait for Suez Denim's confirmed date? Decide before you open the decision.
Mona should mark the fabric-in-house milestone's status as at risk now, but wait for Suez Denim's confirmed date before changing the due date itself.
The two facts that decide this are that the connected workflow tracks the agreed hand-off date, not Suez Denim's own unconfirmed internal schedule, and that changing a due date without a confirmed new date would carry an uncertain, possibly wrong, delay through the linked sewing milestone and everything after it. Marking the status as at risk, without yet moving the due date, tells everyone watching the workflow that a delay is possible without asserting a specific number of days that Suez Denim has not yet confirmed. Once Suez Denim's revised date arrives, Mona updates the due date itself, and the linked sewing, washing, ex-factory, shipping and warehouse milestones recalculate from that confirmed figure.
Order B's jeans total FOB value is fixed by its price and quantity:
If Mona moved the fabric-in-house due date on the strength of an unconfirmed mill estimate, and Suez Denim's actual delay turned out to be longer or shorter, every linked milestone after fabric in-house, sewing, washing, ex-factory, shipping, warehouse arrival, would carry the wrong number forward, on the full USD 29,400 order. Marking the milestone at risk without guessing at an unconfirmed number costs nothing extra and keeps the connected workflow's other five linked milestones honest until Suez Denim's own confirmed date arrives.
Use the T17-C03 Digital critical-path tracker. Combine the approvals, materials, production and shipment milestones for Order B's jeans into one connected sheet, marking which milestones are owned internally, which represent an outside company's hand-off, and which belong to a hybrid account's repeating MTS activity versus its one-time MTO activity.
[Download the Digital critical-path tracker](../../templates/T17-C03-digital-critical-path-tracker.xlsx)
1. Why does keeping approvals, materials, production and shipment in one connected workflow matter more than having four accurate separate trackers?
2. Suez Denim reports a possible yarn delay but has not yet confirmed a new fabric delivery date for Order B's jeans. What should Delta Garments' connected workflow show?
3. Suez Denim sells fabric both against confirmed factory orders, such as Order B's own denim, and from its own forecasted Make to Stock greige stock. How should its hybrid business appear in Delta Garments' connected workflow?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Connected workflow | سير عمل مترابط | Flux de travail connecté | Bağlantılı iş akışı | A single digital workflow holding approvals, materials, production and shipment task records together, instead of four separate trackers. |
| Hand-off | نقطة تسليم بين الشركات | Transfert entre entreprises | Şirketler arası devir | The point where goods, and ownership of them, pass from one separate company to another. |
| Mill-side milestone | مرحلة جانب المصنع النسيجي | Jalon côté moulin | Fabrika tarafı kilometre taşı | A task record whose completion depends on a supplying mill's own work, such as fabric delivery, rather than the factory's own floor. |
| Hybrid account | حساب مختلط | Compte hybride | Hibrit hesap | A buyer relationship that combines Make to Order and Make to Stock business with the same factory. |
| Single source of order truth | المرجع الوحيد لحقيقة الطلبية | Source unique de vérité de la commande | Sipariş için tek doğruluk kaynağı | The one connected workflow record everyone, across stages and companies, checks instead of their own separate tracker. |
| Critical path | المسار الحرج | Chemin critique | Kritik yol | The chain of sequential stages that sets the shortest possible total time for the order. |
Next you will put everything from this course together, building a complete digital critical-path tracker for a live order from confirmation to arrival. Back to the course map