Takt time is the pace of production required to match customer demand, calculated as net available production time divided by the number of units the customer needs in that period. If you have 430 minutes of run time and customers need 215 units, takt time is 2 minutes: one unit must leave the line every 2 minutes.
The word comes from the German Takt, meaning beat or meter, like a conductor's baton. It is one of the core ideas in lean manufacturing because it converts an abstract demand forecast into a number every operator on the line can act on. This post covers the formula, a worked example, how takt differs from cycle time and lead time, and the honest answer to the question every plant eventually asks: what do we do when we can't hit it?
What Is the Takt Time Formula?
The formula is simple division:
Takt time = net available production time ÷ customer demand
Both inputs need to be honest, and both trip people up:
- Net available time is the time the line can actually produce. Start with scheduled shift time, then subtract planned non-production time: lunches, breaks, scheduled meetings, planned maintenance windows. Do not subtract unplanned downtime or changeovers here — those are losses you want takt to expose, not hide.
- Customer demand is what customers will actually pull in the same period, not what sales hopes for and not what the schedule says you should build to refill a warehouse. Use firm orders or a leveled demand rate for the planning period.
A Worked Example (Hypothetical)
The numbers below are a hypothetical illustration, not data from a real plant. Say a packaging line runs one 8-hour shift:
| Input | Value |
|---|---|
| Scheduled shift | 480 minutes |
| Lunch | −30 minutes |
| Two 10-minute breaks | −20 minutes |
| Net available time | 430 minutes |
| Customer demand per shift | 215 units |
| Takt time | 430 ÷ 215 = 2.0 minutes per unit |
Every 2 minutes, a finished unit needs to come off the end of the line. If units come off every 2.2 minutes instead, the line is short about 20 units by end of shift — and somebody is deciding between overtime, expediting, or a missed shipment. For context on the denominator side, the U.S. Bureau of Labor Statistics reports that manufacturing production employees average just over 40 hours per week, with roughly 3 of those hours as overtime (BLS, Manufacturing: NAICS 31-33). Overtime is often exactly where the gap between takt and actual pace goes to hide.
Takt Time vs. Cycle Time vs. Lead Time
These three get mixed up constantly, and the confusion causes real scheduling mistakes. Takt is what the customer requires. Cycle time is what your process delivers. Lead time is what the customer experiences.
| Takt time | Cycle time | Lead time | |
|---|---|---|---|
| What it measures | Required pace to meet demand | Actual time to complete one unit at a process | Total elapsed time from order (or start) to delivery |
| Who sets it | The customer (demand) | Your process (as it really runs) | The whole value stream, including waiting |
| How you get it | Calculated: available time ÷ demand | Measured on the floor or from machine data | Measured end to end, calendar time |
| Typical scale | Seconds to minutes per unit | Seconds to minutes per unit | Hours to weeks |
| Healthy relationship | The target | Slightly below takt | As short as flow allows |
How Do You Implement Takt-Based Pacing?
You implement takt-based pacing by calculating an honest takt, measuring real cycle times, balancing station work below takt, and making the beat visible on the floor. Here is the sequence that works:
- Establish true available time. Pull the real shift calendar — breaks, lunches, planned maintenance, meetings. Resist the urge to pad it.
- Level the demand number. Take the firm demand for the planning period (a week or a month) and convert it to a per-shift or per-day rate. Wildly lumpy demand needs leveling before takt means anything.
- Calculate takt per line or product family. One takt per value stream. A line that runs three product families may need three takt calculations.
- Measure actual cycle time at every station. Not the routing standard — the real number, measured on the floor or captured from machine signals. This is where most plants discover their routing data is fiction.
- Balance stations to slightly under takt. A common target is loading each station to roughly 85–95% of takt, leaving headroom for normal variation. A station loaded at 100% of takt fails every time anything wobbles.
- Make the beat visible. Pace boards, hour-by-hour charts, or live dashboards that show planned vs. actual every hour, not at end of shift. Plants running live factory visibility catch a pace miss in minutes instead of discovering it at the shift handoff.
- Recalculate on a fixed cadence. Demand moves; schedules change. Recheck takt whenever demand shifts materially or the shift pattern changes — monthly is a common rhythm.
What If Cycle Time Exceeds Takt Time?
If cycle time is longer than takt time, the line falls behind on every unit, and the gap compounds all shift. You have four honest options, in rough order of preference:
- Take waste out of the cycle. Watch the station. Split machine time from operator time from waiting. Externalize changeover steps, stage materials at point of use, remove walking and searching. This is the cheapest fix and the most commonly skipped.
- Rebalance the work. If one station runs at 2.4 minutes against a 2.0 takt while its neighbor runs at 1.5, move work elements. The bottleneck station sets the pace of the whole line, so level the load.
- Attack downtime and quality losses. A station whose raw cycle beats takt can still miss it once minor stops, jams, and rework are counted. Effective cycle time — cycle adjusted for uptime and yield — is the number that has to fit under takt.
- Add capacity. Parallel station, added shift, or overtime. Legitimate, but expensive, so it should come after the first three, not instead of them.
The one thing not to do: quietly build ahead into inventory during slow-demand weeks so the miss doesn't show. That hides the problem, ties up cash, and makes the real capacity picture invisible to whoever plans the next quarter.
Why Takt Time Matters Beyond the Line
Takt time turns arguments into arithmetic. Without it, "the line is slow" is an opinion; with it, "station 4 runs 12 seconds over takt on every cycle" is a maintenance ticket, a rebalancing decision, or a capital request with a number attached. It also gives supervisors an early-warning signal: comparing actual output to takt every hour surfaces a bad shift by 9 a.m. instead of at the end-of-day report. That only works if the actual numbers are trustworthy — which is why pairing takt with automatic cycle time capture from the machines themselves, rather than manual tally sheets, changes how fast a plant can react.