A real-time tracking system is only as fast as the entries feeding it. Mona, the merchandiser who checks in on Delta Garments' sewing floor, learned this the hard way: a dashboard built on entries logged in batches, hours after the work happened, is not really real-time at all, whatever the screen calls itself. This lesson teaches how an output entry is actually recorded, bundle by bundle, at the moment a bundle finishes, rather than in a lump sum added later.
Without recording output the moment it happens, a factory can install a real-time system and still keep an end-of-shift reaction-time gap, because the delay simply moves from the report to the entry itself. An operator or supervisor who waits until a convenient break to log three hours of completions has recreated the same problem lesson 26.1.1 described, just one step further down the process.
You need: lesson 26.1.1's reaction-time gap (the delay between a problem starting and someone acting on it) is useful background but not required.
By the end of this lesson you can:
Not covered here: what real-time tracking adds over an end-of-shift count in general (lesson 26.1.1), reading a full dashboard across several operations (lesson 26.1.3), and comparing real-time output against a target pace (lesson 26.1.4).
| Term | Meaning |
|---|---|
| Output entry | A single record of the quantity completed at one operation at one specific moment, the smallest building block a real-time tracking system is made of. |
| Batch entry | An entry that records several completions covering a stretch of time all at once, logged after the fact rather than at the moment each one happened. |
| Cumulative output | The running total of pieces or bundles completed at an operation, added up from the start of the shift to the current moment. |
| Bundle system | Cut pieces grouped into a fixed-quantity bundle that travels together from operation to operation through the sewing line, so progress can be counted bundle by bundle. |
| Entry lag | The time between a unit of work actually finishing and its output entry being logged into the tracking system. |
A dashboard can refresh every second and still show hours-old information, if the entries feeding it were logged in a batch rather than at the moment each completion happened. Entry lag, not dashboard refresh speed, is what actually determines how current a real-time system's picture is; a system fed by output entries logged the instant a bundle finishes has almost no entry lag, while one fed by a batch entry every few hours carries the same reaction-time gap an end-of-shift count would.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| Recording unit | An entry per single piece, per bundle of a fixed quantity, or per hour block of pieces. | A bundle-level entry, as Order A uses, is fine-grained enough to catch a stall within about one bundle's own production time; an hour-level entry cannot catch anything faster than an hour. |
| Recording tool | A paper tally sheet updated by hand, a shared spreadsheet, or a scanner reading a bundle ticket. | A manual tool depends entirely on the operator's own habit of logging immediately; a scanner removes that dependency by logging automatically as a bundle physically passes a point. |
| Business model | An export Make to Order line like Order A's has one fixed deadline pressing on every entry's own timeliness. A domestic Make to Stock floor can tolerate a slightly longer entry lag on a batch with slack in its own schedule. | The value of a near-zero entry lag rises on an order with less remaining slack, the same pattern lesson 26.1.1 showed for reaction time overall. |
| Number of operations feeding the system | A short operation sequence like Order A's T-shirt, or a long sequence on a more constructed garment. | More operations mean more entries to keep current; a single supervisor manually logging many operations is more likely to fall into batching entries out of simple time pressure. |
| Shift structure | A steady single shift, or a shift split by a long lunch break. | A long break is exactly when a habit of batching entries tends to form, since the operator or supervisor waits for a natural pause to log several completions at once. |
On Order A's line, sleeve attach is meant to log an output entry each time a bundle of 60 pieces finishes. Checking the tracking system's own timestamps, Mona finds the supervisor has instead been waiting until three bundles finish, then logging all three entries at once, to save the short walk to the recording station each time.
This batching did not change the sleeve attach operation's own total output for the day, but it meant the tracking system's picture of sleeve attach was, on average, lagging behind the real floor by close to the time it takes to finish one and a half bundles, even though the system itself displayed as fully real-time.
The worked numberBatching three bundles into a single entry nearly triples the tracking system's own average entry lag, from roughly 10 minutes to roughly 29 minutes. Both figures are Delta Garments' own illustrative examples built on Order A's target pace; neither is a fixed cost, but the comparison shows how a recording habit, not the tracking system's software, actually sets how current the picture stays.
A common mistake is treating the purchase or installation of a real-time tracking system as the end of the work, assuming its own live-looking dashboard proves entries are current. As Order A's sleeve attach shows, a person can quietly revert to batching entries out of simple convenience, and the system will display the batched numbers exactly as confidently as it would display instant ones, with no warning that its own picture has gone stale.
The single most important habit behind any real-time system is logging each piece of finished work the moment it actually finishes, not later when it is more convenient. A screen that updates instantly still shows old information if the person feeding it waits an hour, or three bundles, before typing anything in. Checking every so often how the entries are actually being logged, not just how the screen looks, is the only way to know whether a system is really working in real time or only appears to.
Mona has confirmed sleeve attach's supervisor has been batching three bundles into one entry, adding roughly 19 extra minutes of average entry lag compared with logging each bundle.
Should Mona request a scanner immediately, or first ask the supervisor to log each bundle as it finishes and recheck the timestamps in a week? Decide before opening the answer.
Mona should first ask the supervisor to log each bundle as it finishes and recheck the timestamps in a week, not request a scanner immediately.
1. The supervisor confirmed the batching was a convenience habit, not a tool limitation, so a habit change may close most of the entry-lag gap without any new equipment. 2. A scanner has a real cost not yet approved for this line, while a habit change costs nothing and can be checked within a week using the same timestamps Mona already reviewed. 3. Rechecking the timestamps after the request confirms whether the habit actually changed, giving Mona real evidence before asking Delta Garments to approve spending on a scanner.
Mona does not need to solve every operation's entry lag with new equipment before confirming a simple habit change is not enough.
Order A's line processes roughly 3.125 bundles per hour at target pace (docs/02 section 7 derivation shown above). An extra 19 minutes of average entry lag per bundle, if it applied to every bundle logged in a day, would mean the tracking system's own picture ran meaningfully behind the real floor for a large share of the shift, not just for the specific bundles caught in a batch.
The 475-minute figure is Delta Garments' own illustrative example of what a consistent batching habit would cost across a full day if left unaddressed; it is not a fixed cost, since Mona caught the habit before it became consistent, but it shows why a small per-bundle lag is worth correcting early rather than after it becomes routine.
Open the real-time production tracking tracker, "Output entry log" sheet. Enter each bundle's own completion time and the time its entry was actually logged; the sheet calculates the entry lag and flags any pattern of batching. Start with sleeve attach's own figures above, then log one operation of your own.
[Download the real-time production tracking tracker workbook](../../templates/T26-C01-real-time-production-tracking-tracker.xlsx)
1. What is an output entry, as this lesson defines it?
2. Why can a real-time tracking system still carry a meaningful reaction-time gap even with a live-looking dashboard?
3. Sleeve attach's supervisor batched three bundles into one entry instead of logging each bundle at roughly 19.2 minutes apart. What effect did this have on average entry lag?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Output entry | إدخال الناتج | Saisie de production | Çıktı kaydı | A single record of the quantity completed at one operation at one specific moment, the smallest building block a real-time tracking system is made of. |
| Batch entry | الإدخال الدفعي | Saisie groupée | Toplu kayıt | An entry that records several completions covering a stretch of time all at once, logged after the fact rather than at the moment each one happened. |
| Cumulative output | الناتج التراكمي | Production cumulée | Kümülatif çıktı | The running total of pieces or bundles completed at an operation, added up from the start of the shift to the current moment. |
| Bundle system | نظام الحزم | Système de liasses | Demet sistemi | Cut pieces grouped into a fixed-quantity bundle that travels together from operation to operation through the sewing line, so progress can be counted bundle by bundle. |
| Entry lag | تأخر الإدخال | Décalage de saisie | Kayıt gecikmesi | The time between a unit of work actually finishing and its output entry being logged into the tracking system. |
Next you will learn how to read a full real-time dashboard across several operations at once, using the output entries this lesson teaches you to record as its raw material. Back to the course map