Bottleneck calculator for a process or production line: find the step that limits output

A bottleneck is the step with the lowest capacity compared with demand. It caps the output of the whole process: work piles up in front of it and the steps after it wait. Capacity per step is 60 ÷ cycle time × workers; the lowest one is the bottleneck.

Your process, step by step

Starting values are an example, not data about your process. Replace them.

Result

System capacity40/h
Demand30/h
BottleneckPacking
Picking53%
⚠ Packing75%
Shipping70%

Utilization = demand ÷ step capacity. Bar colour and the ⚠ label both mark the bottleneck; the vertical line is 90%. Capacity per step = 60 ÷ cycle time × workers.

Open this exact case in Simflowly

This calculator is deterministic: it ignores variability and queues. Simflowly adds both. Free account needed to save.

The formula

capacity per hour = (60 ÷ cycle time in minutes) × workers utilization = demand per hour ÷ capacity per hour

The bottleneck is the step with the lowest capacity. If demand is higher than that capacity, utilization is above 100% and the process cannot deliver the demand however well the other steps run.

Worked example

Three steps and a demand of 30 units an hour. Picking takes 4.2 minutes with 4 workers: 60 ÷ 4.2 × 4 = 57.1 units an hour. Packing takes 3 minutes with 2 workers: 60 ÷ 3 × 2 = 40 an hour. Shipping takes 1.4 minutes with 1 worker: 60 ÷ 1.4 = 42.9 an hour.

Packing has the lowest capacity, so it is the bottleneck and the whole line can deliver at most 40 units an hour. At 30 units an hour packing is 30 ÷ 40 = 75% busy, picking 53% and shipping 70%. Demand fits today, but a 33% increase in demand would put packing at 100%.

What happens when you fix it

Add a third packer. Packing capacity becomes 60 ÷ 3 × 3 = 60 units an hour, but the line does not get that fast: the slowest step is now Shipping, so the line delivers 42.9 units an hour instead of 40. At 30 units an hour packing falls to 50% and shipping stays at 70%.

The lesson is the one the table shows: the bottleneck moves. Fixing the slowest step only helps up to the next-slowest one, so check every step again after each change, and remember these are averages: they ignore the queues that random arrivals create, which is what a simulation adds.

Questions

How do you find the bottleneck in a process?

Compute the capacity of every step (60 ÷ cycle time in minutes × number of workers) and compare it with demand. The step with the lowest capacity, and the highest utilization, is the bottleneck. Work queues up in front of it.

How do you find the bottleneck of a production line?

List each station in order with its cycle time per unit and its number of workers or machines. Capacity per hour is 60 ÷ cycle time × workers. The station with the lowest capacity limits the whole line. Compare demand with it to see how close to the limit you are.

Is this a PC or computer bottleneck calculator?

No. It is for processes: production lines, warehouses, service points and workflows. It does not compare a processor with a graphics card. Enter steps, cycle times and workers instead.

What is a good utilization for a step?

Below about 70% is comfortable, 70 to 90% needs watching, and above 90% queues grow quickly whenever demand or cycle times vary. At 100% or more the step cannot keep up and the line grows without limit.

Why is utilization below 100% still a problem?

Because real arrivals and cycle times vary. A step at 90% busy can still build long queues in a bad hour. This calculator ignores variability; a simulation includes it.

Can there be more than one bottleneck?

The slowest step limits output at any moment, but once you fix it the next-slowest becomes the limit. That is why the calculator shows utilization for every step, not only the worst.

What does it not tell me?

It uses average cycle times and steady demand, so it cannot show queue lengths, waiting times or how often you miss a deadline. Open the result in Simflowly to simulate those.

Keep going

Updated 13 November 2026. Free to use, no account. The calculation runs in your browser; nothing you type is sent to us.