Esc

↑↓ move↵ openIndex · Pagefind
Project management

Line of Balance

Definition

A location-based schedule chart that plots locations against time, with one sloped line per trade, so you can see each crew moving through the building and where two trades collide.

Topic: Scheduling

A Line of Balance (or flowline) chart puts locations, such as floors, units or zones, on the vertical axis and time on the horizontal axis. Each trade is a line that climbs through the locations as it works. The slope is the trade’s production rate: steep lines move fast, shallow lines move slowly. The gap between two lines in the same location is the buffer between those trades.

Why it matters

On repetitive work a Gantt chart hides the pattern. A flowline shows it at once: lines that touch mean two trades in one place at the same time, lines that cross mean a fast trade has caught a slow one, and wide gaps mean a crew is waiting. Parallel lines with steady buffers are the goal, because crews then move from location to location without stopping.

Worked example

Illustrative: a six-storey apartment block. Framing finishes a floor every 5 working days, drywall every 8. Drywall starts on level 1 a week after framing, but its line is shallower, so the buffer behind framing grows floor by floor. Tape and finish moves every 4 days, and its line crosses drywall’s at level 5: the finishers would arrive before the boards are hung. The fix is to slow finishing or add a drywall crew.

Common mistakes

  • Drawing a flowline from activities with inconsistent location names, so one floor appears twice.
  • Treating every crossing as an error. Sometimes a trade is planned to overtake; check the logic before changing it.
  • Reading the slope without the location sizes. A small floor and a large one take different times at the same rate.

How os.construction handles it

The Planner’s Line of Balance display mode draws a flowline from the calculated dates. Locations come from the activity location field, the project’s Locations or a Location activity code, and trades from a trade field, a code or the activity name. It marks conflicts, tight buffers and crossings, exports SVG and feeds takt planning. Nothing is rescheduled. See Location-based planning.

Open file