Manufacturing lead time is the total elapsed time from releasing a production order to having the finished goods ready to ship. It breaks into five segments, queue, setup, run, move, and wait, and in most plants queue time alone is the largest, often the majority of the clock.
That last point is the whole reason lead time is worth dissecting. Managers instinctively attack run time, the part where machines are cutting metal or filling bottles, because it is the visible work. But run time is usually the smallest slice. The order spends most of its life sitting in a queue waiting for a machine to free up, which means the fastest way to shorten lead time rarely involves making anything faster. This post defines each segment, shows how they stack from order to shipment, gives the arithmetic that ties lead time to inventory, and lays out where the real time hides.
What is manufacturing lead time?
Manufacturing lead time is the clock time a production order takes to move from release to finished, ready-to-ship goods. It is measured per order or per part and covers every hour the order spends inside the plant boundary, whether it is being worked on or simply waiting its turn. It is distinct from purchasing lead time, which covers getting materials in, and from customer lead time, which is what the customer experiences from placing an order to receiving it.
The standard breakdown has five components, and only two of them add value:
- Queue time the order waits at a work center for the machine to become available. Usually the largest single component.
- Setup time programming, tooling, fixturing, and first-piece verification before production begins.
- Run time the active processing time across all operations on the routing.
- Move time transit between operations, work centers, or facilities.
- Wait time the order sits after an operation before it moves on, distinct from queue at the next station.
Setup and run time make up the execution time, the part that actually changes the product. Queue, move, and wait are interoperation time, pure scheduling delay that adds cost and lead time without adding value. That split is the single most useful thing to know about lead time, because it tells you which minutes are candidates for elimination.
Why is queue time the largest part of lead time?
Because most work centers are shared and orders arrive faster than any one machine can clear them, so orders line up and wait. Every time an order reaches a busy work center, it joins a queue behind whatever is already there. Multiply that across a routing with several operations and the waiting compounds. The machines are working the whole time, just not on your order.
This is why run time is a poor lever. Even halving the time a machine spends cutting your part barely moves a lead time that is 80 percent queue. The order still waits the same hours in line before and after that faster cut. The high-leverage move is to shrink the queue itself: release less work so fewer orders are waiting, cut batch sizes so each order clears faster, and add capacity or offload only at the genuine constraint. This is exactly what Little's Law in manufacturing quantifies, lead time = WIP ÷ throughput, so draining the queue is the direct route to a shorter clock.
By the numbers. Manufacturing lead time is standardly decomposed into queue, setup, run, wait, and move time, with queue, wait, and move classed as interoperation time that adds scheduling delay but not value (Lead time, Wikipedia). Because most work centers are shared, queue time dominates the total in typical job-shop and batch environments, which is why lead-time reduction programs target waiting rather than processing (Lean Enterprise Institute, value stream mapping).
How do the five components stack up in numbers?
A worked routing makes the imbalance obvious. The table follows one order through four operations and totals each segment. Notice how little of the total is actual processing.
| Segment | Type | This order | Share of lead time |
|---|---|---|---|
| Queue | Non-value | 52 hours | 72% |
| Wait | Non-value | 8 hours | 11% |
| Move | Non-value | 4 hours | 6% |
| Setup | Value (execution) | 4 hours | 6% |
| Run | Value (execution) | 4 hours | 6% |
| Total lead time | 72 hours | 100% |
Only 8 of the 72 hours, about 11 percent, are spent changing the product. The ratio of value-add time to total lead time is a well-known efficiency measure, and a single-digit percentage like this is common in shops that batch and share machines. Push run time down and you fight over the 11 percent; drain the queue and you go after the 72.
How does manufacturing lead time fit inside total lead time?
Manufacturing lead time is one nested layer inside the longer clock the customer feels. Purchasing lead time comes before it, the time to get raw materials on hand. Manufacturing lead time is the make span, release to ready-to-ship. Customer lead time wraps both plus order processing and outbound shipping, and cumulative lead time is the worst case: material plus make time when nothing is held in stock. Knowing which layer someone means prevents the classic argument where sales quotes one number and the floor measures another.
The layers matter because you can shorten the customer's experience without touching the plant. Holding safety stock of long-lead components collapses purchasing lead time to zero for those parts; finishing to stock instead of to order removes make time from the customer's clock entirely. Manufacturing lead time is only the piece you control on the floor, so improving it is necessary but rarely sufficient, the make-to-stock versus make-to-order decision often moves the customer number more than any shop-floor change.
How do you measure and reduce manufacturing lead time?
Measure it against a fixed boundary, then attack the non-value segments in order of size. The routine below turns lead time from a quoted guess into a number you manage.
- Set the start and end points. Decide exactly when the clock starts (order release, material available) and stops (ready to ship). Every measurement and every quote must use the same two points.
- Measure it two ways and reconcile. Track actual order clock time from timestamps, and independently compute it as WIP ÷ throughput. When the two disagree, the quoted lead time is usually the stale one.
- Split the total into the five segments. Even a rough split shows queue swamping the rest. You cannot shrink what you have not separated.
- Attack queue first, then setup. Cap WIP and cut batch sizes to drain queues; use SMED to shrink setup so smaller batches stay economical. These two moves shorten lead time far more than chasing run time.
- Hold the gain with pull. Lock in a release rule or kanban limit so queues do not silently refill, and re-measure to confirm lead time stayed down.
How is manufacturing lead time different from cycle time and takt time?
They answer different questions and are easy to confuse. Manufacturing lead time is total elapsed clock time for an order, waiting included. Cycle time is how often a finished unit comes off the line, the pace of output, mostly processing. Takt time is the customer demand rhythm, how often you must finish a unit to keep up with orders. An order can have a two-day lead time while the line produces a unit every 30 seconds; the two numbers describe the order's journey and the line's heartbeat, not the same thing.
The link between them is queue. Lead time exceeds pure processing time by exactly the waiting an order does, so the gap between lead time and cycle time is a direct readout of how much queue the order sat through. Watch that gap and you are watching your interoperation waste without a separate study.
How does live floor data shorten lead time?
You cannot manage the queue you cannot see, and in most plants the queue is invisible between weekly reports. Reconstructing lead time from a spreadsheet after the fact tells you what happened, not what is happening now, so orders drift past their promised dates before anyone notices. Live machine monitoring and order tracking show WIP and throughput as they move, which means the WIP ÷ throughput lead-time estimate updates continuously instead of once a week.
That real-time view is what lets a planner cap WIP with confidence, see queues forming at a work center before they blow a due date, and quote lead times that match reality. It is the same connected-floor data behind capacity utilization throughput and the results in the CLS case study. Map the flow first with value stream mapping to find the queues, then use live data to keep them drained.