When Two Factories Both Say ‘On Schedule’
The same green status can describe two very different factories: one has stable flow, while the other is borrowing time from overtime, queues and tomorrow’s capacity.
Factory A and Factory B both send a green update. Both say the order is on schedule. At Factory A, bundles move steadily, quality is stable and the remaining work fits normal capacity. At Factory B, work-in-progress is rising, overtime has been approved and tomorrow’s line plan has been rearranged.
The status is identical. The risk is not.
The short answer
Multi-factory apparel planning fails when sites report conclusions without common evidence. “On schedule” should be supported by the same measures: released quantity, completed good output, work-in-progress by stage, current rate, quality loss, remaining capacity and time to ship. Comparable definitions reveal whether progress is stable or borrowed from future capacity.
Green is not a measurement
Traffic-light status is useful for attention, but it compresses the explanation. A factory may stay green because a manager expects recovery, because a buyer milestone has not yet been missed or because the site counts output differently.
Regional leadership needs to compare operating conditions, not confidence levels. The question is not “Are you on schedule?” but “What must remain true for this order to ship on schedule?”
The schedule-evidence card
For each order and factory, a concise evidence card should show:
- quantity released, started, completed and accepted;
- work-in-progress at critical stages;
- recent good-output rate and quality loss;
- material or approval constraints;
- normal and exceptional capacity committed;
- remaining production and shipment time.
The card does not eliminate local explanation. It gives that explanation a common foundation.
One network, clear local ownership
Central visibility should not turn headquarters into a remote line supervisor. Factories still own execution. The group level owns allocation choices, shared definitions and trade-offs between customers, sites and capacity.
ACC describes multi-factory allocation, inter-site planning and related financial integration within the scope of Venus. The purpose is not a prettier consolidated report. It is the ability to see how moving an order affects materials, capacity, delivery and economics across the network.
Compare flow, not just totals
Two sites can report the same completed quantity while one has a smooth flow and the other has a large queue before a bottleneck. Work-in-progress location matters because it reveals what is likely to become tomorrow’s output—and what may become tomorrow’s surprise.
The best comparison therefore combines lagging results with leading conditions. Shipment completion is definitive but late. Material readiness, line input, throughput and quality trend provide earlier evidence.
For the wider context, read the pillar Inside the Invisible Factory and the companion piece The 9 A.M. Production Meeting a Connected Factory Shouldn’t Need.
The danger of borrowed capacity
Recovery plans are necessary, but they are not free. A site can protect today’s order by taking operators, machines or hours from tomorrow’s programme. The first order remains green while risk moves invisibly to the next one.
A network view should therefore show both the recovery action and its displacement effect. If overtime is added, is labour available and is quality stable? If a line is reassigned, which order loses capacity? If work moves to another site, are materials, approvals and logistics ready there? The strongest plan closes one gap without opening a larger one.
A fairer performance conversation
Common evidence also improves fairness. Factories with transparent exception reporting should not look worse than factories that keep status green until failure is unavoidable. Leadership can separate the existence of a constraint from the quality of the response.
Useful questions include how early the site detected the risk, whether it quantified the consequence, whether the recovery assumptions were realistic and whether learning changed the next plan. This turns comparison from ranking into operational improvement while preserving accountability.
What to standardise—and what not to
Standardise identities, milestone definitions, quantity states and time cut-offs. An order should mean the same commercial object across sites. “Completed good output” should not mean sewn at one factory and packed at another. A quality hold should have a consistent effect on available quantity.
Do not force identical local workflows where products and equipment differ. One site may organise bundles differently or use a specialised finishing route. The network needs comparable evidence at decision points, not uniformity for its own sake.
Allocation before the crisis
The best multi-factory decision is made before a site becomes overloaded. At order acceptance or planning, compare capability, material position, available capacity, lead time, logistics and economic consequence. Keep the assumptions with the allocation so later changes can be understood.
When conditions move, test alternatives as scenarios rather than informal promises. What happens if quantity shifts between sites? Which materials must move? What approvals repeat? Does the alternate factory have genuine capacity for this construction? What happens to orders already in its plan?
Scenario discipline helps management avoid a familiar pattern: solving the most visible order by destabilising several quieter ones.
A weekly network rhythm
Daily factory execution and weekly network planning should use the same underlying order evidence at different levels of detail. The weekly review can focus on capacity exposure, material constraints, transfers and customer commitments across the horizon. Site teams retain the detailed actions.
Track forecast stability as well as final delivery. If an order remains green until the day it turns red, the status process offers little management value. Earlier, better-calibrated warning is a sign of maturity—even when the headline initially appears less comfortable.
Reading green without sharing the same risk
A healthy-looking network can still carry asymmetric exposure. One factory may be green because materials arrived early; another because overtime closed a gap tomorrow cannot repeat. Status language only helps when the evidence card travels with the colour.
Ask each site for the next limiting factor—material, labour, equipment, quality, logistics or approval—and what must remain true for that colour. If it depends on unbooked overtime, unconfirmed transfers or another order slipping, green is provisional. Treating those greens as equal creates a surprise: both plants stayed on schedule until one promise borrowed the other’s future.
Frequently asked questions
What is multi-factory apparel planning?
It is the coordination of orders, materials, capacity, production and delivery across more than one factory using common definitions and clear site responsibility.
Should all factories use identical targets?
Not necessarily. Products and processes differ. The definitions of core events and quantities should be comparable, while targets can reflect each site’s operating context.
Is overtime proof that a factory is late?
No, but dependence on unplanned overtime is a risk signal. It should be visible in the explanation of how the committed date will be achieved.
“On schedule” should be the start of a management conversation, not the end of one.
What to standardise—and what not to
Standardise identities, milestone definitions, quantity states and time cut-offs. An order should mean the same commercial object across sites. “Completed good output” should not mean sewn at one factory and packed at another. A quality hold should have a consistent effect on available quantity.
Do not force identical local workflows where products and equipment differ. One site may organise bundles differently or use a specialised finishing route. The network needs comparable evidence at decision points, not uniformity for its own sake.
Allocation before the crisis
The best multi-factory decision is made before a site becomes overloaded. At planning, compare capability, material position, available capacity, lead time, logistics and economic consequence. Keep assumptions with the allocation so later changes can be understood.
When conditions move, test alternatives as scenarios. What happens if quantity shifts between sites? Which materials must move? What approvals repeat? Does the alternate factory have genuine capacity for this construction? What happens to orders already in its plan? Scenario discipline avoids solving the loudest order by destabilising several quiet ones.
Daily execution and weekly network planning should use the same underlying evidence at different detail. The weekly review can focus on capacity exposure, material constraints, transfers and customer commitments. Track forecast stability as well as final delivery. If an order stays green until the day it turns red, the status process offers little value. Earlier, calibrated warning is a sign of maturity.
Questions for the next regional review
Ask each site to explain one green order and one at-risk order using the same evidence card. Compare not only the answers but the effort required to produce them. If one factory needs a day of spreadsheet work, the network does not yet have common visibility.
Review where recovery capacity comes from, which assumptions are most volatile and how often orders move between sites. Look for repeated late transfers or permanent overtime disguised as exceptions. Confirm that quality and accepted output travel with production quantity; speed without usable product is not recovery.
End by selecting one cross-site dependency to improve. It may be a material transfer, shared approval, capacity definition or shipment cut-off. Small, repeatable improvements to the common operating language are more valuable than a large reporting pack that nobody can explain.
The result is not central control of every line. It is earlier coordination around the few decisions that affect the whole network.