Line balancing

In one line

Balancing a line means spreading the tasks of a process across its workstations so that none is so loaded that it becomes a bottleneck, and none is so light that its operator spends half the cycle waiting.

What it is

In any line where several stations (or several operators) perform consecutive tasks on the same piece, the output speed of the whole line is set by the slowest station — the rest, however fast they work, end up waiting for it. The source illustrates this with a simple case: five operators assemble the same product in sequence, with times of 0.52, 0.48, 0.65, 0.41 and 0.55 minutes each. The 0.65-minute operator sets the pace of the whole line, so the other four end up with waiting time before they can pass on the next piece. Balancing the line is, precisely, the work of narrowing those differences.

For that you need two calculations:

Theoretical minimum number of stations. This is the number of stations you would need if the workload could be distributed perfectly, with no idle time at all:

Minimum N = (sum of the times of all tasks) ÷ (desired cycle time) — always rounded up.

You round up because there is no such thing as a "0.6" station — if the calculation gives 3.4, you need at least 4 stations, even if the fourth one ends up with a light load.

Balancing efficiency. Once the tasks have been assigned to a real number of stations (which in practice is almost always higher than the theoretical minimum, because tasks cannot be cut at any point or reordered freely), you measure how well that installed capacity was used:

Efficiency = (sum of the times of all tasks) ÷ (real number of stations × cycle time)

The result, as a percentage, tells you what share of the total time available on the line is used for real work. Whatever is missing up to 100% is idle time spread across the stations.

What it is used for

It is used to design or redesign a production or assembly line: how many stations (and operators) are needed to sustain a given production rate, and how efficient that distribution of tasks turns out to be once it is set up. It is the tool that turns a list of tasks with their times into a concrete decision about how many workstations to set up and which task goes to each one.

It also works as a diagnostic for a line that already exists: if the calculated efficiency comes out low, it is a numerical sign that there is too much idle time spread across the stations, even if at first glance the line "looks" like it is running fine.

How to apply it

1. List the tasks and their times. Every task in the process, with its standard time (the one that comes out of a time study) and which other tasks have to be finished before this one can start (its precedence).
2. Define the desired cycle time. It comes from demand: the available time in the shift divided by the number of units that have to be produced in that shift. When the goal is for the line to produce at exactly the rate the customer asks for, this desired cycle time is the same as the takt time of the process.
3. Calculate the theoretical minimum number of stations with the formula above. It is the floor: you can never set up the line with fewer stations than that.
4. Assign the tasks to real stations, respecting the precedences and without any station exceeding the cycle time. For this the source describes the Helgeson and Birnie method (1961): it ranks the tasks by their "positional weight" (how much work depends on them further down the sequence) and loads them into each station, from the highest weight to the lowest, until the available cycle time is filled.
5. Calculate the real efficiency with the number of stations you ended up using in the previous step — almost always a few more than the theoretical minimum.
6. If the efficiency comes out low, there is room for improvement: share a task between two neighboring stations, split a task that can be divided, reassign work from the most loaded station to the lightest one, or improve the method of the task that takes the most time.

Real or illustrative example

Illustrative (made-up) example: the source gives generic numerical examples to explain the method (not a case from a real factory with a proper name), so the following case is our own, built to show the calculation with the same two formulas.

An assembly line has 6 tasks, with these standard times:

• Task A: 0.4 min
• Task B: 0.3 min
• Task C: 0.5 min
• Task D: 0.2 min
• Task E: 0.6 min
• Task F: 0.3 min

Sum of times: 0.4 + 0.3 + 0.5 + 0.2 + 0.6 + 0.3 = 2.3 minutes

Shift demand calls for a cycle time of 0.8 minutes per unit.

Theoretical minimum number of stations:

Minimum N = 2.3 ÷ 0.8 = 2.875 → rounded up = 3 stations

In practice, the precedences between tasks do not allow the 2.3 minutes to be spread over just 3 stations without one of them exceeding the 0.8-minute cycle time — the team ends up setting up the line with 4 real stations.

Balancing efficiency:

Efficiency = 2.3 ÷ (4 × 0.8) = 2.3 ÷ 3.2 = 71.9%

That 71.9% says that almost 28% of the time available on the line (4 stations × 0.8 minutes each) ends up as idle time spread across the four stations. It is the number that tells the team whether it is worth reviewing the task assignment before calling the line done.

Template to use

A simple table with the process tasks is enough to start any balancing:

Task	Standard time	Predecessors (must finish first)
A	(fill in) min	—
B	(fill in) min	(fill in)
C	(fill in) min	(fill in)

With that list filled in:

1. Add up all the standard times.
2. Define the desired cycle time (or take it from the takt time, if the goal is to match the pace to customer demand).
3. Divide the sum by the cycle time and round up → theoretical minimum number of stations.
4. Assign the tasks to real stations respecting the precedences, without exceeding the cycle time in any of them.
5. Divide the sum by (real stations × cycle time) → balancing efficiency.

So you do not have to build it by hand, there is a line balancing spreadsheet in Excel with the formulas already in place: it calculates the minimum stations, the time of each station with a warning if it exceeds the cycle time, and the balancing efficiency. The values it comes with are examples and need to be deleted.

Try it with your own tasks

Benefits

• It gives you a concrete number (the theoretical minimum of stations) to start designing a new line, instead of estimating "by eye" how many workstations are needed.
• Balancing efficiency turns a feeling ("the line works well" or "it is sluggish") into a verifiable percentage, comparable across different lines or different versions of the same balancing.
• It forces you to have the list of tasks with times and precedences in writing, which later serves to train new operators or to rebalance if demand changes.

Limitations to keep in mind

• The theoretical minimum number is a mathematical floor: it is almost never achieved in practice, because tasks cannot always be split or reordered freely because of their precedences.
• The result depends entirely on the quality of the standard times used as input — a badly taken time in the time study carries the error into both formulas.
• A balancing calculated for one cycle time (one demand level) stops being valid if that demand changes; you have to recalculate it, not recycle the previous balancing.
• The calculation assumes that each task has a fixed time and that operators do not help each other between stations — on lines where that collaboration does exist, the real efficiency ends up better than the calculated one.

In summary

Balancing a line means spreading tasks with precedences across stations so that none becomes a bottleneck. Two simple calculations organize the decision: the theoretical minimum number of stations (sum of times ÷ cycle time, rounded up) sets the floor of stations needed, and the balancing efficiency (sum of times ÷ (real stations × cycle time)) measures how close to that floor the line ended up once it was set up.