Takt time: set production pace from customer demand

Use the same production window and demand unit before comparing the required pace with observed work at the line.

Kartik Deshpande··6 min read

Before setting the next shift’s target, check the time available and the units customers require from that same window. Takt time is net available production time divided by customer demand, expressed as time per demanded unit. The Lean Enterprise Institute’s takt definition uses available production time and customer demand to establish the production pace needed to match demand.

If a hypothetical shift has 420 available production minutes and demand for 280 units, takt is 1.5 minutes, or 90 seconds, per unit. That is the required pace. You still need observations of the work, quality outcomes, and stop conditions to judge whether the process can deliver it. A demand target alone supplies no evidence about current capability.

Match the time window to the demand window

Choose the process and product family before calculating. A target for a final assembly line should use the units that line must supply under the agreed plan. Orders for another site or products that bypass the line should not enlarge its denominator. Record the source and acceptance status of the demand so a tentative request does not become a released target without review.

Define available production time from the work calendar. State which breaks, shutdowns, or other periods are outside the production window and apply that policy before viewing the result. If one report subtracts a meal break while another uses the full scheduled shift, the targets will differ even when their demand input matches.

Keep the window aligned across both inputs. Weekly demand needs weekly available production time, while shift demand needs the time available in that shift (using the same work calendar). If you allocate weekly demand among shifts, retain the allocation rule. Dividing all weekly orders by a single shift’s minutes creates a target for work that the shift was never assigned to complete.

Calculate the pace and keep the units visible

Assume a teaching example with an eight-hour scheduled shift, 30 minutes of breaks, and 30 minutes of a planned nonproduction meeting. The policy excludes both periods from available production time. Demand is 280 finished units allocated to that shift, with no beginning finished stock used to cover it. These are hypothetical planning assumptions, not factory benchmarks.

Input or resultCalculationValue
Scheduled time8 × 60480 minutes
Declared nonproduction time30 + 3060 minutes
Available production time480 - 60420 minutes
Demand in the same windowAccepted shift allocation280 finished units
Takt420 / 2801.5 minutes per unit
Equivalent target rate280 / 740 units per available hour

Convert minutes to seconds only after the units are clear: 1.5 × 60 = 90 seconds per unit. The target rate is its reciprocal with a matching time base. Forty units per available production hour does not mean every scheduled clock hour contains 60 production minutes; a break inside an hour changes the quantity that hour can support.

If demand rises to 350 units while available time stays at 420 minutes, takt becomes 1.2 minutes, or 72 seconds. If demand instead stays at 280 and the approved available time rises to 450 minutes, takt becomes about 96.43 seconds. The changed targets follow from different inputs. Neither calculation proves that the line can sustain its new requirement.

Keep the demand target separate from measured work
Takt
Required time per demanded unit
Observed cycle
Measured repeat interval
Good output
Accepted completion count
A changed demand input changes the target; observed work establishes whether the process can meet it.

Compare observed cycles on the same production basis

Measure the operation before assigning a cause to a gap. In another hypothetical case, a serial line must produce one unit every 90 seconds, and a required station repeats its work every 105 seconds. Assume one unit per cycle, no parallel station, and enough material. Under those conditions, that station’s observed pace cannot supply the required output for the window.

An observed repeat interval of 80 seconds would leave 10 seconds relative to the 90-second demand pace, but it would not prove the entire shift is feasible. Changeovers, stops, defects, and upstream supply can reduce delivered good output. Keep those observations available when deciding whether to rebalance work or revise the operating plan.

Use the cycle time measurement method to specify which event is being timed. An automatic machine cycle, an operator’s repeating sequence, and the interval between final completions can describe different boundaries. Comparing one station’s machine-only time with a whole-line target can hide loading or unloading work.

Explore a defined production target

Start with a shift calendar and an accepted demand export, then examine the records behind a repeatable calculation.

Separate product mix from a shared output pace

