Direct answer
Start with the decision, then verify the specification.
Plan backwards from the date when the scarves must be usable, not from a single production lead-time number. Include artwork preparation, quotation, sampling, sample transit, buyer review, revisions, material and production, inspection, packaging, freight, customs and internal receiving. Ask what starts every clock and which buyer approvals are assumed. SCARFTEX confirms sampling timing per project after details and the sample fee are confirmed; bulk timing depends on the actual order quantity and scope.
Buyer scenario
Why this question changes the order.
For a fixed event, buyers often count only bulk production and leave no time for sample changes, box approval or receiving. Turn the event date into a reverse schedule, mark every decision gate and add a buffer for freight and internal distribution. The plan does not remove every risk; it makes unresolved risks visible while there is still time to act.
Define the finish line
Write three dates separately: launch or event date, required warehouse arrival and requested shipment date. Add the buyer's inbound checks, allocation, labelling or retail-distribution steps. For a multi-location project, identify whether one consolidated shipment or staged deliveries are required. A date is only meaningful when the delivery point and acceptance condition are named.
Then define the scope that must arrive: style and colourway quantities, labels, retail pack, inserts, replacements, samples and documents. A partial shipment may protect one milestone but change freight, inspection and stock-allocation costs. If it is an option, quote it explicitly rather than assuming the supplier can divide the order later.
Name every approval gate
Typical gates include artwork preflight, layout approval, material selection, print or colour review, construction sample, label and packaging proof, final sample approval, written bulk specification, bulk start authorisation, inspection result and shipment release. Not every project needs every gate, but omitted gates should be intentional. Identify the person authorised to approve each and the maximum buyer review time allowed in the plan.
Approval must be specific. 'Looks good' in a message may not settle the artwork version, colour reference, finished size, edge width or pack-out. Record the approved reference and remaining exceptions. A conditional approval should state what must change and whether another sample or proof is required before the next clock begins.
Find the real schedule drivers
Material availability, print preparation, number of artworks and colourways, hand or machine finishing, label production, packaging structure, testing, inspection booking and freight capacity can sit on different paths. The longest dependent path controls the finish date. A box with its own sample and minimum may drive the project even when scarf production is straightforward.
Ask what work may proceed in parallel and what would be at risk. Ordering packaging before the final scarf fold and dimensions are approved can create a fit problem. Reserving generic material may be possible before final artwork, but a custom component may not be. Record any advance commitment, who authorises it and what cost becomes non-recoverable if the project changes.
Manage change without hiding its impact
Use a change log after the schedule baseline is agreed. For each request, record the new artwork or specification revision, date, affected sample or production step, cost effect and revised milestone. A new colourway, changed label text, different box, added testing or altered quantity can affect different parts of the critical path. The schedule should show the effect rather than preserving an old date that no longer describes the work.
Add decision buffers where uncertainty is highest, especially physical sample transit, buyer review, rework, inspection findings and international transport. Buffer is not wasted time; it is the visible space in which a predictable issue can be resolved without consuming the launch date. If a deadline cannot support the full route, compare scope alternatives honestly.
Maintain one dated schedule visible to the buyer and project team. Mark actual completion separately from forecast completion, and never move a missed milestone without recording the cause and downstream effect. This makes the next required decision clear and prevents different email threads from carrying incompatible launch assumptions. Keep superseded versions for traceability.
Critical-path checklist
Review checklist
- Required-arrival, launch, shipment and internal receiving dates with named locations.
- Styles, colourways, quantities, components, documents and delivery splits in scope.
- Artwork, material, sample, label, packaging, bulk, inspection and release gates.
- Owner and due date for every buyer and production decision.
- Start event and duration basis for sampling and bulk production.
- Dependencies, parallel work, advance commitments and non-recoverable costs.
- Inspection booking, freight booking, transit, customs and last-mile assumptions.
- Change-control rule, revised-date ownership and practical decision buffers.
Treat approvals as production time
A buyer's internal review can take as long as the physical sampling step, especially when design, marketing, procurement and legal teams need to sign off different parts of the product. Put the review owner and target date beside every gate. If a sample is delivered on Monday but the decision maker is away until Friday, the project clock has not really stopped; the launch plan has simply hidden the delay.
Separate the date when production is complete from the date when the goods are usable at the event or in the warehouse. Add packing, booking, customs, delivery, receiving and internal allocation. If the schedule depends on a particular freight mode, destination or nominated forwarder, record that assumption and refresh it when final carton data exists. A realistic plan is not pessimistic; it gives the team a chance to change scope before the date becomes impossible.
Primary references
Sources used for technical context
These sources support the general technical or regulatory context. They do not prove SCARFTEX capability, certification or the specification of a particular order.