Cycle Time Calculator
Finds the average elapsed production time represented by each completed unit. Both the direction of change and the final unit can be checked before accepting cycle time.
Enter the production record
Cycle time
Cycle time: testing the direction of change
Treat the worked value as a baseline, then alter one of available production time, completed units while leaving the other entries fixed. Predict the direction and approximate size of the change before reading the new cycle time. This separates a real relationship in the formula from a typing error or an unnoticed unit conversion.
Build a practical low and high case for cycle time from conditions that can actually occur. The spread in cycle time shows whether a nominal answer is stable or controlled by one uncertain input.
Keep each comparison internally consistent: product, material, tool, machine, geometry, and time boundary must describe a combination that could exist together. In this setup, completed units is part of the same documented condition.
The same production record can also support takt time.
Cycle Time within the stated process boundary
The equation uses available production time, completed units to report cycle time in min/unit. Use net production time on the same boundary as the count; including an idle shift against only its good output changes the question.
A 450-minute run producing 300 units averages 1.5 minutes per unit.
Reversing the calculation to test completed units
Copy the cycle time relationship first, then match each symbol with the labeled available production time, completed units. This keeps the operation boundary visible before arithmetic begins.
A separate dimensional pass is useful for cycle time: simplify the labels without the numbers and confirm that they resolve to min/unit.
Following the symbols from inputs to cycle time
Estimate the order of magnitude before calculating. Then change one input while holding the others fixed and predict whether cycle time should rise or fall.
Rearrange CT = t / Q to recover one entered value. Agreement with the source record checks the algebra in a different direction.
Completed units: credible high and low conditions
Production counts and time records should come from the same shift, line, product definition, and loss convention. The worked condition ties this guidance to available production time rather than to an unlabeled assumption.
Keep those source values with the cycle time result so a corrected dimension, counter, tool record, or bend test can be recalculated from evidence rather than from a rounded answer.
Carry cycle time into the next decision
Store cycle time with its input values, units, date, product or operation, and the equation version. Do not let extra displayed digits imply measurement accuracy the source data did not have.
Separate computational guard digits from usable precision. For cycle time, final rounding should reflect the least certain field and the resolution of the next operation.
Available Production Time does not capture every operating effect
Use net production time on the same boundary as the count; including an idle shift against only its good output changes the question.
Product mix, queues, labor sharing, variability, and changing constraints may require a schedule or simulation rather than a single average. This page preserves available production time and completed units with the answer for that reason.
Before recording cycle time
Does the calculated cycle time replace the governing specification?
No. The calculated cycle time evaluates one stated relationship; drawings, procedures, control plans, equipment limits, and acceptance rules still govern the work.
When should cycle time be recalculated?
Recalculate after a change to available production time, completed units, the operating boundary, or the governing procedure. Start from the revised inputs rather than scaling the previous answer.