Line of Balance Graph: Meaning and How to Read It Clearly

Charts & pivot tables · Updated November 22, 2026

A line of balance graph is a time-and-location chart used to plan and monitor work that repeats across units, such as floors, houses, road sections, or production batches. Time is shown on one axis and the units or locations on the other; each activity is drawn as a line showing where and when a crew or process is scheduled to work.

What a Line of Balance Graph Shows

Line of balance, often shortened to LOB, is a planning and control method for repetitive work. Instead of showing only whether a task is scheduled on a particular date, the graph shows how work progresses through a sequence of similar locations or products. A project team can see whether a crew is keeping pace, whether activities are spaced safely, and where a delay may disrupt following work.

Imagine a building with many similar floors. A conventional schedule might say that plumbing starts on one date and finishes on another. An LOB chart can show the plumbing crew moving from floor to floor over time, alongside framing, electrical work, and inspection. The chart makes the sequence and pace visible in one view.

LOB is especially useful when work repeats in a recognizable pattern. It can be applied to construction, manufacturing, maintenance, and other operations, but it is less informative for a project made up mostly of one-off tasks with no meaningful location or production sequence.

Background and Where the Method Fits

Repetitive projects create a scheduling challenge: teams need to coordinate both the order of activities and the rate at which each team completes its work. A list of start and finish dates can hide uneven progress. For example, two crews might have overlapping date ranges while being assigned to the same floor, or one crew might finish far ahead and wait for the next activity to catch up.

LOB addresses this by representing production as movement through units over time. In construction, a unit might be a floor, apartment, room, or length of roadway. In a factory, it might be a batch, product, or work station. The chart does not replace all project planning; it gives a focused view of repeated-flow work that can sit alongside a broader project schedule.

The name can also be used for related planning and control procedures, so chart conventions are not identical everywhere. Some organizations place time on the vertical axis or use specialized formats. Always check the axis labels and legend before interpreting a particular graph.

Axes, Activity Lines, and Their Meaning

In a common format, the horizontal axis represents calendar time and the vertical axis represents units or locations in sequence. Each activity appears as a sloped line or band. A point on the line indicates that the activity is planned or recorded at a particular location on a particular date.

  • Time axis: Usually marked in days, weeks, or months. The scale should be consistent so that the spacing between dates can be compared.
  • Location or unit axis: Lists the repeated areas in work order, such as floors 1 through 12 or roadway stations from 0 to 5 kilometres.
  • Activity line: Shows the planned or actual progress of a crew or task through those locations. Different colors or line styles may distinguish trades, plans, and actual progress.
  • Line slope: In the common orientation, a steeper line means more locations are covered per unit of time. The exact visual interpretation depends on the axis scales and orientation.

A line is not necessarily a promise that production will be perfectly smooth. It often summarizes an assumed average rate. If actual progress varies substantially, the chart may need points, steps, or separate planned and actual lines to show the variation accurately.

How Activity Rates and Buffers Work

The rate represented by a line comes from the time needed to complete work at each unit and the planned production sequence. Suppose a painting crew is expected to finish one floor every two working days. If floors are on the vertical axis, the crew’s line advances one floor for every two days. A second crew finishing one floor each day would have a different slope.

Activity lines need suitable separation. If the following crew reaches a floor before the preceding crew has completed its work, the schedule may create a conflict, rework, or unsafe congestion. Planners therefore allow a time or location buffer between activities. The buffer is not automatically spare time that can be removed: it may account for curing, inspection, access, variability, or handover requirements.

Rates also depend on assumptions such as crew size, working calendar, material availability, and unit similarity. A crew may not achieve the same rate on every floor if some floors have different layouts or access restrictions. A useful LOB plan makes these assumptions visible rather than treating the line as a guarantee.

A Simple Worked Example

Consider a project with eight identical apartment floors and three sequential activities: rough-in, inspection, and drywall. Assume rough-in takes two working days per floor, inspection takes one day per floor, and drywall takes two days per floor. The sequence requires inspection before drywall begins on each floor.

For a simple illustration, put working days on the horizontal axis and floors 1 through 8 on the vertical axis. If rough-in starts on floor 1 on day 1 and maintains its assumed pace, it reaches each next floor after two working days. Inspection and drywall lines follow with enough separation to respect the required handoffs. Their exact start points depend on whether the team waits until a whole floor is complete, how handovers are managed, and what buffer the project needs.

The graph can reveal a problem that a list of total durations may obscure. If inspection is planned to move more slowly than rough-in, rough-in may eventually catch up to the inspection team, leaving completed work waiting and potentially blocking the rough-in crew from continuing. The scheduler can respond by changing crew capacity, sequencing, or start dates, then check whether the revised lines remain feasible across all eight floors.

This example uses average rates to explain the chart, not to predict a real project. Actual durations should be based on project data and adjusted for working days, nonworking periods, unit differences, and documented constraints.

How to Build and Update One

