What is critical path in apparel? Milestones, TNA and slippage explained.

What the critical path actually is

The critical path for a style is the sequence of dependent milestones between design freeze and the product being in store: BOM sign-off, proto sample, fit approval, pre-production sample, bulk fabric commit, production, inspection, ex-factory, shipping, receipt, live. Each milestone depends on the one before it, which is what makes the path “critical”: a delay anywhere on it delays everything after, ending at the delivery date.

The term comes from project management (critical path method, 1950s construction and defence scheduling) and the apparel industry adopted both the concept and, in its own tradition, the name “time and action calendar” (TNA). Same thing: the dated, owned, dependency-aware milestone list per style or purchase order.

Why it matters commercially: in wholesale, delivery windows are contractual - miss them and orders get cancelled or charged back. In D2C, a late drop misses its marketing moment. The critical path is the instrument that converts “we need it in store April 15” into “which means the proto must be approved by November 22” - and makes today’s small delay visible as April’s missed delivery while there’s still time to act.

The standard milestones

Milestone sets vary by brand and category, but a representative path for a bulk-produced style:

Backward scheduling

Critical path dates are calculated backward from the delivery date. The in-store date is fixed by the range plan’s drop assignment; each milestone’s lead time to the next is subtracted in sequence to produce the latest allowable date for every step.

A simplified example for an April 15 in-store date: receipt at DC by April 1 (allocation buffer) → ex-factory by February 25 (ocean transit + customs) → production start January 15 (six-week production) → fabric commit November 20 (eight-week fabric lead) → PP approval November 13 → fit approval October 16 (assuming one further round) → proto request September 1. The style’s development deadline is thus September 1 - seven and a half months before the customer sees it.

Backward scheduling makes two things explicit that forward planning hides: the latest safe date for every decision, and the true cost of early-stage delay. A two-week slip in fit approval in October is invisible in October; backward-scheduled, it’s already a two-week delivery slip in April unless a downstream buffer absorbs it.

Time and action calendars

Time and action (TNA) is the garment industry’s traditional name for the critical path, and the traditional artefact: a grid of milestones down the side, styles or POs across the top, with planned date, revised date, actual date and responsible party per cell. Merchandisers in sourcing offices have run TNAs for decades, historically on paper, then in Excel.

The TNA tradition carries two useful disciplines worth preserving regardless of tooling: every milestone has one named owner (a date without an owner is a wish), and planned vs revised vs actual are tracked separately (so slippage history is visible rather than overwritten - a path that’s been “revised” four times tells you something the current date alone doesn’t).

Dependencies and buffers

Two structural features separate a real critical path from a list of dates:

Dependencies. Milestones are linked: fit approval cannot precede the fit sample; fabric commit shouldn’t precede PP approval (though brands under time pressure sometimes take exactly that risk, knowingly or not). When dependencies are modelled, a slip in one milestone automatically rolls the dependent dates forward - and surfaces which deliveries are now at risk. When they aren’t modelled, every slip requires someone to manually re-derive the downstream impact, which in practice means it doesn’t happen until the impact arrives on its own.

Buffers. Sensible paths carry deliberate slack at the points of highest variance - usually an extra fit round’s worth of time in development, and a week or two between DC receipt and live. The discipline is knowing where the buffer is and who’s allowed to spend it. Paths without explicit buffer have implicit buffer - taken silently by whoever slips first, leaving none for whoever slips second.

The calendar traps worth modelling explicitly: Chinese New Year (factories close for 2-4 weeks and capacity is constrained for weeks either side), Golden Week, Ramadan and Eid depending on the supply base, and peak-season freight congestion. Every experienced production calendar has these built in; every inexperienced one discovers them.

Why paths slip

1. Fit decisions wait for people. The sample arrived Tuesday; the fit session happens next Thursday because that’s when everyone’s free. Nine days of path spent on scheduling, not work. Multiplied across rounds and styles, this is routinely the largest silent consumer of development time.
2. Sample rounds exceed plan. The path assumed two fit rounds; the style needed four. Partly variance, partly a signal about block quality and spec clarity.
3. Lead times assumed, not confirmed. The path used 6 weeks for fabric; the mill quoted 9 when the order landed. Lead times need confirming per supplier per season, not inheriting.
4. Approvals without deadlines. Lab dips, strike-offs, PP samples sitting in someone’s inbox. Anything awaiting sign-off needs a date and an owner like every other milestone.
5. Holidays not modelled. A path that runs production through Chinese New Year on paper delivers three weeks late in reality.
6. No single owner of the path. Everyone owns their milestone; no one owns the chain. Slippage in the gaps between departments is where deliveries actually die.

What good path management looks like

• Paths generated from templates - a category-specific milestone template applied at adoption, dated backward from the drop, adjusted for the style’s supplier lead times. Not hand-built per style.
• One visible board across styles - the cross-style view of what’s due this week, what’s late, and what the lateness threatens. The per-style view is for diagnosis; the cross-style view is for running the season.
• Slips roll forward automatically - dependent dates update when a milestone moves, and at-risk deliveries surface without anyone doing arithmetic.
• Exception-driven attention - the weekly production meeting reviews the late and the at-risk, not all 200 styles. On-time milestones need no meeting time.
• Factories see their dates - suppliers work from the same milestone dates the brand tracks, not from a PDF calendar emailed once at season start.
• Slippage history reviewed seasonally - which milestones slipped most, which suppliers ran latest, which lead-time assumptions failed. Next season’s templates get corrected from this.

Spreadsheets vs systems

TNA in Excel works at small scale and is where nearly every brand starts. It breaks predictably as style count grows: no automatic dependency rolling, no cross-style exception view without manual consolidation, version chaos once sourcing offices and factories each hold copies, and no connection to the style data the dates refer to - the path says PP approval is due, but the sample status, the spec and the supplier live somewhere else.

Critical path inside a PLM changes the mechanics: paths generate from templates at adoption, dates hang off the same style record as the tech pack and BOM, dependencies roll automatically, and the exception board is a view rather than a weekly consolidation exercise. The judgment calls - which buffer to spend, which delivery to re-drop, which supplier conversation to have - remain human; the system’s job is making sure they happen in November rather than April.

Frequently asked questions