Work breakdown structures and the integrated baseline

0:00 The backbone of every report

Imagine building a house where the architect, the quantity surveyor and the site manager each used a different list of rooms. The architect has a utility room. The surveyor forgot it. The site manager calls it the laundry. Every conversation would be an argument about what you're even talking about. That's what happens on projects without a proper work breakdown structure. In this lecture you'll learn how to build a WBS that everything else can hang from, how to apply the one hundred per cent rule, where control accounts sit, and how the scope, schedule and cost baselines come together into the performance measurement baseline. By the end you'll be able to draft a three-level WBS for any project and check it before anyone approves a budget.

0:55 Why it matters

Why does this matter so much? Because the WBS is the backbone of controls. Schedule activities, budgets, risks, progress measurement and actual costs all attach to it. If the WBS is wrong, every report built on it is wrong, however polished the charts. And there's a second reason that matters more every year. A single, consistent code structure is what lets you join your schedule, your cost system and your risk register. That's integration. It's also exactly what any AI or analytics tool needs to find patterns across your data. No common codes, no meaningful analysis. So time spent on the WBS early is some of the highest-return time in the whole project.

1:44 The concept: deliverables, not departments

Here's the key idea. A WBS is a deliverable-oriented decomposition of the total scope. Deliverables, not departments. Think of it like a recipe card, not an organisation chart. Level one is the project. Level two is usually the major deliverables or phases: site works, structure, building services, commissioning and project management. Then you keep decomposing until you reach a work package, a piece of work that one owner can plan, estimate, schedule and measure. And you apply the one hundred per cent rule. The WBS must include all of the work in scope, and the children of any element must add up to exactly one hundred per cent of the parent. Nothing missing. Nothing counted twice. Above the work packages you define control accounts: management points where scope, schedule and budget are integrated and owned by a control account manager.

2:45 The integrated baseline

Once the WBS exists, you build three baselines and tie them together. The scope baseline is the approved scope statement, the WBS and the WBS dictionary. The schedule baseline is the approved schedule, with every activity mapped to a work package. And the cost baseline is the time-phased budget, created by loading work-package budgets onto the schedule. Together, these form the performance measurement baseline. Plot the cost baseline cumulatively and you get the familiar S-curve, which becomes your planned value line in earned value. Now, two amounts need care. Contingency reserve is for identified risks, the known unknowns. Management reserve is for the unknown unknowns and usually sits outside the PMB, controlled by the sponsor. Terminology varies, so check your own policy. The principle doesn't vary: reserves must be visible and released by a documented decision.

3:44 Worked example one: a website launch

Let's start small. A marketing agency is launching a website for a client, with an illustrative budget of forty thousand pounds. The first draft WBS lists Discovery, Design, Build, Launch and Project management. The budgets add up to thirty-four thousand. Where's the other six? Nobody's quite sure. When we walk through the one hundred per cent rule, asking 'what else must be true for this to be done?', someone says: well, the client's old content has to be rewritten and migrated. That's two hundred pages. It had no owner, no budget and no activities. So we add a Content migration work package, give it an owner and six thousand pounds, and suddenly the WBS reconciles to the budget. That gap would otherwise have surfaced in week ten as a crisis.

4:41 Worked example two: Northbridge Health clinic

Now a more realistic case. Northbridge Health is a fictional UK developer building a regional clinic with a budget of four million pounds. The project manager's first WBS listed departments: civils team, electrical team, procurement. The controls lead restructured it around deliverables. One point one, project management, three hundred and twenty thousand. One point two, site preparation. One point three, structure, one point four million. One point four, building services, one point two million. One point five, fit-out and equipment. And then the question: who owns testing and handover? Silence. It had no budget, no activities and no owner, yet it would take around six weeks. Adding it as one point six, with two hundred thousand, moved the realistic completion date. Uncomfortable at planning. Far more uncomfortable at the end, in front of the client.

5:40 Watch me do it: checking the 100% rule

Let me show you how I check this in a spreadsheet. I keep four columns: code, parent code, element name and budget. So work package one point two point one has parent one point two. In a check column I use SUMIF: sum the budgets of every row whose parent is this row's code. Then a second column subtracts the parent's own budget. If the WBS obeys the one hundred per cent rule, every parent row shows zero. Right now, one point two shows minus forty thousand. The children don't add up. When I look, the survey and setting-out package is missing. I add it, the check turns green, and I've caught the error in two minutes rather than at the first cost report. The formulas are in the lesson text so you can copy them.

6:39 Common mistakes

Let's go through the common mistakes. First, organising the WBS by department or by contract instead of by deliverable. Second, work packages so large that progress can only be guessed. If it runs for months, break it down. Third, using different codes in the schedule, the cost system and the risk register, which makes integration impossible. Fourth, hiding contingency inside activity budgets, so nobody knows how much buffer really exists, and every estimate quietly grows. And fifth, forgetting the scope that isn't physical work: design, permits, training, documentation and, very often, project management itself. Project management is real work with a real cost. Leave it out, and you've built an overrun into the baseline on day one.

7:30 Recap and try this now

Let's recap. The WBS is the backbone of controls, built around deliverables, not departments, and it must pass the one hundred per cent rule. Control accounts sit above work packages and integrate scope, schedule and budget under a named manager. The scope, schedule and cost baselines together form the performance measurement baseline, and reserves sit visibly beside it, never hidden. Here's your try-this-now. Pick a small project, a shop refit, a product launch or a website, and draft a three-level WBS. Mark the control accounts, give each work package an owner and a budget, and run the SUMIF check from the lesson. If every parent shows zero, you're ready to build a schedule on it.