Course contents
Practitioner · Course 3: Retail Critical Path · Lesson 4 of 5

Flagging a delay before it reaches the shop floor

Level: PractitionerTime: 45 minutesOrder used: B (the jeans)Tool: Retail critical-path tracker
For a sourcing agent, or a buyer relying on one, who watches a factory's own milestones for signs of risk and needs to know when to raise an early flag. Lesson 3 of this course is useful preparation, though not required. Figures are teaching figures.
AgentMeridian Sourcing
BuyerEuropean buyer, hybrid account
FactoryDelta Garments
OrderB — 3,000 jeans (MTO line)
Milestone watchedFabric in-house, due week 10
ToolRetail critical-path tracker
02Opening

This page teaches a sourcing agent how to raise an early flag on a slipping milestone before it becomes a shop-floor problem

An agent watching a factory's own progress on behalf of a buyer does not need to wait until a milestone is fully missed to act. Flagging early means raising a flag the moment a milestone shows a real sign of risk, such as slow progress partway through its own window, rather than waiting for its due date to pass. This is chiefly a decision-flow skill: deciding, from partial information, that a risk is real enough to raise now, while there is still time for the buyer or factory to act on it.

Without this step, a delay can sit unreported until its own due date is already missed, by which point every later milestone on the critical path, all the way to the shop floor, has lost the same amount of time.

03Before you start

You need: a basic sense of a factory's own critical path and how one milestone's delay affects the milestones after it. Lesson 3 of this course, on managing many style lines at once, is useful preparation, though not required.

By the end of this lesson you can:

  • explain the difference between flagging early and reporting a milestone once it is already late;
  • recognise the signs that a milestone still inside its own window is genuinely at risk;
  • raise an early flag with the two or three facts that justify it;
  • state why an agent's early flag protects a hybrid account's own MTO and MTS lines differently.

Not covered here: building the complete retail critical-path tracker combining everything in this course (Lesson 5).

04Key terms

Words you will meet in this lesson

TermMeaning
Early flagA risk signal raised on a milestone before its own due date has passed, based on a genuine sign of slow progress.
Risk thresholdThe specific, defined condition that turns a milestone's status from on track to at risk.
Agent-monitored milestoneA milestone an agent checks on the factory's own behalf, on a schedule the buyer and agent agree in advance.
Hybrid accountA buyer relationship that combines Make to Order and Make to Stock business with the same factory.
Shop-floor impactThe effect a factory-side delay will eventually have on a store's own floor-ready date if it is not caught early.
Advance noticeThe amount of time between an early flag being raised and the milestone's own original due date.
05Teaching
The rule

An early flag is raised when a milestone shows a defined risk threshold, not only once its own due date has already passed

Waiting for a due date to pass before reporting a delay wastes the time that was still available while the milestone was at risk. An early flag uses a risk threshold, a specific condition defined in advance, such as no reported progress at the halfway point of a milestone's own window, to raise a flag while there is still time left to act. The flag is raised on the risk threshold being met, not on a guess or a general feeling that something might be wrong.

Risk thresholdDue date
An early flag is raised at a defined risk threshold, well before a milestone's own due date is reached.* Waiting for the due date itself removes the time still available to act.
What you meet in real life

How early a flag is raised, and who raises it, differs by market, business model and product

What can differThe shapes you meetWhy it matters
Export vs. domestic orderAn export account with a long shipping stage, such as Delta Garments' European buyer, needs an earlier flag on a factory-side delay, since the retail-side stages downstream leave less room to absorb it; a domestic account with a short delivery stretch can sometimes absorb a small factory-side slip without missing a floor-ready date.Applying a domestic account's own shorter early-flag window to an export account risks flagging too late for the longer chain of stages still ahead.
MTO vs. MTS vs. hybridAn MTO line's own milestone, once missed, delays one specific confirmed order; an MTS line's own milestone, once missed, delays a recurring reorder cycle that affects ongoing stock cover; a hybrid account needs separate risk thresholds for each kind of line, since a missed milestone means something different for each.Using one single risk threshold for both an MTO line and an MTS line on the same hybrid account can under-flag the line whose own consequences are actually more serious.
Who raises the flagAn agent such as Meridian Sourcing raises a flag on the factory's own behalf when it is monitoring the account directly; a factory's own merchandiser raises the same kind of flag when no agent is involved.Assuming an agent will always catch a risk, when no monitoring schedule has actually been agreed, leaves a gap where nobody is checking.
A short milestone window vs. a longer oneOrder B's jeans fabric-in-house milestone runs a 7-week window; a shorter milestone, such as a 1-week inspection stage, needs a risk threshold checked far sooner within its own window, since there is less time to react.Applying the same "halfway point" rule without adjusting for a much shorter window can leave almost no time to act once the threshold is reached.
Socks, terry and home-textile product familiesA hosiery line's own risk threshold might sit at the linking-and-boarding stage; a home-textile line's own risk threshold might sit at cut-and-sew for a multi-piece set.The early-flag method is the same across product families; only which milestone the threshold is set against changes.
The case we follow

