How should teams validate a trend before sampling?

The problem

Sampling is the first point where a direction consumes serious money — fabric minimums, supplier time, sample rooms, freight — and the last point where stopping is cheap. Everything after it is progressively harder to reverse. A gate here costs an hour and routinely saves the entire cost of a style that had already stopped making sense.

The method

This is not re-litigating the approval. The direction was validated once and the decision stands. What this gate tests is whether the conditions that made the decision correct are still true, because between approval and sampling there is usually a gap of months during which the market did not stop moving.

1. 1Trajectory

   Is the driver still the driver?

   Check that the underlying shift has not been superseded. Drivers occasionally get overtaken — by an economic change, a cultural moment, a new entrant that reframes the category. This is uncommon but not rare, and it is much cheaper to find now than at bulk.

   What to look at

   • Re-read the driver statement and ask whether it is still what is happening.
   • Look for a newer driver that has absorbed this one.
   • If the driver has changed, the specification probably needs to change with it — or the style should stop.
2. 2Adoption

   Has it moved further than expected?

   A direction that has advanced faster than anticipated may now be at a stage where your planned expression is wrong — the version you specified as differentiating may have become the obvious one. Adoption moves during development, and specifications generally do not.

   What to look at

   • Re-check adoption stage against where it was at approval.
   • Search for your specific expression in market again. Three months is long enough for it to appear.
   • If it has become the obvious version, consider shifting the expression rather than cancelling.
3. 3Acceleration

   Is the window still open?

   Redo the arithmetic with the remaining critical path rather than the original one. Development has consumed time, some of it unplanned, and the window has continued to close. A direction that had comfortable room at approval can be marginal by sampling.

   What to look at

   • Use remaining path, not original path.
   • Where the margin has gone, switch to the faster route now while switching is still possible.
   • A negative velocity read at this point is a stop signal, even after development spend — sunk cost is not a reason to add more.
4. 4Regional relevance

   Is the destination market still the destination market?

   Allocation plans change during development. Confirm the markets this is now going to still match the specification — weight, coverage, compliance — because a style respecified for one market and allocated to another is a common and quiet failure.

   What to look at

   • Confirm the current allocation, not the one at approval.
   • Re-check compliance and labelling if markets were added.
   • Where a new market has been added, check the direction exists there at all.
5. 5Impact

   Is the material actually available?

   The most common practical failure at this gate. Confirm the specified fabric is available at your volume, at your price, in your timeframe — not that it exists. Availability is where specifications quietly get substituted, and substitution is how the load-bearing element disappears.

   What to look at

   • Get confirmed availability at volume, not an indication.
   • Check minimums against your actual order quantity.
   • If substitution is required, decide it here deliberately rather than letting it happen in the sample room.
6. 6Product signals

   Has the load-bearing element survived?

   The final and most important check. Between approval and sampling, costing happens, and costing removes things. Verify that the one element the product cannot lose is still in the specification. If it has gone, either restore it or stop — sampling a product that has already lost its reason is spending money to confirm a decision that was made accidentally.

   What to look at

   • Compare the current spec against the original brief line by line for that element.
   • Ask what was removed during costing and why.
   • If it cannot be restored within cost, stopping is usually the right call and almost never the one that gets made.

How F-Predict answers this

ScopeRe-run of the original approval scope, at the pre-sampling date

The practical mechanism is that a scope in F-Trend Predict can be saved and re-run. The gate is a comparison against the run that supported the original approval, rather than a fresh opinion.

Saved scopes

The original approval scope re-run at the current date, so the comparison is like-for-like rather than a new analysis with different parameters.

Season comparison

What changed between the two runs — momentum, adoption direction and colour movement — as a measured difference rather than a recollection.

Narrative intelligence

Current velocity, which is the input to redoing the window arithmetic against the remaining critical path.

Designer campaigns

Whether your specific expression has appeared in market during development — the check that the differentiating version is still differentiating.

Material intelligence

Whether the specified fabric direction is still being promoted, which is an early indicator of availability and price behaviour.

Team workspace decision log

What was originally approved and why, so the gate compares against the actual commitment rather than against what people remember of it.

The same decision from another desk

The six stages are the same across roles; what changes is what each stage means when you are the one making the call.