What Is Takt Time?
Also known as: takt, takt rate
Definition
Takt time is the rate at which a process must complete one unit to meet customer demand, calculated as available production time divided by demand for that period. It sets the pace a line must sustain, not the speed it can achieve.
Takt Time Explained
Takt time comes from the German word for a musical beat, and that is exactly its function: it is the drumbeat of customer demand translated into seconds per unit. The formula is available production time divided by customer demand over the same interval. Available time excludes planned breaks, scheduled meetings, and planned maintenance, but it does not subtract downtime, scrap, or inefficiency. Those losses are what the line must overcome to hit takt, so removing them from the denominator hides the very problem takt is meant to expose.
Takt is a demand-side number, which means it changes when the customer changes and never because the plant got faster. If demand rises from 400 to 500 units per week on the same schedule, takt time shortens and the line must be rebalanced, staffed differently, or given more shifts. Recalculating takt monthly or at each production plan cycle is common practice; recalculating it daily creates churn in line balancing that costs more than it saves.
The practical use of takt is line balancing. Each station's work content is compared against takt, and content is redistributed so that no station exceeds it. Because variation is real, most designers target a planned cycle time of roughly 85 to 95 percent of takt, leaving deliberate headroom for minor stops and operator variation. A line balanced exactly to takt will miss demand every day it has a single hiccup.
In an ERP context, takt rarely appears as a stored field. It is derived from the demand plan and the shop calendar, then compared against routing run times. Where an MRP system schedules by lot and lead time, takt-driven flow schedules by rate, so plants running mixed-model lines often maintain a rate-based build plan alongside ERP work orders and use backflushing to reconcile the two.
Why It Matters
- Turns an abstract sales forecast into a concrete, second-level target every operator on the line can see and act on.
- Provides the reference against which station work content is balanced, exposing overloaded stations that create the line's true constraint.
- Drives staffing math directly: total work content divided by takt time gives the theoretical minimum number of operators.
- Makes demand changes visible as an operational requirement instead of a spreadsheet revision nobody on the floor ever sees.
In Practice
A plant runs two 8-hour shifts with 30 minutes of breaks and 10 minutes of startup meeting per shift, giving 2 x 440 = 880 available minutes per day. Customer demand is 220 units per day. Takt time is 880/220 = 4 minutes per unit. If total hand work content across the line is 34 minutes, the theoretical minimum staffing is 34/4 = 8.5, so nine operators. Designers then balance to a planned cycle of about 3.6 minutes to absorb variation, and only afterward compare that against actual measured cycle time.
Frequently Asked Questions
Should breaks and downtime be subtracted from available time?
Subtract planned, scheduled non-production time such as breaks, shift meetings, and planned maintenance windows. Do not subtract unplanned downtime, changeovers, or scrap allowance. Takt represents the pace required to satisfy the customer, so building known losses into the denominator produces an artificially generous target that hides the improvement work the line actually needs.
Does takt time apply to low-volume or job-shop production?
Partially. Classic takt assumes repetitive demand for a comparable unit. In high-mix, low-volume plants, teams often use a weighted takt based on standard work content per unit, or apply takt only to a repeating family of parts. For pure one-off engineering work, throughput and constraint management are usually more useful pacing tools.
Related Terms
Cycle Time
Cycle time is the actual elapsed time a process takes to complete one unit, measured from the start of work on that unit to the start of work on the next. It describes what the process does, not what the customer requires.
Bottleneck
A bottleneck is the resource in a process whose available capacity is less than the demand placed on it, making it the step that limits total system output. Every other resource can only run as fast as the bottleneck permits.
Lean Manufacturing
Lean manufacturing is a production philosophy derived from the Toyota Production System that maximizes customer value by systematically identifying and eliminating waste, defined as any activity that consumes resources without adding value the customer would pay for.
Go Deeper
Takt Time Calculator
Compute the takt time your line must hit to meet customer demand, plus the required hourly rate for supervisors and schedulers.
Finite Capacity Scheduling: A Practical Guide
Finite capacity scheduling explained: how it differs from infinite MRP loading, APS options for SyteLine and LN, data prerequisites, and AI-assisted scheduling.
MES-ERP Integration for Discrete Manufacturing
MES-ERP integration guide for discrete manufacturers: architecture patterns, ISA-95 mapping, SyteLine and LN connectors, costs, timelines, and AI-driven sync.
Working with Takt Time in a live environment? Our engineers do this every day - and our AI agents automate most of it.