How to Calculate Cycle Time, Takt Time and Lead Time
Takt time is the pace demand requires, cycle time is the pace you work at and lead time is the customer's wait.
This guide explains how to calculate cycle time, takt time and lead time, three measures that are easy to mix up. In short: takt time is the pace you need to meet demand, cycle time is the pace you actually work at, and lead time is how long a customer waits from order to delivery. Each has a simple formula, shown below with worked examples from a factory and an office.
Takt time: the pace demand requires
Takt time tells you how often you must finish one unit to keep up with customers.
Takt time = available working time ÷ customer demand
Available time is the shift length minus planned breaks, meetings and maintenance. Not the time you hope to run, but the time you can.
Example: a line runs one 8-hour shift with two 15-minute breaks and a 30-minute lunch. Available time = 480 − 60 = 420 minutes. Customers order 105 units a day.
Takt time = 420 ÷ 105 = 4 minutes per unit. The line must finish a unit every 4 minutes.
How to calculate cycle time
Cycle time is how long it actually takes to produce one unit, on average.
Cycle time = net production time ÷ number of units produced
Example: in the same 420 minutes, the line made 120 units. Cycle time = 420 ÷ 120 = 3.5 minutes per unit.
Because 3.5 minutes is below the 4-minute takt time, the line has spare capacity: it can produce more than customers need. If the cycle time were 4.5 minutes, the line would fall behind demand every day.
Measuring cycle time with a stopwatch
For a single step, time several units from start to finish and average them. If five units take 3:20, 3:35, 3:28, 3:42 and 3:30, the total is 17:35, or 1,055 seconds; 1,055 ÷ 5 = 211 seconds, a cycle time of 3 minutes 31 seconds. Use the stopwatch with laps for this, and see how to calculate average time for the averaging method.
Cycle time for a process with several steps
When work passes through several stations, the slowest station (the bottleneck) sets the cycle time of the whole line. If three stations take 2.5, 3.8 and 3.1 minutes, the line can only produce one unit every 3.8 minutes.
Lead time: what the customer experiences
Lead time is the total elapsed time from when an order is placed to when it is delivered, including all the waiting.
Lead time = waiting before work starts + processing time + waiting and transport after
Example: an order waits 2 days in the queue, takes 1 day to make, waits 1 day for packing and spends 3 days in transit. Lead time = 2 + 1 + 1 + 3 = 7 days.
Lead time is always at least as long as cycle time; the difference is mostly waiting. Cutting queue time is often the fastest way to shorten lead time.
Side-by-side comparison
| Takt time | Cycle time | Lead time | |
|---|---|---|---|
| Question it answers | How fast must we work? | How fast do we work? | How long does the customer wait? |
| Formula | Available time ÷ demand | Production time ÷ units made | Order to delivery |
| Driven by | Customer demand | The process | The process plus all waiting |
| Typical unit | Minutes or seconds per unit | Minutes or seconds per unit | Hours or days |
| Example above | 4 min | 3.5 min | 7 days |
In offices and software teams
The same ideas apply outside factories. In a support team or software team, lead time runs from when a request is made to when it is done, and cycle time runs from when someone starts working on it to when it is done. If tickets wait 3 days before anyone picks them up and then take 1 day of work, the cycle time is 1 day but the lead time is 4 days.
Example: a team closed 40 tickets in a 4-week month. With 160 working hours available, the average cycle time per ticket across the team is 160 ÷ 40 = 4 working hours.
How to calculate cycle time with Little's Law
If you cannot time each unit, Little's Law gives the average from numbers you already track:
Average cycle time = work in progress ÷ throughput
Example: a software team usually has 12 tickets in progress and finishes 6 tickets a week. Average cycle time = 12 ÷ 6 = 2 weeks per ticket. A workshop with 30 jobs on the floor that completes 10 jobs a day has an average cycle time of 3 days.
The law also shows the quickest lever: with the same throughput, halving work in progress halves cycle time. That is why lean and kanban teams limit how many items can be in progress at once.
Cycle time from start and end timestamps
Many tools record when work started and finished. To calculate cycle time from them, subtract the start from the end for each item, then average the results.
| Item | Started | Finished | Cycle time |
|---|---|---|---|
| A | Mon 9:00 AM | Mon 3:30 PM | 6.5 h |
| B | Mon 1:00 PM | Tue 11:00 AM | 22 h |
| C | Tue 10:00 AM | Tue 4:30 PM | 6.5 h |
| D | Tue 2:00 PM | Wed 4:00 PM | 26 h |
The average elapsed cycle time is (6.5 + 22 + 6.5 + 26) ÷ 4 = 15.25 hours. Notice that B and D sat overnight. If you only count working hours (9 AM to 5 PM), B is 6 h and D is 10 h, and the average falls to 7.25 working hours. Say which one you report. The elapsed time calculator works out each gap between two dates and times.
Worked example: a small bakery
Here is how to calculate cycle time, takt time and lead time together for one business.
- The bakery is open for 10 hours and plans 1 hour of cleaning, so it has 540 minutes available.
- Customers order 180 loaves a day, so takt time = 540 ÷ 180 = 3 minutes per loaf.
- The oven is the bottleneck: it bakes 24 loaves every 60 minutes, a cycle time of 60 ÷ 24 = 2.5 minutes per loaf. The bakery can keep up.
- A wholesale order placed at 4 PM is mixed the next morning at 6 AM, proofed and baked by 9 AM, then delivered at 11 AM. Lead time = 19 hours, of which only about 3 hours is processing.
To shorten lead time here, the bakery would not need a faster oven; it would start overnight dough or deliver earlier.
Ways to reduce cycle time
- Fix the bottleneck first. Speeding up any other step does not change the output of the line.
- Cut changeover time. Faster setups between products free up minutes on every shift.
- Limit work in progress. Fewer items in flight means each one finishes sooner, as Little's Law shows.
- Remove rework. Units that come back for repair use the same station twice.
- Balance the line. Move tasks from slow stations to fast ones so each step is close to takt time.
Common mistakes
- Using total shift time for takt instead of available time after breaks.
- Calling lead time "cycle time", which hides the waiting customers actually feel.
- Averaging the stations to get line cycle time. The slowest station sets the pace.
- Mixing calendar hours and working hours in the same report.
Related measures
- Throughput: units completed per period, the inverse of cycle time. A 4-minute cycle time is 15 units an hour.
- Mean time between failures (MTBF): total operating time ÷ number of failures. 1,000 hours with 4 failures gives an MTBF of 250 hours.
- Mean time to repair (MTTR): total repair time ÷ number of repairs.
Tips for accurate measurements
- Use the same units throughout, usually seconds or minutes. Convert hours and minutes with the time to decimal converter.
- Subtract planned downtime from available time for takt, but not unplanned stops; those show up as a slower cycle time.
- Time several cycles and average them; a single measurement can mislead.
- For total elapsed times between dates, the time duration calculator handles days, hours and minutes.
Summary
Takt time is the target, cycle time is your actual pace, and lead time is the customer's wait. To calculate cycle time, divide production time by units made, time a sample with a stopwatch, or divide work in progress by throughput. Keep cycle time below takt time, and attack waiting to shorten lead time.
Ideal vs effective cycle time
The ideal cycle time is how fast a step runs when nothing goes wrong. The effective cycle time includes small stops, slow running and waiting for parts. If a machine's ideal is 3.5 minutes per unit but it produced 105 units in 420 minutes, the effective cycle time is 420 ÷ 105 = 4 minutes. Its performance is 3.5 ÷ 4 = 87.5%. Knowing how to calculate cycle time both ways shows how much capacity is lost to minor problems.
Takt time with several shifts
Add up the available time across all shifts before dividing. Two shifts of 420 available minutes give 840 minutes. With demand of 210 units a day, takt time = 840 ÷ 210 = 4 minutes. If demand rises to 252 units, takt time falls to 840 ÷ 252 = 3.33 minutes, and a line with a 3.5-minute cycle time can no longer keep up without overtime or a third shift.
Throughput from cycle time
Throughput is the flip side of cycle time. Divide 60 by the cycle time in minutes to get units per hour: a 3.5-minute cycle gives 60 ÷ 3.5 = about 17 units an hour, and over 420 minutes that is 120 units. If you already know throughput, divide the period by it to find cycle time: 120 units in 7 hours is one unit every 3.5 minutes.
Process cycle efficiency
Process cycle efficiency compares the time spent adding value with the total lead time:
Process cycle efficiency = value-added time ÷ lead time
In the bakery example, about 3 hours of the 19-hour lead time is processing, so efficiency is 3 ÷ 19 = about 16%. Figures under 10% are common in offices and supply chains. The low number is not a failure; it points to where the waiting is.
How to calculate cycle time in Excel
Log a start and end time for each item, then:
- Cycle time per item in hours:
=(C2-B2)*24 - In working days only:
=NETWORKDAYS(B2,C2) - Average cycle time:
=AVERAGE(D2:D50) - Median, less affected by outliers:
=MEDIAN(D2:D50) - 85th percentile, for promises to customers:
=PERCENTILE.INC(D2:D50,0.85)
The percentile is useful for forecasting: "85% of requests are finished within 6 days" is a promise you can usually keep. See how to calculate time difference in Excel for date and time formats.
Cycle time in kanban and software teams
Kanban tools record when each card enters "In progress" and when it reaches "Done". The gap is the cycle time, and a scatter chart of every card shows whether the process is getting faster or slower. To calculate cycle time for a sprint or month, average the cards finished in that period, or use Little's Law with the average work in progress. Watch for cards that sit blocked: they inflate cycle time without anyone working on them.
Cycle time in other settings
- Order to cash: days from an order being placed to the payment arriving. Shorter cycles improve cash flow.
- Recruiting: time to hire, from a job opening to an accepted offer.
- Healthcare: patient cycle time, from check-in to check-out, used to plan clinic schedules.
- Construction: the time to complete one repeating unit, such as a floor of a building.
In every case, the method for how to calculate cycle time is the same: define a clear start and end point, measure enough items, and average them.
How to calculate cycle time on the shop floor, step by step
- Define the start and stop points. For example, from picking up a part to placing the finished part on the conveyor.
- Observe at least 10 to 20 cycles. Use a stopwatch with laps so you capture each cycle without resetting.
- Note anything unusual, such as a dropped part or a material shortage, and keep those cycles separate.
- Average the normal cycles for the typical cycle time, and keep the slowest values for capacity planning.
- Compare with takt time. If the cycle time is close to or above takt, that step needs attention.
Repeat the study after any change to the process. Knowing how to calculate cycle time before and after a change is the simplest way to prove an improvement worked.
Line balancing with takt time
Line balancing compares each station's cycle time with takt time. With stations at 2.5, 3.8 and 3.1 minutes and a takt time of 4 minutes, every station is fast enough. If demand rises and takt falls to 3.5 minutes, station 2 is now 0.3 minutes too slow. Moving 0.3 minutes of work to station 1 (which has 1.0 minute spare) brings both within takt: 2.8 and 3.5 minutes. Adding up the work content, 9.4 minutes, and dividing by takt also tells you the minimum number of stations: 9.4 ÷ 3.5 = 2.7, so 3 stations are enough.
Frequently asked questions
How do you calculate cycle time?
Divide the net production time by the number of units produced in that time. 420 minutes and 120 units give a cycle time of 3.5 minutes per unit.
How do you calculate takt time?
Divide the available working time by customer demand for the same period. 420 available minutes and demand of 105 units give a takt time of 4 minutes.
What is the difference between cycle time and lead time?
Cycle time measures the work itself; lead time measures the customer's whole wait, including queues and transport. Lead time is always equal to or longer than cycle time.
What if cycle time is longer than takt time?
The process cannot keep up with demand. You need to speed up the bottleneck, add capacity or extend working time.
How do you calculate cycle time in manufacturing?
Divide the net production time by the number of good units made. 420 minutes of production and 120 units give 3.5 minutes per unit. For a single step, time several units with a stopwatch and average them.
How do you calculate cycle time in Excel?
Subtract the start date-time from the end date-time for each item and multiply by 24 for hours, then use AVERAGE or MEDIAN on that column.
How many cycles should I time to calculate cycle time?
At least 10, and 20 or more for steps that vary a lot. Average the normal cycles and record unusual ones separately.
By the TimeNowTools team · Last reviewed 23 October 2026