How to Prevent Production Delays: Why Small Approvals Become Late Shipments
The hoodie that looked on track in last week's trading meeting is suddenly a week behind, and the only open item is a single colour that is still waiting for lab dip approval. How did one swatch put the launch date at risk? The answer is that a garment order is a chain of dependent steps, and a day lost early on the chain is a day lost at the end unless something absorbs it. The aim of this page is to help you prevent production delays by finding those dependencies before the PO is placed, rather than recovering from them afterwards.
For this guide, a production delay means a confirmed milestone that moves later than its baseline date, whether the cause sits with the factory, a mill, a trim supplier, a freight forwarder or your own approval turnaround. Everything below works backwards from the launch date or delivery window.
The last two tiles come from the worked illustration below: assumptions chosen to show the arithmetic, not benchmarks. For a week-by-week version, see how to build a hoodie critical path.
Step 1: Map the Dependencies Behind Garment Production Delays
To prevent production delays you need to know what each step waits for. Most apparel delays come from six groups of dependencies: fabric, trims, the pre-production sample, cutting, wash and finishing, and shipment. Each has an input it needs, an owner, and a signal that tells you early that it is slipping.
Dependency map for a hoodie order
| Dependency | Needs before it can start | Evidence to ask for | Early warning signal |
|---|---|---|---|
| Fabric | Approved lab dip or colour standard; yarn and knit slot booked | Dated booking confirmation, dye lot plan, in-house inspection report | Lab dip still open after the agreed comment date; no dye slot date |
| Trims | Approved artwork and specification for drawcords, eyelets, labels, cartons | Supplier order confirmation with ship date; photos of received goods | Trim supplier has not confirmed quantity or colour match |
| PP sample | Bulk or approved fabric; signed-off fit comments and wash standard | Dated PP submission, measurement sheet, wash and print references | PP waiting on fabric, or comments from earlier rounds not closed |
| Cutting | Approved PP, fabric in-house and inspected, marker approved | Cutting plan, fabric inspection result, marker efficiency record | Fabric shade or shrinkage test still outstanding |
| Wash and finishing | Sewn garments, approved wash recipe, pilot result where relevant | Pilot lot result, wash capacity booking, shade rating against standard | Subcontracted wash unit has not confirmed a slot |
| Shipment | Packed, inspected goods; booked space; export and import documents | Final inspection report, booking confirmation, packing list | Booking not confirmed by the time sewing finishes |
Illustrative dependency map for a hoodie programme. Add or remove rows for your own product, for example print, embroidery or special packaging.
Fabric sits at the head of the chain, so a slip there moves every later step, and wash is often subcontracted, so the factory does not fully control its calendar. Our guides to fabric dyeing methods and the garment production process explain what each step involves.
Which dependencies are on the critical path?
Not every dependency is critical. Trims might arrive 20 days before sewing needs them, so a short slip there costs nothing. The critical path is the longest chain of dependent steps from PO to delivery. A delay on that chain moves the delivery date day for day, while a delay on a step with float only matters once the float is used up. For each dependency, record how many days of float it has. Float of zero or close to it means the step needs the closest watching.
Step 2: Set Critical-Path Dates and a Shipment Buffer
A schedule that only lists a final delivery date gives nobody anything to manage. Convert the dependency map into dated milestones, each with an owner and an approval window, then work backwards from the date that cannot move. The table shows the baseline used in this guide. Every duration is an assumption for illustration and has to be re-timed for your own product, fabric and factory.
Illustrative baseline schedule: hoodie, one new colour
| Milestone | Assumed duration | Planned day (from PO) |
|---|---|---|
| PO issued; fabric and trim bookings evidenced | Day 0 to day 3 | Day 3 |
| Lab dip submitted; comments due by agreed date | 7 days for review | Day 12 |
| Bulk fabric dyed, finished and in-house | 21 days after lab dip approval | Day 33 |
| PP sample submitted; approved | 3 days to make, 7 days to review | Day 43 |
| Cutting | 3 days | Day 46 |
| Sewing | 14 days | Day 60 |
| Wash and finishing | 7 days | Day 67 |
| Packing and final inspection; goods ex-factory | 5 days | Day 72 |
| Sea freight, clearance and delivery to UK distribution centre | 35 days (assumed) | Day 107 |
| Goods received and ready to sell | 7 days of receiving and processing | Day 114 |
| Shipment buffer | 7 days held in reserve | Day 121 = launch date |
Illustrative assumptions only: they are not typical lead times and not Ruhrose lead times. Check durations with your factory, forwarder and customs broker.
The baseline adds up to 121 days, about 17 weeks, from PO to launch, with 72 days to ex-factory. Our guide to clothing production lead times explains what sits inside each block.
How to size a buffer
A buffer is time you protect on purpose, placed just before the date you cannot move. Size it from the uncertainty of the chain, not from a fixed rule: a programme with a new colour, a new wash and a subcontracted finish needs more than a repeat of a proven style. Keep it visible as its own line and report how much remains at each review, so that early delays are not absorbed silently.
Setting dates and buffer
- 1List milestones backwardsStart at the launch date and subtract each step's duration, including approval windows on your side.
- 2Name an owner for eachOne person per milestone, on both sides, with a deputy for leave.
- 3Mark floatCalculate days of float for each non-critical step so the team knows where slack really is.
- 4Hold the bufferPut reserve time before the fixed date and track how much of it is left at every review.
- 5Agree the update rhythmWeekly status on every open milestone, daily on any amber or red one.
For the supplier side of this agreement, including the weekly report format and named owners, see how to stop chasing suppliers after the PO.
Step 3: Escalate Early to Prevent Production Delays Becoming Misses
Escalation works only when it triggers on forecast, not on failure. If a milestone is reported late on the day it is due, the buffer has already begun to shrink and the next owner has no time to react. Agree the rules before the PO so nobody has to argue about whether a slip is serious enough to raise.
Example escalation triggers (agree your own before the PO)
| Status | Trigger | Who acts | Expected response |
|---|---|---|---|
| Green | Milestone confirmed on time with evidence | Merchandiser and supplier coordinator | Normal weekly update |
| Amber | No evidence two working days before the due date, or one day of forecast slip with float remaining | Buying team lead and supplier merchandiser | Cause and revised date within one working day |
| Red | Forecast slip greater than the float or buffer remaining | Buying manager and factory senior management | Written recovery options with cost and risk within one working day |
The two-day and one-day thresholds are examples for illustration. Set thresholds to suit your calendar, approval cycle and the criticality of the style.
Escalation should include your own side: a PP sample waiting six days for your comments against a seven-day window is a buyer-side amber. Tracking turnaround for both parties shows where time is lost. Repeat sample rounds are a separate cause, covered in our guide to improving sample approval rate addresses.
The most useful escalation message is: "Lab dip comments are due Tuesday, none received, forecast approval now Friday, three days of buffer used." It gives a cause, a new date and the cost to the buffer, which is what a decision-maker needs.
Step 4: Build Recovery Options Without Hiding Risks
Once a milestone is red, the supplier and buyer should put recovery options on the table together. Each option should state the days it recovers, the cost, the quality or compliance risk, and who has to approve it. A recovery plan that only lists the days recovered encourages shortcuts. Common levers are a priority dye slot, cutting at risk, extra sewing hours, a split shipment, air freight for a share of the order, or moving the launch date. The worked illustration below compares them side by side.
There are also options that should be refused. Shortening final inspection, skipping a wash test or approving shade without a reference standard can look like recovery on the schedule but move the problem to your customer. Our guide to AQL inspection explains why quality checks need to stay in the plan.
Worked Illustration: A Delayed Lab Dip Threatens a Hoodie Launch
This is a hypothetical example, labelled illustrative throughout. A buyer places a PO for 6,000 hoodies in three colourways: colour A for 3,000 units, colour B for 2,000, and a new colour C for 1,000. Colours A and B are repeat shades with approved standards. Colour C needs a lab dip. The programme uses the baseline schedule above, with a launch date at day 121.
On day 5 the lab dip for colour C is submitted. Comments are due by day 12, and the shade is rejected on that date. A second lab dip is re-dyed and submitted on day 19 and approved on day 26. The approval has slipped by 14 days against the baseline. The timeline below shows the first week of consequences and then the downstream effect.
Illustrative sequence of the delay (days counted from the PO)
- Day 5Lab dip for colour C submitted as planned.
- Day 12Comments due. The shade is outside the agreed band, so the lab dip is rejected and re-dyeing begins.
- Day 19Second lab dip submitted, seven days after the first rejection.
- Day 26Lab dip approved. Planned approval was day 12, so the slip is 14 days. Buffer of 7 days now looks too small.
- Day 47Bulk fabric in-house, 14 days later than the planned day 33, because the 21-day dye and finish block cannot start before approval.
- Day 57PP sample approved 14 days late. Cutting follows, sewing and wash move back by the same 14 days.
- Day 86Goods ex-factory, against a planned day 72. Sea transit is unchanged, so UK receipt moves from day 107 to day 121.
- Day 128Goods ready to sell after 7 days of processing. The launch date is day 121, so the programme is 7 days late even after using the 7-day buffer.
Illustrative arithmetic: 12 + 14 = 26; 26 + 21 = 47; 47 + 3 + 7 = 57; 57 + 3 + 14 + 7 + 5 = 86; 86 + 35 = 121; 121 + 7 = 128. 128 minus 121 launch equals 7 days late.
The chart shows how the original slip carries through unchanged. Every step after the lab dip is a fixed block of work that cannot start until the one before it finishes, so the variance is the same 14 days at each critical milestone.
Planned day to forecast day for key critical milestones (illustrative)
Each bar runs from the planned day to the forecast day
Illustrative values from the worked example. Bars show the span of the slip for each milestone, not duration of the activity.
Trims were booked for delivery at day 30, so a 14-day slip in fabric does not affect them: float on that step stays positive. That is why the dependency map from step 1 matters, because it stops the team from chasing steps that are not critical.
Recovery Options Compared in the Illustration
The programme is 7 days late. The recovery options are not equal. The table below applies each lever from step 4 to the example and shows what it recovers, using clearly illustrative assumptions: a priority dye slot saves 4 days from the 21-day block, extra sewing hours save 3 days from the 14-day block, cutting at risk from PP submission rather than PP approval saves 7 days, and air freight for colour C replaces 35 days of sea transit with an assumed 10 days.
Recovery scenarios for the delayed colour (illustrative)
| Scenario | Days recovered | Launch-ready position | Main risk |
|---|---|---|---|
| Do nothing, ship all colours together | 0 | 7 days late (day 128 against day 121) | Colours A and B wait for colour C; the whole 6,000-unit order launches late |
| Priority dye slot (4) plus extra sewing hours (3) | 7 | On the launch date, zero buffer left | Shade checks compressed; overtime must stay within compliance limits |
| Cut at risk from PP submission | 7 | On the launch date, zero buffer left | If PP needs a pattern change, cut panels are wasted |
| Split shipment: A and B on plan, C follows | 0 for C | A and B ready on original dates; C 7 days late | Staggered availability; extra freight handling |
| Air freight for colour C only (1,000 units) | 25 | 18 days ahead of launch for colour C | Freight cost per unit has to be weighed against the margin on those units |
Illustrative arithmetic: 4 + 3 = 7; air recovery is 35 minus 10 = 25 days, so colour C is ready at day 86 + 10 + 7 = 103, which is 18 days before day 121. These are assumptions, not quotes.
The right choice depends on the product and the stakes. Colour C is 1,000 of 6,000 units. If it is a hero colour in a launch campaign, the air freight route may be justified. If it is a secondary colour, a split shipment with a short stagger is cheaper and carries no quality risk. The least attractive combination is one that spends the whole buffer to save the date, as it leaves nothing for the next surprise.
KPIs: OTIF, Critical Path Variance and Lead Time
Three measures tell you whether your approach to prevent production delays is working. Each has to be defined before the season so that buyer and supplier read the same number.
The three KPIs defined
| KPI | Definition and formula | Watch for |
|---|---|---|
| OTIF (on time, in full) | Share of order lines or units delivered by the agreed date in the agreed quantity. Lines: OTIF lines divided by total lines. Units: units on time and in full divided by total units ordered | State the denominator (lines or units), the date being measured (ex-factory, port or distribution centre) and any tolerance on quantity. Definitions vary by retailer |
| Critical path variance | Forecast or actual date minus baseline date for each critical milestone, in days. Buffer remaining equals planned buffer minus the variance on the last critical milestone | Track separately by owner (buyer, factory, third party) so that the cause of lost time is visible |
| Lead time | Days from PO (or from approval of a defined input) to a defined end point. Production lead time ends at ex-factory; total lead time ends at goods received or ready to sell | Say which start and end points you use. A quoted lead time and an actual lead time are two different numbers |
Definitions as commonly used. Confirm the exact measurement basis with your own retail or brand programme.
In the worked example, planned production lead time was 72 days, or 10.3 weeks, and the actual was 86 days, or 12.3 weeks. Total lead time to the UK distribution centre moved from 107 to 121 days. Critical path variance was +14 days at every critical milestone, and the buffer remaining went from 7 to minus 7 days.
OTIF for the example order under two outcomes (illustrative)
| Outcome | Lines on time and in full | Units on time and in full | OTIF by lines | OTIF by units |
|---|---|---|---|---|
| All colours shipped together, 7 days late | 0 of 3 | 0 of 6,000 | 0% | 0% |
| Split shipment: A and B on plan, C late | 2 of 3 | 5,000 of 6,000 | 66.7% | 83.3% |
Illustrative: 2 divided by 3 is 66.7%; 5,000 divided by 6,000 is 83.3%. The same delivery scores differently depending on whether lines or units are counted, so fix the method up front.
The split improves the score but colour C still launches late. OTIF is a useful trend measure for supplier reviews, such as those in our supplier scorecard guide, but it does not show which lines matter most to the trading plan.
What to Decide, and What Would Change the Decision
For the example above, the default decision is to split the shipment, because it recovers the two largest colours at no quality risk, and to ask the factory for a priced air freight quote for colour C only if that colour is central to the launch. If the launch is a single campaign built around colour C, the decision flips and the air route or a launch date move becomes the first choice.
Evidence that should change a decision is specific: a confirmed dye slot date, a PP review that closes without comments, a quote that shows air freight cost per unit, or a factory report that overtime would exceed agreed limits. Name the KPI you will watch afterwards. For this case it is critical path variance on colour C at each remaining milestone, reviewed twice a week until the goods are ex-factory.
Pre-PO checklist to prevent production delays
- Dependency map completed for fabric, trims, PP, cutting, wash and shipment, with an owner for each
- Baseline schedule worked backwards from the launch date, with float marked on non-critical steps
- Shipment buffer set, visible as its own line and reported at every review
- Escalation triggers agreed for amber and red, with response times
- Recovery rules agreed: what can be approved quickly, what needs written buyer approval, what is never allowed
A rough rule for new colours or new finishes is to test them in advance rather than inside a live programme, which is the logic behind a test-and-scale approach. It lowers risk but does not remove it. For your next programme, which single dependency has the least float, and who owns the date for it?
How Ruhrose Approaches Production Planning
Ruhrose develops hoodies, fleece, jersey, denim and woven casualwear for UK buyers, with production in Bangladesh. We sample before bulk and plan the dependencies, especially lab dips, fabric booking, PP approval, wash and shipment, with the buyer before the PO is placed. We do not quote lead times in guides like this one, because they depend on fabric, colour, trims and wash. If you are importing for the first time, our guide to importing clothing from Bangladesh to the UK covers the shipment side.