Takt Time vs Cycle Time: How to Balance a Line to Customer Demand

People mix up takt time and cycle time all the time, and the confusion is understandable because both are measured in seconds per unit. But they answer different questions. Takt time asks how fast you need to go to satisfy the customer. Cycle time tells you how fast you are actually going at a given step. Line balancing is the work of lining those two numbers up so the factory produces exactly what demand calls for, no more and no less.

This guide walks through both formulas, shows the difference next to lead time, and runs a full worked example with real numbers so you can see how a bottleneck station quietly caps your output. By the end you will know how to calculate takt, measure cycle time, size the number of stations you need, and spot the common mistakes that make a line miss its target even when everyone looks busy.

What takt time is

Takt time is the pace of customer demand expressed as a unit of time. The word comes from the German Takt, meaning a beat or rhythm, like a metronome for the factory. If the customer wants a finished unit every 30 seconds, then takt time is 30 seconds per unit and every part of the line should aim to release a unit at that beat.

The formula is simple:

Takt time = available production time per shift / customer demand per shift

Available production time is not the whole shift. You subtract planned stops such as breaks, meetings, and scheduled maintenance, because those are times the line was never meant to run. Customer demand is the number of units you actually need to ship in that window. The result is a target that comes entirely from the market, not from your machines. You can measure and improve cycle time, but takt is handed to you by demand. Use the takt time calculator to run this for your own shift pattern.

What cycle time is

Cycle time is the actual elapsed time to complete one unit at a process. It is something you observe and measure with a stopwatch, not something you calculate from demand. If a worker at an assembly station finishes one unit every 28 seconds, the cycle time at that station is 28 seconds.

There is an important distinction here between station cycle time and line cycle time. Station cycle time is the time for a single step. Line cycle time, sometimes called effective cycle time, is the pace at which finished units leave the whole line, and it is set by the slowest station. That slowest station is the bottleneck. It does not matter how fast the other stations run, because the line can only push out product as quickly as its slowest point allows.

So when someone asks for the cycle time of a line, the honest answer is the bottleneck’s cycle time. That single number governs throughput. You can confirm your own figures with the cycle time calculator.

Takt vs cycle vs lead time

Three timing terms get tangled together: takt time, cycle time, and lead time. They describe different things, and keeping them separate is half the battle. Here is a compact comparison.

Lead time is the full journey from start to finish, including all the waiting between steps. It connects to Little’s Law, which states that work in process equals throughput multiplied by lead time. Rearranged, lead time equals work in process divided by throughput, so if you want shorter lead times you either raise throughput or cut the inventory sitting in the line. The Little’s Law calculator makes this relationship easy to test with your own numbers.

How to calculate takt time

Calculating takt time takes three steps.

First, find your available production time. Start with the scheduled shift length and subtract every planned stop. Say you run one 8-hour shift, which is 480 minutes, and you have 30 minutes of breaks and planned stops. That leaves 450 minutes of available time, or 27,000 seconds.

Second, find the customer demand for that same window. Suppose the customer needs 900 units per shift.

Third, divide.

Takt time = 27,000 seconds / 900 units = 30 seconds per unit

That is the beat. Every 30 seconds, one finished unit needs to come off the line to keep pace with demand. Notice that only planned time counts. Unplanned downtime such as breakdowns is not subtracted here, because takt describes the ideal demand pace, not your real performance. Real performance and losses are what the OEE calculator handles separately.

How to calculate and measure cycle time

Cycle time is measured, not derived. Stand at a station and time how long it takes to complete one unit, from the moment work begins to the moment it is ready to pass on. Take several readings, because human work varies, and use a representative figure rather than the single fastest run you happened to catch.

Once you have cycle times for every station, the line cycle time is simply the largest of them, since the slowest station sets the beat for the whole line. If you are designing a line rather than measuring an existing one, you estimate task times from standard work and add them up per station. Either way, the key output is the bottleneck cycle time, because that is what you compare against takt.

The balancing rule: cycle time vs takt

Here is the rule that ties everything together. To meet demand without overproducing, every station’s cycle time must be at or below takt time.

