A single bundle's status tells you about that one bundle. A full WIP report, listing every bundle at every operation, tells you about the order as a whole, and reading it correctly is a different skill from checking one bundle. Karim, the production manager at Delta Garments, runs this report daily on Order A's line to answer one question: which operation, across all 250 bundles, is the order's real constraint today.
Without reading the full report, a manager can fix the wrong operation, moving an extra operator to a station that only looks busy, while the operation actually piling up bundles sits untouched. This lesson teaches how to read the report's own totals per operation, not just one bundle's row, to find where an order is genuinely stuck.
You need: lesson 24.3.1's bundle location log (recording where one bundle physically sits) as background is useful but not required.
By the end of this lesson you can:
Not covered here: logging one bundle's physical location (lesson 24.3.1), moving completed bundles into the finished goods store (lesson 24.3.3), and reconciling finished goods against a shipment (lesson 24.3.4).
| Term | Meaning |
|---|---|
| Work-in-progress (WIP) | Garments that have entered the sewing line but are not yet fully sewn, sitting at some operation between cutting and final finishing. |
| 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. |
| Bottleneck | The one stage in a production flow whose limited output slows down every stage after it, even when every other stage has spare capacity. |
| WIP report | A single report listing every bundle's quantity issued, quantity completed and quantity remaining at every operation on a line, read together rather than bundle by bundle. |
| Waiting-bundle count | The number of bundles sitting unfinished in front of a single operation at one point in time, used to rank operations against each other. |
A WIP report becomes useful only when its rows are compared across operations, not read one at a time. Summing the bundles waiting at each operation, across all 250 bundles on Order A's line, turns dozens of individual rows into a handful of operation-level totals, and the operation with the largest total, relative to its own normal pace, is the order's real constraint.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| Number of operations on the style | Order A's T-shirt has a shorter operation sequence than a more constructed garment, so its WIP report has fewer rows per bundle to sum. | Fewer operations make the report faster to scan, but the same ranking method applies regardless of how many rows exist. |
| How bundles are released to the line | Bundles can be released steadily through the day, or in a single large batch each morning. | A large morning batch makes early-operation waiting counts look high for a few hours by design, not because of a real bottleneck; timing matters when reading the report. |
| Business model | An export Make to Order line like Order A's runs one report against one fixed 250-bundle order. A domestic Make to Stock floor runs several smaller orders through the same operations at once, so the report must be read style by style, not just operation by operation. | Mixing styles on one floor without separating the report by style can make an operation look like a constraint on Order A when the real pile-up is another order's bundles. |
| How completion is recorded | Some lines record completion after every operation; others batch the entries and update the report only at shift end. | A report updated only at shift end always shows a WIP picture that is hours old, which matters when deciding whether to act immediately. |
| Urgency in the order's timeline | Early in Order A's 16-week timeline, a moderate waiting-bundle count at one operation is normal and self-corrects. Closer to the 2-week sewing window's own end, the same count needs action the same day it appears. | The same report reading calls for a different response depending on how much slack remains before the order's own shipment date. |
On production day 9 of Order A's sewing window, Karim pulls the full WIP report across all 250 bundles. Rather than checking one bundle, he sums each operation's own waiting-bundle count for the day.
| Operation | Bundles issued | Bundles completed | Bundles waiting |
|---|---|---|---|
| Shoulder join | 250 | 246 | 4 |
| Sleeve attach | 250 | 210 | 40 |
| Neck rib attach | 250 | 232 | 18 |
| Side seam and hem | 250 | 220 | 30 |
Reading the four operation totals side by side, sleeve attach shows 40 bundles waiting, clearly larger than neck rib attach's 18 and side seam and hem's 30. A supervisor who only checked a single bundle at neck rib attach earlier that morning, where a small queue happened to be visible, could easily have assumed neck rib attach was the problem operation.
The worked numberSleeve attach alone accounts for 44% of every bundle currently waiting anywhere on Order A's line, nearly double side seam and hem's share and more than double neck rib attach's. That single comparison, not a walk past one operation, is what tells Karim where to act first.
A single bundle queued at one operation is easy to notice while walking the floor, and easy to mistake for the whole order's problem. The report's own totals across all 250 bundles are the only reliable way to confirm which operation is really carrying the largest share of the order's delay; a visible queue at one station can be smaller, in total, than a less visible queue spread across many bundles at another operation.
Checking one bundle tells you about that one bundle. Adding up how many bundles are waiting at each step, across the whole order, tells you which step is really holding everything back. A queue you can see with your own eyes at one station does not automatically mean that station is the problem; another step, with bundles waiting less visibly across many different rows, can be carrying a much bigger share of the delay. The only way to know for sure is to add up every step's own waiting count and compare them side by side, not to trust whichever queue happens to catch your eye first.
Order A's WIP report on day 9 shows sleeve attach with 40 bundles waiting, the largest share of the line's 92 total waiting bundles.
Should Karim move the spare operator to neck rib attach, the queue he saw first while walking the floor, or to sleeve attach, the operation the report's own totals rank highest? Decide before opening the answer.
Karim should move the spare operator to sleeve attach, the operation the WIP report's own totals rank highest, not to neck rib attach simply because its queue was the one he noticed first.
1. Sleeve attach's 40 waiting bundles are the largest total on the line, well above neck rib attach's 18, so it is carrying the biggest share of today's delay. 2. A queue's visibility while walking the floor does not measure its size relative to the rest of the line; neck rib attach's queue happened to sit near the entrance, not because it was the largest. 3. Reinforcing the operation the report ranks highest addresses the largest share of the delay with the one spare operator available, rather than spending that resource on a smaller, more visible problem.
Karim does not need to check every bundle individually before deciding; the report's own operation-level totals already rank sleeve attach as today's real constraint.
Order A's own timeline allows 2 weeks for sewing within its 16-week schedule (docs/02 section 7). If Karim reinforces neck rib attach instead of sleeve attach, sleeve attach's 40-bundle queue continues to grow while the wrongly reinforced operation, already at 18 bundles and clearing normally, gains little benefit.
The figure here is framed against the sewing window's own length rather than a fixed cost from the master order data, since no per-day delay cost is fixed for Order A; it shows why reading the report's totals correctly, rather than acting on the most visible queue, protects the time already built into the schedule.
Open the WIP and finished goods tracker, "WIP report by operation" sheet. For each operation, enter the bundles issued and bundles completed across the whole order; the sheet calculates each operation's waiting-bundle count and its share of the line's total waiting bundles. Start with Order A's day-9 figures above, then rank one operation set of your own.
[Download the WIP and finished goods tracker workbook](../../templates/T24-C03-wip-finished-goods-tracker.xlsx)
1. What does a full WIP report show that a single bundle's row cannot?
2. Order A's day-9 report shows sleeve attach with 40 bundles waiting and neck rib attach with 18. Which operation is the real constraint, and why?
3. Why might reinforcing neck rib attach instead of sleeve attach make Order A's overall delay worse, not better?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Work-in-progress (WIP) | أعمال قيد التشغيل (WIP) | Encours de production (WIP) | Ara stok (WIP) | Garments that have entered the sewing line but are not yet fully sewn, sitting at some operation between cutting and final finishing. |
| 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. |
| Bottleneck | عنق الزجاجة | Goulot d'étranglement | Darboğaz | The one stage in a production flow whose limited output slows down every stage after it, even when every other stage has spare capacity. |
| WIP report | تقرير الأعمال قيد التشغيل | Rapport d'encours | Ara stok raporu | A single report listing every bundle's quantity issued, quantity completed and quantity remaining at every operation on a line, read together rather than bundle by bundle. |
| Waiting-bundle count | عدد الحزم المنتظرة | Nombre de liasses en attente | Bekleyen demet sayısı | The number of bundles sitting unfinished in front of a single operation at one point in time, used to rank operations against each other. |
Next you will learn how a completed bundle is checked, counted and formally handed from the sewing floor into the finished goods store, so a piece is never lost in the gap between the two. Back to the course map