Resources/Glossary/
Cycle Time
Pull and Flow

Cycle Time

How long one part takes at one station. The number a stopwatch can answer.

Updated
·
4
min read
Definition

What is Cycle Time?

Cycle time is the time required to complete one unit of work at one process, from the moment the operator starts on a part until they hand the next one off. It is a measurement, not a target. Cycle time is what a stopwatch on the shop floor will tell you, and it is the building block underneath lead time, takt time, and capacity planning.

Cycle time is the most measurable thing in lean and also the most misunderstood. Most shops think they know their cycle times. They have ERP numbers that say a part takes nine minutes to mill. When somebody actually times the work with a stopwatch, the real cycle is usually fifteen minutes once setup, reaching, repositioning, and small inspections get counted. That gap, between the cycle time on paper and the cycle time on the floor, is where most flow problems hide.

"Cycle is what a stopwatch knows. Anything else is a guess dressed in software."

How cycle time works

Cycle time is measured at one process, on one operator, for one full unit of work. The clock starts when the operator picks up or begins on a part. It stops when they hand off the finished piece and reach for the next one. That total includes everything the operator actually does: the value-added work (cutting, bending, fastening, assembling), the necessary work (reaching, repositioning, quick visual checks), and any micro-waste that sits inside the operation (looking for a tool, fixing a small mis-feed).

Five to ten observations is usually enough to spot a stable average. The numbers will vary. The variation itself is data: a station with a tight spread is consistent; a station with a wide spread has hidden problems. Lean shops record both the average and the spread. Both feed into how the cell gets balanced.

Cycle time then becomes the input to everything else. Capacity per shift is available time divided by cycle time. The bottleneck of a value stream is the operation with the longest cycle. Whether the line can keep up with demand is a comparison between cycle time and takt time. Whether a pull system will work is partly a question of whether cycle times across stations are close enough to each other to flow without buffering between them. None of that math works if cycle time is a guess.

Where cycle time fits on the shop floor

Picture a small contract manufacturer running plastic injection mold parts for three customers. The shop has six presses. The owner thinks press four is the bottleneck because it runs the longest jobs. A morning of cycle-time measurement says otherwise. Press four runs a 90-second cycle on its biggest job, which sounds long but matches the takt the shop needs. Press two, the smallest press, runs at 45 seconds but has so many tool changes that effective cycle is closer to 80 seconds. Press six, the newest press, is running a 60-second cycle on a 30-second job because the operator was trained to baby the machine.

That single morning of stopwatch work tells the owner where the actual bottleneck is (press two, because of changeover, not press four) and where the spare capacity is hiding (press six, because of operator habit). No software discovered any of that. A stopwatch did. The owner moves one operator and one job, and the shop's effective output goes up by twelve percent the next week.

Common mistakes with cycle time

  • Trusting the ERP number. ERP cycle times are usually whatever was entered at quote time. Real cycle time is whatever the stopwatch says today.
  • Timing only the value-added portion. Reach, reposition, quick inspection, and tool grab are all cycle. Excluding them hides the gap between paper and reality.
  • Averaging without spread. A cycle that varies from four to ten minutes is a different problem than a cycle that varies from six to seven. Track both.
  • Optimizing the wrong station. A faster cycle at a non-bottleneck just produces parts the next station cannot absorb, growing work in process.
  • Confusing cycle with takt. Cycle is what your process does. Takt is what demand wants. Treating them as one number means you cannot see capacity problems.

Cycle time and related Lean tools

Cycle time is the building block under most flow metrics. Takt time is the customer-driven pace cycle has to live underneath. Lead time is the customer-facing total, of which cycle time is a small fraction. Throughput time is the elapsed time across all cycles in a stream. Process cycle efficiency, the ratio of value-added time to total lead time, is the metric that exposes how much of the lead time is actually cycle work and how much is just waiting.

Common questions

The questions we hear most about this term.

How does cycle time work?
You time one operator doing one full pass on one part, from the moment they pick it up to the moment they hand off the finished piece. You do this five or ten times and average the results. That average is the operation's cycle time. It includes the work you can see (cutting, bending, fastening) and the work that gets ignored (reaching for the next part, repositioning, brief inspections). Cycle time then becomes the building block for everything else: how many parts the line can produce per shift, where the bottleneck is, whether the station can keep up with customer demand.
How is cycle time different from takt time?
Cycle is what your process does. Takt is what your customer wants. Cycle is measured. Takt is calculated from demand. If your station has a cycle time of seven minutes and your takt time is five minutes, the station cannot keep up with demand and needs help. If cycle is two minutes and takt is five, the station has spare capacity that should not get spent making extra units. The whole point of distinguishing them is to see those gaps clearly and decide what to do about them.
Is cycle time the same as lead time?
No, and this is one of the most consequential mix-ups in shops that are new to lean. Cycle time is one operation. Lead time is the entire stream from order to delivery. A part with a four-minute cycle on the mill might have a six-week lead time because it spends most of that six weeks waiting in carts. Optimizing cycle time without touching the carts barely moves lead time. The two metrics belong to different problems. Cycle is a machine problem. Lead time is a flow problem.
What are common mistakes with cycle time?
Timing only the obvious work is the big one. The cycle is the full hand-off, not just the moment the machine is running. Skipping the setup or the brief between parts hides real time. Second mistake: averaging without context. A cycle measured during a calm shift with no interruptions will not match the lived rhythm of a busy day. Third: chasing cycle time at one station while the next station chokes. If the next operation cannot absorb your faster output, you are just building inventory faster.
What does cycle time look like on the shop floor?
It looks like a number on a card or sticker at each station, usually updated quarterly. A small machine shop running production work would have a printed sheet at every station showing the part number, the standard cycle time, and the takt the cell needs to hit. Operators glance at it. Lead operators time a few parts each week and update the number if the process has changed. There is no real-time dashboard. The information is on the wall where the work is.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.