If a station’s cycle time is above takt, that station cannot keep up and the line falls short of demand. If a station’s cycle time is far below takt, that station sits idle part of the time, which is wasted capacity and an invitation to overproduce. The goal is to get each station close to takt but never over it.

Let us run the numbers from the takt example above. Available time is 27,000 seconds and takt is 30 seconds per unit. Suppose the current process has five stations with cycle times of 24, 28, 33, 22, and 26 seconds.

The bottleneck is station 3 at 33 seconds, which is above the 30 second takt. Because the line can only move as fast as its slowest station, throughput is capped at 27,000 / 33, which comes to about 818 units. That is well short of the 900 units the customer wants. Everyone can be working hard and the line will still miss target, because one station is over takt.

After rebalancing so the busiest station runs at 29 seconds, capacity becomes 27,000 / 29, which is about 931 units. That clears the 900 unit demand with a small buffer. The line now makes what the customer needs without piling up excess.

Line balancing to takt

Line balancing is the practice of distributing task work across stations so each one runs close to takt without going over. The first question is always how many stations you need at minimum.

Minimum stations = sum of all task times / takt time

In our example the five task times add up to 133 seconds. Divide by the 30 second takt and you get 4.43, which rounds up to at least 5 stations. You cannot have a fraction of a station, so you always round up. This tells you the floor. In practice you may need more stations than the minimum because tasks cannot always be split cleanly, and some work has to stay together.

Balancing is rarely a one time exercise. When demand rises, takt shrinks, and a line that was balanced yesterday may now have stations over takt. When demand falls, takt grows and you can consolidate stations. The line balancing calculator handles the arithmetic of assigning tasks and checking each station against takt, so you can test scenarios before you move anyone on the floor.

Common mistakes

The first mistake is treating takt and cycle time as the same number. They are not. Takt comes from the customer and cycle time comes from your process. Setting them equal by accident hides the very gap you are trying to manage.

The second mistake is forgetting to subtract planned stops when calculating takt. If you use the full 480 minute shift instead of 450 available minutes, your takt comes out too high and you plan the line to run slower than it really needs to, which quietly builds in a shortfall.

The third mistake is ignoring the bottleneck. Improving a station that was already faster than takt does nothing for output. Only work on the slowest station moves the line. A fourth common error is chasing a cycle time far below takt in the name of efficiency, which just produces inventory faster than the customer can absorb it.

When takt does not apply

Takt time works beautifully for steady, repetitive, high-volume production where demand is reasonably level. It struggles in low-volume, high-mix environments where every order is different and demand is lumpy. If you build custom machines one at a time, or your product mix swings wildly week to week, a single takt beat does not describe reality.

In those settings, teams lean on other tools. Little’s Law still helps you reason about lead time and work in process even without a fixed takt, and finite capacity scheduling or pull systems such as kanban manage flow when a rhythmic beat is not practical. The point is not to force takt onto work that does not fit it, but to use the right lens for the demand pattern you actually have. Browse the full Lean Production hub for the tool that matches your situation.

Three expert tips

Balance to about 85 to 90 percent of takt, not to takt exactly

If you balance every station to hit takt on the nose, you have zero room for the normal variation that real work always carries. A part sticks, an operator sneezes, and you are already behind with no way to catch up. Leaving a small buffer under takt, so busy stations run at roughly 85 to 90 percent of the beat, gives the line the slack it needs to recover from minor hiccups and still meet demand.

Recalculate takt every time demand changes

Takt is not a permanent number. It moves whenever customer demand or your available time changes. A jump in orders shrinks takt and can push previously fine stations over the line. Make recalculating takt a routine step whenever the demand plan updates, and check your station cycle times against the new beat before the shift starts rather than discovering the gap halfway through.

Separate takt planning from OEE reality

Takt tells you the pace you need in a perfect world with no unplanned losses. OEE tells you how much of that ideal you actually capture once availability, performance, and quality losses are counted. Keep them in separate calculations. If you bury real downtime inside your takt math, you lose the clean demand signal that makes takt useful in the first place, and you cannot tell whether a shortfall is a balancing problem or a reliability problem.

