How many cycle time observations should I record for a valid time study?

Aim for 10 to 20 consecutive cycles for a stable manual operation, which is why this template holds 20 rows. Automated stations with low variation can use 5 to 10. If your max reading is more than 25 percent above the min, the process is unstable, so take more observations and note the conditions before trusting the average against takt.

Should I use average or maximum cycle time when comparing against takt time?

Compare average cycle time against takt for capacity planning, since a station that averages 50 seconds against 55 second takt keeps pace over a shift. But watch the maximum, because if peak cycles hit 62 seconds regularly, you will accumulate a backlog during those runs. A tight min-max spread means you can trust the average; a wide one means you need buffer or root-cause work.

What does it mean when average cycle time exceeds takt time?

The station cannot keep up with customer demand and becomes the line constraint. If takt is 55 seconds and the station averages 60, you fall 5 seconds behind every unit, roughly 8 percent short of schedule. Options are rebalancing work to adjacent stations, adding an operator, cutting non-value-added motion, or investing in a faster process. Flag the station and quantify the gap in seconds first.

How do I calculate estimated capacity per shift from cycle time?

Divide net available shift seconds by average cycle time. An 8 hour shift with 30 minutes of breaks gives 27,000 net seconds; at a 45 second average cycle time that is 600 units. This template does the division automatically once you enter observations and shift time, so you can compare estimated capacity directly against the daily demand your schedule requires.

What is the difference between cycle time and takt time?

Cycle time is how long the station actually takes to complete one unit, measured with a stopwatch. Takt time is the pace you must hit to meet demand, calculated as net available time divided by required units. Cycle time is a fact about your process; takt is a requirement set by the customer. You control cycle time; demand controls takt. Keep cycle time below takt to stay on schedule.

Why does my cycle time vary so much between observations?

Common causes are operator technique differences, waiting on upstream parts, tool changes, reaching for material outside the work zone, and machine warm-up. Use the notes column to tag each slow reading. If variation clusters around specific conditions, that is your improvement target. A well-controlled manual station should hold observations within about 10 to 15 percent of the average once standard work is in place.

Production and Throughput

Cycle Time Tracker Spreadsheet Template

Log and analyze cycle times by operation, workstation, or part number to identify variability and compare against takt time.

Overview

This template logs repeated cycle time observations for a single operation, workstation, or part number so an industrial engineer or line supervisor can see how much a station actually varies. Guessing from a single stopwatch reading hides the spread that kills throughput. Recording 20 observations and comparing the average against takt time tells you whether the station is truly capable or just occasionally lucky, which is the difference between a schedule you hit and one you miss.

You enter the part number, operation name, and up to 20 individual cycle times. From those observations the sheet returns average, minimum, and maximum, so you can see the range and spot outliers. You add a takt time target, and the comparison column flags whether average cycle time sits under or over it. Estimated capacity per shift is derived from the average cycle time and available shift seconds, and the notes column captures conditions like tool changes or material issues that explain a slow reading.

In practice you run a time study, capturing 10 to 20 consecutive cycles at the station, and paste each into an observation row. If average cycle time is 58 seconds against a 55 second takt, the station is the constraint and needs balancing, a faster fixture, or a second operator. Use it to set standard work, then hand the numbers to the Cycle Time Calculator to model a proposed change before you touch the line or commit to overtime.

What this template includes

Part number and operation name fields
Individual cycle time observations (up to 20)
Average, minimum, and maximum cycle time
Takt time target input
Cycle time vs. takt time comparison
Estimated capacity per shift
Notes column for process conditions

Suggested use case

Use this during a time study, when setting standard work, or when investigating why a line is falling short of schedule.

How to use it

Record the part number and operation being measured.
Enter each observed cycle time in the observation rows.
Enter the takt time target for the operation.
Review average cycle time vs. takt to see if the station is at risk.
Flag stations where average cycle time exceeds takt time.

Frequently Asked Questions

How many cycle time observations should I record for a valid time study?: Aim for 10 to 20 consecutive cycles for a stable manual operation, which is why this template holds 20 rows. Automated stations with low variation can use 5 to 10. If your max reading is more than 25 percent above the min, the process is unstable, so take more observations and note the conditions before trusting the average against takt.
Should I use average or maximum cycle time when comparing against takt time?: Compare average cycle time against takt for capacity planning, since a station that averages 50 seconds against 55 second takt keeps pace over a shift. But watch the maximum, because if peak cycles hit 62 seconds regularly, you will accumulate a backlog during those runs. A tight min-max spread means you can trust the average; a wide one means you need buffer or root-cause work.
What does it mean when average cycle time exceeds takt time?: The station cannot keep up with customer demand and becomes the line constraint. If takt is 55 seconds and the station averages 60, you fall 5 seconds behind every unit, roughly 8 percent short of schedule. Options are rebalancing work to adjacent stations, adding an operator, cutting non-value-added motion, or investing in a faster process. Flag the station and quantify the gap in seconds first.
How do I calculate estimated capacity per shift from cycle time?: Divide net available shift seconds by average cycle time. An 8 hour shift with 30 minutes of breaks gives 27,000 net seconds; at a 45 second average cycle time that is 600 units. This template does the division automatically once you enter observations and shift time, so you can compare estimated capacity directly against the daily demand your schedule requires.
What is the difference between cycle time and takt time?: Cycle time is how long the station actually takes to complete one unit, measured with a stopwatch. Takt time is the pace you must hit to meet demand, calculated as net available time divided by required units. Cycle time is a fact about your process; takt is a requirement set by the customer. You control cycle time; demand controls takt. Keep cycle time below takt to stay on schedule.
Why does my cycle time vary so much between observations?: Common causes are operator technique differences, waiting on upstream parts, tool changes, reaching for material outside the work zone, and machine warm-up. Use the notes column to tag each slow reading. If variation clusters around specific conditions, that is your improvement target. A well-controlled manual station should hold observations within about 10 to 15 percent of the average once standard work is in place.