---
title: "Work breakdown structures and the integrated baseline"
description: "Why the WBS comes first The work breakdown structure (WBS) is a deliverable-oriented, hierarchical decomposition of the total scope. It is the backbone…"
url: https://optimizeall.com/learn/project-controls-with-ai/wbs-and-baselines
updated: 2026-10-05
---

Project Controls in the AI Era · Foundations of project controls · lesson 2 of 22 · 14 min

# Work breakdown structures and the integrated baseline

## Why the WBS comes first

The **work breakdown structure (WBS)** is a deliverable-oriented, hierarchical decomposition of the total scope. It is the backbone of controls because schedule activities, budgets, risks, progress and actual costs all hang off it. If the WBS is wrong, every report built on it is wrong.

The key rule is the **100% rule**: the WBS must include 100% of the work defined by the scope, and the children of any element must add up to exactly 100% of the parent. Nothing is missing, nothing is counted twice.

## Building a good WBS: step by step

1. **Start with deliverables, not departments.** Level 1 is the project. Level 2 is usually major deliverables or phases (for example, "Site works", "Building structure", "MEP systems", "Commissioning", "Project management").
2. **Decompose until work is manageable.** Stop at a **work package**: a piece of work that one owner can plan, estimate, schedule and measure. A common heuristic is that a work package should be short enough to measure meaningfully within a few reporting periods.
3. **Write a WBS dictionary.** For each work package, record scope description, owner, deliverables, acceptance criteria, assumptions and exclusions.
4. **Create control accounts.** A **control account** is a management control point where scope, schedule and budget are integrated and assigned to a responsible manager (the control account manager, CAM). Control accounts usually sit one level above work packages.
5. **Code everything.** Give each element a unique code (1.2.3) used consistently in the schedule, cost system and risk register. This single code structure is what allows integration and, later, AI analysis across data sets.

## WBS template

```
Code   | Element                      | Type             | Owner        | Budget (illustrative)
1      | Regional Clinic Project      | Project          | PM           | 4,000,000
1.1    | Project management           | Control account  | PM           | 320,000
1.2    | Site preparation             | Control account  | Civil lead   | 380,000
1.2.1  |   Survey and setting out     | Work package     | Surveyor     | 40,000
1.2.2  |   Excavation and grading     | Work package     | Civil lead   | 340,000
1.3    | Structure                    | Control account  | Struct lead  | 1,400,000
1.4    | MEP systems                  | Control account  | MEP lead     | 1,200,000
1.5    | Fit-out and equipment        | Control account  | Fit-out lead | 500,000
1.6    | Testing and handover         | Control account  | PM           | 200,000
```

Notice that project management itself is a WBS element. Omitting it is a classic cause of overruns because its cost is real.

## The integrated baseline

Once the WBS exists, controls builds three baselines and ties them together:

- **Scope baseline:** approved scope statement + WBS + WBS dictionary.
- **Schedule baseline:** the approved schedule with activities mapped to work packages.
- **Cost baseline:** the time-phased budget, built by loading work-package budgets onto the schedule.

Together these form the **performance measurement baseline (PMB)**. The time-phased cost baseline, plotted cumulatively, produces the familiar **S-curve**, which is the planned value line used in earned value management.

Two amounts sit *outside* the PMB and must be understood clearly:

| Reserve | Purpose | Who controls it | In the PMB? |
|---|---|---|---|
| Contingency reserve | Identified risks ("known unknowns") | Usually project manager, per policy | Often included in cost baseline, but held separately from work-package budgets |
| Management reserve | Unidentified risks ("unknown unknowns") | Sponsor or senior management | No |

Terminology differs slightly between organisations and standards, so always check your own policy. The principle is universal: reserves are visible, separately tracked and released through a documented decision.

## Worked example

*Illustrative.* Northbridge Health, a fictional UK developer, is building a regional clinic. The project manager's first WBS listed departments: "Civils team", "Electrical team", "Procurement". The controls lead restructured it around deliverables, as in the template above, and found that nobody owned "Testing and handover". It had no budget, no activities and no owner, yet it would take roughly six weeks. Adding it early moved the realistic completion date and avoided an argument with the client at the end.

## Common mistakes

