A linked digital workflow, built in Lessons 1 and 2, already shows every milestone's owner, due date, status and downstream effect. On a single export order, a merchandiser can still open it once a day and scan seven or eight rows by eye. On a domestic Make to Stock programme running several reorder cycles at once for a brand such as Cedar & Co., that manual scan stops being realistic: there are simply too many task records for one person to check individually every day. Alert and escalation rules solve this by defining, in advance, exactly which condition on a task record should raise an alert, and which condition should escalate it to a manager, so the workflow itself does the watching. This is chiefly a decision-flow skill: deciding in advance what counts as a genuine exception, so a merchandiser's attention goes to real problems instead of every task.
Without these rules, a merchandiser either checks everything, which does not scale past a handful of orders, or checks nothing until a buyer or shop complains, which is worse.
You need: Lessons 1 and 2 of this course, which build the digital workflow's owner, due-date, status and linked-milestone fields.
By the end of this lesson you can:
Not covered here: combining approvals, materials, production and shipment updates in one workflow (Lesson 4), and building the complete tracker for a live order (Lesson 5).
| Term | Meaning |
|---|---|
| Alert | An automatic flag raised by the digital workflow when a task record meets a defined risk condition. |
| Escalation rule | A rule that sends a specific kind of alert straight to a named manager instead of leaving it in a merchandiser's own queue. |
| Exception | A task record that no longer matches its expected on-track status and therefore needs a human decision. |
| Replenishment cycle | One repeating round of Make to Stock production, run against a forecast rather than a single confirmed order. |
| Stock cover | The number of weeks a brand's current stock is expected to last before it runs out, given its normal sales rate. |
| Due date | The date a milestone must be completed for the rest of the critical path to hold. |
An alert rule is a plain condition written against a task record's own fields: for example, "if a milestone's due date has passed and its status is not complete, raise an alert." An escalation rule then decides where that alert goes: some alerts can wait in the merchandiser's own queue for the next routine check, while others, because of what they risk, go straight to a manager the moment they are raised. Together, these rules let a digital workflow manage many task records without requiring a person to read every one of them every day.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| MTO export order vs. MTS domestic programme | A single MTO export order, such as Order B's jeans, has few enough task records for routine alerts alone; a domestic MTS programme running several reorder cycles at once needs escalation rules to filter which of many alerts truly need a manager. | Without escalation rules, an MTS programme's merchandiser drowns in alerts from cycles that are only mildly behind, missing the one cycle at real risk of a stock-out. |
| A milestone close to the ship date vs. one with weeks of slack | A milestone approaching its due date with no slack left, such as ex-factory a few days out, deserves immediate escalation if it slips; a milestone with several weeks of slack before it affects anything can sit in a routine alert queue. | Escalating every slipped milestone equally buries a genuinely urgent one under routine ones that will resolve themselves. |
| Stock cover above vs. below a set threshold | A domestic brand's stock cover comfortably above its reorder threshold generates no alert; stock cover approaching or below the threshold should raise an alert automatically, before shelves actually run empty. | Waiting for a shop to report an empty shelf, rather than alerting on stock cover, turns a preventable gap into a lost sale. |
| Who owns the escalation | A factory-side escalation for a domestic MTS programme typically goes to the factory's own production manager; an export order's most severe escalations may need to reach the buyer's own office as well. | Escalating only inside the factory when a buyer genuinely needs to know leaves the buyer unable to plan around a risk that affects them directly. |
| Socks, terry and home-textile product families | A hosiery or bedding replenishment programme uses the same alert-and-escalation logic, with that family's own risk thresholds, such as a shorter reorder lead time for a fast-moving sock style. | The logic of defining a condition and an escalation path does not change by product family; only the thresholds do. |
Cedar & Co., the domestic brand with 12 shops, runs a Make to Stock reorder programme with Delta Garments for a denim style built on Order B's own five-pocket, 12 oz denim construction, sold to Cedar & Co. on 60-day open account. This programme is illustrative: Cedar & Co. has no order figures fixed elsewhere in the academy's master cast, so this lesson uses a clearly labelled illustrative batch size of 1,000 pieces per reorder cycle, run on a 4-week production cycle against Cedar & Co.'s own sales forecast.
Because several reorder cycles can be in progress at once, Mona does not want to check every task record by hand each morning. She sets an alert rule: any milestone whose due date has passed with a status other than complete raises an alert. She sets an escalation rule on top of it: an alert on a milestone within one week of that cycle's own planned delivery date goes straight to Karim, the production manager, instead of waiting in her own routine queue.
The worked numberWithout the escalation rule, all four overdue milestones would look equally urgent on the page. With it, the workflow itself separates the one cycle genuinely close to missing its delivery date from three cycles that still have enough slack to recover through normal follow-up.
A common mistake is writing an alert rule but skipping the escalation threshold, so every overdue milestone, regardless of how much slack remains, reaches Karim's queue immediately. At first this feels safer, but a manager who receives ten escalations a day, most of which resolve themselves within the existing slack, quickly starts skimming or ignoring the queue altogether. When a real, urgent exception then arrives, it is treated with the same low attention as the routine noise around it. A workflow that escalates everything protects nothing.
A digital workflow with many task records cannot rely on a person checking every row every day; there are simply too many. Alert and escalation rules solve this by having the tool itself decide, using a simple condition, when something needs attention, and how urgently. A milestone that is a little behind but still has time to recover can wait in a routine queue. A milestone close to a real delivery or ship date, with no time left, should reach a manager immediately. Setting these rules in advance, and reviewing them against what actually happens, is what lets one merchandiser manage many reorder cycles without either drowning in alerts or missing a genuine risk.
A fifth reorder cycle for Cedar & Co.'s jeans style has a fabric-booking milestone that is now three days overdue. The cycle's planned delivery date to Cedar & Co. is five weeks away.
The relevant line from the workflow's own alert log:
Should this alert escalate to Karim today, or wait for Mona's next routine review? Decide before you open the decision.
It should wait for Mona's next routine review, due within two working days, rather than escalate to Karim immediately.
The two facts that decide this are the escalation rule's own one-week threshold, which this alert sits far outside, and the workflow's own record that no downstream milestone has yet moved into an at-risk status because of this delay. Escalating a five-week-out delay to Karim today would train him to expect low-urgency escalations, weakening his response the next time a genuinely urgent one arrives. Mona reviews it at her next routine check, well before the one-week escalation threshold could ever be reached, and confirms fabric booking has been recovered before it becomes a real risk to the delivery date.
The illustrative reorder cycle's own value, at Order B's own jeans per-piece price applied to this batch, gives a sense of scale:
If the escalation threshold were set too loose, at four weeks instead of one, Cycle 3's genuinely urgent packing delay above would have escalated to Karim a full three weeks earlier than needed, alongside every other mildly late milestone across four active cycles, most of which would have resolved on their own. If the threshold were set too tight, at only one day, a real risk to the roughly USD 9,800 cycle above could sit unescalated until delivery is only hours away, with no time left to recover. Setting the threshold at a point that matches how much slack a stage genuinely has left is what keeps escalation useful rather than either noisy or too late.
Use the T17-C03 Digital critical-path tracker. Add an alert condition column and an escalation threshold column for the replenishment programme's task records, and record which named manager each escalated alert reaches. Review the thresholds after each reorder cycle closes, adjusting them if real outcomes show they are too loose or too tight.
[Download the Digital critical-path tracker](../../templates/T17-C03-digital-critical-path-tracker.xlsx)
1. What is the difference between an alert rule and an escalation rule in a digital workflow?
2. A domestic MTS programme has four active reorder cycles with overdue milestones today. Only one is within its escalation rule's one-week delivery threshold. What should the workflow do?
3. A different domestic bedding replenishment programme sets its escalation threshold at four weeks before delivery, four times looser than the jeans programme's one-week threshold. What is the likely result?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Alert | تنبيه | Alerte | Uyarı | An automatic flag raised by the digital workflow when a task record meets a defined risk condition. |
| Escalation rule | قاعدة تصعيد | Règle d'escalade | Yükseltme kuralı | A rule that sends a specific kind of alert straight to a named manager instead of leaving it in a merchandiser's own queue. |
| Exception | استثناء | Exception | İstisna | A task record that no longer matches its expected on-track status and therefore needs a human decision. |
| Replenishment cycle | دورة تجديد المخزون | Cycle de réassort | Yeniden stoklama döngüsü | One repeating round of Make to Stock production, run against a forecast rather than a single confirmed order. |
| Stock cover | تغطية المخزون | Couverture de stock | Stok kapsama süresi | The number of weeks a brand's current stock is expected to last before it runs out, given its normal sales rate. |
| Due date | تاريخ الاستحقاق | Date d'échéance | Vade tarihi | The date a milestone must be completed for the rest of the critical path to hold. |
Next you will learn how to keep approvals, materials, production and shipment updates inside one connected workflow instead of four separate trackers that never quite agree with each other. Back to the course map