Most CNC shop owners can tell you their revenue, their payroll, and their machine utilization off the top of their head. Far fewer can tell you how many dollars are sitting, unfinished, on the shop floor right now. That number is work-in-process inventory, and when it quietly climbs, it eats cash the same way an unnoticed leak drains a tank: gradually, then all at once when payroll or a tooling order comes due.
This self-audit gives you 10 concrete signs that WIP is trapping more cash than it should, a quick way to estimate what that's costing you, and a scored path to the specific fixes that apply to your shop.
TL;DR:
Run the 10-question audit below. Each "yes" is a specific, fixable pattern that inflates WIP days and ties up cash.
Estimate cash at risk with one formula: daily production value × excess WIP days.
Your score points to a short reading list, not a generic action plan. Fix the two or three highest-impact items first.
Answer yes or no to each. Be honest rather than aspirational; this is diagnostic, not a report card.
Batch sizes are set to amortize setup time, not to match actual demand. If fixture changeovers drive lot sizes rather than order quantity, parts sit waiting for the rest of the batch to finish. See tactics for cutting setup time without inflating batches in the setup and cycle time reduction guide.
There are no WIP limits at the cell level. Without a cap on how much can queue between operations, queues grow until something forces a reschedule. Compare pull-based options in the kanban vs. continuous flow comparison.
Scheduling is still push-based or spreadsheet-driven rather than finite-capacity. Push scheduling loads work ahead of real machine and operator availability, which is one of the most common causes of high WIP in job shops. The production planning and scheduling guide covers the shift to finite-capacity planning.
Cycle times used for planning are rules of thumb, not measured values. Planners using historical averages plus a safety buffer routinely overstate standard times, which inflates planned WIP. See the technical method in the G-code cycle time extraction workflow.
WIP is counted manually, and only weekly or at month-end. Infrequent, manual counts mean a bottleneck can build for days before anyone notices. The shop-floor management and WIP tracking guide compares manual and automated tracking methods.
Barcode scans or manual logs are the only way parts get tracked between operations. Manual scanning adds handling steps and delay at every handoff. See the comparison in IoT sensors vs. manual scanning for WIP delays.
You don't have a clear per-operator workload view, so you can't tell if a queue is a scheduling problem or a staffing problem. The operator workload indicators guide lays out five formulas for measuring this directly.
When a cell falls behind, the default response is to add headcount rather than rebalance the existing team. In many shops, existing operators have unused capacity that better allocation can unlock. See know your operators' workload before you hire.
Job completions reach the ERP with a lag, or get entered twice by different people. Delayed or duplicate posting is the leading cause of phantom WIP, inventory the ERP thinks exists but the floor has already finished or never started. The shop-floor-to-ERP integration guide covers reconciliation patterns that prevent this.
Nobody has calculated what a WIP reduction would actually be worth in dollars. Without a baseline, it's hard to justify a pilot or measure whether a change worked. The ROI model for production management software walks through the calculation.
See where your WIP is actually building up. Real-time machine monitoring shows queue and cycle data as it happens, not at next week's count.
Count your "yes" answers.
| Score | What it likely means |
|---|---|
| 0 to 3 | WIP is reasonably well controlled. Small process refinements are more useful than a platform overhaul right now. |
| 4 to 6 | Cash is probably tied up somewhere specific. Isolate the highest-scoring category above and start there. |
| 7 to 10 | Several compounding issues are likely inflating WIP days significantly. A structured pilot, not a single fix, is the faster path. |
A rough estimate of cash at risk uses one formula:
Cash at risk = daily production value × excess WIP days
Example: a shop selling $7,500 of finished parts per day, carrying what it believes is 10 days more WIP than necessary, has roughly $75,000 tied up that could otherwise fund payroll, tooling, or maintenance. For the full worksheet, including carrying-cost conversion to an annual figure, see the ROI model for production management software.
Turn your audit score into a dollar figure. Get a side-by-side view of what reduced WIP days and improved scheduling are worth for a shop your size.
Rather than repeating tactics that are already covered in depth elsewhere, here's where to go depending on which questions you answered yes to.
If questions 1 to 3 (scheduling and batching) scored highest: start with the production planning and scheduling guide, then evaluate whether your shop's mix fits kanban or continuous flow. For high-mix environments specifically, the capacity planning platforms for high-mix production comparison narrows vendor options.
If questions 4 to 6 (data and visibility) scored highest: the shop-floor management and WIP tracking guide is the right starting point, with the daily production routine article showing how a live morning review closes the visibility gap day to day.
If questions 7 to 8 (labor and workload) scored highest: the operator workload indicators guide gives you the formulas, and connected worker solutions covers how real-time task visibility keeps operators from becoming the hidden bottleneck.
If questions 9 to 10 (systems and financial tracking) scored highest: the shop-floor-to-ERP integration guide and the operator-data-to-ERP/MES guide both cover low-disruption ways to close the reconciliation gap. For the full workforce piece, see the complete guide to workforce management.
Not sure where to start? A short conversation can help you prioritize based on your actual audit score and shop size.
WIP rarely drains cash through one dramatic failure. It's usually five or six small, ordinary habits, oversized batches, manual counts, rule-of-thumb cycle times, that compound quietly until the dollar figure is too large to ignore. Run the audit, score it honestly, and fix the highest-scoring category first rather than trying to overhaul everything at once.
Any pattern that lets partially finished parts sit longer than necessary between operations, oversized batches, uncapped queues, or slow data reconciliation, counts. Each extra day of WIP ties up cash equal to your daily production value, whether or not anyone notices it happening.
Four or more suggests cash is tied up in a specific, identifiable way. Seven or more usually means several issues are compounding, and a structured pilot will resolve them faster than fixing items one at a time.
Several audit items, batch sizing and WIP limits in particular, can improve with process changes alone. Others, like real-time cycle-time capture or ERP reconciliation, are hard to fix reliably without connected data. Start with the process changes your score points to, then decide if the data gap is the limiting factor.
Tracking WIP days tells you the size of the problem. This audit tells you where it's coming from, so you can address the specific cause instead of generically trying to "reduce WIP" without knowing which lever to pull first.