.png)
Takt time is the rate at which products must be completed to meet customer demand. It is not the rate at which your equipment runs. It is the rate your customer requires.
The word comes from German: "Takt" means beat or pulse. In manufacturing, takt time sets the production rhythm. If a line is beating faster than takt time, it is producing more than demand requires. If it is beating slower, the line is falling behind.
Understanding takt time does not require a lean certification. It requires one formula and one comparison: takt time versus the actual time your process takes to complete each unit.
Takt Time = Available Production Time / Customer Demand
Where:
Both values must use the same time unit. If available production time is in minutes, customer demand must be expressed as units per that shift or period.
A furniture manufacturer runs one 8-hour shift, five days per week. The shift includes a 30-minute lunch break and two 10-minute breaks (50 minutes total of planned stops).
Available Production Time:
Customer Demand:
Takt Time:
The line must complete one unit every 5 minutes to meet demand without overtime or missed orders.
If the line currently takes 6 minutes per unit (the actual cycle time), it produces 71 units in 430 minutes. The line is short by 15 units per shift. The gap between takt time and cycle time makes the shortfall explicit.
Takt time is not cycle time. Cycle time is how long your process actually takes. Takt time is how long it should take. These numbers are often different. The relationship between them is what drives production decisions. See Cycle Time vs Takt Time: What Is the
Difference and Why It Matters for the full comparison.
Takt time is not a speed target for individual machines. It is a target for the output rate of the line as a whole. Individual machines may run faster or slower than takt time, as long as the line as a whole completes one unit per takt interval.
Takt time does not account for quality losses. Takt time assumes all units produced are good units. If your first pass yield is below 100%, you need to produce more than the takt time interval allows in order to ship the required number of good units. Adjust the required output to account for expected defects.
Takt time changes whenever available production time or customer demand changes. It is not a fixed number.
Common situations that change takt time:
Demand increases. If the customer requires 100 units per day instead of 86, takt time drops from 5 minutes to 4.3 minutes. The line must run faster. If current cycle time is already at 5 minutes, a process improvement or capacity addition is needed.
Demand decreases. If demand drops to 60 units per day, takt time increases to 7.2 minutes. The line has more time per unit than before. Options: run fewer hours, bank the capacity buffer for future demand spikes, or plan maintenance during available slack time.
Shift hours change. Adding a second shift doubles available production time. Takt time doubles (because the same demand is now spread across more available time), which means each shift can run more slowly while still meeting total demand.
Recalculate takt time whenever your schedule or demand changes. Using a takt time from a previous period as if it were current is one of the most common planning errors in manufacturing scheduling.
Takt time is the denominator that makes OEE's Performance component meaningful.
The Performance score in OEE measures how fast equipment runs relative to its ideal (fastest possible) cycle time. But "ideal cycle time" should be set at or near takt time for lines producing to customer demand. An OEE Performance score of 90% on a line running at takt time means the line is producing slightly fewer units per hour than the customer requires.
Tracking takt time alongside OEE reveals whether performance losses translate to actual customer impact. A 10% Performance loss on a line with 20% capacity buffer relative to takt time has no customer impact. The same 10% loss on a line already running at takt time will result in short shipments.
For the OEE formula and component calculations, see OEE Formula: How to Calculate Overall Equipment Effectiveness.
Using gross shift time instead of available production time. Takt time is calculated against net available time after planned stops. Using the full 8 hours instead of 7 hours 10 minutes inflates takt time and makes the production pace look more achievable than it is.
Treating takt time as fixed. Demand changes. Scheduling changes. Recalculate takt time when either changes, not annually.
Ignoring product mix. If a line produces multiple products at different rates, a single takt time does not apply. Calculate takt time per product or per product family, weighting for the mix of demand across each.
Confusing takt time with the scheduling interval. Takt time tells you how fast to produce. It does not tell you when to change over to a new product, how to sequence orders, or how to handle schedule variability. Those are scheduling decisions; takt time is an input to them.
Not accounting for yield. If 5% of units fail inspection, you need to produce 105 units to ship 100. Effective takt time is not 430 / 100 = 4.3 minutes. It is 430 / 105 = 4.1 minutes. Build the yield assumption into the required output figure before calculating takt time.
Takt time is most useful when it is compared to actual cycle time in real time, not at shift end.
A supervisor who reviews yesterday's production report at 8am and discovers the line ran 12% below takt time cannot do anything about the previous shift. The same information delivered at 10am on the day of the shift, when 6 hours remain, creates time to act.
n8n workflow for takt time monitoring:
Schedule Trigger (runs every hour during shift hours)
→ Google Sheets (read current shift production count)
→ Code node (calculate implied cycle time so far this shift)
→ IF node (is implied cycle time > takt time by more than 5%?)
→ Gmail or Slack (send alert to line supervisor with current pace vs takt)
The Code node calculation:
const startTime = new Date($json['Shift Start']);
const now = new Date();
const elapsedMinutes = (now - startTime) / 1000 / 60;
const unitsProduced = Number($json['Units This Shift']);
const taktTime = Number($json['Takt Time Minutes']);
const impliedCycleTime = elapsedMinutes / unitsProduced;
const behindPace = impliedCycleTime > taktTime * 1.05;
return [{ json: {
implied_cycle_time: impliedCycleTime.toFixed(2),
takt_time: taktTime,
behind_pace: behindPace,
pct_gap: (((impliedCycleTime - taktTime) / taktTime) * 100).toFixed(1)
}}];
When the line is running slower than takt time by more than 5%, the alert fires with the current pace and the gap. The supervisor has context to investigate during the shift rather than after it.
For the framework for sequencing this type of monitoring workflow alongside other automation builds, see What Is Business Process Automation for Manufacturers.
Takt time is set by customer demand: it is the rate at which the line must produce to meet orders. Cycle time is set by your process: it is the rate at which the line actually produces. Takt time is a target; cycle time is reality. See Cycle Time vs Takt Time: What Is the Difference and Why It Matters for the full breakdown.
There is no universal benchmark for takt time. The right takt time is whatever your customer demand and available production time calculate to. A takt time of 30 seconds is normal in high-volume automotive assembly. A takt time of 3 days is normal in custom equipment manufacturing. What matters is whether your cycle time meets it.
Recalculate whenever demand or scheduled production time changes. For most manufacturers, this means at the start of each new scheduling period: weekly, monthly, or per customer order.
When cycle time is less than takt time, the line has a capacity buffer relative to current demand. This buffer absorbs variability in demand, unplanned downtime, and changeover time. Some buffer is healthy. A large, persistent buffer suggests the line is over-scheduled or demand is lower than planned.
The Flow Kaizen guide covers how to build the monitoring workflows that connect takt time targets to real-time production data, including how to structure the Google Sheets data model that feeds these comparisons.
.png)
