Takt time vs cycle time: the two numbers that run your line
Every production line is governed by two numbers, and most planning mistakes come from confusing them.
Takt time is the rate at which you must produce to meet demand. It comes from the market, not the floor:
Takt time = available production time ÷ customer demand
Cycle time is how long a station actually takes to complete its work on one unit. It comes from the floor, not the market. Nobody assigns it — it is whatever your process, tooling, and operators deliver.
The entire discipline of line balancing is making every station's cycle time sit at or below takt. Takt is the budget; cycle times are the spending.
A worked example
A plant runs one 8-hour shift with two 15-minute breaks: 450 minutes of available time. Customers order 300 units a day.
- Takt time = 450 min ÷ 300 units = 1.5 minutes per unit. A unit must leave the line every 90 seconds.
The line has four stations with measured cycle times: 80 s, 95 s, 70 s, and 88 s.
- Three stations fit inside takt. Station 2, at 95 s, does not.
- Station 2 is the bottleneck — and here is the part that surprises people: the line's real output is set entirely by that 95-second station. Not the average (83 s), not the sum. One unit every 95 seconds is 284 units a day. You will miss demand by 16 units every day, while stations 1 and 3 stand idle part of every cycle.
The fix is rebalancing: move roughly 10 seconds of work from station 2 to station 3, and every station fits under takt. Same people, same machines, 300 units — the capacity was there all along, hidden behind uneven loading.
The mistakes that hide in these numbers
Planning to average cycle time. Averages lie. A line of 80/95/70/88 "averages" 83 s — comfortably under takt — while structurally missing demand every single day. Only the slowest station matters.
Confusing cycle time with lead time. Lead time is how long one unit spends going through the whole line end to end; cycle time is the interval between finished units. A line can have a 90-second cycle and a 40-minute lead time. Customers feel lead time; capacity is set by cycle time.
Treating takt as fixed. Takt moves whenever demand or available time moves — a new order, a lost shift, seasonal swing. A balance that was correct in March can be quietly wrong in July. If rebalancing takes a week of spreadsheet work, it simply doesn't happen, and the line runs unbalanced between studies.
Measuring cycle time once. Cycle times drift: operators learn, tools wear, a fixture change speeds one station and strands its neighbor. The numbers in last year's study are not the numbers on your floor.
Quick reference
| Takt time | Cycle time | |
|---|---|---|
| Set by | Demand and available time | Process, tooling, operators |
| Formula | Available time ÷ demand | Measured per station |
| Changes when | Orders or shifts change | The process changes (or drifts) |
| Goal | — | Every station ≤ takt |
| The line's output is set by | — | The slowest station, alone |
Where this fits in planning
Takt and cycle time are the entry point to every serious line decision: how many stations you need, where the bottleneck sits, whether a demand increase needs new equipment or just a rebalance. In Emboscale, those rollups are computed across the whole line automatically — describe the line, and the Factory Agent balances it against your takt, flags the binding station, and validates the result with discrete-event simulation. When demand changes, rebalancing is a prompt, not a study.
Further reading: line balancing · shift scheduling · factory layout planning