WBS Structure Design
Last reviewed 9 September 20262,278 words10 min read
Building one that survives three years — because you cannot rebuild it in month fourteen
🟩 In one line: The WBS is the one hierarchy every activity belongs to exactly once; build it contract → phase → area or level → discipline, five or six levels deep, from nouns not verbs, aligned to how the job is paid and reported — and put everything else in codes, because the WBS is the only structure you can't change without breaking every baseline comparison.
👤 Who this is for: J/M/S. Prerequisites: schedule-levels-1-to-5, setting-up-a-p6-project. Companion to activity-coding-structure.
First, let's be honest about why this page exists
The WBS gets built in the first week by whoever is free, usually by copying the last project and renaming nodes. Eighteen months later the client wants progress by zone, the QS wants it by BOQ section, the subcontractor wants it by package, and the WBS delivers none of them because it was built around the site layout the tender team had in mind. Restructuring it now means moving 3,000 activities, and Schedule Comparison against the accepted baseline stops matching the day you do.
The WBS answers one question: where does this activity belong? Every other question — who does it, which zone, which package, which drawing — is answered by a code. Get that division right in week one and the structure lasts.
🟨 The standard — what "good" looks like
| Source | What it asks for (paraphrased) | Consequence |
|---|---|---|
| PMI Practice Standard for Work Breakdown Structures, 3rd ed. | Deliverable-oriented, hierarchical, 100% rule — each level fully decomposes its parent, nothing outside | Nouns (deliverables), not verbs; no activity without a home; no node that overlaps another |
| ISO 21511:2018 | WBS defines total scope hierarchically for management and control | Same principles, international wording |
| GAO Schedule Assessment Guide, BP 1 and 5 | All activities captured; schedule traceable to the WBS and to the cost/scope baseline | WBS aligned to the cost breakdown, so EV and cash flow roll up |
| AACE RP 38R-06 | Basis records the WBS and its rationale | Structure diagram and rules in the SBM |
| PMI Practice Standard for Scheduling, 2nd ed. | Activities organised under a WBS; consistent decomposition | Same depth rule applied across the job |
| FIDIC 1999 Cl 8.3 / 2017 Cl 8.3; NEC Cl 31.2 | Programme shows order and timing of the Works; NEC lists what the programme must show | A WBS that lets the reviewer find any part of the Works quickly is how these are satisfied |
| Client schedule specifications (typical Gulf) | Frequently prescribe the top three levels and a match to the payment breakdown | The spec's structure is adopted; your detail hangs below it |
🟢 Rule: one WBS, deliverable nouns, 100% rule at every level, top levels matching the contract's payment and reporting structure, no deeper than six, frozen at baseline — and anything you would ever want to slice a second way goes in an activity code instead.
How it actually works
1. The shape
| Level | Content | Example — residential tower, Abu Dhabi | Who reads at this level |
|---|---|---|---|
| 0 | Project | AUH-RT14 Residential Tower | Board |
| 1 | Phase / major deliverable | Design & approvals · Procurement · Construction · T&C & handover · Prelims | Client Level 1 report |
| 2 | Area / element | Substructure · Tower · Podium · External works · Infrastructure connections | Level 2 report; sectional completions |
| 3 | Sub-area / level band | B2–B1 · GF–L4 · L5–L9 · L10–L14 · Roof | Level 3 = contract baseline |
| 4 | Discipline / trade | Structure · Blockwork · MEP first fix · Finishes · Façade | Site team; payment application sections |
| 5 (optional) | Floor or zone where a band holds several | L5 · L6 · L7 … or Zone A / Zone B | Level 4 look-ahead |
| Activities | Verbs live here | "Pour L5 slab", "First fix L5 Zone A" | — |
Five levels covers most buildings; six for towers with zoned floors; four for a small fit-out. Infrastructure swaps "level" for chainage or structure; EPC uses system or unit. The depth rule is the same everywhere: the same kind of thing at the same level across the whole tree. If Level 4 is discipline under the tower, it is discipline under the podium too.
2. WBS or code? The test
| If you want to… | Use |
|---|---|
| Find where an activity belongs; roll up cost, hours and progress for the payment application; report at L1/L2/L3 | WBS |
| Filter or group by something that cuts across the tree — subcontractor, zone across all floors, drawing, system, responsibility, change reference | Activity code |
| Store a number or text against the activity — quantity, rate, crew, duration basis | UDF |
The tell: if an activity could sit in two nodes, one of those dimensions is a code. A subcontract package spans areas → code. A zone that appears on every floor → code (or level 5, but not both). A variation → own WBS node (change-control-in-a-live-schedule) and the Change Ref code — the node because its cost must roll up separately, the code because it must also be filterable across the tree.
3. Alignment with money
The WBS at levels 1–3 should map to the payment breakdown — BOQ bills or milestone schedule — closely enough that the cost-loaded schedule rolls up to the application without a cross-reference table. Where the BOQ is by trade and the site is run by area, put area at level 2 and trade at level 4; the roll-up by trade is then a Group & Sort on the discipline code. Never invert the WBS to suit the QS if the site team will live in it every day; give the QS a code.
4. Nodes that always exist
| Node | Why |
|---|---|
| Milestones (contractual key dates, planned completion, contractual completion) | One place to find every date the contract cares about |
| Preliminaries / site establishment | LOE activities live here, out of the production tree |
| Procurement & long-lead | Submittal → approval → fabrication → delivery chains, per item |
| Design & approvals | Where design is the contractor's; review cycles are activities |
| Variations (one child node per VO/CE) | Cost and time per change, filterable |
| T&C and handover | Systems, not floors — MEP completion is by system |
| Recovery / TRA (where named contingency exists) | "TRA — …" activities visible, not buried |
5. Building it in P6
- Projects → WBS view; add children with Insert; codes auto-build from the separator set in Project Details → Settings.
- WBS code short and stable (RT14.CON.TWR.L05.BLK); the name carries the words. Codes appear in every export and every Power BI table — keep them under 20 characters per segment.
- Each node: Responsible Manager (OBS), Earned Value tab set per rule of credit where it differs from the project default, Notebook "WBS Scope" one line per node stating what is in and out.
- Anticipated dates left blank on nodes that have activities; used only on placeholder nodes in rolling-wave planning until detail exists.
- Freeze at baseline acceptance. After that, additions (variations, splits) are new nodes under existing parents; no renames, no moves, no deletions of existing nodes without a baseline revision and a mapping table.
6. Checks before baseline
| Check | Pass |
|---|---|
| Every activity in a leaf node (no activities on nodes that also have child nodes) | Yes |
| Same kind of thing at the same level across every branch | Yes |
| Every node has at least one activity or a documented rolling-wave placeholder | Yes |
| Node names are nouns; activity names are verb + object + location | Yes |
| Depth ≤ 6 | Yes |
| Top three levels match the client spec and the payment breakdown | Yes |
| No two nodes could hold the same activity | Yes |
| WBS diagram and rules in SBM section 4 | Yes |
🟥 Where people go wrong
- Copying the last job's WBS. A hospital's tree on a residential tower, with "Operating theatres" renamed "Apartments" and the depth wrong from level 2 down. Build from the contract's own breakdown.
- Verbs at node level. "Excavate", "Construct tower", "Install MEP" as nodes; then activities repeat the verb. Nodes are things — Substructure, Tower, MEP — and the verbs are the activities inside.
- Subcontractor as a WBS level. The mechanical sub's scope spans every floor; the tree forces every floor to repeat under every sub. Subcontractor is a code; the tree is physical.
- Uneven depth. Tower goes six levels, external works two. The Level 3 report then mixes floors with whole areas and the roll-up percentages mean nothing. Same kind of thing at the same level.
- Restructuring mid-project. Moving activities between nodes breaks the baseline comparison at node level and the payment roll-up in the same month. Additions only after baseline; a restructure is a baseline revision with a mapping table.
- Activities on parent nodes. An activity sitting on "Tower" alongside child nodes "L5", "L6" rolls up nowhere sensible and is invisible in the level reports. Leaf nodes only.
- No node for milestones, prelims, procurement or variations. They get scattered through the production tree and the LOE ends up under "L5 Blockwork". Standing nodes, every project.
⚖️ When you're challenged
"The QS wants the WBS by BOQ bill so the cost loads directly." Levels one to three already follow the payment breakdown — that's what the application rolls up from. Below that the site team needs area and level, because that's how the work is run. The BOQ bill is a code on every activity, so the QS gets the bill view with a Group & Sort. Both get what they need from one structure.
"Add a 'Phase 2' node and move the L10–L14 activities into it." Moving them breaks the comparison to the accepted baseline at node level and changes the roll-up in the application. If Phase 2 is a real contractual sectional completion we do it as a baseline revision with a mapping table. If it's a reporting view, it's a code and a layout — done this afternoon, nothing moves.
"Why is the mechanical subcontractor not in your WBS?" Because their scope is on every floor, and a tree can only hold each activity once. They're the Subcontractor code on 340 activities; grouping by that code gives their whole programme in one view, across the tree.
📄 Related pages
- Activity Coding Structure — the second axis: everything that isn't the tree
- Schedule Levels 1 to 5 — which WBS level each report reads
- Setting Up a P6 Project — separator, code length, defaults
- Cost Loading and Cash Flow — the payment roll-up the WBS must serve
- Rolling Wave Planning — placeholder nodes and anticipated dates
- Change Control in a Live Schedule — the variation node convention
- Splitting In-Progress Activities — additions after baseline without moving nodes
- Schedule Basis Memorandum — where the diagram lives
✏️ Worked example
A mixed-use podium-and-tower in Riyadh; client spec prescribes levels 1–2 (Phase, Area) and a match to the milestone payment schedule. The first-week WBS and the corrected one:
| Issue in the first draft | Correction | Reason |
|---|---|---|
| Level 3 = subcontract package (Structure Sub, MEP Sub, Façade Sub) | Level 3 = level band; Subcontractor moved to a project activity code | Packages span areas; tree is physical |
| Tower decomposed to floor and zone (6 levels); podium stopped at discipline (4 levels) | Podium given a level band and, where zoned, a zone level | Same kind of thing at the same level |
| "Install MEP", "Construct structure" as node names | "MEP", "Structure" | Nouns at nodes |
| 41 activities on parent nodes | Moved to leaf nodes; 3 new leaf nodes created | Roll-up |
| Variations planned as extended durations on existing activities | "Variations" node with one child per VO | Time and cost per change |
| No milestone node; contractual dates scattered | "Milestones" node; 11 contractual milestones with FOoB constraints and register rows | One place |
| Tower crane, hoists, supervision under "Structure" | "Preliminaries" node; all LOE | Out of production tree; excluded from metrics |
Result: 5 levels under the tower, 5 under the podium, 3 under external works (deliberately shallower — smaller scope, still same kind of thing at each level); 2,860 activities; payment application rolls up from level 3 without a cross-reference; SBM section 4 carries the diagram and the WBS-or-code rule. Eighteen months in, 6 variation nodes and 34 split activities added, zero nodes moved.
📖 References
- PMI Practice Standard for Work Breakdown Structures, 3rd ed.
- ISO 21511:2018, Work breakdown structures for project and programme management
- GAO Schedule Assessment Guide (GAO-16-89G), Best Practices 1, 5
- AACE International RP 38R-06, Documenting the Schedule Basis
- PMI Practice Standard for Scheduling, 2nd ed.
- FIDIC Conditions of Contract for Construction, 1999 and 2017, Cl 8.3; NEC3/NEC4 ECC Cl 31.2 (check the edition in your contract)
- Oracle Primavera P6 Professional User Guide — Work Breakdown Structure; WBS Earned Value settings; Project Settings (WBS separator)
From the field
Experience from working planners. Unreviewed — read it as experience, not guidance.
Add what you know about wbs structure design. What worked, what the consultant pushed back on, what you would do differently next time. A paragraph is plenty.
Contributors get their name and one link on the site — your own templates, course or consultancy. We take nothing and hold nothing.
Add your experience