WIP Tracking for Garment Factories — How to Monitor Work-in-Progress in Real Time

You have got 200 operators on three sewing lines. It is 2 PM and you have no idea how many pieces are sitting between your overlock and single-needle stations. You will not know until your supervisors count at end of day. By then, Line 2 has been bottlenecked for four hours and you have lost 300 pieces of output.

I have watched this exact scenario play out in factories across Nepal. The production manager looks at output numbers at 5 PM, realizes they are 20% short, and blames the operators. But the operators were not the problem. A single flatlock machine went down at 10 AM, and nobody redistributed the work because nobody knew. The bundles just sat there, quietly piling up between stations while the rest of the line starved.

This is what work-in-progress (WIP) looks like when you cannot see it. And in most garment factories in South Asia, you cannot.

The Real Cost of Invisible WIP

Let me put a number on it. Say your factory produces 5,000 pieces per day at an average FOB of $4.50. Your cut-to-pack cycle is 5 days, which is typical for a mid-sized factory without real-time tracking. That means at any given moment, you have roughly 25,000 pieces sitting on your floor as WIP. At $4.50 each, that is $112,500 of working capital tied up in fabric, thread, and labor that has not converted to revenue yet. Research published on ResearchGate estimates that 60-70% of all wastes in garment manufacturing are directly attributable to WIP inventory.

Simon Gibson, who spent 26 years in garment manufacturing consulting across Asia, calculated similar numbers for ApparelResources: a factory doing 15,000 pieces per day at $5 FOB with a poorly managed WIP pipeline can have $787,500 locked up on the floor. His benchmark: poorly managed factories run 18-24 days of WIP. Well-managed ones run 4-12 days.

According to ILO productivity studies on South Asian garment factories, the average sewing floor efficiency in the region sits between 40-60%. The global best practice is 75-85%. A ScienceDirect study on shirt manufacturing found that 91.86% of production lead time was non-value-added — meaning operators were waiting, not working. That gap is not mainly about operator skill. It is about management visibility. You cannot fix what you cannot see.

What WIP Tells You That Output Reports Do Not

This is the key insight most factory owners miss: output is a lagging indicator. WIP is a leading one.

Your end-of-day output report tells you what already happened. It is a post-mortem. By the time you see the number, the damage is done. But WIP levels at 10 AM tell you what your output at 5 PM will be. If bundles are piling up at your buttonhole station at 10 AM, you already know your finishing line will be starved by 2 PM. You have four hours to fix it.

I have seen factory owners stare at their output reports every evening like they are reading tea leaves, trying to figure out why production missed target. The answer was sitting on their sewing floor all day, visible to anyone who knew where to look. They just had no system to look.

WIP data tells you three things output never will:

• Where the constraint is right now — not where it was yesterday
• How long bundles have been waiting — aging WIP means something is wrong, even if output looks okay so far
• Whether your line is balanced — before imbalance shows up as missed targets

A Line Imbalance That Cost 900 Pieces

One factory we worked with had a persistent problem on their polo shirt line. Output was consistently 15% below target and nobody could figure out why. The overlock section was fast. The operators were experienced. The supervisors said everything was running fine.

When we started tracking WIP by operation, the problem showed up within the first hour. The overlock stations were processing 80 pieces per hour. The single-needle station doing placket attachment was handling 50. That is a gap of 30 pieces per hour. Within three hours, 90 bundles were sitting dead between those two stations. The single-needle operators physically could not clear them without help.

Worse, the downstream stations — buttonhole, button attach, finishing — were starving. Operators sat idle because no work was reaching them. The line was producing at the speed of its slowest operation, while paying all operators for a full shift. That gap of 30 pieces per hour, compounded across a 10-hour shift, meant 300 lost pieces per day. Across three days before we caught it, that was 900 pieces — nearly a full day of production gone.

The fix took ten minutes. The supervisor moved one helper from the overlock section to assist with placket attachment. WIP at the single-needle station cleared within two hours. But without real-time data, that ten-minute fix would have taken three more days to discover through output reports alone.

How QR-Based WIP Monitoring Works

The mechanics are straightforward. Every bundle gets a unique QR code printed at cutting. The QR encodes the style, lot, color, size, bundle number, component, and quantity. When an operator picks up a bundle, they scan. When they finish, they scan again. Two scans per operation. That is the entire operator workflow.

1. Bundle creation at cutting: QR labels printed on a thermal printer. Each label carries all the metadata needed to track the bundle through its entire lifecycle on the floor.
2. Scan on start: Operator scans the QR code. The system records who, what operation, which machine, and when.
3. Scan on completion: Operator scans again. Duration and piece count are recorded automatically. The bundle moves to the next operation's queue.
4. Real-time aggregation: Every scan feeds a live dashboard. Supervisors see WIP counts at every operation, pieces per hour per operator, and alerts when accumulation exceeds thresholds.

