Free Cycle Time Tracker Excel Template
Compare what the routing says a job should take with what it actually takes. Most manufacturers find routings are 20–40% off reality — that is the biggest source of schedule misses.
What you get
Working cycle-time log with standard vs actual variance by operation. Captures the data needed to fix outdated routings before they cause customer impact.
Free 30-day trial · No credit card required · Used by manufacturers since 1991
Why manufacturers still use Excel for this
Cycle time is the foundation everything else builds on. If your routing says operation 3 takes 45 minutes and it actually takes 70, every promise date downstream is wrong by that gap multiplied by the queue. Inaccurate cycle times are the silent killer of manufacturing schedules.
Most shops set cycle times once — usually 5+ years ago — and never revisit them. Tooling improves, programs get tuned, operators get faster. The routing standards rot in the ERP. This template gives you a structured way to compare reality to standard, operation by operation, until you have the data to update the routings.
A 30-day capture window for the top 20 routings is usually enough. The pattern emerges quickly: some operations are 30% faster than standard, some are 50% slower. Both directions matter. After the routings are updated, RMX or RMDB can capture cycle time automatically from shop floor moves, eliminating the manual log.
What's inside the template
Cycle-time observation log
Date, work order, part, operation, work center, operator, standard time, actual time, variance, and notes.
Standard-vs-actual variance
Auto-calculated % variance per row. Color-coded: green if within 10%, amber 10–25%, red beyond 25%.
Operation-level rollup
Average actual cycle time per operation, with sample size. Lets you trust the data — 3 observations is noise, 30 is signal.
Routing-update worksheet
Top variance operations sorted by impact (variance × frequency). This is your routing-correction priority list.
Operator effect filter
Filter cycle time by operator to identify training gaps without exposing individuals (the data drives a group conversation, not a callout).
Bottleneck detection
Operations where actual cycle time is significantly higher than the next operation downstream — usually the real bottleneck.
How to use this template
A practical walkthrough, from the sample data to a plan built on your own numbers.
- 1
Pick 20 routings to start
Trying to track every routing fails. Pick the top 20 by volume or revenue — that covers 80% of your throughput.
- 2
Use stopwatch or shop-floor stamps
Either is fine. The discipline matters more than the precision. A stopwatch observation by a supervisor once per shift is enough to build a meaningful sample.
- 3
Gather 30+ observations per operation
Less than 30 and you cannot distinguish noise from signal. The variance column lights up red on individual rows but you only act on the operation-level rollup.
- 4
Update the routing in your ERP
Once an operation has a stable 30+ observation set, update the routing standard in your ERP. Then the schedule starts matching reality.
When you outgrow this template
Excel is the right answer for early-stage planning, until it isn't. These are the warning signs that you need a real production scheduling tool.
If three or more of these apply, you have outgrown spreadsheet planning. EDGEBIC, the current generation of RMDB, is User Solutions' finite capacity scheduling and production planning software. It imports the same orders, routings, work centers and stock from Excel, CSV or your ERP, schedules them against real machine, labor and material limits, and shows the result on a drag-and-drop Gantt chart. It is a one-time license: EDGEBIC APS is $25,000, and EDGEBIC Complete, which adds MRP, inventory and purchasing, is $35,000.
See EDGEBICNot ready to decide? Read what actually changes when you move off the spreadsheet, or see the published price before you talk to anyone.
Frequently asked questions
What is the difference between cycle time and takt time?+
Cycle time is how long an operation actually takes to produce one unit. Takt time is the rate at which you must produce one unit to meet customer demand. Cycle time < takt time = you can keep up. Cycle time > takt time = you are falling behind no matter how hard you push.
How many observations do I need before updating a routing?+
30 minimum. Anything less and you are reacting to noise. The exception: if every one of 5 observations is dramatically different from standard in the same direction, that is signal — but treat it as a flag to gather more data.
What if cycle times vary by operator?+
Operator-driven variance signals one of two things: training gap (consistent slow performer) or technique difference (some operators have a better method). Both are improvement opportunities — the spread is the lesson.
How often should I refresh cycle time standards?+
Annually at minimum for any routing that runs regularly. After any major change — new tooling, new program, new fixture — re-baseline immediately. Routings that have not been touched in 5+ years are almost certainly wrong.
Start with the spreadsheet. Move to EDGEBIC when it breaks.
The template handles the math for a small plan. EDGEBIC is what manufacturers move to when orders, routings and capacity change faster than a spreadsheet can follow: published one-time pricing, and implementation measured in days.