Cycle Time Calculator
Convert a timed observation into seconds per unit and units per hour.
Cycle time
52.9
- Throughput
- 68.0 units/hr
- Output per 8-hour shift
- 544 units
- Seconds per 100 units
- 5,294 sec
Cycle time is the elapsed time between one unit coming off a process and the next. It is the number you compare against takt time, the number that determines throughput, and the number that reveals which station is the bottleneck. Getting it right starts with a clean observation window: time a run of consecutive units in steady state, not the first ten minutes after a changeover.
This calculator converts an observation into three figures you will actually use: seconds per unit, units per hour, and the equivalent output over an eight-hour shift. The distinction that matters is between cycle time and lead time — cycle time is how fast the process repeats, lead time is how long one unit spends inside it. A process with a 50-second cycle time and three hours of work in process has both a short cycle time and a long lead time.
How the result is calculated
Cycle time = (Observation time × 60) ÷ Units completed- Cycle time (sec/unit) = Observation minutes × 60 ÷ Units produced in that window
- Throughput (units/hr) = Units ÷ (Observation minutes ÷ 60)
- Output per shift = Throughput × shift hours
Variables
| Symbol | Meaning | Unit |
|---|---|---|
CT | Cycle time | sec/unit |
t | Observation window | min |
n | Units completed | units |
Worked example
An operator is timed for 60 minutes in steady state and completes 68 units, with no stoppages during the window.
- Cycle time = (60 × 60) ÷ 68 = 3,600 ÷ 68
- Cycle time ≈ 52.9 seconds per unit
- Throughput = 68 ÷ 1 hour = 68 units per hour
- Output per 8-hour shift = 68 × 8 = 544 units
The station runs at 52.9 seconds per unit, or 68 units per hour. Compared with a takt time of 103.8 seconds, it has substantial slack — roughly twice the capacity needed, which means it is not the constraint and any improvement effort spent here will not increase line output.
What this calculation does not cover
- The observation must be in steady state. Including a changeover, a tool change or the first units after a start-up inflates cycle time and makes the station look slower than it normally runs.
- Sample size matters. A single 60-minute window in a stable process is usually adequate; in a highly variable process you need several windows across shifts and record the spread, not just the average.
- This is the average cycle time. For line balancing you also need the minimum and maximum, because the slowest unit sets the pace of everything downstream.
- Throughput calculated here is theoretical: it assumes no downtime, no starvation and no blocking. Use the production capacity calculator with an efficiency or OEE figure to get a realistic number.
Frequently asked questions
Is cycle time the same as lead time?
No. Cycle time is how often the process produces a unit — the repeat interval. Lead time is the total elapsed time a single unit spends from order release to completion, including all waiting. A process can have a 30-second cycle time and a two-day lead time if inventory queues between steps.
How many observations do I need for a reliable cycle time?
For a stable, repetitive process, 10 to 20 consecutive units is enough to establish the typical value. For manual assembly with noticeable variation, time at least 20 cycles and report the median alongside the mean; a single outlier can shift the mean enough to change your capacity conclusion.
What should I do if cycle time is higher than takt time?
You have four options, in rough order of cost: reduce work content at the station, split the work across two stations, run overtime or an extra shift, or add capacity. Do not solve it by asking operators to work faster — if the work content genuinely exceeds takt, effort alone will not close a sustained gap and it will show up as quality problems instead.