Discrete ManufacturingFree calculatorPDF, Excel, Word export

Little's Law Lead Time and WIP Calculator

Little's Law says average lead time equals average work in process divided by average throughput. It is the quickest way to see why cutting WIP shortens lead time and how big a WIP cap you need.

Your numbers

units

Average units in the process between start and finish.

units/day

Average completed units per working day.

hours

Total hands-on processing time per unit across all steps.

hours
days
$

Used to value inventory tied up.

Your results

Lead time
4
Little's Law: lead time equals WIP divided by throughput.
WIP cap for target lead time
120
Lead time in working hours
32 hrs
Process cycle efficiency
4.7%
Share of lead time spent adding value.
WIP reduction needed
120
Inventory value released
$10,200

Little's Law holds for a stable system with averages measured over a long period. Variation, batching and changing demand make real lead times differ from the average.

Save results:

Lead time (days) as WIP changes

Sweeps Work in process from 20 to 400, holding your other inputs fixed.

Compare calculated lead time with ERP planning data

Optional review of whether your ERP lead times match actual flow.

Optional. The tool and every export work without this. No spam.

How to use the calculator

Enter the average number of units in process, average completed units per working day, and the touch time per unit. The calculator returns lead time in days and hours, process cycle efficiency, the WIP cap that would deliver your target lead time at the same throughput, and the inventory value released if you reach that cap. The chart shows how lead time falls linearly as WIP is reduced, with the line reading directly at your throughput.

  • Use averages over weeks, not a single day
  • Count all WIP between release and completion
  • Use finished-goods throughput for the same boundary

The formula and its assumptions

Lead time = WIP / throughput. It holds for any stable process, whatever the order of service or variation, as long as the averages are measured over the same boundary and period. Process cycle efficiency is value-add time divided by lead time; values below 5 percent are common in batch shops, while well-run flow lines reach much higher. A WIP cap, as in CONWIP or kanban, is the practical lever: it stops new work entering until work leaves.

Reading the result and ERP notes

If lead time is much longer than the quoted lead time in your ERP, the WIP count or throughput may be inconsistent or the planning parameters are out of date. Reducing WIP without raising throughput shortens lead time, but cutting too deep exposes variability and starves bottlenecks, so lower in steps and watch the constraint. Update ERP planned lead times only after the new level has held for several weeks.

Frequently Asked Questions

What is Little's Law?

It states that the long-run average number of items in a system equals the average arrival rate times the average time each item spends in the system. In manufacturing: WIP equals throughput times lead time, so lead time equals WIP divided by throughput.

Does it work with batches and variation?

Yes, for averages over a long period in a stable system. It does not predict the lead time of one order, and variation, batching and shifting demand mean individual orders can take much longer or shorter than the average.

What is a good process cycle efficiency?

It depends on the process. Many discrete shops see under 5 percent. Lean flow lines may reach 25 percent or more. The aim is to track the trend and find where the queue time is, not to hit a universal number.

How does it relate to kanban?

A kanban system sets a cap on WIP with cards. Little's Law then tells you the resulting lead time for the throughput you achieve. Fewer cards means a lower WIP cap and shorter lead time, until the process starves.

Netray can pull WIP and throughput from your ERP to run this calculation by work center and compare it with the lead times in your item master.