Cycle time is the time it takes to complete one unit or operation, start to finish. Lead time is the total time from when an order is placed to when it ships, including queue time, wait time, and every process step in between. Cycle time measures how fast a single process runs. Lead time measures how long a customer waits. A machine can have a fast cycle time and a slow lead time at the same time, if parts sit in queue between operations.
Cycle time and lead time both describe how long something takes, but they answer different questions, and mixing them up leads to bad promises to customers and bad decisions on the floor. If you're a plant manager, operations leader, or scheduler trying to set realistic delivery dates or find where production is actually losing time, the distinction matters more than it looks.
This guide covers what each term means, how they're calculated, and how they relate so you can use the right metric for the right decision.
Cycle time is the total elapsed time to complete one unit or one operation, from start to finish, at a single process step. Cycle time breaks down into components:
Machine cycle time: the time a single machine takes to complete one operation on one part, for example the time a CNC mill takes from cut start to part ejection
Process cycle time: the total time from when a part enters a process step to when it exits, including any waiting or loading time at that step
The basic formula for total cycle time at a process step is: Process Time + Move Time + Inspection Time + Queue Time at that step. Cycle time is a machine-level or station-level metric. It tells you how fast one piece of your operation runs, not how long the whole order takes.
Lead time is the total time from when an order is placed, or raw material enters the plant, to when the finished product ships. It's the metric customers actually feel.
Manufacturing lead time is the sum of every process cycle time in the routing, plus every queue time between steps: Manufacturing Lead Time = Sum of All Process Cycle Times + Sum of All Queue Times Between Steps.
That queue time component is usually the biggest and least visible piece. A part might spend three minutes actually being machined and eighteen hours sitting in a staging area waiting for the next operation. Cycle time only sees the three minutes. Lead time sees the full eighteen hours and three minutes.
The two metrics measure different scopes of the same production flow.
Scope: Cycle time measures a single process step. Lead time measures the entire order, from start to shipment.
What it captures: Cycle time captures active processing time at one station. Lead time captures processing time plus every queue, wait, and move between stations.
Who feels it: Cycle time is felt by production planners sizing capacity at a station. Lead time is felt by the customer waiting for delivery.
Typical driver of change: Cycle time improves through faster machines, better tooling, or reduced changeover. Lead time improves through reduced queue time and better scheduling, often without touching a single machine's speed.
Relationship: Lead time is always equal to or greater than the sum of cycle times in the routing. The gap between them is queue and wait time.
Takt time is a third metric worth separating out, because it's easy to confuse with cycle time. Takt time is the maximum time allowed to produce one unit in order to meet customer demand, calculated by dividing available production time by demand.
Comparing your actual cycle time to takt time tells you whether a station can keep up with demand. If cycle time is less than takt time, that station has headroom. If cycle time exceeds takt time, that station is a constraint that will show up as extended lead time downstream. Cycle time and takt time live at the station level. Lead time is the sum of everything, stations and the gaps between them, that determines when the order actually ships.
Plants that focus exclusively on cycle time often miss the bigger opportunity. If cycle time is efficient but lead time is still long, the loss is almost always sitting in queue and wait time between operations, not in the machines themselves.
Common causes of that gap include:
Batching parts before moving them to the next operation instead of moving smaller lots continuously
Poor scheduling visibility that leaves work orders sitting idle waiting for the next available machine
Unplanned downtime at a downstream station that backs up queue for everything upstream
Manual handoffs between departments with no real-time signal that a part is ready to move
Closing that gap has a bigger impact on delivery performance than shaving seconds off an already-fast cycle time.
Cycle time is straightforward to track with automated cycle time tracking, since it's captured directly from machine start and stop signals with no manual timing required. Lead time is harder, because it depends on visibility across every step in the routing, including the queue time that manual systems rarely capture consistently.
Manufacturers using Caddis Systems can pull actual machine cycle times directly from the cycle time calculator to compare real performance against takt time targets, and use that same real-time data to spot where queue time is building up between stations before it compounds into a missed ship date.
Not exactly. Lead time typically refers to internal production time, from order or material receipt to finished goods. Delivery time adds shipping transit on top of lead time.
Yes, and it's often the faster win. Reducing queue time, batch sizes, or scheduling delays between operations can cut lead time significantly without changing how fast any single machine runs.
Cycle time is how long a process actually takes. Takt time is how long a process is allowed to take to meet customer demand. Comparing the two tells you whether a station can keep pace with orders.
Queue time is invisible without a tracking system, so it tends to accumulate unnoticed between every handoff. In many operations, actual processing time is a small fraction of total lead time, with the rest sitting in queues.
Cycle time should be monitored continuously, not recalculated periodically, since tooling wear, process drift, and machine condition can shift actual cycle time gradually over weeks without anyone noticing until output slows down.
Cycle time tells you how fast a single process runs. Lead time tells you how long a customer actually waits. Both matter, but they point to different fixes: cycle time issues get solved on the machine, lead time issues usually get solved in the gaps between machines. See how Caddis Systems gives your team the real-time cycle data to close both gaps. Book a demo today.