What Is a WBS in Construction? Work Breakdown Structure

<div class="ge-article-wrapper"><nav class="ge-toc" aria-label="Table of contents"><p class="ge-toc-label">In this article</p><ul class="ge-toc-list"><li><a href="#the-100-rule">The 100% Rule</a></li><li><a href="#the-wbs-tree">The WBS Tree</a></li><li><a href="#wbs-as-the-foundation-of-evm">WBS as the Foundation of EVM</a></li><li><a href="#worked-example-building-a-wbs-for-a-30m-mixed-use-development">Worked Example: Building a WBS for a £30M Mixed-Use Development</a></li><li><a href="#wbs-dictionary-dont-skip-it">WBS Dictionary: Don't Skip It</a></li><li><a href="#common-mistakes">Common Mistakes</a></li><li><a href="#frequently-asked-questions">Frequently Asked Questions</a></li></ul></nav><article class="ge-article-body"><p>A Work Breakdown Structure (WBS) is a hierarchical decomposition of everything the project must deliver, broken down from the top level (the whole project) through phases and packages until you reach the lowest manageable level: the <a href="/en/earned-value/definitions/work-package">work package</a>. Every piece of scope that has a cost, a duration, and an owner lives somewhere in the WBS. If it's not in the WBS, it's not in the project. That principle alone makes the WBS the most important document in <a href="/en/earned-value">earned value management</a>.</p><p>This term is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. The WBS creates the structural backbone that feeds into <a href="/en/earned-value/definitions/control-account">control accounts</a>, <a href="/en/earned-value/formulas">earned value formulas</a>, and every variance report the project controls team produces.</p><h2 id="the-100-rule">The 100% Rule</h2><p>The one rule that governs every WBS. The total scope at any level must equal 100% of the scope at the level above. No gaps. No overlaps.</p><p>If the project is a £30M mixed-use development, then the sum of all level-2 elements must equal £30M. The sum of all level-3 elements under "Superstructure" must equal whatever the superstructure budget is. Break this rule and you've either missed scope (gaps) or double-counted it (overlaps). Both will corrupt your <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> and every metric that flows from it.</p><h2 id="the-wbs-tree">The WBS Tree</h2><pre class="ge-ascii-diagram ge-anim"> WBS – £30M MIXED-USE DEVELOPMENT (LEEDS) ============================================= LEVEL 1: PROJECT ┌───────────────────────────────────────────────────┐ │ £30M Mixed-Use Development │ │ WBS 1.0 │ └───────────┬──────────┬──────────┬────────┬────────┘ │ │ │ │ LEVEL 2: PHASES ┌───────────┐ ┌────────┐ ┌───────┐ ┌──────┐ ┌──────┐ │Substructure│ │ Super │ │ M&amp;E │ │ Ext. │ │Prelims│ │ WBS 1.1 │ │ 1.2 │ │ 1.3 │ │ 1.4 │ │ 1.5 │ │ £4.8M │ │ £10.2M │ │ £8.1M │ │ £4.4M│ │ £2.5M│ └─────┬─────┘ └───┬────┘ └───┬───┘ └──┬───┘ └──────┘ │ │ │ │ LEVEL 3: PACKAGES ┌─────┴─────┐ ┌───┴────┐ │Piling │ │RC Frame│ (and so on for each phase) │WBS 1.1.1 │ │WBS 1.2.1│ │£1,800,000 │ │£5,400,000│ └─────┬─────┘ └───┬────┘ │ │ LEVEL 4: WORK PACKAGES ┌─────┴─────┐ ┌────┴────┐ ┌─────────┐ │Piling │ │Columns │ │Slab L1 │ │(secant) │ │to L2 │ │pour │ │WBS 1.1.1.1│ │WBS 1.2.1.1│ │WBS 1.2.1.2│ │£1,200,000 │ │£2,100,000│ │£1,400,000│ └───────────┘ └─────────┘ └─────────┘ LEVEL 1 = Project total (£30M) LEVEL 2 = Phases (must sum to £30M – the 100% rule) LEVEL 3 = Packages (map to control accounts) LEVEL 4 = Work packages (lowest EV measurement level)</pre><p>The number of levels depends on project complexity. A £5M fit-out might need 3 levels. A £200M infrastructure programme might need 5 or 6. The right answer is: as many levels as you need for the lowest level to be manageable by a single <a href="/en/earned-value/definitions/control-account-manager">CAM</a> with a clear scope, budget, and schedule.</p><h2 id="wbs-as-the-foundation-of-evm">WBS as the Foundation of EVM</h2><p>Without a WBS, you can't do earned value. It's that fundamental.</p><p>Every EVM metric ultimately traces back to the WBS. <a href="/en/earned-value/definitions/planned-value">Planned Value</a> is the time-phased budget of WBS elements. <a href="/en/earned-value/definitions/earned-value">Earned Value</a> is the budgeted value of completed WBS elements. <a href="/en/earned-value/definitions/cost-variance">Cost Variance</a> is calculated at WBS level and rolled up. The WBS is where scope, cost, and schedule converge.</p><pre class="ge-ascii-diagram ge-anim"> WBS – THE INTEGRATION POINT ============================================= SCOPE (what) COST (how much) SCHEDULE (when) ────────────── ────────────── ────────────── Specifications Budget estimates Programme dates Drawings Rate build-ups Durations Requirements Allowances Dependencies │ │ │ └────────────────────┼─────────────────────┘ │ ┌────┴────┐ │ WBS │ │ │ │ Scope + │ │ Cost + │ │ Schedule│ │ = EVM │ └────┬────┘ │ ┌───────────────┼───────────────┐ │ │ │ Control Performance Variance Accounts Measurement Analysis Baseline (PMB) Reports</pre><p>I've seen teams try to run EVM without a proper WBS. They assign costs to activity codes in the programme and call it earned value. It works for about three months until someone asks "why is the M&amp;E package showing 40% complete but the budget says 60% should be spent?" and nobody can reconcile the numbers because the activity codes don't map to a coherent scope hierarchy. The WBS prevents that chaos.</p><h2 id="worked-example-building-a-wbs-for-a-30m-mixed-use-development">Worked Example: Building a WBS for a £30M Mixed-Use Development</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £30M NEC4 Option C mixed-use development in Leeds (12 residential units above ground-floor retail). The commercial team needs to build a WBS that supports <a href="/en/earned-value">earned value management</a>. The project has a 22-month programme starting April 2025.</p><p><strong>Step 1: Define level 2 (phases)</strong></p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>WBS Code</th><th>Phase</th><th>BAC</th></tr></thead><tbody><tr><td>1.1</td><td>Substructure</td><td>£4,800,000</td></tr><tr><td>1.2</td><td>Superstructure</td><td>£10,200,000</td></tr><tr><td>1.3</td><td>M&amp;E (all services)</td><td>£8,100,000</td></tr><tr><td>1.4</td><td>External Works</td><td>£4,400,000</td></tr><tr><td>1.5</td><td>Prelims &amp; Site Management</td><td>£2,500,000</td></tr><tr><td></td><td><strong>Total (BAC)</strong></td><td><strong>£30,000,000</strong></td></tr></tbody></table></div><p>100% rule check: £4.8M + £10.2M + £8.1M + £4.4M + £2.5M = £30M. Correct.</p><p><strong>Step 2: Break level 2 into level 3 (packages)</strong></p><p>Taking WBS 1.2 (Superstructure) as an example:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>WBS Code</th><th>Package</th><th>BAC</th></tr></thead><tbody><tr><td>1.2.1</td><td>RC Frame</td><td>£5,400,000</td></tr><tr><td>1.2.2</td><td>Structural Steelwork</td><td>£2,200,000</td></tr><tr><td>1.2.3</td><td>Roof Structure</td><td>£1,600,000</td></tr><tr><td>1.2.4</td><td>Masonry / Cladding</td><td>£1,000,000</td></tr><tr><td></td><td><strong>Superstructure Total</strong></td><td><strong>£10,200,000</strong></td></tr></tbody></table></div><p>Each level-3 package becomes a <a href="/en/earned-value/definitions/control-account">control account</a> with a named <a href="/en/earned-value/definitions/control-account-manager">CAM</a>. The <a href="/en/earned-value/definitions/responsibility-assignment-matrix">RAM</a> assigns accountability.</p><p><strong>Step 3: Break level 3 into level 4 (work packages)</strong></p><p>Taking WBS 1.2.1 (RC Frame, £5.4M):</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>WBS Code</th><th>Work Package</th><th>BAC</th><th>Duration</th><th>EVT</th></tr></thead><tbody><tr><td>1.2.1.1</td><td>Columns to level 2</td><td>£2,100,000</td><td>6 weeks</td><td><a href="/en/earned-value/definitions/weighted-milestones">Weighted milestones</a></td></tr><tr><td>1.2.1.2</td><td>Slab level 1 pour</td><td>£1,400,000</td><td>3 weeks</td><td>0/100</td></tr><tr><td>1.2.1.3</td><td>Columns level 2 to roof</td><td>£1,200,000</td><td>5 weeks</td><td>Weighted milestones</td></tr><tr><td>1.2.1.4</td><td>Roof slab</td><td>£700,000</td><td>2 weeks</td><td>0/100</td></tr><tr><td></td><td><strong>RC Frame Total</strong></td><td><strong>£5,400,000</strong></td><td></td><td></td></tr></tbody></table></div><p>Each work package has a defined scope, budget, schedule, and earned value technique (EVT). This is the level where progress is physically measured on site.</p><p><strong>Result:</strong> 4-level WBS with 22 work packages across 10 control accounts, all summing to £30M. Each work package can be measured independently, rolled up to control account level for <a href="/en/earned-value/definitions/control-account-manager">CAM</a> reporting, and further rolled up to project level for the board report.</p></div><h2 id="wbs-dictionary-dont-skip-it">WBS Dictionary: Don't Skip It</h2><p>Every WBS element should have a dictionary entry. I know that sounds like bureaucracy. It's not. The <a href="/en/earned-value/definitions/wbs-dictionary">WBS dictionary</a> is the document that defines exactly what's in and what's out of each element. Without it, the boundary between "RC Frame" and "Structural Steelwork" is ambiguous. Does the frame package include the steel connections? The holding-down bolts? The grout packs?</p><p>On one project I worked on, a £45M logistics warehouse, the WBS didn't define whether the mezzanine steel was in "Superstructure" or "Fit-out." Both CAMs excluded it from their budgets. It was a £380K gap that didn't surface until month 9 when the steel was fabricated and nobody had a budget line for it.</p><p>A two-paragraph dictionary entry per work package would have caught that at mobilisation.</p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Organising by phase instead of deliverable.</strong> A WBS that reads "Design / Procurement / Construction / Commissioning" is a schedule, not a WBS. The WBS should decompose what you're delivering (substructure, superstructure, M&amp;E), not when you're delivering it. The programme handles the "when."</li><li><strong>Going too deep or too shallow.</strong> If the lowest WBS level is "Superstructure, £10.2M," it's too high for meaningful EV measurement. If it's "Install individual rebar cage in column C14," it's too detailed for monthly reporting. The right level is where a single person can own the scope, budget, and schedule. Usually that's the work package level at £100K to £2M each.</li><li><strong>Violating the 100% rule.</strong> The most common violation: forgetting to include prelims, temporary works, or design costs in the WBS. They're real scope with real budgets. If the WBS only covers construction activities, 10-15% of BAC is floating outside the WBS structure. That distorts every EV calculation.</li><li><strong>No WBS coding system.</strong> Using descriptive names without hierarchical codes makes roll-up impossible. "1.2.1.3" tells you instantly that this element sits under superstructure (1.2), RC frame (1.2.1), and is the third work package. "Roof slab" tells you nothing about hierarchy.</li></ol><div class="ge-product-note ge-anim"><p><strong>How Gather helps.</strong> Gather's AI reads your site diaries daily and maps progress against your cost-loaded programme, giving you accurate earned value data without manual spreadsheet updates. <a href="https://gatherinsights.com/contact">Book a demo</a> to see it working on a live NEC4 project.</p></div><h2 id="frequently-asked-questions">Frequently Asked Questions</h2><h3>How many levels should a construction WBS have?</h3><p>Three to five. On most UK construction projects between £5M and £50M, four levels work well: project, phase, package, work package. Larger programmes (£100M+) might need a fifth level to keep work packages at a manageable size. Going beyond five levels usually means you're over-decomposing, save that detail for the programme, not the WBS.</p><h3>What's the difference between a WBS and a programme (schedule)?</h3><p>The WBS shows what. The programme shows when and in what order. The WBS is a hierarchical tree of deliverables. The programme is a sequence of activities with durations, dependencies, and dates. They're connected, every programme activity should map to a WBS element, but they're separate documents serving different purposes. You can have a WBS without a programme (at tender stage). You shouldn't have a programme without a WBS.</p><h3>Can the WBS change after the baseline is set?</h3><p>Yes, but through a controlled process. Scope changes (compensation events on NEC4, variations on JCT) can add new WBS elements or change existing budgets. This is a formal <a href="/en/earned-value/definitions/re-baselining">re-baselining</a> exercise: update the WBS, adjust BAC, revise the PV curve, and document the change. Don't just add a line to the spreadsheet and carry on.</p><h3>Does the WBS include subcontracted work?</h3><p>Yes. Subcontracted work is still project scope. The WBS includes it; the <a href="/en/earned-value/definitions/organisational-breakdown-structure">OBS</a> assigns a CAM to manage it. The CAM might be a package manager who oversees the subcontractor's delivery. The fact that another company is doing the physical work doesn't exempt it from EVM tracking.</p></article></div>