A seasonal collection plan is only as good as the calendar behind it. Without dates, the plan is a wish list; with dates, it is a program that tells every stakeholder when a decision must be made, when a sample is due, and when the bulk container leaves.
The sequence
1. **Collection brief and assortment** โ the styles, the fibres, the quantities, the price band, and the season they are built for. 2. **Tech pack and spec** โ one tech pack per style, with construction, measurements, tolerances, materials and artwork before a sample is cut. 3. **Development and first sample** โ the first physical answer to the spec, reviewed against fit, construction, hand-feel and workmanship. 4. **Correction and counter-sample** โ the changes, if any, captured on the make-sheet so the next sample is a controlled revision, not a reset. 5. **Pre-production sign-off** โ the build that tells the factory the bulk will be made to this standard and this documentation. 6. **Bulk and delivery** โ production against the approved spec, with the scheduled delivery to the agreed port or DC.
Each step has an owner and a date. The calendar is what makes the season happen.
The failure modes
- A collection that starts planning after the season has begun.
- A style that reaches bulk before the tech pack is signed off.
- A sample approved without a clear make-sheet, so the bulk is a different garment.
- A delivery date set before the freight and customs steps are understood.
How to make it stick
Write the collection calendar with the factory and the forwarder, not just internally. Set the development window, the first sample date, the correction cycle, the sign-off date and the container departure date โ and build the landed cost against the delivery date, not the wish date.
A seasonal plan is a calendar with named dates, not a mood board. The dates are what ship the collection.