Esc

↑↓ move↵ openIndex · Pagefind
Project management

Work Breakdown Structure

Definition

A hierarchy that breaks the whole scope of a project into smaller, manageable pieces of work, used to organize the schedule, the budget and progress reporting.

Topic: Scheduling

Updated

A work breakdown structure (WBS) is a hierarchy that breaks a project’s total scope into smaller pieces of work. PMI’s PMBOK Guide describes it as a hierarchical decomposition of the total scope of work to be carried out by the project team. In construction the WBS gives every schedule activity a home, so dates, cost and progress can be rolled up and reported by building, floor, phase or system.

The WBS answers “what work is there?” The schedule answers “in what order, and when?” Each lowest-level piece, often called a work package, should be small enough to estimate, assign to one party and measure.

How it works

  1. Start at the project. Level 1 is the whole job.
  2. Break down by the way you will manage it. Common second and third levels are building or area, then phase (sitework, structure, envelope, interiors, MEP, closeout), then floor or zone.
  3. Stop at work packages. The lowest level holds the work a single trade or crew delivers, such as “Level 3 drywall, east wing.”
  4. Check the 100% rule. Every piece of scope appears once, children add up to their parent, and nothing outside the contract scope is included.
  5. Hang activities under it. In a CPM schedule each activity belongs to exactly one WBS node. The node rolls up its children’s dates, durations, cost and percent complete.
  6. Code it. Each node gets a code, such as RMC.B1.03.INT, that sorts and filters predictably.

For the full method, including a WBS dictionary and a budget roll-up check, see how to create a work breakdown structure for a construction project.

WBS vs cost codes vs MasterFormat

WBS Cost codes CSI MasterFormat
Organizes One project’s work Company cost across jobs Specifications and work results
Usually breaks down by Area, phase, system Trade or division, plus cost type 50 divisions of work results
Main users Schedulers, PMs, owners Estimators, accounting, PMs Designers, specifiers, estimators
Varies per project Yes Mostly fixed company-wide Industry standard
Lives in Schedule (P6, Planner) Budget and job cost Project manual, estimates

The three often overlap. Many contractors base cost codes on CSI MasterFormat divisions, and some build the lower levels of the WBS from the same divisions. Where a WBS node meets a cost code, the intersection works as a control account: the place where scope, schedule and budget are measured together.

Why it matters

A schedule without a sensible WBS is a long flat list that nobody can review. With one, a superintendent can collapse to “Building B, Level 2,” an owner can see milestones by phase, and a scheduler can confirm that every part of the scope has activities. That last point is the real value: a gap in the WBS is usually a gap in the plan. Government schedule guidance, such as GAO’s Schedule Assessment Guide, expects the schedule to capture all the work defined in the WBS.

A stable WBS also makes comparison possible. When the WBS barely changes between updates, the schedule baseline and each update can be compared node by node. When it is reorganized midstream, every comparison breaks.

Worked example

Illustrative: a scheduler builds the WBS for a two-building medical campus.

  • Level 1: Riverside Medical Center
  • Level 2: Sitework; Building A (clinic); Building B (parking structure); Closeout
  • Level 3 under Building A: Foundations; Structure; Envelope; Interiors; MEP; Commissioning
  • Level 4 under Interiors: Level 1; Level 2; Level 3

The Level 3 drywall activities sit under Building A > Interiors > Level 3. In the review meeting, the owner looks at Level 2 summaries only; the drywall foreman filters to his branch. When the steel package slips, the scheduler can show the effect on the Building A summary bar and on the critical path without walking anyone through 1,400 activities.

Common mistakes

  • Building the WBS like an org chart or a cost code list instead of around how the work is delivered.
  • Going too deep, so a three-week job has six summary levels.
  • Leaving scope out, such as permits, submittals, procurement or commissioning.
  • Reorganizing the WBS after the baseline, which breaks every comparison.
  • Using the WBS for groupings that belong in activity codes, such as responsible trade or area, when the same activity needs to be grouped more than one way.

How os.construction handles it

In the app today, the Planner keeps a WBS tree with summary bars that span each branch’s earliest start and latest finish, and you can filter the activity grid and Gantt to a WBS branch and everything beneath it. P6 XER and XML imports bring the WBS across with activities and logic, and an import can add a file’s work under a chosen WBS node (import from P6 and Project). Company templates and fragments keep their WBS when they are inserted into a plan, and P6 cost accounts can be mapped to the project’s cost codes (resources and costs).

FAQ

What is a work breakdown structure in construction?

A work breakdown structure (WBS) is a tree that divides a project's total scope into smaller pieces: the project, then phases, areas or systems, then work packages small enough to estimate, schedule and assign. In construction scheduling each activity sits under one WBS node, so the schedule can be summarized, filtered and reported by building, floor, phase or trade.

What is the 100% rule in a WBS?

The 100% rule says the WBS must include all of the project's work and nothing outside it, and each level's children must add up to exactly their parent. If a piece of scope has no home in the WBS, it tends to have no activity, no budget and no owner.

What is the difference between a WBS and cost codes?

A WBS organizes the work for a specific project, often by location, phase or system. Cost codes organize cost across the company, usually by trade or CSI division, so jobs can be compared. Many contractors use both: the WBS for the schedule and reporting by area, cost codes for the budget and job cost. Where they cross, a control account ties schedule and cost together.

What does WBS mean in Primavera P6?

In P6, the WBS is the project's hierarchy of summary nodes. Every activity belongs to one WBS element, and P6 rolls dates, durations, costs and progress up through the tree. WBS summaries show as bars spanning their children's earliest start and latest finish. It is separate from activity codes, which let you group the same activities in other ways.

How detailed should a WBS be?

Detailed enough that each lowest-level work package has a clear scope, one responsible party and a duration you can plan and measure, and no more. A common approach is to break down by building or area first, then by phase or system, then by trade work package. Too many levels make the schedule hard to read and maintain.

Sources

Keep exploring

Related across os.construction

Open file