.png)
Cycle time and takt time both measure production rate, both use the same units (time per unit), and are frequently confused with each other. They measure completely different things.
Takt time is the rate at which your line must produce to meet customer demand. It is set externally, by your customer's order quantity and your available production time.
Cycle time is the rate at which your line actually produces. It is set by your process: your equipment speed, operator pace, and the number of steps in each production sequence.
Takt time is the target. Cycle time is the result. The gap between them is either a capacity buffer (if cycle time is lower than takt time) or a production constraint (if cycle time is higher than takt time).
Cycle time is the time required to complete one unit of production through a specific process step, measured from when the step starts to when it ends.
Formula: Cycle Time = Net Production Time / Units Produced
Where:
A stamping press runs for 375 minutes during a shift (after accounting for downtime and planned stops) and produces 300 parts.
Cycle Time = 375 / 300 = 1.25 minutes per part
The press takes 1.25 minutes on average to stamp one part.
Cycle time is always measured at a specific process step, not for the whole plant. A plant-level average hides bottlenecks. The stamping press at 1.25 minutes per part may be feeding a welding station that takes 2 minutes per assembly, which is the actual constraint.
These two are also frequently confused. Cycle time measures the time to complete one unit through a single step. Lead time measures the total time from order receipt to customer shipment, including waiting time between all steps.
A product might have a cycle time of 4 minutes through assembly but a manufacturing lead time of 5 days because it spends most of that time waiting in queue between process steps. Reducing cycle time improves throughput. Reducing wait time between steps reduces lead time.
Takt time is the available production time per unit of customer demand.
Formula: Takt Time = Available Production Time / Customer Demand
For the full calculation and examples, see Takt Time Formula: What It Is and How to Calculate It.
If a shift has 430 minutes of available production time (480 minutes minus planned breaks and maintenance) and the customer requires 86 units per shift, takt time is 430 / 86 = 5 minutes per unit.
Every 5 minutes, one unit must exit the line. That is the cadence the customer is paying for.
Both are expressed in the same unit (time per unit), which is what makes them directly comparable and also what makes them easy to confuse.
The comparison between cycle time and takt time is where the operational insight lives.
Cycle Time less than Takt Time (CT < TT): capacity buffer
The process completes units faster than the customer requires. If cycle time is 4 minutes and takt time is 5 minutes, the line produces 20% more capacity than current demand needs.
A buffer is not waste. It absorbs demand spikes, scheduled maintenance windows, and unplanned downtime events without impacting customer delivery. A buffer of 10-20% is generally healthy. A persistent buffer of 50% or more suggests the line is over-scheduled or that demand assumptions are significantly higher than actual.
Cycle Time equal to Takt Time (CT = TT): perfectly balanced
The line runs exactly to demand. Every disruption, whether a 5-minute equipment stop or an operator taking a bathroom break outside the scheduled break, creates a delivery delay. Perfect balance is theoretically ideal and practically fragile.
Cycle Time greater than Takt Time (CT > TT): production constraint
The process cannot produce fast enough to meet demand. If cycle time is 6 minutes and takt time is 5 minutes, the line is 20% short. At shift end, 14 units short of the daily requirement.
The appropriate response depends on where the cycle time excess lives:
OEE's Performance component is a direct measurement of the cycle time / takt time relationship at the equipment level.
Performance = Ideal Cycle Time / Actual Cycle Time (simplified)
Or equivalently: how fast is the equipment running relative to how fast it should run?
A Performance score of 85% means the equipment is producing at 85% of its ideal rate. If ideal cycle time is designed around takt time, an 85% Performance score means the equipment is running 15% slower than the production pace the customer requires.
Understanding OEE Performance becomes much more actionable when takt time is used as the reference point for ideal cycle time. See OEE Formula: How to Calculate Overall Equipment Effectiveness for the full component calculation.
Line balancing is the process of distributing work across process steps so that each step runs at approximately the same pace. When the steps are unbalanced, one step is always the constraint and others are always waiting.
The method:
The goal is not to have every step at exactly takt time. It is to have no step above takt time and to minimize idle capacity at steps well below it.
Comparing cycle time to takt time manually at shift end is the minimum viable approach. Real-time comparison during the shift is what enables intervention.
What the automation looks like in practice:
An n8n workflow runs every hour during shift hours. It reads the current shift production count from Google Sheets (where an operator, scanner, or machine updates units completed in real time). It calculates the implied cycle time for the shift so far: elapsed time divided by units produced. It compares that implied cycle time to the takt time stored in a configuration row of the same spreadsheet. If the implied cycle time exceeds takt time by more than a configurable threshold (e.g., 8%), it sends an alert to the line supervisor.
The alert message includes: units produced so far, units required by shift end, implied cycle time, takt time, and units short at the current pace if nothing changes.
This approach gives supervisors the information they need to make in-shift decisions: add operators to a bottleneck station, call maintenance to investigate a slowing machine, or adjust priorities if one product is pulling pace below target.
For the Google Sheets connection that feeds this workflow, see How to Automate Google Sheets with n8n (No Code).
For the full framework for sequencing production monitoring workflows alongside other operations automation, see Manufacturing KPIs: The Metrics Operations Teams Actually Track.
No. Takt time is set by customer demand and represents the required production rate. Cycle time is measured from your process and represents the actual production rate. When they are equal, the line exactly meets demand. When cycle time exceeds takt time, output falls short of demand.
Both are necessary. Takt time alone tells you what the target is, not whether you are hitting it. Cycle time alone tells you how fast you are running, not whether that speed is fast enough. The comparison between them is the metric that drives decisions.
Yes, if demand or available production time changes. In practice, takt time is usually set at the start of the scheduling period and held constant for the shift or the day. Intra-shift takt time changes are rare but occur in highly responsive make-to-order environments.
Cycle time: time to complete one unit through one step. Takt time: required time per unit to meet demand. Lead time: total elapsed time from order to shipment, including waiting time between all steps. Improving cycle time increases throughput. Improving takt time means demand increased (or available time decreased). Reducing wait time between steps reduces lead time.
The Flow Kaizen guide covers how to build the production monitoring workflows that make cycle time vs takt time comparison an automated, real-time function rather than a manual shift-end calculation.
.png)
