How the takt time calculator works
Takt time tells you how often a unit has to be finished to match customer demand. The calculator first works out the available production time from the shift length, breaks and number of shifts, then divides it by demand.
Cycle time and lead time answer different questions, so they are treated separately. For the difference, read takt time vs cycle time vs lead time.
Use net available time: breaks and planned stops removed, and demand for the same period.
Worked example
Load the example. A cell runs one 8-hour shift with 60 minutes of breaks, so 420 minutes are available. Customer demand is 210 units a day.
| Step | Calculation | Result |
|---|---|---|
| Available time | 8 × 60 − 60 | 420 min |
| Takt time | 420 ÷ 210 | 2 min (120 sec) |
| Cycle vs takt | 144 sec vs 120 sec | 20% too slow |
| Capacity at 144 sec | 25,200 ÷ 144 | 175 units a day |
How to read your result
If your cycle time is above takt, the process cannot meet demand at its current design. If it is below takt, look at what the average hides: downtime, changeover, starvation and quality loss. The line balancing guide shows how to distribute work across operators, and value-stream mapping shows where the queues are.
- Cycle above takt: reduce work content, add capacity or rebalance the work.
- Cycle below takt: check that effective capacity, not just the average cycle, covers demand.
- Operators: the minimum is a lower bound. Precedence and walking usually add one.
Common mistakes with takt time
Takt is simple to calculate and easy to misuse.
- Treating takt as a target speed for each machine instead of the pace demand requires.
- Using gross shift time and forgetting breaks and planned stops.
- Dividing by a different period than the demand covers.
- Not recalculating takt when demand or available time changes.
- Comparing takt with a machine cycle rather than the full station or operator cycle.