Cycle time is the measured time it takes a process to produce one unit, start to finish, as observed rather than as designed. The Lean Enterprise Institute defines it plainly as the time required to produce a part or complete a process as timed by actual measurement. This cycle time calculator derives it from the numbers most operations already track — available run time and good units produced — and puts it next to the takt time your demand implies.
Arb Digital builds free calculators for the operational arithmetic behind business decisions, and this pair of measures is one of the most commonly muddled. The two words are used interchangeably in conversation and mean genuinely different things, which is why this page keeps them visibly separate and reports the gap between them as a number.
What This Cycle Time Calculator Does
It divides your net available production time by the number of good units you actually produced in that time, giving the average seconds per unit the process delivered. That figure is then inverted into throughput — units per hour — because capacity conversations tend to happen in units per hour while improvement conversations happen in seconds per unit, and having both on screen avoids a lot of arithmetic in meetings.
If you enter a daily customer demand figure, the tool also computes takt time from the same available run time, subtracts one from the other, and reports whether the process is running faster or slower than demand requires. The final grid item converts that gap into whole units per day, which is usually the form the conversation actually needs: not "we are seven seconds over takt" but "we are eighty units short every day".
How to Use It
- Enter shift length and shifts per day. Use scheduled attendance time, before any deductions.
- Enter planned stoppages per shift. Breaks, scheduled changeovers and planned maintenance come out of available time. Unplanned breakdowns should not — leaving them in makes a broken process look like a slow one.
- Enter good units produced per day. Count only units that passed quality first time. Including scrap flatters the cycle time by crediting the process with output it did not usefully deliver.
- Enter daily customer demand if you want the takt comparison. Leave it at zero to get cycle time and throughput on their own.
- Read the gap. A positive "cycle minus takt" means each unit takes longer than demand allows, and the daily shortfall shows the size of the problem in units.
The Formula and How It Is Calculated
Net available time is the starting point for both measures:
Available time = (shift length − planned stoppages) × shifts per day
and then:
Cycle time = available time ÷ good units produced
Takt time = available time ÷ customer demand
Working the defaults through: a 450-minute shift less 30 minutes of planned stoppages leaves 420 minutes, and two shifts give 840 minutes of available time per day. Producing 720 good units in that window gives a cycle time of 840 ÷ 720 = 1.1667 minutes, or 70 seconds per unit. Inverted, that is 51.4 units per hour. With demand at 800 units a day, takt time is 840 ÷ 800 = 1.05 minutes, or 63 seconds. Cycle exceeds takt by 7 seconds per unit, and at 70 seconds per unit the line can only make 720 units in 840 minutes — an 80-unit daily shortfall against demand of 800.
Cycle Time Is Not Takt Time, and the Difference Is the Point
Takt time is set entirely outside the factory: it is available time divided by customer demand, and nothing you do on the line changes it except changing the hours you run. Cycle time is set entirely inside the factory: it is what your equipment, layout, staffing and methods achieve. One is a requirement, the other is a capability, and improvement work is the business of closing the distance between them.
Three situations follow. When cycle time exceeds takt time, the process cannot meet demand and will fall behind every single day — overtime and expediting hide it temporarily but the arithmetic does not change. When cycle time equals takt time exactly, the line meets demand with zero buffer, which sounds elegant and is fragile, because any variation immediately becomes a miss. When cycle time is comfortably below takt time, the line has spare capacity, and the honest question becomes whether that spare capacity is worth its cost. Our takt time calculator approaches the same relationship from the demand side and works out how many workstations a target takt requires; use this page when you are measuring what you have, and that one when you are designing what you need.
Cycle Time, Lead Time and Throughput Time Are Three Different Things
Cycle time covers the processing step. Lead time covers everything the customer waits through — order entry, queueing, processing, inspection, packing and dispatch. Throughput time, sometimes called flow time, covers the period a unit spends inside the process from the moment work starts on it. In most real operations lead time is many multiples of cycle time, because units spend far longer waiting between steps than being worked on.
That gap is where the money usually is. A line with a 70-second cycle time and a four-day lead time does not have a speed problem at the workstation; it has a queueing problem between workstations. Cutting the cycle time to 60 seconds in that situation changes the customer experience almost not at all. Measuring both figures before choosing what to improve is the difference between a project that pays back and one that does not.
Why Averaged Cycle Time Hides the Bottleneck
The figure this calculator produces is a line-level average: total time divided by total output. It is exactly right for capacity planning and exactly wrong for finding where to intervene. A five-station line whose stations run at 40, 45, 70, 42 and 44 seconds has a line cycle time of 70 seconds, because the slowest station governs the whole flow. The average of the five station times, 48 seconds, describes nothing that exists.
So use this tool for the line-level number, then time each station individually and plot them against takt. The resulting bar chart — usually called a yamazumi or operator balance chart — shows immediately which single station is setting the pace and which stations have slack that could absorb work from it. Rebalancing across stations is very often cheaper than speeding any station up, and it is invisible to an averaged calculation.
What Happens to Cycle Time When Quality Slips
Because this calculator divides by good units, defects inflate cycle time automatically, and that is deliberate. A line running a nominal 60-second station cycle with a 10% scrap rate produces good units at an effective 66.7 seconds each: the time spent making the scrapped units was consumed and produced nothing sellable. Rework is worse still, because the unit passes through the process twice.
This is why quality and speed are not the trade-off they are often presented as. If your measured cycle time is above takt, checking the defect rate before buying faster equipment is nearly always the cheaper first move. Our DPMO calculator quantifies the defect rate as defects per million opportunities and its equivalent sigma level, and the process capability index calculator tests whether the process is capable of holding its specification limits at all. The US Department of Commerce's NIST Manufacturing Extension Partnership provides value stream mapping and operational improvement support to smaller manufacturers working through exactly this kind of question.
Getting the Available Time Figure Honest
Most disputes about cycle time turn out to be disputes about the denominator. If planned stoppages are understated, available time is overstated and cycle time looks better than it is. If unplanned downtime is quietly folded into planned stoppages, a reliability problem disappears from the numbers entirely and reappears as a mysteriously good cycle time next to a mysteriously poor output figure.
Keep the two categories separate. Planned stoppages are time the process was never scheduled to run: breaks, planned changeovers, scheduled maintenance. Everything else is running time, whether the machine was actually running or not. Measured that way, cycle time captures both speed losses and availability losses, which is what makes it comparable across weeks. If you need the labour cost implications of the resulting schedule, the work hours calculator converts shift patterns into hours, and the employee cost calculator puts a figure on them.
Arb Digital builds interactive tools and the content around them — correct arithmetic, fast pages, and the technical work that gets them found in search.
Browse All Free Tools Talk to Arb DigitalCommon Mistakes to Avoid
- Counting total units instead of good units — scrap consumed cycle time and produced nothing, so including it understates the real time per sellable unit.
- Folding unplanned downtime into planned stoppages — it removes a reliability problem from the numbers and makes cycle time look artificially good.
- Using the line average to find the bottleneck — the slowest station governs the line, and averaging across stations describes a process that does not exist.
- Treating cycle time and lead time as the same measure — customers experience lead time, and it is usually dominated by waiting rather than processing.
- Comparing cycle times across different shift patterns without recalculating available time — the denominator changes and the comparison stops meaning anything.
Related Free Tools From Arb Digital
Pair this with the takt time calculator for the demand side, the DPMO calculator and process capability index calculator for quality, the inventory turnover calculator for what the output does next, and the work hours calculator for scheduling arithmetic. The full free online tools hub lists everything.
Frequently Asked Questions
Cycle time is the time a process actually takes to produce one unit, measured rather than designed. At the line level it is net available production time divided by the number of good units produced in that time.
Cycle time is what the process achieves; takt time is what customer demand requires. Cycle time is calculated from units produced, takt time from units demanded, and both use the same available production time as the numerator.
The process cannot meet demand within the scheduled hours. The daily shortfall shown in the calculator is the size of the gap in units, and closing it needs either a faster process, more capacity, or more running time.
No. Count only good units. Time spent producing units that were scrapped was still consumed, so excluding scrap correctly loads that lost time into the cycle time figure.
No. Cycle time covers the processing step; lead time covers everything the customer waits through, including queueing between steps. Lead time is usually many times longer than cycle time.
Time each station separately and compare each one against takt time. The station with the longest individual cycle time governs the whole line, and a line-level average will not reveal it.
Yes. Any repeatable process with countable output works — claims handled per day, tickets resolved, orders picked. Substitute your unit of work for units produced and the arithmetic is identical.
