A production count is a fact about output; when that count is taken decides how useful the fact is. Sara, the buyer at Northline Apparel, and Karim, the production manager at Delta Garments, both watch Order A's sewing line, but they are used to different pictures: Karim's floor gets a single total at the end of each shift, while a real-time tracking system would show the same line's output building up hour by hour, as it happens. This lesson teaches what that difference is actually worth, in reaction time, not just in how the numbers look on a page.
Without understanding the difference, a factory can treat real-time tracking as a nice-to-have screen rather than a tool that changes when a problem is caught. An end-of-shift count is accurate about the past shift, but it cannot tell anyone that a line stalled at hour two until the shift is already over, by which point the hours already lost cannot be recovered.
You need: no previous lesson in this course; general familiarity with how a sewing line records its own output is useful but not required.
By the end of this lesson you can:
Not covered here: how one operation's own output is actually recorded the moment it happens (lesson 26.1.2), reading a full real-time dashboard across several operations (lesson 26.1.3), and comparing real-time output against an operation's own target pace (lesson 26.1.4).
| Term | Meaning |
|---|---|
| Real-time tracking | Recording production output at the moment it happens, rather than totalling it once at a fixed point such as the end of a shift. |
| End-of-shift count | A production count taken only once, after a shift ends, that shows what happened during the shift but not when a problem inside it actually began. |
| Reaction time | The gap between the moment a production problem starts and the moment someone actually acts on it. |
| Target pace | The output rate, in pieces or bundles per hour, an operation should achieve, calculated from its own standard minute value (SMV). |
| Stalled line | A line whose output has stopped, or fallen well below its usual pace, for longer than a normal short stop explains. |
Two lines can finish a shift with the exact same total output and still have had very different days. One line ran steadily all day; the other stalled for three hours and then caught up. An end-of-shift count cannot tell these two days apart, because it only ever reports the final total. Real-time tracking reports the same total, but broken into the hours it actually built up in, which is the only way to see the stall while the shift is still running.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| Shift length and structure | A single 8-hour shift, or two shorter shifts back to back. | A longer shift leaves a bigger reaction-time gap if only an end-of-shift count is used, since more hours can pass before a stall is even visible. |
| Business model | An export Make to Order line like Order A's runs against one fixed deadline. A domestic Make to Stock floor runs against its own forecast, with more flexibility on exactly which day a batch finishes. | An MTO order close to its shipment date needs the earlier warning real-time tracking gives; an MTS batch with slack in its own schedule can sometimes tolerate an end-of-shift count. |
| Number of lines running at once | One line making one style, or several lines making several styles in parallel. | An end-of-shift count on several lines only tells a manager which line underperformed after the fact; real-time tracking lets a manager compare lines while the shift is still running. |
| How urgent the order's own timeline is | Early in Order A's 2-week sewing window, a short stall self-corrects. Close to the window's own end, the same stall needs same-day action. | The value of catching a stall early rises sharply as an order's own deadline gets closer. |
| Product family | A T-shirt line with a short operation sequence, or a more constructed garment with more operations. | More operations mean more places a stall can start, which raises the value of seeing output build up by the hour rather than waiting for one shift-end total. |
Order A's sewing line reports output once, at the end of each 8-hour shift. On production day 6, the line stalled for three hours in the middle of the shift because of a machine fault at sleeve attach, then ran extra hours of overtime to catch up. The end-of-shift count that reached Sara the next morning showed the day's full target of 1,500 pieces met, with no mention of the three-hour stall or the overtime it caused.
Sara only learned about the stall when Karim mentioned it in a separate phone call, days later, while explaining why overtime costs had been higher that week than usual. The end-of-shift count was accurate about the total, but it never showed her the stall itself, because a single end-of-shift total has no way to show what happened inside the shift.
The worked numberThe 1,125-piece figure is Delta Garments' own illustrative example of what a 6-hour reaction-time gap represents at Order A's own target pace; it is not a fixed cost, since the line made up some of the lost output through overtime, but it shows how large a gap an end-of-shift count alone can leave open before anyone even knows there was a problem to react to.
A common mistake is reading a shift's final total as evidence the whole shift ran smoothly, simply because the number met target. An end-of-shift count that meets target can still hide a multi-hour stall covered by overtime, as Order A's day 6 shows; the cost of that stall, in overtime pay and in a reaction-time gap that could have been shorter, never appears in the final total at all.
A count taken once, at the end of the day, tells you how much was made, but not when it was actually made. Two days can end with the exact same total even though one ran smoothly all day and the other stopped for hours in the middle and then rushed to catch up. Checking output as it happens, hour by hour instead of once at the end, is the only way to notice a stop while it is still happening, instead of hearing about it afterwards when the hours already lost cannot be brought back. The total does not change; how soon someone can act on a problem does.
Order A's line has run on an end-of-shift count since the order started. Karim has offered to move the line onto real-time tracking for the rest of the order, at no extra cost, since Delta Garments already tracks two other lines this way.
Should Sara ask Karim to keep the end-of-shift count, since Order A has always met its daily total, or move the line onto real-time tracking for its final days? Decide before opening the answer.
Sara should ask Karim to move Order A's line onto real-time tracking for its final days, not keep the end-of-shift count simply because the order has always met its daily total.
1. A met daily total does not prove a stall did not happen, as day 6 already showed; it only proves the shift's final number reached target, however it got there. 2. The order's remaining 4 days leave less slack to absorb a repeat stall than the days already completed did, so a shorter reaction-time gap is worth more now than it was earlier in the order. 3. Moving to real-time tracking costs nothing extra, since Delta Garments already runs it on other lines, so there is no real reason to keep the wider reaction-time gap for the order's final, most time-sensitive days.
Sara does not need to see another stall happen before deciding; the reaction-time gap an end-of-shift count leaves open is the same risk whether or not a stall has occurred yet.
Order A's own timeline allows 2 weeks for sewing within its 16-week schedule (docs/02 section 7). With only 4 working days left, a repeat of day 6's roughly 1,125-piece reaction-time gap, if it went unseen until the next morning's end-of-shift count, would leave far less time to recover than it did earlier in the order.
The figure here is framed against the sewing window's own remaining length rather than a fixed cost from the master order data, since no per-stall cost is fixed for Order A; it shows why the value of a shorter reaction-time gap rises as an order's own deadline gets closer, not why real-time tracking has one fixed price.
Open the real-time production tracking tracker, "Shift output comparison" sheet. Enter a line's daily target and shift length; the sheet calculates its own target pace per hour, and lets you record when a stall started and when it was actually caught, to see the reaction-time gap for yourself. Start with Order A's day 6 figures above, then compare one shift of your own.
[Download the real-time production tracking tracker workbook](../../templates/T26-C01-real-time-production-tracking-tracker.xlsx)
1. What is the main difference between real-time tracking and an end-of-shift count, for the same shift's total output?
2. On Order A's day 6, the line stalled at hour 2 of an 8-hour shift and this was reported only at shift end. What was the reaction-time gap, and roughly how many pieces did it represent at target pace?
3. Why does an end-of-shift total that meets target not prove a shift ran without a stall?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Real-time tracking | التتبع الفوري | Suivi en temps réel | Gerçek zamanlı takip | Recording production output at the moment it happens, rather than totalling it once at a fixed point such as the end of a shift. |
| End-of-shift count | عدّ نهاية الوردية | Comptage de fin de poste | Vardiya sonu sayımı | A production count taken only once, after a shift ends, that shows what happened during the shift but not when a problem inside it actually began. |
| Reaction time | زمن الاستجابة | Temps de réaction | Tepki süresi | The gap between the moment a production problem starts and the moment someone actually acts on it. |
| Target pace | الوتيرة المستهدفة | Cadence cible | Hedef tempo | The output rate, in pieces or bundles per hour, an operation should achieve, calculated from its own standard minute value (SMV). |
| Stalled line | خط متوقف | Ligne à l'arrêt | Duran hat | A line whose output has stopped, or fallen well below its usual pace, for longer than a normal short stop explains. |
Next you will learn how to record one operation's own completed output the moment it happens, the single building block a real-time tracking system is actually made of. Back to the course map