Meridian Sourcing raises an early flag on Order B's fabric-in-house milestone for a European buyer's hybrid account with Delta Garments

Meridian Sourcing is an agent in Egypt working for a European buyer that runs a hybrid account with Delta Garments: a confirmed Make to Order line, Order B's jeans, alongside a separate recurring Make to Stock line for the same buyer. the jeans order's own fabric-in-house milestone is due at week 10, a 7-week window running from week 3. Meridian Sourcing's own agreed monitoring schedule checks progress at week 6 and a half, roughly the halfway point of that window. At that check, Delta Garments reports that Suez Denim has not yet delivered any of the ordered denim, though half the fabric window has already passed.

The worked number

Zero fabric delivered at the halfway point of a 7-week window is the defined risk threshold that triggers Meridian Sourcing's flag

Order B's jeans, fabric-in-house window fixed at 7 weeks (week 3 to week 10):
Halfway point of the window: week 6.5
Risk threshold: no fabric delivered by the halfway point
Fabric actually delivered by week 6.5: none
Result: risk threshold met → early flag raised, 3.5 weeks of advance notice remaining before the week-10 due date

The 7-week window is the jeans order's own fixed figure (section 7). The halfway-point risk threshold is an illustrative monitoring rule Meridian Sourcing applies, not a fixed academy fact, since no specific risk-threshold percentage is fixed for this course; it is shown clearly as illustrative so a reader can see how a threshold turns a partial fact into a decision to flag.

Flag raised, wk 6.5Due, wk 10
No fabric delivered by the halfway point of the seven-week window is the defined risk threshold. Raising the flag at week 6.5 leaves 3.5 weeks of advance notice, instead of discovering the delay only at the week-10 due date.
The method

Four steps for raising an early flag on an agent-monitored milestone

  1. Define the risk threshold for the milestone in advance, agreed between the agent and the buyer.
  2. Check progress against that threshold at the agreed monitoring point, not only at the due date.
  3. Confirm the threshold has actually been met, using a real reported fact, not a guess.
  4. Raise the flag immediately once the threshold is met, naming the fact that triggered it and the advance notice remaining.
The trap

A common mistake is treating a milestone still inside its own window as safe simply because its due date has not yet passed

A common mistake is an agent checking only whether a due date has been missed, rather than whether real progress is on track within the window still remaining. If Meridian Sourcing had waited until week 10 to check Order B's jeans fabric-in-house milestone, it would have discovered the delay with none of the 3.5 weeks of advance notice left to act on, and every milestone after it, sewing, washing, ex-factory, shipping, and finally the shop-floor date, would already be at risk together instead of one at a time. Checking at a defined point inside the window, not only at its end, is what turns a late discovery into an early one.

06In plain words

A milestone can be in trouble long before its own deadline actually passes. Watching only for a missed deadline means finding out too late to do much about it. Checking partway through, against a clear rule agreed in advance, such as "flag it if nothing has happened by the halfway point," catches the same problem while there is still time left to fix it. An agent working on a buyer's behalf uses exactly this kind of rule, so a slipping milestone is raised as a flag while there is still room to act, not just recorded as a miss after the fact.

07Quick check
  • An early flag is raised at a defined risk threshold, not only once a due date has already passed.
  • A risk threshold is a specific, agreed-in-advance condition, such as no progress by the halfway point.
  • An MTO line and an MTS line on the same hybrid account may need different risk thresholds.
  • A shorter milestone window needs its risk threshold checked sooner, since less time remains to react.
  • An agent's own agreed monitoring schedule is what makes early flagging possible at all.
  • Waiting for the due date itself removes the advance notice an early flag exists to provide.
08Workplace scenario

Meridian Sourcing must decide whether to raise the flag immediately or wait one more week to see if fabric arrives

