Structure that survives.

Most people rush it. They open a spreadsheet, list the trades — excavation, concrete, steel, MEP — and call it a WBS.

That's not a breakdown of the work. That's a list of who's on site.

Things, not doing

Here's the rule that fixes most bad WBSs: a WBS is made of nouns.

You break the project down by what you are delivering — the substructure, the deck, the approach roads — not by what people are doing. The doing comes later, in the schedule, as activities. Deliverables first, verbs second.

You keep breaking each piece down until you reach a work package: a chunk of deliverable small enough that one person can own it, you can price it, and you can tell when it's finished.

That's your stopping point. Not the activity — the package. Activities hang below it, and those belong to the schedule.

And one arithmetic rule holds the whole thing together: every level must add up to exactly 100% of the level above it. If the substructure, superstructure and approach roads don't fully account for the bridge, then whatever is missing isn't in the WBS — which means it isn't in the schedule, isn't in the budget, and isn't in anybody's job. It will still get built. It just won't get planned or paid for.

Work not in the WBS is work nobody owns.

The two jobs of scope

Once the structure exists, you have exactly two responsibilities. They pull in opposite directions.

Deliver everything inside it. Flawlessly.

Keep everything else out. Ruthlessly.

The second one is where projects die — and it rarely feels like a threat when it's happening.

It's the site engineer who upgrades a finish because "the client will love it." The extra socket. The better handrail. Nobody asked for any of it. It's called gold plating, and it's the most well-intentioned way to lose money on a project. You're paying for work you'll never be paid for — and quietly moving a date you'll be held to.

Quality isn't the same thing. Quality means the concrete meets its spec, the welds pass, the tolerances hold. That's baked into the scope. Gold plating is giving people something they never asked for, and it's neither generous nor professional. It's just unmanaged.

The ripple

Then there's the other kind of scope change — the one that arrives as a small favour.

"Can we just move the door two metres?"

It's five minutes on the drawing. It is not five minutes on the project. The blockwork sequence shifts. The MEP first-fix clashes. Someone re-orders the frame. The cost changes, so someone has to approve it. And half the team hasn't heard.

This is the ripple effect, and it's why the answer to a small change is never a quick yes. It's: let me price the ripple, not the change.

Say yes to twenty of those and nobody can point to the moment the project went wrong. That's scope creep. It doesn't arrive as a decision. It arrives as a series of favours.

The baseline has exactly one door

Which brings us to the thing all of this protects.

Back in Week 7 we froze the baseline — the approved snapshot every future measurement is judged against. Its whole value comes from one property: it does not move.

Except it does. Because scope changes, and sometimes legitimately. So the baseline needs a door — exactly one.

Every other route in is a leak. A verbal yes at the site gate. A drawing quietly revised. A favour for the client that never made it onto paper.

Each of those changes what gets built without changing what gets measured. And two years later, when the delay claim lands and someone asks why the project ran late, the baseline can't answer. It was moved by people who weren't keeping count.

A baseline that moves without a door isn't a baseline. It's a rumour with dates on it.

Scope is the same discipline. The job isn't to give the client everything you can think of. It's to deliver exactly what was agreed — completely, and with nothing extra smuggled in.

Practical insight

Pull up your project's WBS and check three things.

Is it made of deliverables, or is it a list of trades? Does each level actually add up to the whole of the level above — or is there work being built that lives nowhere in the structure? And can you point to the single approved route by which your baseline is allowed to change?

If a change can reach the site without passing through that door, you don't have a baseline. You have a first draft that people keep editing.

Key takeaways

✔ The WBS is the structure every schedule, budget and report inherits — get it right first.
✔ Break down by deliverables (nouns), not by trades or tasks (verbs).
✔ Stop at the work package: ownable, priceable, and clearly finishable.
✔ Every level adds up to 100% of its parent — work outside the WBS is work nobody owns.
✔ Deliver everything in scope flawlessly; keep everything else out ruthlessly.
✔ Gold plating isn't generosity — it's unpaid work that moves a date you'll be held to.
✔ Price the ripple, not the change — scope creep arrives as a series of favours.
✔ The baseline has exactly one door: change control. Every other route is a leak.

What's coming next

We now have the structure, and a baseline that's protected.

Next week we go back inside the model and connect it all up — activities, logic and sequencing. How work really links together on site, which relationship types earn their place, and why the wrong link can hand you a critical path that runs through the wrong part of the job entirely.

The structure is set. Now we wire it.