terican

Last verified · v1.0

Calculator · business

Cycle Time Calculator

Calculate cycle time per unit by entering shift hours, break time, downtime, and total units produced. Supports output in seconds, minutes, or hours.

FreeInstantNo signupOpen source

Inputs

Cycle Time per Unit

Explain my result

0/3 free

Get a plain-English breakdown of your result with practical next steps.

Cycle Time per Unittime

The formula

How the
result is
computed.

What Is Cycle Time?

Cycle time measures how long a production process takes to complete one unit of output. In lean manufacturing and operations management, it is one of the most critical performance metrics — used to identify bottlenecks, optimize throughput, and align production pace with customer demand. Whether applied to a factory floor, a software sprint, or a service desk, the cycle time formula provides a precise, data-driven view of operational efficiency.

The Cycle Time Formula

Cycle Time = Net Production Time ÷ Number of Units Produced

The key calculation step is determining Net Production Time, which strips away all non-productive intervals from gross shift hours. The full expansion is:

Net Production Time = (Shift Length × Number of Shifts × 60) − (Break Minutes × Number of Shifts) − (Downtime Minutes × Number of Shifts)

Multiplying shift length by 60 converts hours to minutes so all inputs share a consistent unit before dividing by units produced. The result can then be converted to seconds, minutes, or hours depending on the output unit selected.

Variable Definitions

  • Shift Length (hours): Total scheduled duration of each production shift. Common values are 8, 10, or 12 hours in discrete manufacturing environments.
  • Number of Shifts per Day: How many shifts run within the measurement period — typically 1, 2, or 3 per day.
  • Break Time per Shift (minutes): All scheduled rest and meal periods. A standard 8-hour shift in U.S. manufacturing typically includes 30–60 minutes of breaks.
  • Unplanned Downtime per Shift (minutes): Machine failures, material shortages, or quality holds not scheduled in advance. This is distinct from planned breaks and must be tracked and reported separately to preserve analytical accuracy.
  • Total Units Produced: Count of conforming (non-defective) units completed across all shifts in the measurement period. Only good units count — reject parts do not contribute to productive output.
  • Output Unit: Display preference for the final cycle time result — seconds, minutes, or hours per unit.

Step-by-Step Worked Example

A plastic injection molding plant runs 2 shifts per day, each 8 hours long. Each shift includes 30 minutes of scheduled breaks and averages 15 minutes of unplanned downtime. The line produces 480 good parts across both shifts.

  1. Gross time: 2 × 8 × 60 = 960 minutes
  2. Total break time: 2 × 30 = 60 minutes
  3. Total unplanned downtime: 2 × 15 = 30 minutes
  4. Net Production Time: 960 − 60 − 30 = 870 minutes
  5. Cycle Time: 870 ÷ 480 = 1.8125 minutes per unit (approximately 108.75 seconds)

One unit rolls off the line roughly every 1 minute and 49 seconds. If the customer's takt time is 2.0 minutes per unit, the line is running faster than demand — a signal to investigate overproduction waste or consider re-deploying labor.

Why Net Production Time Is Critical

Using raw shift hours rather than net production time understates cycle time and inflates apparent capacity. According to MABTS cycle time calculation guidelines, planners must deduct every non-productive interval — both scheduled and unscheduled — before computing cycle time. Omitting unplanned downtime is the most common calculation error and consistently produces optimistic estimates that collapse under real operating conditions.

Cycle Time vs. Takt Time vs. Lead Time

  • Cycle Time: How fast the process actually produces one unit, based on observed output and net available time.
  • Takt Time: How fast units must be produced to satisfy customer demand — calculated as Available Production Time ÷ Customer Demand.
  • Lead Time: Total elapsed time from order placement to delivery — encompasses queue time, process time, and transport time, and will always exceed cycle time.

MIT's foundational operations research paper on safety stock and performance cycles establishes that shorter cycle times directly shrink the demand-variability exposure window, enabling leaner safety stock levels and tighter inventory control across the supply chain.

Applications Across Industries

Manufacturing

Automotive assembly plants balance workstations by comparing individual station cycle times. If one station runs at 90 seconds and the next at 120 seconds, the slower station is the line constraint. Reducing that station's cycle time by 25% balances the line and raises daily throughput proportionally, without adding shifts or headcount.

Software Development

Agile teams measure cycle time from when a task enters In Progress to Done. A team averaging 3.5 days per story uses that figure to forecast sprint completion and flag delays in code review or testing stages — the same net-time logic, applied to knowledge work.

Service Operations

In a customer service center operating one 8-hour shift with 45 minutes of breaks and 10 minutes of system downtime, net production time is 425 minutes. Processing 200 calls yields a cycle time of 2.125 minutes per call — a concrete benchmark for staffing models and queue management decisions.

How to Reduce Cycle Time

The highest-leverage interventions are: (1) eliminating unplanned downtime through predictive and preventive maintenance programs, (2) cutting changeover time using SMED (Single-Minute Exchange of Die) methodology, (3) balancing workloads across parallel stations to remove constraints, and (4) improving operator proficiency through structured training. In the molding plant example, reducing unplanned downtime by just 5 minutes per shift recovers 10 minutes of net production time daily — enough to produce approximately 5.5 additional units at the current cycle rate without any capital investment.

Reference

Frequently asked questions

What is cycle time in manufacturing?
Cycle time in manufacturing is the average time required to complete one unit of production. It is calculated by dividing net available production time by the number of good units produced. For example, if a day yields 870 net minutes of production and the line completes 480 parts, cycle time equals 1.8125 minutes per part — approximately 109 seconds each.
How do you calculate net production time for a shift?
Net production time equals gross shift duration minus all non-productive intervals. For an 8-hour shift (480 minutes) with 30 minutes of scheduled breaks and 15 minutes of unplanned downtime, net production time is 480 minus 45, equaling 435 minutes per shift. Multiply by the number of shifts to get total net production time for the full measurement period.
What is the difference between cycle time and takt time?
Cycle time measures how fast a process actually produces one unit, based on observed output and net available time. Takt time measures how fast units must be produced to meet customer demand, calculated as available production time divided by required units. When cycle time exceeds takt time, the process cannot satisfy demand without adding capacity, overtime, or additional shifts.
How does unplanned downtime affect cycle time?
Unplanned downtime directly reduces net production time and therefore increases cycle time. If a line loses 15 minutes per shift to breakdowns across two shifts, 30 minutes of daily production time disappear. On a 480-unit run, this raises cycle time from a theoretical 1.75 minutes to 1.8125 minutes per unit — a meaningful efficiency gap that compounds at high production volumes.
What is a good cycle time for a production line?
A good cycle time equals or is lower than the customer takt time. If customers demand 500 units per shift and net production time is 870 minutes, the target cycle time is 870 divided by 500, equaling 1.74 minutes per unit. Any cycle time at or below that threshold means the line can satisfy demand within normal operating hours without adding overtime or extra staffing.
Can the cycle time calculator be used for service or software teams?
Yes. Service and software teams adapt the calculator by treating tasks or tickets as units produced and work sessions as shifts. A software team working 8-hour days with 45 minutes of meetings and 10 minutes of system downtime has 425 minutes of net productive time. Completing 6 features in that period yields a cycle time of approximately 70.8 minutes per feature — a concrete throughput benchmark.