Cycle Time Calculator
CT = Total Time / Units Produced. Best when downtime is negligible or already excluded.
Total run time for the production period (shift, batch, or measurement window).
Total number of parts or items produced during the production period (include defects).
Enter Production Data
Fill in total production time and units produced to calculate your cycle time, production rate, and efficiency metrics.
How to Use the Cycle Time Calculator
Choose Your Formula Mode
Select Basic for a quick calculation using total run time and units produced. Choose Net Production Time if your shift includes scheduled breaks or maintenance you want to exclude. Use Quality-Adjusted if you want to measure cycle time only against good, defect-free units — the most rigorous approach used in Lean manufacturing.
Enter Production Data
Input the total production time in your chosen unit (seconds, minutes, hours, or days), then enter the number of units produced in that period. For Net or Quality-Adjusted modes, also enter planned downtime and defective unit counts. Use data from actual production logs, shift reports, or time studies for the most accurate results.
Compare with Takt Time (Optional)
Expand the Takt Time section and enter your available production time and customer demand for the same period. The calculator will show you takt time, an efficiency percentage, and a visual comparison bar. An efficiency below 95% means your process cannot meet customer demand at its current pace — action is required.
Analyze Bottlenecks and Export
Use the Multi-Step Bottleneck Analysis to enter individual step cycle times and instantly identify which step is constraining your throughput. Enable the Capacity Estimator to project annual production output. Once satisfied with your analysis, export results to CSV for reports or print for shop floor review.
Frequently Asked Questions
What is the difference between cycle time and takt time?
Cycle time is a measurement — it tells you how long your process actually takes to produce one unit based on real production data. Takt time is a target or constraint derived from customer demand: it is the maximum time you are allowed to spend on each unit if you want to exactly satisfy orders. The formula for takt time is available production time divided by customer demand. When cycle time equals takt time, your process is perfectly synchronized with demand. When cycle time exceeds takt time, you cannot meet orders at the current pace and have a capacity problem. When cycle time is less than takt time, you have surplus capacity. Comparing these two metrics is the foundation of lean production scheduling.
Which cycle time formula should I use — basic, net, or quality-adjusted?
Use the basic formula when your total production time figure already excludes downtime, or when planned downtime is negligible. Use the net production time formula when your total time includes scheduled breaks, maintenance windows, or changeovers — this gives a more realistic view of process efficiency by only counting time the process was actually running. Use the quality-adjusted formula when defect rates are significant and you need to understand the true resource cost per acceptable unit. This is the most rigorous method and is favored in ISO and Six Sigma quality systems. If you are unsure, start with basic and progressively add detail as you gather more accurate production data.
How do I identify the bottleneck in a multi-step production process?
The bottleneck is simply the step with the longest individual cycle time. In any sequential production process, the slowest step determines the maximum output rate of the entire system — regardless of how fast all other steps run. This is the core principle of Goldratt's Theory of Constraints. To identify it, measure or estimate the cycle time for each individual operation, then find the maximum. The bottleneck step is where improvement efforts will yield the greatest throughput gains. Use the Multi-Step Bottleneck Analysis section of this calculator to enter up to eight step cycle times — the bottleneck will be highlighted automatically. Reducing the bottleneck step's cycle time (by adding capacity, streamlining the operation, or redistributing work) is the highest-leverage improvement action available.
What is a good cycle time for my process?
There is no universally 'good' cycle time in absolute terms — it depends entirely on your customer demand. The correct benchmark for your cycle time is takt time. A cycle time slightly below takt time (efficiency around 95–105%) is considered ideal in lean manufacturing: it means you can meet demand without significant waste from overproduction. Cycle times that are much faster than takt time indicate overproduction — you are consuming resources to make products faster than customers need them, which creates inventory and cash flow issues. Cycle times slower than takt time indicate a constraint that will lead to backorders. For continuous improvement purposes, track cycle time trends over time to measure the impact of process changes.
How does cycle time relate to Overall Equipment Effectiveness (OEE)?
OEE is a composite metric that measures manufacturing productivity across three dimensions: Availability (percentage of planned production time the equipment is actually running), Performance (how fast the equipment runs compared to its ideal speed), and Quality (proportion of good units produced). The Performance component of OEE is directly calculated from cycle time: Performance = (Ideal Cycle Time × Total Unit Count) / Run Time. Ideal cycle time is the theoretical minimum time per unit under perfect conditions. If your actual cycle time is higher than ideal, performance is below 100%. A world-class OEE score is typically considered 85% or above. Reducing cycle time toward the ideal value is one of the primary levers for improving OEE performance.
Can cycle time be used in agile software development?
Yes — cycle time is a key metric in agile and Kanban-based software development, though the definition shifts slightly. In software contexts, cycle time measures how long a work item (user story, bug fix, feature) spends in active development — from the moment it enters the 'In Progress' state to when it is marked 'Done.' It excludes the time an item spends waiting in a backlog before work begins (that broader measure is lead time). High-performing agile teams typically aim for cycle times under 48 hours for individual work items. Long cycle times in software indicate large, complex tasks, work-in-progress overload, or handoff bottlenecks between team members. Tracking and reducing cycle time in agile teams improves predictability, reduces risk, and accelerates delivery frequency.