Line balancing calculation: the formulas, and a worked assembly line.

Production / Lean July 7, 2026 9 min read 1,700 words

An unbalanced line hides in plain sight: every operator looks busy, yet output is set by one overloaded station while the rest wait on it. Line balancing is the arithmetic of distributing work so every station carries close to the same load, paced to demand. Four formulas cover the whole method — here they are, with a complete worked example you can copy.

What line balancing is

Assembly line balancing assigns individual tasks to workstations so that no station exceeds the takt time and idle time across stations is minimised. The inputs are simple: the list of tasks with their standard times, the precedence between them (you cannot torque the bolt before inserting it), and the demand rate. The outputs are the number of stations, which tasks go where, and two health metrics — line efficiency and balance delay.

The prize is real. Rebalancing a line from 70 to 85 percent efficiency delivers roughly a fifth more output from the same people and floor space — the cheapest capacity you will ever buy.

The four formulas

QuantityFormula
Takt timeAvailable working time / Required output
Minimum workstations (theoretical)Σ task times / Takt time, rounded up
Line efficiencyΣ task times / (No. of stations × bottleneck station time) × 100%
Balance delay100% − line efficiency

Two definitions to keep straight. The bottleneck station time is the largest total time assigned to any single station — it becomes the line's effective cycle time. And takt is set by demand, not by the line: if the difference between the two confuses your team, the takt time vs cycle time guide settles it.

A worked example

A two-wheeler component assembly cell in a Chennai plant runs one 8-hour shift with 30 minutes of planned breaks. The customer schedule needs 300 assemblies per shift. The work content breaks into six tasks:

TaskDescriptionTime (min)Must follow
ALoad housing & insert bearing0.7
BPress shaft assembly0.9A
CFit seals & circlip0.6A
DTorque fasteners & grease fill1.2B, C
ELeak test0.8D
FFinal inspection & pack0.5E

Step 1 — Takt time. Available time = 480 − 30 = 450 min. Takt = 450 / 300 = 1.5 min per unit.

Step 2 — Total work content. Σt = 0.7 + 0.9 + 0.6 + 1.2 + 0.8 + 0.5 = 4.7 min.

Step 3 — Minimum stations. 4.7 / 1.5 = 3.13 → round up → 4 stations.

Step 4 — Assign tasks respecting precedence, keeping every station at or under takt (1.5 min):

StationTasksStation time (min)Idle vs bottleneck
S1A + C1.30.1
S2B + F1.40 (bottleneck)
S3D1.20.2
S4E0.80.6

Step 5 — Score it. Bottleneck = 1.4 min, so the line produces one unit every 1.4 minutes. Line efficiency = 4.7 / (4 × 1.4) = 83.9%. Balance delay = 16.1%. Capacity check: 450 / 1.4 = 321 units per shift — comfortably above the 300 required, with a 7% buffer for minor stops.

(One practical note: assigning F to station S2 assumes the layout returns the tested unit to that operator — a U-shaped cell does exactly this. On a straight line you would keep F at S4 with E, giving S4 = 1.3 min and the same efficiency.)

Let the tools do the arithmetic Get your takt from the free takt time calculator, and check each station's achievable rate with the cycle time calculator before you commit the new layout.

How to assign tasks (when it gets bigger)

With six tasks you can balance by eye. With sixty, use the ranked positional weight (RPW) heuristic: for each task, add its own time to the times of every task that must follow it; sort descending; then assign tasks in that order to the earliest station that has room and satisfies precedence. RPW gets within a few percent of optimal for most practical lines, and a spreadsheet does it in an afternoon. Longest-task-time-first is a simpler fallback that works acceptably on short lines.

Remember the theoretical minimum is a floor, not a promise: indivisible long tasks (a 1.2-minute torque-and-fill you cannot split) and precedence chains often force one more station than the arithmetic suggests. That is normal — the metric that matters is efficiency at the station count you actually build.

What counts as a good balance

Line efficiencyVerdict
> 90%Excellent — typical of mature, kaizen-ed lines
85–90%Well balanced — standard target for manual assembly
75–85%Acceptable — rebalance at next model or volume change
< 75%Money on the floor — rebalance now

Efficiency measures the balance, not the line's overall health: a beautifully balanced line still underperforms if stations stop for quality problems or material shortages. Track it alongside OEE — balance tells you the design is right, OEE tells you the day ran right.

Common mistakes

  • Balancing to cycle time instead of takt. If you distribute work to match the current bottleneck rather than customer demand, you optimise yesterday's line.
  • Using best-case task times. Standard times must include allowances (fatigue, handling); balancing on stopwatch-best times overloads every station by 10–15%.
  • Ignoring precedence. A balance that looks perfect on paper but violates assembly order dies on day one.
  • Loading every station to 100% of takt. Leave a small buffer (station time ≤ ~95% of takt) or every minor variation becomes a missed unit.
  • Balancing once and forgetting. Demand changes move takt; a line balanced for 300/shift is unbalanced at 240. Rebalance at every significant schedule change.
  • Splitting inspection thin. Scattering quality checks as filler across stations destroys accountability — keep inspection tasks coherent.

Inspection stations need clean paperwork too

Final-inspection stations (task F above) live or die on how fast the operator can check against the drawing. A ballooned drawing with numbered characteristics turns inspection into a checklist instead of a treasure hunt. CadNexa's auto-ballooning tool converts a PDF drawing into a numbered inspection sheet in minutes — useful when the takt allows 30 seconds for the check, not 3 minutes.

Related reading: the full takt time calculation guide, cycle time calculation, and standard production study formats on the templates page.

RR
Rajadurai R
Founder, MetricMech · 14 years plant-head experience