Takt Time Calculator: Match Production Pace to Customer Demand
This free takt time calculator computes the production pace a line or cell must sustain to meet customer demand, built for lean leaders, production supervisors, and industrial engineers in discrete manufacturing. Enter shift length, planned stops, shifts per day, and daily demand; the tool returns takt in seconds and minutes plus the required hourly output rate. At the defaults - one 480-minute shift with 50 minutes of planned stops and 400 units of daily demand - takt is 64.5 seconds. Takt is the reference heartbeat for line balancing, staffing, and spotting overproduction before it turns into inventory.
Your numbers
Total paid shift length in minutes.
Breaks, team meetings, planned maintenance, and cleanup. Do not subtract unplanned downtime - takt uses available time.
Number of production shifts running this line or cell each day.
Average daily demand. Use firm orders plus forecast over the planning horizon, not peak demand.
Your results
Estimates only. Takt time assumes level demand; if your demand is lumpy, calculate takt over the interval you actually level-load (week or month).
Get your full takt and line balance report
We will email you a personalized takt analysis with line balancing recommendations for your demand profile, and a Netray lean-ERP specialist will follow up to review it with you.
No spam. Your results stay private. Unsubscribe anytime.
The takt time formula and what belongs in it
Takt time equals available production time divided by customer demand for that period. Available time is paid time minus planned stops - breaks, meetings, planned maintenance - but you deliberately do not subtract unplanned downtime or changeovers. That is the point: if takt is 64.5 seconds and your actual cycle time is 60 seconds, you only have 7% of buffer to absorb every breakdown, jam, and changeover. Demand should be the average over the interval you level-load, typically firm orders plus forecast across a week or month. Using peak-day demand produces an artificially tight takt that drives overstaffing; using optimistic forecasts produces the opposite.
Takt versus cycle time: the comparison that matters
Takt alone tells you nothing until you place actual cycle times against it. Four situations cover almost every line:
- Cycle time well below takt at every station: you are staffed to overproduce - rebalance work or reassign people.
- Cycle time just below takt (90-95%): healthy for stable processes, risky for lines with frequent minor stops.
- One station above takt: that is your bottleneck - every takt-interval it overruns is a late unit at day's end.
- All stations above takt: demand exceeds capacity - you need overtime, another shift, or process improvement, not exhortation.
Using takt in a mixed-model, ERP-driven shop
Classic takt thinking assumes one product on one line, but most SyteLine and LN shops run mixed-model schedules. The practical adaptation is to compute takt at the value-stream level using demand in a common unit - often labor hours or a representative unit of the runner product - and to recalculate whenever demand shifts by more than about 10%. Post the required hourly rate at the line and compare against actuals every hour; a day's miss found at 9 a.m. is recoverable, one found at shift end is not. Feeding actual counts back from the floor hourly is exactly the kind of data loop that separates plants that use takt from plants that just talk about it.
How Netray helps you run to takt
Netray implements the ERP and shop floor plumbing that makes takt operational: demand aggregation out of Infor SyteLine or LN to compute value-stream takt automatically, hour-by-hour production boards fed by real shop floor transactions, and alerts when actual rate falls behind required rate. For clients running high-mix aerospace and electronics work, we add on-prem AI scheduling assistance that re-sequences orders when demand or capacity shifts, keeping the released schedule consistent with takt instead of fighting it. The typical starting point is one value stream instrumented in 4-6 weeks.
Frequently Asked Questions
What is the difference between takt time and cycle time?
Takt time is set by the customer: available time divided by demand, the pace you must achieve. Cycle time is set by your process: how long it actually takes to produce one unit. Takt is a target, cycle time is a measurement. Line balancing is the work of arranging operations so every station's cycle time sits safely below takt without excessive idle time.
Should changeovers be subtracted from available time?
In the strict lean definition, no - changeovers are a loss to be reduced, and hiding them inside available time removes the pressure to shrink them. Practically, high-mix shops with unavoidable long changeovers sometimes subtract a planned changeover allowance to get a workable takt. If you do, track it explicitly and treat every minute of that allowance as an SMED improvement target, not a fixed cost.
How often should I recalculate takt time?
Recalculate whenever demand or available time changes materially - a good rule of thumb is any sustained shift of 10% or more, and at minimum monthly. Chasing daily demand noise with daily takt changes destabilizes staffing and line balance. Most plants set takt for a fixed interval (two to four weeks), buffer short-term variation with small finished-goods or FIFO buffers, and re-level at the boundary.
Have Netray wire your takt calculation directly to live demand and shop floor counts in SyteLine or LN.
Related Tools
Cycle Time & Capacity Calculator
Translate cycle time, parallel stations, shift pattern, and realistic utilization into hourly, daily, and annual production capacity.
Discrete ManufacturingOEE Calculator (Overall Equipment Effectiveness)
Break your Overall Equipment Effectiveness into availability, performance, and quality, and see how far you sit from the 85% world-class benchmark.
Discrete ManufacturingProduction Scheduling Maturity Assessment
Score your scheduling practice across method, capacity logic, adherence, and shop floor feedback - and see the staged path to finite-capacity scheduling.
Go Deeper
Aligning Lean Manufacturing with Your ERP
Align lean manufacturing with ERP: kanban and MRP coexistence, backflushing, value stream costing, pull signals in SyteLine and LN, plus AI-driven kaizen.
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.