Cycle Time Calculator
Calculate cycle time for a process, task, or production run from start to finish.
What Is Cycle Time?
Cycle time measures the total elapsed time from the start to the end of a process, task, or production run. It includes both active work time and any waiting or idle periods within that specific process. Unlike takt time, which is set by customer demand, or lead time, which covers the entire order-to-delivery timeline, cycle time focuses strictly on the duration of one complete operation.
Manufacturing teams, software developers, and operations managers use cycle time to identify bottlenecks, set realistic schedules, and measure process efficiency. A shorter cycle time generally indicates a faster, more responsive process.
How to Calculate Cycle Time
The calculation is straightforward:
Cycle Time = Total Time / Number of Units Produced
For example, if a production line runs for 480 minutes in a shift and produces 240 units, the cycle time is 2 minutes per unit. The same formula applies to non-manufacturing processes. A customer service team that handles 60 tickets in an 8-hour shift has a cycle time of 8 minutes per ticket.
Time should be measured in consistent units. Most operations use minutes or hours, but seconds may be appropriate for highly automated, fast-cycle processes.
Common Mistakes When Measuring Cycle Time
Including Unrelated Downtime
Only include time that falls within the process being measured. If a machine sits idle overnight due to a scheduled shutdown, that time should not be counted unless the process definition explicitly includes it.
Confusing Cycle Time with Lead Time
Lead time spans from customer order to delivery and includes queue time, transport, and other delays outside the specific process. Cycle time covers only the active process duration. Using the wrong metric leads to inaccurate capacity planning.
Using Averages Without Context
A single average cycle time can hide significant variation. If one batch takes 10 minutes and another takes 50 minutes, the average of 30 minutes does not represent either scenario well. Track individual cycle times to understand process stability.
Practical Use Cases
- Manufacturing: Determine how long each assembly step takes and identify which station slows down the entire line.
- Software Development: Measure the time from when work starts on a feature to when it is ready for deployment. Shorter cycle times enable faster feedback and iteration.
- Customer Support: Track how long agents take to resolve tickets. This helps set staffing levels and identify training needs.
- Order Fulfillment: Calculate the time required to pick, pack, and ship an order. Reducing this cycle time improves delivery speed.
Limitations of Cycle Time
Cycle time is a useful operational metric, but it does not capture everything. It does not account for quality. A process with a very short cycle time that produces defective units is not efficient. It also does not reflect customer satisfaction or resource utilization on its own. For a complete picture, pair cycle time with quality metrics, throughput, and capacity data.
Cycle time calculations assume a stable process. If the process changes frequently or operates under highly variable conditions, the calculated value may not be reliable for forecasting.
FAQ
What is the difference between cycle time and takt time?
Takt time is the rate at which a product must be completed to meet customer demand. It is calculated as available production time divided by customer demand. Cycle time is how long it actually takes to complete one unit. If cycle time exceeds takt time, the process cannot keep up with demand.
Can cycle time be less than takt time?
Yes. When cycle time is less than takt time, the process runs faster than customer demand requires. This creates idle time or allows for overproduction, which may lead to excess inventory.
Should I include breaks and lunch in cycle time?
It depends on the purpose of the measurement. If you are measuring the actual time a process takes from start to finish, include all elapsed time including breaks. If you are measuring pure working time, exclude scheduled breaks. Be consistent and document your definition.
How do I reduce cycle time?
Identify the bottleneck step in the process and focus improvements there. Common approaches include eliminating non-value-added steps, reducing setup times, improving workflow layout, cross-training staff, and automating repetitive tasks. Measure cycle time before and after changes to confirm improvement.
Is cycle time the same as processing time?
Not exactly. Processing time refers only to the time a unit is actively being worked on. Cycle time includes processing time plus any waiting, inspection, or movement time within the process. Processing time is always shorter than or equal to cycle time.