The result is that every bundle has a known location at every moment. Every operation has a measurable throughput rate. Every bottleneck is visible within seconds of forming — not hours.

The Metrics That Actually Matter

I have seen factories drown in dashboards full of metrics they never act on. For WIP, focus on these:

The single most important metric is WIP aging. A bundle that has been sitting at a station for 45 minutes when the operation SAM is 2 minutes is screaming at you. Either the operator left, the machine broke, or nobody assigned that bundle. Whatever the reason, aging WIP is a leading indicator of a production hole that will show up in your output four hours later.

What Happens When a Bundle Gets Stuck

In the Scan ERP system we built for our factory floor, here is what happens when a bundle gets stuck at Station 12 for more than 15 minutes:

First, the live dashboard on the factory floor TV turns that station amber. The supervisor can see it from across the room on a 43-inch display mounted at the end of the sewing line. At the same time, the system sends a WhatsApp message to the line supervisor's phone — not email, because no supervisor on a factory floor checks email. The message says exactly which bundle, which operation, which operator, and how long it has been sitting.

If nobody acts within another 15 minutes, a background monitor kicks in. It automatically resets the stuck operation so that it does not block the five dependent operations downstream. The bundle goes back to READY status so another operator can pick it up.

This three-layer system — visual alert, WhatsApp notification, automatic resolution — means a bottleneck cannot hide. We built it this way because we learned the hard way that any single notification channel gets ignored. Supervisors walk away from dashboards. They mute WhatsApp groups. But when the big screen turns amber AND their phone buzzes AND the system starts auto-correcting, they act.

The Biggest Benefit: Catching Bottlenecks Before They Cost You

I could list a dozen benefits of real-time WIP tracking. Better delivery timelines. Accurate piece-rate payments. Data-driven line planning. Historical analysis of which operations bottleneck on which styles. All true, all valuable.

But the one that pays for the entire system is this: you catch bottlenecks in real time instead of at end of day. Everything else is a bonus.

In a factory producing 3,000 pieces per day, a bottleneck that runs for 7 hours undetected (the norm with manual tracking — problem starts at 9 AM, discovered at 4 PM) costs you roughly 450 pieces at a 15% efficiency loss. At $4 FOB, that is $1,800 per day. Across a month, $39,600. Across a year, nearly half a million dollars.

With real-time tracking, that same bottleneck is detected in 30 seconds and resolved in 10-15 minutes. The loss drops from 450 pieces to maybe 20. That is the ROI calculation. Not features. Not dashboards. Just the difference between knowing at 9:01 AM and knowing at 4 PM.

The other benefits layer on top. A lean implementation study on ResearchGate documented a 74.3% WIP reduction in T-shirt production lines after implementing real-time tracking and cellular layouts, with lead times dropping from 2 days to under 20 minutes in some cases. Throughput time drops from 3-5 days to 1-2 days because WIP flows instead of piling up. Operator piece-rate payments become transparent because the data comes from their own scans, not a supervisor's estimate. Line planning shifts from gut feel to evidence — you learn which operations consistently bottleneck on specific styles and staff accordingly before the lot even hits the floor.

Day 1 vs. Day 30

On Day 1, you print QR labels at cutting and put phones at each workstation. Operators learn to scan in about 20 minutes — it is literally point and tap. Supervisors need a day or two with the dashboard. That is the full implementation.

The first thing that happens is uncomfortable. You see problems you did not know you had. One factory we set up discovered that their finishing section had been running at 60% utilization because the upstream quality check was creating a bottleneck nobody noticed. The QC station had one operator doing the work of two. Bundles were aging 40+ minutes at QC while finishing operators sat idle. The supervisor thought finishing was the slow section because that is where output was low. The data showed the opposite.

By Day 30, you have enough historical data to start planning proactively. You know that Style X always bottlenecks at collar attachment because it has a complex construction. You know that Operator 15 runs 30% faster on overlock than the line average. You know that Monday mornings consistently start slow because of machine warm-up. You stop reacting and start predicting.

That shift — from reactive firefighting to proactive management — is what separates factories that grow from factories that just survive.

A Note on Factory Size

According to FNCCI data, most garment factories in Nepal run between 100-500 operators. In Bangladesh, BGMEA-registered factories range from small units of 200 operators to mega-factories of 10,000+. WIP tracking is not a large-factory luxury. A 150-operator factory running three lines has exactly the same visibility problem as a 2,000-operator factory. The bundles still pile up. The bottlenecks still hide. The only difference is the scale of money lost.

If anything, smaller factories benefit more because they have less margin for error. A large factory can absorb a bad day. A factory running 1,500 pieces per day on thin margins cannot afford to lose 300 pieces to an invisible bottleneck.

If you do not know your WIP right now — at this exact moment — how do you know your factory is running efficiently?

Santosh Rijal is the founder of Scan ERP, a garment manufacturing ERP system designed for factory floor operations. He works directly with sewing lines, cutting rooms, and production supervisors across Nepal's garment manufacturing sector.