A buyer's team reviews supplier reports every week. Some of those reports show whether the shipment eventually left on time. Others show whether the materials needed to make that shipment are on track, weeks before the ship date arrives. Both numbers matter, but they do very different jobs. One tells you a problem already happened. The other tells you a problem might be about to happen, while you can still do something about it.
This lesson mainly teaches the decision flow on the buyer's own side: which KPI gives Sara, the buyer at Northline Apparel, an early warning she can act on, and which KPI only tells her, after the fact, that the warning would have been useful. Confusing the two is one of the most common reasons a company discovers a late shipment only when it is already too late to fix.
You need: the KPI-definition rule from Lesson 4.1: a KPI names a decision, a decision owner and a trigger value. You also need a basic understanding of a production timeline.
By the end of this lesson you can:
Not covered here: how to verify that the data behind a KPI is itself correct; that is covered in Lesson 4.3. This lesson assumes the numbers reported are accurate and focuses only on timing.
| Term | Meaning |
|---|---|
| Leading KPI | A measure taken early enough in a process that acting on it can still change the final result. |
| Lagging KPI | A measure that only confirms a result after the process it describes has already finished. |
| Early warning | A signal that a plan is at risk, given while there is still time to respond. |
| Milestone check | A planned point partway through a timeline where progress is compared against the plan. |
| Contingency plan | A prepared alternative action, ready to use if a leading KPI shows the main plan is at risk. |
| Confirmed result | A fact that is now certain and can no longer be changed by any action. |
The same underlying process, such as an order moving from fabric to shipment, can be measured at different points. A measurement taken partway through, while corrective action is still possible, is a leading KPI. A measurement taken once the process is finished, such as whether the shipment sailed on time, is a lagging KPI. Both are legitimate and both belong on a report, but only one of them can still change what happens on this order.
| What can differ | The shapes you will meet | Why it matters to you |
|---|---|---|
| Export, made-to-order production | A fabric-receipt or cumulative-sewing check (leading) is paired with the final on-time-shipment result (lagging). | The leading KPI is only useful if it is checked with enough days left in the timeline to still act. |
| Domestic, made-to-stock replenishment | A stock-cover check partway through a selling period (leading) is paired with an eventual stock-out event (lagging). | The stock-out is the lagging KPI a business is trying to avoid by watching the leading one early. |
| Buyer or brand side | The buyer's own early visibility, such as a fabric-receipt confirmation from the factory, is a leading KPI the buyer does not create but can still watch. | Because the buyer does not control the factory floor, its leading KPI has to trigger a conversation or a contingency plan, not a direct instruction. |
| Mixed export and domestic portfolio | A manager compares several orders' leading KPIs side by side to decide where limited attention should go this week. | A leading KPI on one order can be at a completely different stage than a leading KPI on another, so each is read against its own timeline. |
| Different product families | Socks and hosiery use a mid-run linking-output check as a leading KPI for the final packed-quantity result; bedding sets use a mid-run cut-and-sew completion check for the final on-time-shipment result. | The measured activity changes with the product, but the same leading-versus-lagging pairing applies. |
Order A's 16-week timeline runs: approvals 2 weeks, fabric 5 weeks, sewing 2 weeks, inspection/packing/documents 1 week, shipping 4 weeks, warehouse and distribution 2 weeks. The vessel sails on day 16 of the shipping stage. Sara does not sit at Delta Garments and cannot see the sewing line directly, but she still needs to know, well before day 16, whether the shipment is at risk.
Sara agrees a leading KPI with Mona, the merchandiser: fabric receipt confirmed by the end of week 7 (2 weeks approvals + 5 weeks fabric), the point where fabric procurement is supposed to finish and sewing is supposed to begin. If Mona confirms fabric receipt by week 7, Sara has good reason to expect the rest of the timeline to hold. If fabric receipt is not confirmed by week 7, Sara still has 9 weeks left before the vessel sails, enough time to discuss a contingency with Delta Garments. The lagging KPI, whether the order actually shipped by day 16, only confirms the result Sara was trying to manage in advance.
The worked numberOrder A's timeline gives an exact number of weeks each KPI leaves for action:
Nine weeks is enough time for Sara to raise a fabric delay with Delta Garments, discuss a recovery plan for the two-week sewing window, or, in a worst case, plan an alternative shipping method well ahead of the cut-off. Zero weeks means the lagging KPI can only be used to record what happened, assign responsibility for it afterwards, or adjust expectations for a future order; it cannot change the outcome of this shipment.
A common mistake is presenting an on-time-shipment percentage as though watching it more closely will improve this order's outcome. By the time that number exists, the order has already sailed or already missed its date; the number cannot change either fact. The lagging KPI is genuinely useful, but its job is to improve future orders, confirm accountability, and check whether the leading KPIs used during the order were trustworthy, not to manage the order that already finished.
The better habit is to ask, for every lagging KPI on a report, "what leading KPI, checked earlier in this same timeline, would have given a chance to change this result?"
Some numbers tell you about a problem while you can still fix it. Other numbers only tell you about a problem after it is already too late to fix. A number checked partway through a job, while there is still time to act, is a leading indicator. A number checked only once the job is finished is a lagging indicator. Both are useful, but for different reasons: the leading number can still change what happens, and the lagging number can only tell you, afterwards, whether the leading number was worth trusting.
Order A has reached the end of week 7. Delta Garments reports that only 70% of the approved fabric has been received; the remaining 30% is delayed at Rowad Knits, the knitting mill. Nine weeks remain before the vessel sails on day 16. Sara has not yet raised the delay with Delta Garments.
Should Sara treat this week-7 update as a leading KPI and act on it now, or wait for the on-time-shipment result to know whether there is a real problem? Decide before opening the answer.
Sara should treat the week-7 fabric update as the leading KPI it is, and raise the delay with Delta Garments immediately rather than waiting for the shipment result.
1. The checkpoint is at week 7 of 16, leaving 9 weeks to act. This is exactly the leading-KPI window Sara and Mona agreed on, and it still has time left in it. 2. A 30% fabric shortfall at this checkpoint is a real early warning, not a rounding error; it threatens the two-week sewing window that has not yet begun. 3. Waiting for the on-time-shipment result would remove Sara's only chance to influence the outcome. By day 16, the shipment has either sailed or it has not, and nothing Sara does at that point can change which one happened. 4. Raising the delay now lets Delta Garments and Rowad Knits discuss a recovery plan, such as prioritising the remaining fabric or adjusting the sewing schedule, while 9 weeks of the timeline are still unused.
The lagging KPI, the eventual on-time-shipment result, will still be reported at the end. But by then it can only confirm whether Sara's early action on the leading KPI worked.
Order A's total FOB value is fixed:
If Sara acts on the week-7 leading KPI, the cost of the conversation and any resulting schedule adjustment is close to zero in direct terms; it is a coordination cost, not a cash cost. If Sara instead waits for the lagging KPI and only learns about the problem once the vessel has already missed day 16, Order A moves into the same fallback economics already fixed for this order: overtime at USD 0.15 per piece (USD 2,250 for the whole order) if there is still time to recover through the factory's own effort, or air freight at USD 1.80 per piece (USD 27,000 for the whole order) if there is not. Watching the leading KPI does not guarantee a perfect outcome, but it is the only point at which the cheaper options are still on the table.
Use the T17-C04 KPI and decision-data workbook. For each lagging KPI you already track, record the leading KPI that could warn about the same result earlier, the checkpoint in the timeline where it should be measured, and how many days or weeks of action time that checkpoint leaves. Start with Order A's fabric-receipt and on-time-shipment pair, then repeat the exercise for one pair already used in your own workplace.
[Download the KPI and decision-data workbook](../../templates/T17-C04-kpi-and-decision-data-workbook.xlsx)
1. What makes a KPI leading rather than lagging?
2. Why does Sara still need a leading KPI on Order A even without controlling Delta Garments' factory floor?
3. A domestic replenishment program, using 12,000 pieces of stock, checks stock cover every 4 weeks during a 12-week selling period; a stock-out is confirmed only once it happens. Which statement separates the two KPIs correctly?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Leading KPI | مؤشر قائد | Indicateur avancé | Öncü KPI | A measure taken early enough in a process that acting on it can still change the final result. |
| Lagging KPI | مؤشر تابع | Indicateur retardé | Gecikmeli KPI | A measure that only confirms a result after the process it describes has already finished. |
| Early warning | إنذار مبكر | Alerte précoce | Erken uyarı | A signal that a plan is at risk, given while there is still time to respond. |
| Milestone check | نقطة تفتيش مرحلية | Contrôle jalon | Kilometre taşı kontrolü | A planned point partway through a timeline where progress is compared against the plan. |
| Contingency plan | خطة بديلة | Plan de contingence | Acil durum planı | A prepared alternative action, ready to use if a leading KPI shows the main plan is at risk. |
| Confirmed result | نتيجة مؤكدة | Résultat confirmé | Onaylanmış sonuç | A fact that is now certain and can no longer be changed by any action. |
Next you will learn how to check whether a dashboard number is built from correct, current data before you use it to make a decision. Back to the course map