Meridian Sourcing has confirmed, at week 6.5, that no denim has yet been delivered for Order B's jeans, against a fabric-in-house due date of week 10.

  • The agreed risk threshold, set with the European buyer in advance, is: flag immediately if no fabric has been delivered by the halfway point of the fabric window.
  • Delta Garments tells Meridian Sourcing that Suez Denim has promised delivery "soon," with no specific date given.
  • Waiting one more week, to week 7.5, would leave only 2.5 weeks of advance notice instead of 3.5 if the delay turns out to be real.
  • The buyer's own contract with Meridian Sourcing states the agent's role is to flag against the agreed threshold, not to judge whether a delay will resolve itself.

The relevant note from Meridian Sourcing's own monitoring agreement:

Meridian Sourcing, monitoring agreement with the buyer. "The agent raises a flag immediately once an agreed risk threshold is met, without waiting to see whether the underlying cause resolves on its own."

Should Meridian Sourcing raise the flag now or wait a week? Decide before you open the decision.

Show decision

Raise the flag now, since the agreed risk threshold has already been met and the agreement does not allow waiting to see if the delay resolves itself.

The two facts that decide this are that the risk threshold, no fabric delivered by the halfway point, is already met, and that the monitoring agreement explicitly states the agent's role is to flag against the threshold, not to judge whether "soon" will turn out to be true. Waiting a week to see what happens is exactly the choice the agreement rules out, and it would also give the buyer one week less advance notice if the delay turns out to be real. Raising the flag now, with the fact that triggered it and the 3.5 weeks of advance notice remaining, lets the buyer and Delta Garments decide together how to respond while there is still time.

09What it costs

Waiting one extra week to raise the flag would have cost Meridian Sourcing's buyer a full week of the advance notice available

Order B's jeans total FOB value is fixed by its price and quantity:

3,000 pieces × USD 9.80 per piece = USD 29,400 total FOB value

If Meridian Sourcing had waited until week 7.5 instead of flagging at week 6.5, the advance notice remaining before the fixed week-10 fabric-in-house due date would have dropped from 3.5 weeks to 2.5 weeks, one full week less time for the buyer, Delta Garments and Suez Denim to resolve the fabric delay before it pushes into sewing, washing, ex-factory, shipping and finally the shop floor. Raising the flag the moment the agreed threshold is met, rather than waiting to see if the problem resolves itself, is what protects the full advance notice the whole USD 29,400 order's own schedule was built to allow.

10Working template

Retail critical-path tracker: the columns this lesson fills

Use the T19-C03 Retail critical-path tracker. For Order B's jeans MTO line, record the fabric-in-house milestone, its risk threshold, the date the threshold was checked, and the status change to at risk once the threshold is met. Note the advance notice remaining at the time the flag is raised.

[Download the Retail critical-path tracker](../../templates/T19-C03-retail-critical-path-tracker.xlsx)

Download the Retail critical-path tracker (Excel)

11Check yourself

1. What triggers an early flag on a monitored milestone?

2. A milestone has a 2-week window instead of Order B's jeans 7-week fabric window. How should its risk threshold be set?

3. An agent's monitoring agreement says to flag immediately once a threshold is met. The agent instead waits to see if the delay resolves itself. What is the risk?

12Glossary
ENARFRTRMeaning
Early flagتنبيه مبكرAlerte précoceErken uyarıA risk signal raised on a milestone before its own due date has passed, based on a genuine sign of slow progress.
Risk thresholdحد المخاطرةSeuil de risqueRisk eşiğiThe specific, defined condition that turns a milestone's status from on track to at risk.
Agent-monitored milestoneمرحلة تحت متابعة الوكيلJalon suivi par l'agentAcente tarafından izlenen kilometre taşıA milestone an agent checks on the factory's own behalf, on a schedule the buyer and agent agree in advance.
Hybrid accountحساب مختلطCompte hybrideHibrit hesapA buyer relationship that combines Make to Order and Make to Stock business with the same factory.
Shop-floor impactالأثر على أرضية المتجرImpact sur le point de venteMağaza rafına etkisiThe effect a factory-side delay will eventually have on a store's own floor-ready date if it is not caught early.
Advance noticeالإخطار المسبقPréavisErken bildirim süresiThe amount of time between an early flag being raised and the milestone's own original due date.
13Next

Lesson 3.5: Building a complete retail critical path tracker

Next you will bring every part of this course together into one complete retail critical-path tracker, combining MTO and MTS lines in a single working record. Back to the course map

14Ladder

RecognizeName the difference between an early flag and a report of an already-missed milestone.
ConnectSee how a risk threshold turns a partial fact into a decision to flag.
CompareSeparate the risk threshold an MTO line needs from the one an MTS line needs.
DecideJudge whether to raise a flag immediately or wait for more information.