- Organising the WBS by department or by contract rather than by deliverable.
- Work packages so large that progress can only be guessed.
- Different coding in the schedule, cost system and risk register, making integration impossible.
- Hiding contingency inside activity budgets, so no one knows how much buffer really exists.
- Forgetting non-construction scope such as design, permits, training, documentation and project management.

## Checklist before baselining

- Does the WBS pass the 100% rule?
- Does every work package have an owner, a budget, and schedule activities?
- Are control accounts defined with named managers?
- Are contingency and management reserve explicitly separated?
- Has the baseline been formally approved and version-stamped?

## Hands-on: a 100% rule checker in Excel

Lay the WBS out flat, one row per element, with its parent code:

| A Code | B Parent | C Element | D Budget | E Level | F Sum of children | G Check |
|---|---|---|---|---|---|---|
| 1 | | Regional Clinic Project | 4,000,000 | 1 | | |
| 1.1 | 1 | Project management | 320,000 | 2 | | |
| 1.2 | 1 | Site preparation | 380,000 | 2 | | |
| 1.2.1 | 1.2 | Survey and setting out | 40,000 | 3 | | |

```text
E2   =LEN(A2)-LEN(SUBSTITUTE(A2,".",""))+1          WBS level from the code
F2   =IF(COUNTIF(B:B,A2)=0,"",SUMIF(B:B,A2,D:D))     sum of this element's children
G2   =IF(F2="","leaf",IF(ROUND(F2-D2,0)=0,"OK","MISMATCH "&TEXT(F2-D2,"#,##0")))
```

Every parent must show `OK`. Store codes as text (format the column as Text before typing) so `1.10` is not converted to `1.1`.

The same check in Python, useful when the WBS comes from a P6 or Microsoft Project export:

```python
import pandas as pd

wbs = pd.read_csv("wbs.csv", dtype={"code": str, "parent": str})
children = wbs.groupby("parent")["budget"].sum()
parents = wbs.set_index("code")["budget"]
check = (children - parents.reindex(children.index)).round(0)
print(check[check != 0])   # any non-zero row breaks the 100% rule
```

## Second worked example: a software product

*Illustrative.* A Riyadh fintech builds a merchant app. The WBS by deliverable: 1.1 Product management, 1.2 Onboarding capability, 1.3 Payments capability, 1.4 Reporting capability, 1.5 Security and compliance (penetration test, regulatory submission), 1.6 Release and hypercare. The 100% check reveals that "regulatory submission" existed in nobody's backlog; adding it as a work package with an owner prevented a launch-week surprise.

## How to measure success

- Zero `MISMATCH` rows at baseline approval.
- Every work package has an owner, a budget, schedule activities and a WBS dictionary entry.
- The same codes appear in schedule, cost and risk exports (test with a simple join; unmatched codes should be zero).

## Video lecture: Work breakdown structures and the integrated baseline

Lecture coming soon · 9 chapters · about 8 minutes. Read the full transcript below.

1. The backbone of every report
2. Why it matters
3. The concept: deliverables, not departments
4. The integrated baseline
5. Worked example one: a website launch
6. Worked example two: Northbridge Health clinic
7. Watch me do it: checking the 100% rule
8. Common mistakes
9. Recap and try this now

## Lecture transcript

### 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.

### 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.

### 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.

### 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.

### 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.

### 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.

### 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.

### 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.

### 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.

## Key takeaways

- The WBS is deliverable-oriented and follows the 100% rule.
- Control accounts integrate scope, schedule and budget under one accountable manager.
- The performance measurement baseline links the scope, schedule and cost baselines; its cumulative curve is the S-curve.
- Keep contingency and management reserve visible and separate from work-package budgets.

## Try it

Draft a three-level WBS for a small project (e.g., a shop refit or a website launch) using the template. Mark control accounts, give each work package an owner and check it against the 100% rule.

- [Previous: What project controls really is](https://optimizeall.com/learn/project-controls-with-ai/the-control-cycle)
- [Next: Scheduling and the critical path](https://optimizeall.com/learn/project-controls-with-ai/scheduling-and-critical-path)
- [All lessons of Project Controls in the AI Era](https://optimizeall.com/learn/project-controls-with-ai)