A shared takt can describe the required final output of a product family, but it does not make every model require the same work. Assume the example’s 280 units include 200 standard and 80 reinforced products. Both count as one finished unit, while the reinforced version requires an extra operation. Preserve that mix when checking the resources that serve only the reinforced version.

You can compare a mix-weighted work requirement with the available labor or equipment time, using approved standards. Keep the individual work contents alongside the average. A feasible average can conceal a run of heavier products that overloads a station during a particular part of the shift. The short-horizon sequence needs its own check after the overall load has been accepted.

Batch processes also need a declared output basis. If a cycle produces several pieces at once, retain both its elapsed batch time and pieces per batch before converting to an equivalent per-piece pace. Include the qualification that pieces emerge together. An equivalent average interval does not promise evenly spaced completions.

Keep loss assumptions separate from the demand calculation

Use an agreed calendar definition for takt, then show the operating losses that threaten delivery. Do not remove an unplanned breakdown from available time after the shift and present the revised takt as the original customer requirement. That would change the target at the same moment the process missed it. Preserve the planned target and explain the lost production opportunity.

If you set an internal operating cycle faster than takt to allow for expected losses, label the distinction and retain the allowance. The customer requirement still comes from demand and available time. Your operating target incorporates an additional assumption that must be reviewed against observed performance and the approved work method.

The OEE formula addresses availability, performance, and quality losses with its own inputs and time rules. Keep its denominator visible if you use that report alongside takt. The two measures answer different questions, and changing a calendar policy to improve one percentage can make comparisons harder to interpret.

Use the gap to select a planning decision

When the required pace is beyond observed capability, record the resource and assumption behind the gap. A staffing change requires qualified people and a feasible work split. Added working time requires an accepted calendar change. Re-sequencing products needs a check on setup and downstream effects, while changing the demand commitment needs its own commercial approval.

Keep those decisions attached to the calculation version. If the target changes after a new order is accepted, preserve the earlier target so the shift review can distinguish added demand from a production miss. Broader manufacturing capacity planning compares resource loads across the planning horizon before a detailed schedule is released.

Permute: shared definitions behind the pace calculation

Permute sells the context layer between business data and the AI tools people already use. We connect approved demand and calendar records from sources such as NetSuite and Excel and implement the period, unit, and exclusion rules your team supplies. The resulting view can retain the records that explain why a shift’s target changed.

We make accepted definitions reusable across reports and applications, with current permissions on the underlying data. An operations manager can inspect the demand allocation behind a target before asking Claude, ChatGPT, or Copilot to explain the accepted figures. Source references let you distinguish a changed order input from a changed calculation rule.

Keep demand approval and line design with the operating team

We are not a forecasting engine, and we do not choose the demand commitment or certify a work method as safe. For this analytical workflow, we read connected records; schedule changes and production release stay with their owners. An output target remains provisional when the demand basis or work calendar has not been approved.

Takt time translates accepted demand and available production time into the required time per unit. The hypothetical shift needs a 90-second pace, while a change in demand or available time changes that target. Observed cycles, product mix, and losses determine whether the operating plan can support it. Retain both the target and the evidence behind the delivery decision.

Review the inputs behind your production pace

Bring the demand allocation, work calendar, and observed performance records. We can review the connections and definitions needed for a traceable operating view.

Questions about takt time

What happens when demand is zero?

The division has no finite result, so label the window as having no defined takt rather than displaying zero seconds. Review whether the process is intended to build stock under a separate approved plan. Do not infer a production requirement from an empty demand field.

Should every shift have the same takt?

Only if the approved time and demand allocations support the same ratio. Different available minutes or assigned quantities can produce different targets. Preserve those inputs so a target difference does not get mistaken for a change in measured performance.

Can I replace the measured cycle time with takt in a report?

Keep the two fields separate. Takt expresses the demand requirement, while observed cycle time records what the process did within its stated measurement boundary. Replacing the observation with the target removes the evidence needed to assess a delivery gap.