WIP metrics are the handful of measures that tell you whether work-in-process is healthy: how much is on the floor (units and dollars), how long it sits (days and lead time), and how fast it turns over (inventory turns). Read together, they answer one question, is material flowing, or is it piling up and aging between operations?
Work-in-process is every part that has left raw storage but has not yet reached finished goods: parts being worked, parts in queues, parts in totes between cells. It is easy to see and hard to measure, because most systems log transactions, not the hours a part waits between them. This post covers the four WIP measures worth tracking, how they connect through Little's Law, and which one to lead with depending on what you are trying to fix.
What are WIP metrics?
WIP metrics quantify the standing inventory inside the process from four angles: quantity, value, time, and turnover. No single one tells the whole story. Units answer "how many," dollars answer "how much cash," days answer "how long," and turns answer "how fast." A plant that watches only one, usually dollars, because finance asks for it, misses the flow problems the other three would have caught.
| Metric | What it measures | Best for |
|---|---|---|
| WIP units | Count of parts in process | Floor-level flow, cap enforcement |
| WIP dollars | Value of in-process inventory | Cash tied up, finance reporting |
| Days of WIP | WIP divided by daily usage | How long material sits before finishing |
| Inventory turns | How many times WIP cycles per year | Trend and cross-period comparison |
The reason to track more than one is that they can disagree in useful ways. WIP dollars can look flat while WIP days climb, if the mix shifted to cheaper parts that are still aging in queues. Days is the honest flow signal; dollars is the cash signal. You want both.
How do you calculate each WIP metric?
Each has a simple formula, and the discipline is consistency, not precision. Use the same boundaries, where WIP starts and ends, every time you count.
- WIP units. Count the parts between the raw-material gate and finished goods. A physical count on a quiet shift beats an ERP guess; systems drift from reality.
- WIP dollars. Value each in-process part at its accumulated cost so far, material plus the labor and overhead already added. This is the cash sitting on the floor.
- Days of WIP. Divide WIP (units or dollars) by average daily usage in the same terms. Fifteen days of WIP means material takes about fifteen days to clear the process at current rates.
- Inventory turns. Divide annual cost of goods sold by average WIP value. Higher turns mean inventory cycles faster and less cash sits idle; six turns is far leaner than two.
- Flow time via Little's Law. Flow time equals WIP divided by throughput. This ties your standing inventory directly to how long a part takes to get through, the metric customers actually feel.
Notice that days of WIP, turns, and flow time are three views of the same truth: how long material lingers. If any one moves, the others should move with it. When they do not, your counts or your boundaries are inconsistent, which is itself a useful finding.
How do WIP metrics connect through Little's Law?
Little's Law is the spine that links them. It states that average WIP equals throughput times flow time. Fix any two and the third is determined; you cannot cut WIP without either raising throughput or shortening flow time. That is why WIP metrics are not four independent dials, they are one relationship seen from different sides.
The practical use: if WIP is high and throughput is flat, flow time must be long, so material is aging in queues and your lead time is bloated. You do not need a separate study to know that; the law guarantees it. This is the same relationship a WIP cap calculation rearranges to set a ceiling, and the same one wait-time reduction exploits to shorten delivery.
What makes WIP pile up?
Almost all excess WIP has one of four causes, and naming the cause tells you which metric will catch it first. Watch for these before you blame the numbers.
- A constraint losing time. When the slowest step stops or slows, everything upstream keeps feeding it, so WIP stacks in front of it. Days of WIP at that queue spikes first.
- Large batches. Running and moving in big lots forces parts to wait for their whole batch, inflating standing inventory at every step. WIP units climb even when demand is flat.
- Overproduction. Making to a forecast or to keep people busy releases work the floor cannot clear, the worst of the lean wastes. WIP dollars rise with nothing to invoice.
- Unbalanced lines. Any step that runs faster than the one it feeds builds a pile between them. The imbalance shows up as WIP concentrated at specific handoffs, not spread evenly.
The tell is where WIP sits. Evenly distributed WIP is usually just the natural content of the process; WIP concentrated in one or two queues points straight at a constraint or an imbalance. A metric that only reports plant-total WIP hides that; a metric that reports WIP by location finds the problem in seconds.
What is a good WIP level?
Low enough that lead time is short and cash is free, high enough that the constraint never starves. There is no universal target, because the right level depends on your demand variability, changeover times, and how reliable your equipment is. The honest benchmark is your own line over time: falling days of WIP and rising turns at steady or rising throughput is unambiguously good.
Beware the two failure modes. Too much WIP hides problems and lengthens lead time, the pile absorbs every hiccup, so nothing forces a fix. Too little WIP starves the constraint, and an idle constraint is lost throughput you never get back. The goal is the least WIP that keeps the slow step fed, which is exactly what a WIP cap is built to hold. Track the level against that cap rather than against a generic industry number.
One refinement worth adopting is standard WIP: the specific quantity a stable process should hold to run at its planned rate, calculated rather than accumulated. Standard WIP gives each location a target, so a supervisor can see at a glance whether a queue is over or under where it should be, instead of judging a pile by feel. Deviations from standard WIP are an early warning, a queue drifting above standard flags a downstream slowdown before the lead time number ever moves.
How often should you measure WIP?
Match the cadence to the decision. Floor-level WIP units and location want a real-time or shift view, because that is the signal supervisors act on within the day, a pile forming in front of a machine is a now problem. WIP dollars and inventory turns are finance and trend measures, so monthly is usually enough; they answer questions about cash and direction, not about what to do on this shift. Days of WIP sits in between, useful weekly to confirm that flow is holding. The mistake is measuring everything monthly because that is when finance closes the books, by then the flow problems the fast metrics would have caught have already cost you a month of lead time.
By the numbers
WIP is a real chunk of the national balance sheet, and it is measured. U.S. manufacturers reported total inventories of about $962.0 billion with an inventories-to-shipments ratio of 1.47 in May 2026, per the U.S. Census Bureau's M3 Manufacturers' Shipments, Inventories, and Orders report roughly a month and a half of shipments held as stock, work-in-process among it. The relationship that governs how that inventory behaves was proved by John D. C. Little in 1961 in "A Proof for the Queuing Formula: L = λW," Operations Research 9(3):383–387. Together they say the quiet part out loud: a lot of manufacturing capital is standing inventory, and Little's Law is the lever for freeing it.
How do these fit your KPI set?
WIP metrics belong beside output and quality, not on their own dashboard. On their own, low WIP could mean great flow or a starved constraint; paired with throughput and cycle time the picture is unambiguous. The clean panel is throughput, WIP days, and flow time together, the three sides of Little's Law, plus WIP dollars for finance. Fold that into your broader manufacturing KPIs so WIP is read in context, and watch it next to OEE at the constraint, since constraint losses are usually why WIP backs up in the first place.
The measurement itself is the hard part. WIP hides because most systems record a part scanned in and a part scanned out, not the hours it waited between them, so days-of-WIP and flow time get estimated instead of measured. Plants like CLS replaced paper production logging with real-time capture, so the count and the aging are live rather than reconstructed at month-end. For the companion levers that move these numbers, see work-in-process reduction; to size the constraint losses behind a rising WIP, start with a free OEE calculator.