Rex says
Everyday utility math — the kind you'd otherwise pull up four browser tabs for. I keep it to one clean answer.
Try a scenario
Click to load — tweak from there.Inputs
Result
Stations/operators needed
3
Exact ratio (before rounding)
2.38
Resulting utilization
79.2%
Combined labor cost per hour
$114.00
Psst — share this and help Rex grow
One click, a permanent link with your numbers baked in.
How to use this
- 1Enter process cycle time (sec).
- 2Enter takt time (sec).
- 3Enter cost per station/operator per hour ($).
- 4Read your stations/operators needed on the right — it updates as you type.
- 5Hit Share to keep the scenario or send it to someone.
About this calculator
This tool compares your actual process cycle time against takt time to tell you whether a single station can meet demand, or how many parallel stations/operators you need to add. It's the practical follow-up to a takt time calculation: knowing the target pace is useless without knowing whether you can hit it. The math divides cycle time by takt time and rounds up — a process that takes 90 seconds against a 40-second takt time needs 3 stations (2.25 rounded up) running in parallel, or a faster machine/process. This is standard line-balancing math used when deciding whether to buy a second machine, add a shift, or redesign a workstation. It also reports the utilization you'd get with your chosen station count, since rounding up always leaves some slack — better to know that slack exists than to be surprised by it on the floor.
Worked example
Using the values the calculator loads with:
Inputs
- Process cycle time: 95 sec
- Takt time: 40 sec
- Cost per station/operator per hour: 38 $
Results
- Stations/operators needed: 3
- Exact ratio (before rounding): 2.38
- Resulting utilization: 79.2%
- Combined labor cost per hour: $114.00
What each field means
Inputs
- Process cycle time (sec)
- The process cycle time used in the calculation, measured in sec. Starts at 95 sec so you have a working example on load.
- Takt time (sec)
- The takt time used in the calculation, measured in sec. Starts at 40 sec so you have a working example on load.
- Cost per station/operator per hour ($)
- The cost per station/operator per hour used in the calculation, measured in $. Starts at 38 $ so you have a working example on load.
Results
- Stations/operators needed
- Returned as a whole number and shown as the headline result. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Exact ratio (before rounding)
- Returned as a decimal number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Resulting utilization
- Returned as a percentage. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Combined labor cost per hour
- Returned as a money amount in US dollars. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
FAQ
Why round up instead of down?
Rounding down means the line physically cannot meet takt time — you'd fall behind every cycle and the shortfall compounds over a shift. Always round up to the next whole station, then look for ways to shave cycle time to improve utilization on those stations.
What if utilization comes out low, like 60%?
That's the cost of rounding up — with 2.25 stations needed you round to 3, and 2.25/3 = 75% utilization at best. Low utilization signals you should look at combining tasks, running a mixed-model line, or accepting the slack as buffer capacity for demand spikes.
Can this replace a full line balance study?
No — this gives you the headcount/station math for one bottleneck operation. A full line balance also sequences tasks across stations to equalize workload station-to-station, which this tool doesn't do. Use this as the first-pass sizing check before that deeper work.
How often should I re-run this?
Any time takt time changes (new demand) or cycle time changes (new tooling, different operator, process improvement). It's a quick five-minute sanity check worth doing before committing capital to a new station.
Accuracy and limitations
- Estimates assume standard, average conditions — local rules, pricing, and materials vary.
- Results are rounded for readability; add a buffer before ordering, booking, or committing.
- Double-check anything with a real cost attached against a local quote.
Related tools
Takt Time Calculator
The pace you must produce at to match customer demand — no faster, no slower.
Capacity vs. Shifts Calculator
How many shifts you need to hit a volume target, and the capacity headroom you'd have.
OEE Calculator (Overall Equipment Effectiveness)
Availability × performance × quality — the real health of a machine or line.
Cite this calculator
Writing about this topic? Grab a citation — every link helps keep these tools free.
RevenueLab. (2026). Cycle Time vs. Demand Calculator. Retrieved from https://www.revenuelab.fyi/toolbox/cycle-time-vs-demand
<p>Source: <a href="https://www.revenuelab.fyi/toolbox/cycle-time-vs-demand" target="_blank" rel="noopener">Cycle Time vs. Demand Calculator — RevenueLab</a> (2026).</p>
Source: [Cycle Time vs. Demand Calculator — RevenueLab](https://www.revenuelab.fyi/toolbox/cycle-time-vs-demand) (2026).