Free lean calculators for this

You do not have to do any of this arithmetic by hand. These free tools cover the whole workflow from setting the demand beat to balancing the line and checking real performance.

• Takt Time Calculator for the demand drumbeat from your shift and order figures.
• Cycle Time Calculator to find your station and line cycle times.
• Line Balancing Calculator to assign tasks and check each station against takt.
• OEE Calculator to measure real performance against the ideal.
• Little’s Law Calculator for lead time, throughput, and work in process.
• The full Lean Production hub for every related tool in one place.

Frequently asked questions

Is takt time the same as cycle time?

No. Takt time is the required pace set by customer demand, calculated as available time divided by demand. Cycle time is the actual time a process takes to make one unit, which you measure. They can happen to be equal, but they come from different sources and answer different questions.

What happens if cycle time is higher than takt time?

The line cannot keep up with demand. Since throughput is set by the slowest station, a bottleneck above takt caps output below what the customer needs. In our example a station at 33 seconds against a 30 second takt limited the line to about 818 units instead of the required 900. You fix it by moving work off the bottleneck or adding a parallel station.

Can cycle time be less than takt time?

Yes, and it usually should be by a small margin. A cycle time just under takt means the station can comfortably meet the beat with a little buffer for variation. But a cycle time far below takt signals idle capacity, which risks overproduction and wasted resources.

How do breaks affect takt time?

Breaks and other planned stops reduce your available production time, which raises takt time. In the worked example, 30 minutes of breaks cut a 480 minute shift down to 450 minutes of available time, giving a 30 second takt. If you forget to subtract breaks, your takt comes out too high and you plan the line to run slower than demand actually requires.

How do I calculate takt time for multiple products?

For a mixed line you calculate a weighted takt based on total demand across all products in the shared window, or you calculate separate takt times per product family if they run in dedicated blocks. The core formula stays the same: available time divided by the demand you are trying to satisfy in that time.

What is the difference between takt time and lead time?

Takt time is the pace at which units need to leave the line, measured in seconds per unit. Lead time is the total elapsed time for one unit to travel through the whole system, including waiting, and is usually measured in minutes, hours, or days. Lead time relates to work in process through Little’s Law.

How many stations do I need to meet takt?

At minimum, divide the sum of all task times by the takt time and round up. In the example, 133 seconds of total task time divided by a 30 second takt gives 4.43, which rounds up to at least 5 stations. You may need more if tasks cannot be split cleanly across stations.

Does takt time change over time?

Yes. Takt changes whenever customer demand or available production time changes. Higher demand shrinks takt and demands a faster beat, while lower demand grows takt and lets you consolidate stations. Recalculate it every time the demand plan updates.

Should I balance stations exactly to takt?

No, leave a small buffer. Balancing every station to hit takt exactly leaves no room for normal variation, so any small disruption puts you behind. Aiming for roughly 85 to 90 percent of takt on the busiest stations gives the line slack to recover and still meet demand.

Does takt time include unplanned downtime?

No. Takt uses only planned available time, so you subtract scheduled breaks and maintenance but not breakdowns. Unplanned losses belong in your OEE calculation, which measures how much of the ideal takt pace you actually achieve. Keeping them separate preserves a clean demand signal.

What if my process cannot get below takt time?

If a task genuinely cannot be shortened or split to fit under takt, you add capacity by running that step in parallel, so two or more units are processed at the same time. This effectively halves the station’s contribution to line cycle time and lets the line clear demand.

Does takt time apply to low-volume, high-mix production?

Not cleanly. Takt assumes fairly level, repetitive demand. When every order is different and demand is lumpy, a single beat does not describe the work well. In those cases teams rely on pull systems such as kanban, finite capacity scheduling, and Little’s Law reasoning instead of a fixed takt.

Takt time and cycle time are two of the most useful numbers in lean production once you stop confusing them. Takt tells you the beat the customer expects, cycle time tells you the beat your process actually delivers, and line balancing is the ongoing work of keeping every station under takt so you make exactly what demand calls for. Run your own figures through the calculators above, watch for the bottleneck, and revisit the numbers whenever demand moves.