A practical LOB graph starts with a defined sequence of repeated units and activities. Before drawing lines, agree on what counts as a completed unit and how progress will be measured. Otherwise, a reported rate such as “three units done” may mean different things to different teams.

  1. List the units in work order. Number floors, sections, rooms, batches, or other repeatable locations.
  2. Identify the activities and dependencies. Record which tasks must precede others and note access, inspection, or handover conditions.
  3. Estimate production rates. Use relevant past performance or a justified estimate, with the crew and work calendar stated.
  4. Set start dates and buffers. Place activities so crews can follow the intended sequence without unacceptable clashes or idle gaps.
  5. Plot planned lines and label them. Include units, dates, activity names, and a legend. The chart should be readable without relying on color alone.
  6. Record actual progress regularly. Compare completed locations and dates with the plan, then investigate meaningful deviations.

Updates are most useful when they are timely and consistent. If progress is recorded only as a project-wide percentage, it may be impossible to tell which locations are behind. Location-specific reporting lets the team distinguish a slow rate from a late start or a temporary interruption.

How to Read Delays and Schedule Conflicts

Compare planned and actual progress at the same location and date. If an actual line runs behind the planned line, the activity is late relative to its baseline; if the line is flatter, its observed production rate may be slower. A late start can shift a line while preserving its slope, whereas low productivity changes the slope. Those causes need different responses.

Watch for lines that approach or cross in ways that violate the work sequence. A crossing may indicate that a following activity is scheduled to arrive before the preceding activity has released the location. It can also be a sign that assumptions, reporting, or the chosen unit of analysis need review. The graph highlights a potential conflict; the team still has to confirm what is happening on site.

Unexpected gaps can matter too. A large gap between crews may represent deliberate protection or a required curing period, but it may also mean that a team is waiting or that the schedule is inefficient. The explanation should come from project constraints and field conditions, not from the shape of a line alone.

Line of Balance Compared With Gantt and CPM

A Gantt chart lists activities against a time scale, making it easy to see start dates, finish dates, and overlaps. It can be less direct for showing how a crew moves through many repeated locations. An LOB graph makes that location-by-location production flow more visible, but may be harder to use for a project dominated by unique tasks.

Critical path method (CPM) scheduling focuses on activity dependencies and identifies the sequence of tasks that determines the earliest possible project completion under the schedule assumptions. LOB focuses on the continuity, pace, and spatial or unit sequence of repetitive work. The methods can complement one another: a CPM schedule can represent the overall network, while an LOB view examines production flow in a repetitive portion of the project.

Neither chart is inherently more accurate. Accuracy depends on sound durations, realistic resource assumptions, reliable progress updates, and a suitable level of detail. A polished graph cannot compensate for an unrealistic production rate or missing dependencies.

Common Limitations and Mistakes

LOB is powerful when repeated work has enough consistency to compare units. It can mislead when the chart suggests a smooth flow that the work cannot deliver. A special floor, material shortage, weather restriction, or inspection hold may disrupt the assumed rhythm and require a revised plan.

  • Using an unclear unit: Define whether progress means started, substantially complete, or accepted by the next trade.
  • Assuming identical locations: Adjust for units that have different scope, access, or completion requirements.
  • Ignoring calendars: A line based on calendar days will not match a rate calculated in working days unless the conversion is handled.
  • Leaving out constraints: Include dependencies, approvals, curing periods, and access restrictions that affect the sequence.
  • Updating too slowly: Old actual data can make a schedule look healthy after the project has already developed a problem.
  • Overloading the chart: Too many activities or labels can conceal the relationships the graph is meant to clarify.

A common misconception is that parallel lines always mean a well-balanced plan. Parallel activity lines may show similar production rates, but the spacing between them must also be workable, and the lines must respect dependencies and resource limits. Conversely, nonparallel lines are not automatically bad; rates may differ by design if enough time and space separate the crews.

Frequently Asked Questions

What does an LOB graph stand for?
LOB stands for line of balance. It is a scheduling and control approach that shows how repetitive activities progress through units or locations over time.

What do the axes show on a line of balance graph?
In the common format, the horizontal axis shows time and the vertical axis shows units or locations in sequence. Some formats reverse the axes, so read the labels rather than assuming the orientation.

What does a steeper line mean?
With time on the horizontal axis and location on the vertical axis, a steeper line generally represents a faster rate of progress through locations. Axis scales and chart orientation affect the visual slope, so compare the labeled values.

Is a line of balance graph the same as a Gantt chart?
No. A Gantt chart emphasizes activity dates and durations; an LOB chart emphasizes the movement and production rate of activities across repeated units. They can be used together.

When should a project use a line of balance graph?
Use it when work repeats across units or locations and the sequence and pace of crews matter. For mostly one-off tasks, a Gantt or network schedule may communicate the plan more clearly.

Related

Try it: the Percentage Formula Generator: percent of, percent change, increase and decrease, with the formula.

More in Charts & pivot tables

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.