What Is a WBS Dictionary? Definition, Template & Example

<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="#why-you-need-one">Why You Need One</a></li><li><a href="#what-a-wbs-dictionary-entry-contains">What a WBS Dictionary Entry Contains</a></li><li><a href="#the-essential-fields">The Essential Fields</a></li><li><a href="#worked-example-building-a-wbs-dictionary-for-a-school-extension">Worked Example: Building a WBS Dictionary for a School Extension</a></li><li><a href="#how-the-wbs-dictionary-connects-to-evm">How the WBS Dictionary Connects to EVM</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 WBS Dictionary is the companion document to the <a href="/en/earned-value/definitions/work-breakdown-structure">Work Breakdown Structure</a> that describes exactly what each WBS element contains, its scope, deliverables, budget, schedule, responsible <a href="/en/earned-value/definitions/control-account-manager">Control Account Manager</a>, and the <a href="/en/earned-value/definitions/units-complete">earned value technique</a> used to measure progress. Without it, a WBS is just a tree diagram with labels. With it, everyone on the project knows precisely what's included in "Structural Frame" and what isn't.</p><p>The WBS Dictionary is part of the <a href="/en/earned-value/definitions">earned value definitions glossary</a>. For the broader EVM setup process, see the <a href="/en/earned-value/implementation-guide">implementation guide</a>.</p><h2 id="why-you-need-one">Why You Need One</h2><p>I'll be direct. Most scope disputes on construction projects happen because two people had different assumptions about what was included in a work package. The subcontractor assumed temporary works were in the main contractor's scope. The QS assumed the M&amp;E subcontractor was providing builders' work. The project manager thought the design consultant was doing the coordination drawings.</p><p>A WBS Dictionary eliminates that ambiguity. Every element in the WBS gets a written definition that says: this is what's in, this is what's out, and here's who's responsible.</p><p>On one hospital project I worked on, the absence of a WBS Dictionary led to a £340,000 dispute over who was responsible for fire stopping around M&amp;E penetrations. Both the main contractor and the M&amp;E subcontractor assumed it was the other's scope. Neither had priced it. A single paragraph in a WBS Dictionary would have prevented the entire argument.</p><h2 id="what-a-wbs-dictionary-entry-contains">What a WBS Dictionary Entry Contains</h2><pre class="ge-ascii-diagram ge-anim">WBS DICTIONARY ENTRY – Example ============================================= +--------------------------------------------------+ | WBS ELEMENT: 3.2.1 | | TITLE: Structural Frame – Steel Erection | +--------------------------------------------------+ | | | SCOPE OF WORK: | | Supply, delivery, and erection of structural | | steelwork to floors 1-6 including primary beams, | | secondary beams, columns, and bracing. Includes | | holding-down bolts, base plates, shear studs, | | and all connections. Excludes metal decking | | (see WBS 3.2.2) and fire protection coating | | (see WBS 3.2.4). | | | +--------------------------------------------------+ | DELIVERABLES: | | - Approved fabrication drawings | | - Material test certificates | | - Erected steelwork (455 tonnes) | | - Torque certificates for HSFG bolts | | - As-built survey | +--------------------------------------------------+ | CONTROL ACCOUNT: CA-003 (Superstructure) | | CAM: R. Patel | +--------------------------------------------------+ | BUDGET: £1,820,000 | | DURATION: 12 weeks (3 Mar – 23 May 2026) | +--------------------------------------------------+ | EVT: Weighted Milestones | | Milestones: | | M1: Steel delivered to site 10% (£182K) | | M2: Floors 1-2 erected 25% (£455K) | | M3: Floors 3-4 erected 25% (£455K) | | M4: Floors 5-6 erected 25% (£455K) | | M5: Connections complete + survey 15% (£273K) | +--------------------------------------------------+ | EXCLUSIONS: | | - Metal decking (WBS 3.2.2) | | - Fire protection intumescent coating (WBS 3.2.4) | | - Crane hire (WBS 5.1.3 – Preliminaries) | | - Tower crane foundation (WBS 3.1.2) | +--------------------------------------------------+ | ASSUMPTIONS: | | - Access to all floors via core for erection | | - Steel fabrication lead time: 8 weeks | | - No out-of-sequence working required | +--------------------------------------------------+ | RISKS: | | - Steel supply chain disruption (medium) | | - Adverse weather affecting crane operations (med)| | - Design changes to connections (low) | +--------------------------------------------------+</pre><p>Every field serves a purpose. Take any one away and you've got a gap that someone will exploit, accidentally or otherwise.</p><h2 id="the-essential-fields">The Essential Fields</h2><p>Not every project needs every field above. But these are non-negotiable:</p><div class="ge-table-wrap ge-anim"><table class="ge-table"><thead><tr><th>Field</th><th>Why It's Essential</th></tr></thead><tbody><tr><td><strong>WBS Element ID</strong></td><td>Unique reference. Ties to cost codes, schedule activities, and EVM data</td></tr><tr><td><strong>Scope of Work</strong></td><td>What's included. Written in enough detail that any QS could price it</td></tr><tr><td><strong>Exclusions</strong></td><td>What's NOT included. With cross-references to the WBS elements that do cover it</td></tr><tr><td><strong>Control Account</strong></td><td>Which CA this element rolls into for EVM reporting</td></tr><tr><td><strong>CAM</strong></td><td>Who's accountable. One person, not a team</td></tr><tr><td><strong>Budget</strong></td><td>The <a href="/en/earned-value/definitions/budget-at-completion">BAC</a> for this element</td></tr><tr><td><strong>EVT</strong></td><td>How progress is measured, <a href="/en/earned-value/definitions/units-complete">units complete</a>, <a href="/en/earned-value/definitions/weighted-milestones">weighted milestones</a>, percent complete, or Level of Effort</td></tr><tr><td><strong>Deliverables</strong></td><td>Tangible outputs. These are what you measure progress against</td></tr></tbody></table></div><p>The exclusions field is arguably the most important. It's the one that prevents scope disputes. "Structural Frame includes X, Y, Z" is good. "Structural Frame includes X, Y, Z and excludes A, B, C, see WBS elements [ref] for those" is bulletproof.</p><h2 id="worked-example-building-a-wbs-dictionary-for-a-school-extension">Worked Example: Building a WBS Dictionary for a School Extension</h2><span class="ge-worked-label">Worked Example</span><div class="ge-callout ge-anim"><p><strong>Scenario:</strong> A £8M NEC4 Option A primary school extension in Leeds. The WBS has 4 levels and 38 elements at the <a href="/en/earned-value/definitions/work-package">work package</a> level. The commercial manager is building the WBS Dictionary during mobilisation.</p><p><strong>Three sample entries:</strong></p><p><strong>Entry 1: WBS 2.1.1, Strip Foundations</strong></p><ul><li>Scope: Excavation, blinding, formwork, reinforcement, and concrete to strip foundations. Includes mass concrete fill to trenches.</li><li>Exclusions: Piled foundations (WBS 2.1.2), ground beams (WBS 2.1.3), ground floor slab (WBS 2.2.1)</li><li>CA: CA-001 (Substructure) | CAM: D. Ahmed</li><li>Budget: £340,000 | Duration: 5 weeks</li><li>EVT: Units complete (linear metres of foundation cast)</li><li>Total quantity: 420 linear metres at £810/m</li></ul><p><strong>Entry 2: WBS 3.4.1, Curtain Walling</strong></p><ul><li>Scope: Supply and installation of aluminium curtain walling system to south and east elevations. Includes structural silicone glazing, thermal breaks, and flashings. Excludes internal reveals and decoration (WBS 4.2.3).</li><li>Exclusions: Brickwork below DPC (WBS 3.3.1), internal window boards (WBS 4.2.3), external doors (WBS 3.4.2)</li><li>CA: CA-003 (Envelope) | CAM: S. Williams</li><li>Budget: £620,000 | Duration: 8 weeks</li><li>EVT: Weighted milestones (4 milestones: mock-up approved 10%, south elevation 35%, east elevation 35%, snagging complete 20%)</li></ul><p><strong>Entry 3: WBS 5.1.1, Site Management</strong></p><ul><li>Scope: Site manager, project engineer, and site secretary for 36-week contract duration. Includes welfare facilities running costs.</li><li>Exclusions: Temporary works coordinator (WBS 5.1.3), health and safety advisor (WBS 5.1.4)</li><li>CA: CA-007 (Preliminaries) | CAM: T. Reynolds</li><li>Budget: £285,000 | Duration: 36 weeks</li><li>EVT: Level of Effort (apportioned to programme duration)</li></ul><p>The WBS Dictionary for all 38 elements took the commercial manager 3 days to compile. That's 3 days upfront to prevent months of arguments during delivery.</p></div><h2 id="how-the-wbs-dictionary-connects-to-evm">How the WBS Dictionary Connects to EVM</h2><p>The WBS Dictionary is the bridge between scope definition and <a href="/en/earned-value/definitions/earned-value">earned value</a> measurement. The EVT field in each entry determines how progress is measured. The budget field establishes the <a href="/en/earned-value/definitions/budget-at-completion">BAC</a>. The deliverables field defines what "complete" means for each milestone or unit.</p><p>Under <a href="/en/earned-value/definitions/eia-748-standard">EIA-748</a>, criteria 6-9 require that authorised work is scheduled, broken into work packages, and budgeted at the appropriate level. The WBS Dictionary is the document that demonstrates compliance with all four criteria.</p><h2 id="common-mistakes">Common Mistakes</h2><ol><li><strong>Writing scope descriptions that are too vague.</strong> "Structural works" isn't a scope description. "Supply, delivery, and erection of structural steelwork to floors 1-6 including primary beams, secondary beams, columns, bracing, holding-down bolts, base plates, shear studs, and all site connections" is. If a QS can't price it from the description, it's not detailed enough.</li><li><strong>Skipping the exclusions field.</strong> This is the field that pays for itself ten times over. Every scope gap dispute I've arbitrated could have been avoided if someone had written down what wasn't included. Write the exclusions. Cross-reference the WBS elements that pick up the excluded work. Do it properly.</li><li><strong>Not updating the dictionary after scope changes.</strong> When a <a href="/en/earned-value/definitions/variation-order">variation order</a> or compensation event adds scope, the WBS Dictionary must be updated. New work packages need entries. Existing entries may need revised budgets, durations, or milestones. A WBS Dictionary that reflects the original scope but not the current scope is worse than useless. It's misleading.</li><li><strong>Treating it as a one-time exercise.</strong> The WBS Dictionary is a living document. Update it at every baseline review, after every major scope change, and whenever control accounts are restructured. Some teams review it quarterly. I'd recommend monthly on projects with active change management.</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>Who is responsible for maintaining the WBS Dictionary?</h3><p>The project controls team typically owns the document, but each <a href="/en/earned-value/definitions/control-account-manager">CAM</a> is responsible for the accuracy of entries within their control account. The commercial manager should review the dictionary whenever scope changes are processed. On smaller projects without a dedicated controls team, the QS usually takes ownership.</p><h3>Is the WBS Dictionary the same as the Bill of Quantities?</h3><p>No. A Bill of Quantities (BoQ) is a pricing document that itemises work for tendering and valuation. A WBS Dictionary is a scope management document that describes what each WBS element covers, who manages it, and how progress is measured. There's overlap, both describe scope, but the WBS Dictionary serves EVM while the BoQ serves contract payment. On NEC4 Option B (bill of quantities), the two documents should be cross-referenced.</p><h3>How detailed should WBS Dictionary entries be?</h3><p>Detailed enough that a competent QS who's never visited the site could understand what's included and what's excluded. That's the test. If they'd need to make assumptions or ask questions, the entry isn't detailed enough. One to two paragraphs of scope description, a clear exclusions list, and the EVT with milestones or units. That's typically sufficient.</p></article></div>