Takt time vs cycle time: the difference, formulas and examples

Takt time is the pace you must produce at to meet customer demand. Cycle time is the pace a station actually works at. A line meets demand only when every station's cycle time is at or below takt, and most line planning mistakes come from mixing the two up.

Takt time is set by the market:

Takt time = available production time ÷ customer demand

Cycle time is set by the floor. Nobody assigns it. It is whatever your process, tooling and operators deliver, and you find it by measuring:

Cycle time = net production time ÷ units produced

Line balancing is the work of making every station's cycle time sit at or below takt. Takt is the budget; cycle times are the spending.

Takt time vs cycle time at a glance

A worked example

A plant runs one 8-hour shift with two 15-minute breaks: 450 minutes, or 27,000 seconds, of available time. Customers order 300 units a day.

• Takt time = 27,000 s ÷ 300 units = 90 seconds per unit. A finished unit must leave the line every 90 seconds.

The line has four stations with measured cycle times of 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 it alone sets the line's output. The average (83 s) and the sum (333 s) don't matter. One unit every 95 seconds is 27,000 ÷ 95 = 284 units a day, so the line misses demand by 16 units every day while stations 1 and 3 stand idle for part of every cycle.

The fix is rebalancing. Move about 10 seconds of work from station 2 to station 3, and the stations run at 80, 85, 80 and 88 s. Every station now fits under takt and the line makes its 300 units with the same people and the same machines. The capacity was there all along, hidden behind uneven loading.

Two more numbers fall out of the same data:

• Minimum number of stations = total work content ÷ takt = 333 ÷ 90 = 3.7, so at least 4 stations. No balance can hit takt with three.
• Balance efficiency = total work content ÷ (stations × slowest cycle time). Before rebalancing: 333 ÷ (4 × 95) = 87.6%. After: 333 ÷ (4 × 88) = 94.6%. The 47 seconds of idle time per cycle before the rebalance drop to 19.

When demand changes: a second example

Takt moves every time demand or available time moves. Say orders rise to 340 units a day on the same single shift.

• New takt = 27,000 s ÷ 340 = 79.4 seconds.
• The rebalanced line (80, 85, 80, 88 s) now has every station above takt.
• Minimum stations = 333 ÷ 79.4 = 4.2, so the line needs a fifth station, or overtime. At the 88 s bottleneck, 340 units take 340 × 88 = 29,920 s, about 49 minutes of overtime a day.

A 13% increase in demand turned a balanced line into one that needs new capacity. That is why takt time belongs in every demand forecast review, and why a balance done once a year is usually wrong by the time anyone checks it.

How to calculate cycle time

There are two cycle times worth knowing, and both come from measurement:

• Station cycle time: time one station's full work content, start to finish, over at least 10 to 20 consecutive cycles. Use the typical value for planning and keep the spread: a station that averages 85 s but often hits 100 s will behave like a bottleneck.
• Line cycle time: net production time ÷ units produced. If the line above ran 450 minutes and shipped 284 units, its line cycle time was 27,000 ÷ 284 = 95 s, which matches the bottleneck station. When the two numbers disagree, look for starved or blocked time between stations.

"Net" production time excludes planned breaks and planned downtime. Unplanned stops stay in, because they are part of the pace the line really achieves.

Takt time lookup table

Takt for common shift patterns, assuming 450 available minutes per shift:

At the same demand, adding a shift doubles available time and doubles the takt, which is why a second shift is often the cheapest answer to a bottleneck you can't rebalance away.

Takt rate vs takt time

Takt rate is the same requirement expressed as units per hour: demand ÷ available hours. In the first example, 300 units ÷ 7.5 hours = 40 units per hour, which is the 90-second takt time inverted (3,600 ÷ 90 = 40). Use takt time when balancing stations, because cycle times are measured in seconds. Use takt rate when talking to sales or scheduling, because orders are counted in units.

The mistakes that hide in these numbers

Planning to the average cycle time. Averages lie. A line of 80/95/70/88 averages 83 s, comfortably under a 90 s takt, while missing demand every single day. Only the slowest station matters.

Confusing cycle time with lead time. Lead time is how long one unit spends travelling through the whole line, end to end. Cycle time is the interval between finished units. A line can have a 90-second cycle time and a 40-minute lead time. Customers feel lead time; cycle time sets capacity.

Treating takt as fixed. As the second example shows, 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, and a fixture change speeds up one station and strands its neighbour. Last year's time study doesn't describe your floor today.

Running faster than takt. A station well under takt looks efficient, but it builds inventory in front of the next station or waits. Spare time below takt is capacity to reassign during the next rebalance.

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, and whether a demand increase needs new equipment or just a rebalance. Emboscale, an AI factory agent that plans layouts, balances lines, schedules shifts and writes verified robot programs, computes those numbers across the whole line automatically. Describe the line, and it balances it against your takt, flags the binding station, and validates the result with discrete-event simulation. When demand changes, you rebalance with a prompt, and the same model feeds the factory layout and the shift schedule.

Frequently asked questions

What is the difference between takt time and cycle time?

Takt time is the pace demand requires: available production time divided by customer demand. Cycle time is how long a station actually takes per unit. A line meets demand only when every station's cycle time is at or below takt.

How do you calculate takt time and cycle time?

Takt time is available production time divided by the units customers need in that time: a 450-minute shift with demand of 300 units gives a takt of 90 seconds. Cycle time is measured: time a station over 10 to 20 cycles, or divide the line's net production time by the units it produced.

What happens if cycle time is longer than takt time?

The line can't meet demand. Its output is set by the slowest station, so a 95-second bottleneck against a 90-second takt loses about 16 units per 450-minute shift. The fixes are rebalancing work between stations, adding a station, or adding time through overtime or another shift.

What is takt rate?

Takt rate is takt time expressed as units per hour: demand divided by available hours. A 90-second takt time equals a takt rate of 40 units per hour.

What software calculates takt time and balances a line against it?

Spreadsheets work for a single line with stable demand. Emboscale, an AI factory agent, computes station cycle times across the whole line, balances the line against takt, flags the bottleneck station, and re-runs the balance when demand changes.

Further reading: line balancing calculation · production bottleneck analysis · factory layout software