Blog / Metrics
Metrics · Guide

Takt Time vs Throughput: How to Compare Them

OL By OEE Lab Editorial |Updated 2 November 2026 |6 min read
Short answer

Takt time is the pace demand asks for, in seconds per unit. Throughput is the pace you really deliver, in good units per hour. To compare them, convert takt: required rate = 3,600 / takt. Example: a 40-second takt needs 90 units an hour, so a throughput of 78 misses it by 12 an hour.

One asks, the other answers

Takt comes from the customer and stays the same however well the line runs. Throughput comes from the line, and a bigger order does not make the line any faster.

Neither one tells you much alone. The gap between them tells you whether the plan will be met.

Takt timeThroughput
QuestionHow often must a unit finish?How many good units came out?
Comes fromDemand and available timeThe line, with all its losses
Usual unitSeconds per unitGood units per hour or shift
Moves whenOrders or shift length changeStops, speed or rejects change
FormulaAvailable time / demandGood units / time
A target and a result, in units that are the inverse of each other.

We use throughput here for good units over a stated time, as in how to calculate throughput. Some people mean the speed of the slowest step, which is the best the line could do, and throughput time is a different metric again.

How to convert one into the other

Takt is seconds per unit and throughput is units per hour, so you divide one into 3,600. Turn either one around, and they can sit on the same line of a report.

Required rate = 3,600 / takt = 3,600 / 40 = 90 units per hour
Time per good unit = 3,600 / throughput = 3,600 / 78 = 46.2 s
Both directions, using the example below. Compare 90 with 78, or 40 s with 46.2 s, and never 40 with 78.

The units per hour calculator does this conversion for you. It helps when one team talks in takt and another in UPH.

Worked example

Example: a hypothetical bottling line has 7.5 available hours, which is 27,000 seconds, and demand for 675 cases a shift. Takt = 27,000 / 675 = 40 seconds, or 90 cases an hour.

The slowest machine has an ideal cycle time of 36 seconds a case, which is 100 cases an hour. The shift delivers 585 good cases, so throughput = 585 / 7.5 = 78 cases an hour.

Ideal rate (36 s per case)100 / h
Required by takt (40 s per case)90 / h
Actual throughput (585 / 7.5 h)78 / h
The line could meet demand, since 100 is above 90. It delivered 78, or 90 cases short over the shift.

Three numbers give the whole picture. The ideal rate of 100 says the line can do it, the required rate of 90 says what it must do, and the throughput of 78 says what it did.

Where OEE fits between them

Good units per scheduled hour divided by the ideal rate is OEE, when scheduled hours match planned production time. So here OEE = 78 / 100 = 78%.

The OEE this line needs is ideal cycle / takt = 36 / 40 = 90%. So the line is 12 points short, and with an ideal rate of 100 cases an hour, each point here is one case an hour; how to set OEE targets builds on this.

What happens when demand moves

Takt moves with demand, and the line does not. The same line can look fine in one month and hopeless in the next, and nothing on the floor has changed.

DemandTaktRequired rateOEE neededAt 78 cases an hour
54050.0 s72 / h72%45 cases too many
67540.0 s90 / h90%90 cases short
81033.3 s108 / h108%225 short, and out of reach
One line at 78 cases an hour, in three different months. Available time stays at 7.5 hours.

At 810 cases, takt is shorter than the ideal cycle, so no amount of OEE work will meet demand in this shift. Even at the ideal rate, 810 x 36 s takes 8.1 hours, which means more time or more capacity.

At 540 cases, running at full throughput builds stock nobody asked for. The line should stop at the plan, as OEE and seasonal demand and OEE with no orders explain.

The time base trap

Takt uses available time, after breaks and planned stops. So throughput must use the same hours, or the comparison is off before you start.

Example: 585 cases over a full 8 paid hours gives 73.1 an hour, and over the 7.5 available hours it gives 78. Only the second may be set against the 90 from takt.

Likewise, a throughput per run hour leaves the stops out. It tells you how fast the line goes, but it cannot tell you whether you met the plan.

Reading the gap

1
Throughput meets the required rate
The plan is safe. Hold the pace and do not build extra stock.
2
Throughput below required, ideal above it
The line can do it, and losses are in the way. Work on stops, slow running and rejects at the bottleneck.
3
Ideal rate below required
Losses are not the main issue. Add time or capacity, or rebalance the slowest step.
4
Throughput far above required
You have spare capacity. Stop at plan, and use the time for changeovers, training and care of the machines.
Compare throughput and the ideal rate with the rate takt asks for, then act on the case you are in.

To find where the losses are, start with the bottleneck and the six big losses. For added capacity, see how to increase production capacity.

How to run this on the floor

  • Post both on one board. Show the required rate from takt next to the good count each hour, as on a takt time board.
  • Count at the end of the line. A count at a faster upstream machine overstates throughput.
  • Recalculate takt when the plan changes. A stale takt makes the whole comparison wrong.
  • Use one case size. A pack of 6 and a pack of 12 are not one unit, so convert first.

Traps in the comparison

  • Setting takt from throughput. Takt then says whatever the line already does, and it can never show a gap.
  • Treating a high throughput as good by itself. Above the required rate, extra units are stock and not sales.
  • Comparing takt with ideal cycle time only. A 36-second ideal under a 40-second takt looks safe, and it leaves only 10% room for all losses.
  • Mixing in the money meaning. In the Theory of Constraints, throughput means money per unit of time, so it cannot be compared with takt at all.

Compare them on your line

Enter your good units and hours in the throughput calculator, and get takt from the takt time calculator. Then track the two against each other with plan attainment.

See it live in Fabrico

To see the gap during the shift, you need a count you can trust. Fabrico takes counts, speed and stops live from PLCs or from external sensors on older machines, and shows OEE per line and shift. See how Fabrico connects machines.

What people ask next

What is the difference between takt time and throughput?

Takt is the pace demand needs, in seconds per unit. Throughput is the pace the line delivered, in good units per hour. Compare them after converting with 3,600 / takt.

How do you convert takt time to units per hour?

Divide 3,600 by takt in seconds. A 40-second takt is 90 units an hour. The units per hour calculator does it in both directions.

Can throughput be higher than takt requires?

Yes, and then the line is building more than was ordered. That stock ties up cash and floor space, so stop at the plan. Use the spare time for changeovers or training.

Is takt time the inverse of throughput?

Only as a formula shape. Takt inverts the required rate, and throughput is the actual rate. They match only when the line delivers exactly what demand asks for.

What if takt time is shorter than my ideal cycle time?

The line cannot meet demand in that available time, even at 100% OEE. Add time or capacity, or cut work from the slowest step. See the line balancing calculator.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · Open the throughput calculator →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES