Cycle time is the pace your process actually runs at; takt time is the pace customer demand requires. The healthy relationship is simple: every station's cycle time should sit just below takt time, close enough to be efficient, with enough headroom to absorb normal variation. When cycle time climbs above takt, the line falls behind every cycle.
These two numbers get confused constantly, and the confusion is expensive: it drives wrong staffing decisions, wrong capital requests, and schedules that quietly fail. This is a comparison guide focused on the relationship between the two, why cycle has to sit under takt, what the gap between them means for staffing and cost, and how to read that gap on a balance chart. For the deep mechanics of each number on its own, we have dedicated guides: how to measure and find the bottleneck in cycle time and the formula and worked example in takt time. This post is about how they fit together.
What is the difference between cycle time and takt time?
The core difference is that takt time is calculated from demand while cycle time is measured on the floor. Takt is a target you are handed by the customer; cycle time is a result your process produces. One is what you need, the other is what you have.
| Cycle time | Takt time | |
|---|---|---|
| What it is | Actual time to complete one unit at a process | Required pace to match customer demand |
| Who sets it | Your process, as it really runs | The customer (demand) |
| How you get it | Measured on the floor or from machine data | Calculated: net available time ÷ demand |
| Changes when | Methods, tooling, staffing, or downtime change | Demand or the working schedule changes |
| Healthy value | Just below takt | The target everything is measured against |
A quick numeric anchor. If a line has 430 minutes of net available time and the customer needs 215 units, takt is 2.0 minutes, one unit must leave the line every 2 minutes. If the slowest station takes 2.2 minutes to do its work, that is its cycle time, and the line is short about 20 units by end of shift. The gap between 2.0 and 2.2 is not a rounding error; it is the shortfall, compounding every cycle.
Notice the direction of causation. You do not get to negotiate takt, it moves only when demand or the schedule moves. Cycle time is the lever you actually control: methods, tooling, layout, staffing, and reliability all push it up or down. So the practical question is never how to change takt but how to get every station's cycle time to land in the healthy band under the takt you have been handed.
Why must cycle time sit just below takt time?
Cycle time has to sit just below takt because a station loaded right at takt fails the moment anything wobbles, and a station loaded well below takt wastes capacity. The word doing the work is just there is a target band, and both sides of it cost you.
Cycle time above takt is the obvious failure: the station cannot keep up with demand, so the line produces less than customers need and the shortfall compounds all shift. This station is the constraint, and no amount of speed elsewhere fixes it.
Cycle time far below takt is the quieter, more common waste. A station cycling at 1.2 minutes against a 2.0 takt looks great on a stopwatch, but it means the station has capacity demand does not need. Left unmanaged, that spare speed turns into overproduction (making ahead into inventory) or overstaffing (an operator who could be balanced across two stations). Faster than takt is not better; it is just a different waste.
Cycle time just below takt is the target, typically loading a station to roughly 85–95% of takt. That small gap is the buffer that absorbs the normal jitter of real work: the slightly slow cycle, the momentary reach for a part, the minor stop. A station loaded to exactly 100% of takt has no buffer and misses the beat every time reality is imperfect, which is always.
What does the gap between cycle time and takt tell you about staffing?
The gap between cycle time and takt is, in effect, a staffing and capacity signal. Read it right and you can size a line without guessing.
Sum the cycle-time work content across all stations, divide by takt, and you get the theoretical minimum number of stations or operators the line needs. If total work content is 12 minutes and takt is 2 minutes, you need at least six balanced stations. Fewer than that and someone is over takt; many more than that and you are carrying stations that are mostly idle. This is the arithmetic behind line balancing spreading the total work so every station lands in that healthy band just under takt, rather than one drowning while its neighbor waits.
The gap also tells you where not to spend. Speeding up a station that already sits well below takt buys you nothing the line can use, it just builds inventory in front of the real constraint. Money and effort belong on the station whose cycle time is closest to (or over) takt. Chasing seconds on a non-bottleneck is one of the most common and expensive misreads on a plant floor.
How do you read cycle time and takt on a balance chart?
A balance chart puts one bar per station against a single takt line, and the whole health of a line is visible in one picture. Bars below the line are stations with headroom; a bar touching or crossing the line is the constraint. The shape tells you the story:
What to look for, in order:
- Any bar over the line. That station is the constraint and sets the line's real output. Fix it first, with waste removal, faster changeovers or rebalancing, before anything else.
- Uneven bar heights. A jagged chart means work is poorly balanced. The total work might fit under takt, but it is piled unevenly, so one station chokes while another idles. Level it.
- Everything hugging the line. If every station sits at 98% of takt, the line has no buffer anywhere and will miss demand on any bad day. You may need more headroom or to attack variation directly.
- Everything far below the line. Lots of headroom on every station means you may be overstaffed for the current demand, or takt has loosened since the line was designed. Recheck the staffing math.
Why does the effective cycle time matter more than the raw number?
The number that actually has to fit under takt is effective cycle time, raw cycle time adjusted for downtime and rework, not the clean cycle you time on a good run. A station cycling at 100 seconds but down 15% of the time behaves like a 118-second station, and against a 120-second takt it has almost no headroom left even though the stopwatch said it was comfortable.
This is why comparing cycle time to takt on paper can mislead. A balance chart built from ideal cycles can show every station safely under takt while the line still misses demand daily, because the chart never counted the micro-stops, the jams, and the rework that eat the real gap. The honest comparison uses effective cycle time captured from how the line actually runs, including the bad cycles the stopwatch study skipped.
That is also the argument for measuring cycle time continuously rather than in a one-day study. When cycle timestamps come straight from the machines and stations and feed a single operational layer, effective cycle time is computed from every cycle on every shift, so the comparison to takt reflects reality, not a good Tuesday. Harmony connects the machines, software, and paperwork on a line into one live layer no rip-and-replace, so the gap between cycle and takt is measured from source signals rather than reconstructed from a clipboard. When CLS moved off paper logging that gap became visible during the shift instead of at the next morning's report.
Keep the relationship in your head and it stays simple: takt is the beat, cycle time is whether you can keep it, and the small gap between them is the room you need to breathe. Size the line to that gap, watch the effective number, and put your effort on the station closest to the line.