On this page
- Step 1: Start with the whole scope
- Step 2: Choose the second-level split
- Step 3: Break down to work packages
- Step 4: Check the 100% rule
- Step 5: Number it and write the dictionary
- Step 6: Tie it to cost codes
- Step 7: Hang the schedule activities and freeze it
- Worked example: a three-story office building
- Common mistakes
- How os.construction handles it
- FAQ
To create a work breakdown structure, put the whole contract scope at level 1, choose a second-level split that matches how the job will be built and reported, and break each branch down until every piece is a work package one party can own, estimate and measure. Check that every node’s children add up to the whole of it, write a one-paragraph dictionary entry for each work package, then tie the packages to your cost codes and hang the schedule activities under them.
A work breakdown structure answers “what work is there?” before the schedule answers “in what order, and when?” Get it right and the schedule, the budget and the progress report all roll up the same way, so the superintendent, the PM and the owner are looking at the same job cut three ways. Get it wrong and the schedule is a flat list of 1,400 activities nobody can review, or worse, the plan quietly misses part of the scope.
Step 1: Start with the whole scope
Level 1 is the project: everything the contract requires, including the work people forget to schedule, such as permits, submittals and procurement, commissioning, closeout and turnover. Pull the scope from the contract, the drawings and the specification table of contents. If you can’t list the major deliverables, you’re not ready to break them down.
Step 2: Choose the second-level split
This is the decision that matters most. Common choices on building jobs:
- By building or area, when parts of the job are built and turned over separately.
- By phase, such as sitework, substructure, structure and envelope, interiors, systems and closeout, when the job is built in that order as one piece.
- By system, which suits heavy civil and process work, where the deliverables are systems.
Pick the axis your team will actually review the job by, and use one axis per level. Mixing “Level 2” and “Electrical” as siblings at the same level is how work ends up in two places or none. Other ways of slicing the same work, such as responsible trade or area within a floor, can be carried as activity codes instead of extra levels.
Step 3: Break down to work packages
Keep decomposing each branch until you reach a work package: a piece of work with a clear scope, one responsible party, a cost you can estimate and progress you can measure. “Level 3 interiors” is usually a work package; “Level 3 drywall, east wing” might be, if that’s how you’ll manage it. Stop there. The activities go under the work packages in the schedule, not into the WBS as more levels.
A rule of thumb many planners use is that a work package should be big enough to be worth tracking on its own and small enough to finish within a few reporting periods, so its progress is visible. It’s a guide, not a law; let the job decide.
Step 4: Check the 100% rule
For every node, the children must add up to the whole of the parent: all of its scope, nothing outside it, and no piece in two places. PMI’s practice standard for work breakdown structures calls this the 100% rule. Two quick tests:
- Scope test. Walk the specification sections and the major drawing scopes. Each one should land in exactly one branch.
- Budget test. Load the estimate by work package and check that the children’s budgets sum to each parent’s. A mismatch means a gap or a duplicate.
Step 5: Number it and write the dictionary
Give each node a code that sorts and filters predictably, such as 1.5.2 for Level 2 interiors. Then write a short dictionary entry for each work package:
- What it includes and what it excludes.
- Who’s responsible: a trade, a crew or a person.
- The cost codes it uses and its budget.
- Key quantities and how progress will be measured.
The dictionary is where you settle questions like whether the stair framing belongs to structure or interiors, once, in writing.
Step 6: Tie it to cost codes
The WBS and your cost codes are different lists. Cost codes describe the kind of cost the same way on every job; the WBS describes this job’s scope. Where they meet, a work package’s spending on one cost code, you have a control account, the place where budget, cost and progress are compared. Keep the cost code list company-wide and let the WBS carry the job-specific structure, rather than inventing new codes for every floor.
Step 7: Hang the schedule activities and freeze it
Every schedule activity sits under exactly one work package. The WBS summaries then roll up dates, cost and percent complete. Before you save the schedule baseline, review the WBS with the superintendent and PM, then freeze it. Changing the structure after the baseline breaks every comparison between updates; add new scope to the right branch instead of reorganizing.
Worked example: a three-story office building
A GC builds a three-story office building with a $10,100,000 cost budget. The team builds the structure, envelope and systems as one building, but finishes interiors floor by floor, and the owner wants interiors reported by floor. So level 2 is by phase, and the interiors branch splits by floor at level 3.
| Code | WBS element | Budget |
|---|---|---|
| 1 | Office building | $10,100,000 |
| 1.1 | Sitework | $640,000 |
| 1.2 | Substructure | $820,000 |
| 1.3 | Superstructure and envelope | $3,150,000 |
| 1.4 | Building systems (mechanical, electrical, plumbing, fire protection) | $2,310,000 |
| 1.5 | Interiors | $2,420,000 |
| 1.5.1 | Level 1 interiors | $860,000 |
| 1.5.2 | Level 2 interiors | $780,000 |
| 1.5.3 | Level 3 interiors | $780,000 |
| 1.6 | Project management, general conditions and closeout | $760,000 |
Budget test at level 2: $640,000 + $820,000 + $3,150,000 + $2,310,000 + $2,420,000 + $760,000 = $10,100,000. At level 3 under interiors: $860,000 + $780,000 + $780,000 = $2,420,000. Both tie.
Control accounts under 1.5.2. Level 2 interiors uses five cost codes:
| Control account | Budget |
|---|---|
| 1.5.2 × 08 Doors, frames and hardware | $160,000 |
| 1.5.2 × 09 21 Gypsum board assemblies | $312,000 |
| 1.5.2 × 09 51 Acoustical ceilings | $96,000 |
| 1.5.2 × 09 65 Resilient and carpet flooring | $148,000 |
| 1.5.2 × 09 91 Painting | $64,000 |
| Total, ties to 1.5.2 | $780,000 |
Two decisions are worth noticing. Building systems stay as one branch at level 2, not split by floor, because the mechanical and electrical rough-in, risers and equipment are bought and managed as whole-building packages; floor-by-floor progress for those trades is carried as a location code on the activities. And the stair framing, which could plausibly sit in structure or interiors, is written into the 1.3 dictionary entry so nobody budgets it twice.
When the owner asks how Level 2 is doing, the PM reports one node with its dates, budget, cost and percent complete. When drywall on Level 2 runs over, the control account 1.5.2 × 09 21 shows exactly where.
Common mistakes
- Using the cost code list as the WBS. You get a trade list with no sense of area or phase, and every job looks the same.
- Mixing axes at one level, such as floors and trades as siblings, so work lands twice or not at all.
- Going too deep. Levels nobody reviews make the schedule harder to read and maintain.
- Leaving out scope: permits, procurement, submittals, commissioning, closeout.
- No dictionary, so the boundary between branches is settled by whoever codes the invoice.
- Reorganizing after the baseline, which breaks every period-to-period comparison.
- Budgets that don’t tie, because the estimate was loaded on a different structure.
The construction schedule (Gantt) template is a simple place to try a WBS before you build it in your scheduling tool, and line of balance is worth a look if repetitive floors or units are the main shape of your job.
How os.construction handles it
In the Schedule, you add WBS summaries for the phases or areas you schedule by, nested as deep as you need, and each activity points at its summary. Summary bars span each branch’s earliest start and latest finish, and you can filter the grid and Gantt to one branch and everything beneath it (activity grid and Gantt). Company schedule templates and fragments keep their WBS when inserted into a plan (creating schedules), and earned value can be read for the project and per WBS. On the cost side, the project’s financial records include a work breakdown structure alongside the budget and commitments, and budgets sit on cost codes as described in cost codes and budgets. See construction scheduling software for the wider Schedule tool.
FAQ
How do you create a work breakdown structure for a construction project?
Start with the whole contract scope as level 1. Choose the second-level split that matches how the job will be built and reported, usually by area, building or phase. Break each branch down until you reach work packages that one party can own, estimate and measure. Check that the children of every node add up to the whole of the parent, write a short dictionary entry for each work package, then link the work packages to cost codes and hang the schedule activities under them.
How many levels should a construction WBS have?
As few as you need for the decisions people make with it. Many building projects work with three to five levels: project, area or building, phase or system, then floor or zone work packages. If a level doesn't change how anyone reviews or reports the job, it probably isn't needed.
What is the 100% rule in a WBS?
The WBS must include all of the project's scope, and nothing outside it, and the children of each node must add up to exactly the whole of the parent. If you check a level and something in the contract scope has no home, or two branches both contain the same work, the WBS needs fixing.
Is a WBS the same as a cost code list?
No. Cost codes are a company-wide list of the kinds of cost, usually by trade or division, used on every job. The WBS is specific to one project and organizes its scope, usually by area, phase or system. They meet where a WBS work package uses a cost code; that intersection is often called a control account.
What is a WBS dictionary?
A short description of each work package: what's included and excluded, who's responsible, the cost codes it uses, key quantities, and how progress will be measured. It stops two people from reading the same WBS line two different ways.
Share this article