Hoodie Critical Path: Why One Late Approval Moves the Delivery Date
Is the black fleece hoodie still on track for the launch window, or has a week already disappeared somewhere between the lab dip and the pre-production sample? In a Monday trading meeting that question usually gets an answer based on the last email, not on a plan with dates, owners and evidence. A hoodie critical path replaces that with a short list of milestones that each depend on the one before, so that anyone can see which delay moves the delivery date and which does not.
The critical path is the longest chain of dependent tasks between order confirmation and the date goods leave the factory. Tasks on it have no slack: if lab dip approval slips by two days and nothing else changes, everything after it moves by two days. Tasks off the path, such as hangtag artwork that is needed only at packing, can slip without moving the ship date until they use up their own float. Float is the time a task or the whole programme can slip before the committed date moves.
A hoodie path is more fragile than a basic jersey tee: a fleece body, rib, drawcords and eyelets, often a wash or print, and a heavier carton profile each add a dependency. The template here is a starting point that each programme must re-time against real fabric, factory and freight quotes.
Everything numeric here is illustrative; the clothing production lead times guide explains why one universal duration would mislead. What does not change is the method: book early, gate every dependency, escalate by rule and protect the transit leg.
Step 1: Set Fabric and Trim Booking Dates by Working Backwards
Fabric and trims are the inputs the factory cannot work around, so their booking dates sit at the front of any hoodie critical path. Booking means a written supplier confirmation with the quantity, the specification reference and a committed delivery date, not a verbal assurance. The date to calculate is the latest booking date, found by working backwards from when each item is needed.
Use one formula for every material: latest booking date = need-by date minus the supplier process time minus any transit to the factory minus a safety margin. The need-by date is set by the first task that consumes the material, for example fabric by the pre-production sample, packaging by the start of packing. Compare the latest date with the date you actually plan to book. The gap is the spare time you have bought, or the risk you have accepted.
Illustrative booking back-schedule for a fleece hoodie
| Material | Assumed process time | Need-by (end of week) | Latest booking (end of week) | Planned booking | Spare weeks |
|---|---|---|---|---|---|
| Fleece body fabric (knit, dye, finish) | 4 weeks | 5 | 1 | Week 1 | 0 |
| Rib for cuffs, hem and collar | 4 weeks | 5 | 1 | Week 1 | 0 |
| Drawcords and eyelets | 3 weeks | 5 | 2 | Week 1 | 1 |
| Main labels and care labels | 2 weeks | 5 | 3 | Week 1 | 2 |
| Print or embroidery elements | 3 weeks | 6 | 3 | Week 1 | 2 |
| Polybags, cartons and hangtags | 2 weeks | 8 | 6 | Week 2 | 4 |
Illustrative assumptions only: process times are hypothetical and must be replaced with confirmed supplier lead times. Spare weeks = latest booking week minus planned booking week.
Body fabric and rib have no spare time in this template, so any delay in confirming the order or the fabric specification goes straight onto the critical path. Trims and packaging have slack, as long as artwork and approvals are not forgotten.
Close the first gate only when you hold written booking confirmations for the body fabric, rib and long-lead trims. If the factory is waiting on a fabric mill, ask for the mill booking confirmation or the yarn allocation date. The guide to stopping supplier chasing after the PO covers how to request this evidence without nagging.
Step 2: Track Lab Dips, PP, Cutting, Wash and Packing
Once materials are booked, the hoodie critical path is held together by approvals, each with a buyer owner, a supplier owner, a baseline date and a defined piece of evidence.
Lab dips and fabric lot tests
Lab dips are small dyed swatches submitted for colour approval before bulk dyeing starts, and the colour decision is a buyer decision with a deadline. Set a response time, for example two working days, and say what happens if it is missed: the supplier proceeds with the nearest option, or the date moves day for day. How a colour is achieved matters too, and our fabric dyeing methods guide shows why reactive, pigment and garment dyeing carry different risks. Finished fabric should then be tested for shrinkage, colour fastness and weight, using the methods and pass criteria your programme specifies.
Pre-production sample (PP)
The PP is made from bulk fabric and bulk trims with the bulk construction, so it confirms that the approved sealed sample can be repeated. It is the gate that releases cutting. Approve it against a written checklist and consolidate comments into one response. The garment sampling process guide explains how the earlier sample rounds feed this one.
Cutting, wash and packing
Cutting should not start before the PP is approved and the fabric tests are in, because every cut panel is a commitment of fabric you cannot reverse. Reconcile cut quantities against the size ratio at the end of cutting. If the style is washed, approve a pilot wash standard before bulk washing and agree how shade variation will be judged. Packing needs approved labels, packaging and carton marks, and the final inspection should happen on finished, packed goods early enough to leave time to react to a failure.
Milestone register for the hoodie critical path
| Milestone | Gate it closes | Buyer-side owner | Supplier-side owner | Evidence | Typical red trigger |
|---|---|---|---|---|---|
| Fabric and trim booking confirmed | G1 | Sourcing lead | Merchandiser | Written booking confirmations | No confirmation by the planned date |
| Lab dip decision | G2 | Product developer | Merchandiser | Signed colour approval, swatch retained | No buyer response by the deadline |
| Fabric and trims in-house, lot tested | G3 | Technologist | Fabric and quality managers | Receipt record, test report | Receipt date forecast later than baseline |
| PP approved, cutting released | G4 | Product developer | Sample room lead | Signed PP comments | PP rejected or comments unconsolidated |
| Wash standard and cut quantity cleared | G5 | Technologist | Production manager | Pilot wash approval, cut reconciliation | Pilot fails, or cut count short |
| Final inspection passed, ship released | G6 | Quality lead | Quality manager | Inspection report, packing list | Fail result, or no slot booked |
A suggested register. Owners, evidence and triggers are proposals to agree with the supplier before the PO, not fixed rules.
A 12-Week Hoodie Critical Path With Decision Gates (Illustrative Template)
The chart below puts the stages on a single week-by-week scale for one fleece hoodie. It is an illustrative template, not a benchmark: every programme must re-time it using confirmed fabric lead times, factory capacity, the wash route and the shipping mode. Treat the bars as the shape of the plan, and the week numbers as placeholders to be overwritten.
Week-by-week template: fabric booking to ex-factory
Week scale, 0 to 12
Illustrative template only. Durations are hypothetical placeholders, not typical lead times; re-time every bar for the actual fabric, factory and wash route. Colour key: dark blue = materials, green = approvals, gold = production, grey = float.
Fabric is the long pole: the PP cannot start until it is in-house and tested, so it sits directly on the path. After PP approval, production runs as overlapping stages that end with final inspection and a one-week float.
The six decision gates
- Gate 1, end of week 1Booking confirmed in writing for body fabric, rib and long-lead trims. Decision: proceed, or reselect the source.
- Gate 2, end of week 2Lab dip approved. Decision: release dyeing, or resubmit once with a fixed deadline.
- Gate 3, end of week 5Fabric and trims in-house and lot tested. Decision: release the PP, or hold for rework or a replacement lot.
- Gate 4, end of week 6PP approved against the written checklist. Decision: release cutting, or require a second PP before any panel is cut.
- Gate 5, end of week 7Pilot wash standard approved and cut quantity reconciled. Decision: release sewing and bulk wash.
- Gate 6, end of week 11Final inspection passed on packed goods. Decision: release shipment, or hold, rework and re-inspect using the float.
Illustrative template. Gate timing follows the bar chart above and must be re-timed per programme.
Each gate is a go or no-go decision with a named person, not a status update. The point of a gate is that nobody downstream starts work on an assumption: cutting does not begin because the PP is probably fine, and shipping does not begin because the inspection is probably clear. For the wider production sequence behind these stages, see the garment production process guide.
Step 3: Escalate Red Milestones With Named Owners
A critical path only works if slippage triggers action before the next milestone, not after the ship date has gone. The simplest rule links status to float. Amber means a milestone is forecast late but the programme can absorb it. Red means the forecast delay, together with any earlier delay, would use up more than half of the float or has already missed a gate. The half-float line is a proposed convention to agree with your supplier, not an industry standard.
A proposed RAG and escalation rule
| Status | Trigger | Action | Who is told | Response time |
|---|---|---|---|---|
| Green | On baseline date, evidence received | None; log it | Merchandiser | Weekly report |
| Amber | Forecast late, and cumulative slip is less than half the float | Supplier sends cause and recovery step | Buyer and supplier merchandisers | Same working day |
| Red | Cumulative slip is more than half the float, or a gate is missed | Recovery plan with options and cost; decision meeting | Sourcing lead and supplier production manager | Within 24 hours |
| Critical | Cumulative slip exceeds all float | Choose: re-date, re-route freight, partial shipment or cancel; record the decision | Buying director and supplier senior management | Within 48 hours |
Illustrative rule: the thresholds and response times are suggestions to agree in advance, not fixed standards.
Naming owners matters as much as the thresholds. A red milestone with no owner on both sides becomes an email thread. The supplier names who will recover it; the buyer names who decides what only the buyer can, such as accepting a partial shipment or paying for air freight.
Escalation ladder for a red milestone
- 1Flag the same dayThe supplier merchandiser reports the miss with a cause, the new forecast date and the milestones affected.
- 2Quantify the floatCalculate cumulative slip against the remaining float. Do not describe a delay as small until this is done.
- 3Offer optionsThe supplier proposes at least two recovery routes with cost, quality and date trade-offs.
- 4Decide and recordThe named buyer decision-maker chooses, and the change to the baseline is recorded with the date.
- 5Re-forecastReissue the path with the new dates, and tell sales and planning teams the revised ex-factory date.
A suggested sequence. Adapt the response times to your own governance.
Step 4: Validate Realistic Transit Buffers
A factory date is not a delivery date. The ex-factory date is only the start of the transit leg, and the buyer needs the goods booked into the distribution centre or warehouse. The transit buffer is the total time from ex-factory to booked-in stock, plus a safety allowance. It should be built from components that you confirm with your freight forwarder, not copied from a previous order.
Use this formula: required ex-factory date = required booked-in date minus transit, port and customs processing, inland delivery, receiving time and safety buffer. Because the numbers below are assumed, the logic is the lesson, not the totals.
Illustrative transit buffer allowance (sea freight)
| Component | Assumed days | What to confirm |
|---|---|---|
| Main sea transit | 35 | Current sailing schedule and any transhipment from the forwarder |
| Port handling, customs and release | 5 | Customs broker timing, documents ready before arrival |
| Inland delivery to the warehouse | 3 | Haulier booking and delivery slot |
| Warehouse receiving and booking-in | 2 | Receiving appointment and putaway time |
| Safety buffer | 7 | Seasonal congestion and the cost of arriving late |
| Total from ex-factory to booked-in | 52 | 7 weeks and 3 days |
All figures are assumed for illustration only. Replace them with current, dated figures from your forwarder and customs broker; do not treat them as typical transit times.
On these assumptions, a 12-week production path plus the 52-day allowance is 84 plus 52, or 136 days from fabric booking to booked-in stock, which is about 19 weeks and 3 days. The practical use is to start from the date the product must be on sale, subtract the allowance, and see whether the booking date has already passed. If it has, the options are a shorter route, a smaller first quantity, or a later launch date. Air freight can rescue a late programme, but it is a cost and a signal, not a plan. See our guide to importing clothing from Bangladesh to the UK for the freight and customs steps in more detail, and check the current UK Trade Tariff and your forwarder for duty and clearance requirements.
Worked Example: Small Slips That Add Up Without Anyone Calling Red
The next illustration shows why a hoodie critical path needs a cumulative view. It uses the template above, with 7 days of float. No single slip in this example looks serious. The first is two days at the lab dip gate, and the largest is three. The programme is still late.
Illustrative gate slips against the 7-day float
| Gate | Slip added at this gate (days) | Cumulative slip (days) | Status under the half-float rule (3.5 days) | Float remaining (days) |
|---|---|---|---|---|
| G1 booking | 0 | 0 | Green | 7 |
| G2 lab dip | 2 | 2 | Amber | 5 |
| G3 fabric and trims tested | 3 | 5 | Red | 2 |
| G4 PP approved | 2 | 7 | Red | 0 |
| G5 wash and cut cleared | 0 | 7 | Red | 0 |
| G6 final inspection | 3 | 10 | Critical (float exceeded) | Minus 3 |
Hypothetical slips for illustration. They are not typical delays and do not describe any real order.
The same figures are easier to read as a chart. The bars show cumulative slip at each gate, and the float sets the line that matters.
Cumulative slip by gate against 7 days of float
Illustrative values taken from the table above. The float is 7 days, so the bar crosses the float at G4 and passes it at G6.
The status column is where the half-float rule earns its keep. At G2 the slip is amber. By G3 the cumulative slip is 5 days, above the 3.5 day line, so the programme turns red with 2 days of float left and there is still time to choose a recovery option. Without the rule, the first formal alarm would come at G6, when the options are limited to expensive ones. Total slip is 2 plus 3 plus 2 plus 3, which is 10 days; against 7 days of float, the ex-factory date moves by 3 days. If a shipping slot is fixed, that is the difference between the booked vessel and the next one.
The sum of small slips behaves like one large one. For a single large slip and its recovery options, see our guide on how to prevent production delays.
KPIs: OTIF, Late Milestones and Days Lost
Three measures turn the path into something you can review weekly and compare across seasons. Define each one before the PO and say how it is measured, because definitions vary between retailers and suppliers and an unclear definition makes the numbers unusable in a supplier review.
The three KPIs and how to calculate them
| KPI | Definition and formula | How to measure | Watch-out |
|---|---|---|---|
| OTIF (on time in full) | Share of order lines delivered by the agreed date in the agreed quantity. OTIF % = lines on time and in full divided by total lines, times 100 | State the date (ex-factory or booked-in), the tolerance for quantity and whether you count lines or units | A line one day late or one unit short usually counts as a miss; agree this up front |
| Late milestones | Milestones completed after the baseline date. Late % = late milestones divided by milestones due, times 100 | Count against the original baseline, not the latest re-forecast | Re-baselining hides the problem; keep both dates |
| Days lost | Days added to the committed ex-factory date. Days lost = actual ex-factory minus committed ex-factory, or cumulative slip minus float, if positive | Record the slip added at each gate to find where the days went | A programme with float can have late milestones and zero days lost |
Definitions vary by retailer and supplier. Agree the exact formula in the supplier terms.
In the worked example, 5 of the 6 gates are late against the baseline (G2 to G6), so late milestones is 5 of 6, while days lost is 3. These tell different stories: the first points to a pattern of late approvals, the second to the effect on the date. OTIF is the outcome measure and is only available once the goods ship. If, in a hypothetical season, 7 of 10 order lines were delivered on time and in full, OTIF would be 70 per cent, but the figure means little until you know which gates produced the 3 misses.
Track the three together. Late milestones is the leading indicator, days lost is the effect on the date, and OTIF is the result. The scorecard in our supplier scorecard guide shows how to combine them with quality measures over several seasons.
Decision: What to Do and What Would Change It
Treat the template as a default and change it only for a reason you can state. The decision for most hoodie programmes is to commit to the gates before the PO, hold at least one week of float after the last gate, and refuse to start cutting without a signed PP. The right amount of float depends on fabric risk, the cost of late arrival and how much of the delivery is fixed to a campaign or launch date.
Pre-PO checklist for the hoodie critical path
- Latest booking dates calculated for body fabric, rib and each long-lead trim.
- Six gates agreed, each with a buyer owner, a supplier owner and a named piece of evidence.
- Lab dip and PP response times agreed, with the consequence of a missed response stated.
- RAG thresholds linked to float, and escalation response times written into the supplier terms.
- Transit buffer built from current forwarder figures, with a safety allowance and a booked-in date.
- KPI definitions agreed: how OTIF is measured, what counts as late, how days lost is calculated.
Adapt to your own governance. Items are suggestions, not a compliance standard.
Evidence that should change the plan includes a fabric supplier that cannot confirm a booking date, a lab dip that is rejected twice, a PP that fails on construction rather than colour, or a forwarder who reports a congestion risk on the intended route. Any of these should trigger a re-time of the whole path, not a patch of the next date. If the style is new to the factory, treat the schedule with more caution and consider the staged approach described in our guide to test-and-scale manufacturing, which is a risk-reduction model rather than a guarantee.
Review the three KPIs weekly, and compare actual gate dates against baseline season by season. If a gate is late on every order, the fix is usually a deadline or a decision right, not more reminders. Which gate in your current hoodie programme has no named owner on either side, and what would happen to the delivery date if it slipped by a week?
How Ruhrose Approaches the Hoodie Critical Path
Ruhrose develops and produces hoodies, jersey, denim and woven casualwear in Bangladesh with UK buyer support, and sampling comes before bulk. We plan hoodie timelines around the same gates described here: material booking, lab dips, a PP from bulk fabric, wash approval where relevant and a final inspection before shipping. We do not quote a standard lead time, because it depends on fabric, wash route and order size. If you want to discuss a specific date, shortening development time is the place to start, and we are happy to talk through a template for your own programme.