Takt time vs cycle time: two clocks, one line.

Takt time and cycle time get mixed up on the shop floor every day, yet they answer completely different questions. One is set by your customer; the other is set by your process. Confuse them and you either build too slow to ship or too fast to sell. Here is the clean distinction, with the numbers that make it obvious.

Two different clocks

Think of a line running to a heartbeat. Takt time is the beat the customer demands — how often a finished unit must come off the line to exactly meet orders. Cycle time is the beat your process can actually deliver — how long it really takes to complete one unit. The whole game of line balancing is making your cycle time fit inside the takt beat.

The word takt is German for a batōn's beat or rhythm. That is the right mental image: takt is externally imposed by demand, cycle time is internally measured on the floor, and the gap between them tells you whether you are ahead of or behind the customer.

Takt time: the demand rhythm

Takt time is pure arithmetic from demand and available time:

Net available time is the shift length minus planned stoppages: breaks, meetings, planned maintenance. It is not the full clock time. If you run one 8-hour shift with 30 minutes of breaks, net available time is 450 minutes. Against a demand of 300 units, takt time is 450 / 300 = 1.5 minutes (90 seconds) per unit. That is the pace the whole line must match. Compute it directly with the takt time calculator.

Cycle time: what the process actually does

Cycle time is measured, not demanded. It is the time between one finished unit and the next at a given station or for the whole line. For a single process it is the hands-on time to complete the operation; for a line, the bottleneck cycle time (the slowest station) sets the line's true output rate.

There is an important cousin here. Machine cycle time plus load/unload and walk time gives the operator cycle time, and it is the operator cycle time that must sit under takt. Get the full method and the WIP-and-throughput link in our cycle time calculation guide.

Where lead time fits

People throw a third term into the mix — lead time. Keep them separate:

• Takt time — the demand rate. Customer-driven.
• Cycle time — active processing time per unit. Process-driven.
• Lead time — total elapsed time from order to delivery, including all the queuing and waiting. This is the one the customer feels.

By Little's Law, lead time = work-in-progress / throughput. Because throughput is capped by your bottleneck cycle time, cutting cycle time below takt lets you drain WIP, and less WIP directly shortens lead time. That is the chain that connects all three.

Side-by-side

Worked example: balancing a sub-assembly line

An MSME in Coimbatore assembles pump housings. One shift = 8 h = 480 min; breaks and standup meeting = 30 min, so net available time = 450 min. Customer demand = 300 units/shift.

Step 1 — takt time: 450 min / 300 = 1.5 min = 90 s/unit. A finished housing must leave the line every 90 seconds.

Step 2 — measure station cycle times:

Step 3 — find the constraint: Station 3 at 105 s is above the 90 s takt. The line can only deliver one unit every 105 s, so real output is 450×60 / 105 = 257 units — 43 units short of the 300 needed.

Step 4 — rebalance: Move the bolt pre-fit into Station 2 (raising it to 88 s) and leave final torque in Station 3 (dropping it to 84 s). Now every station is under 90 s, the bottleneck cycle time is 88 s, and output = 450×60 / 88 = 306 units. Demand met, with a thin buffer. Lock the takt-to-cycle target at roughly 85–90% so variation does not push you back over the line.

Common mistakes

• Using gross shift time for takt. Always subtract planned breaks and meetings first, or your takt is falsely generous.
• Balancing to average, not bottleneck. The slowest station sets output, not the line average. Fix the constraint.
• Confusing cycle time with lead time. A 90 s cycle time can still sit inside a three-day lead time if WIP is piled between stations.
• Ignoring changeover. If you build a mix, changeover eats available time and raises effective takt — account for it, or use the OEE calculator to see where the time really goes.
• Chasing cycle time far below takt. Running much faster than takt just builds inventory you cannot sell. Match the beat, do not beat it.

One more discipline point: the moment demand changes, takt changes, and every station target moves with it. Recompute takt whenever the order book shifts, and re-check that your measured cycle times still fit underneath.

Where does drawing quality touch all this? A rebalanced line only holds if every part is inspected to print. CadNexa's auto-ballooning tool tags each dimension and tolerance straight off the PDF so inspection stays fast and error-free while your stations run to takt.

Frequently asked questions

What is the difference between takt time and cycle time?

Takt time is the customer demand rate (available time / demand). Cycle time is how long your process actually takes per unit. For a line to keep up, cycle time must be less than or equal to takt time.

What is the formula for takt time?

Takt time = net available production time / customer demand. For 450 minutes against 300 units, takt is 1.5 minutes (90 seconds) per unit.

Should cycle time be higher or lower than takt time?

Lower. If cycle time exceeds takt you cannot meet demand. Most lean lines target cycle time at about 85–90% of takt for a buffer.

How do takt and cycle time relate to lead time?

Lead time is total order-to-delivery time including queues. Cutting cycle time below takt lets you reduce WIP, which shortens lead time.