Cycle Time Calculator
Measure how long it takes to produce a single unit, understand throughput, and compare against customer demand.
Include time for set-up, processing, inspection, and delays.
Adjust for breaks or multiple shifts to reflect actual availability.
Cycle Time Summary
Cycle time
12 min
0.2 hours per unit
Throughput capacity
40 units/day
Based on 8 working hours/day
Takt time
2.7 min/unit
Meet demand of 180 units in 8 hours
How to Use This Calculator
Measure production span
Track how long a batch or work order takes from start to finish, including setup, processing, inspection, and wait time.
Count the output
Divide total time by the number of finished units to determine average time per unit.
Benchmark against demand
Compare cycle time to takt time (customer demand rate) to see whether capacity is enough or needs balancing.
Formula
Cycle Time = Total Production Time ÷ Units Produced
Throughput = Working Hours per Day ÷ Cycle Time
Takt Time = Working Hours per Day ÷ Demand per Day
Example: 40 hours to produce 200 units → Cycle time = 0.2 hours (12 minutes). With 8 working hours/day, throughput = 8 ÷ 0.2 = 40 units/day. If demand is 180 units/day, takt time = 8 ÷ 180 = 0.044 hours (2.7 min).
Cycle Time Basics
Cycle time reveals how efficiently teams convert input to output. Tracking it highlights bottlenecks, justifies automation, and surfaces process variation. Combine it with lead time and queue lengths for a complete flow picture.
Ways to reduce cycle time
- Eliminate non-value-added steps such as excessive inspections or handoffs.
- Balance workloads across stations to prevent idle time and backlogs.
- Standardize work instructions and provide training to cut rework.
- Automate repetitive tasks or use parallel processing where possible.
Frequently Asked Questions
What is the difference between cycle time and lead time?
Cycle time is the active work time to produce one unit. Lead time measures the total elapsed time from order to delivery, including waiting and queue time.
How often should I measure cycle time?
Track cycle time regularly—per shift, day, or sprint—to catch drifts early and validate process improvements.
What if production runs are inconsistent?
Use averages over multiple runs, or track best/typical/worst scenarios to gauge variability and plan buffers.
Can service teams use cycle time?
Absolutely. Support desks, software teams, and hospitals use cycle time to measure turnaround per ticket, task, or patient visit.