A work breakdown structure (WBS) is a hierarchical breakdown of the total scope of a project into smaller, manageable deliverables, with the work packages at the bottom. In Primavera P6 it is the tree that every activity belongs to, and P6 uses it to roll up dates, budgets, actuals and earned value.
A good WBS follows the 100% rule, is built around deliverables, stays three to five levels deep and has activities only at its lowest levels. This guide covers how to build one in P6, how it differs from activity codes, how to draft it in Excel, and the mistakes a schedule review usually finds.
What is a work breakdown structure?
The WBS decomposes the scope of the project, level by level, until each lowest element (a work package) is small enough to plan, estimate, assign and measure. It describes what will be delivered, not who delivers it or in what order. Sequence comes from the logic in the schedule, and responsibility comes from the organisation breakdown, resources or activity codes.
A well-structured WBS is the backbone of:
- Scope definition: every activity belongs to a WBS element that represents a deliverable or outcome, so nothing in scope is missed and nothing out of scope creeps in.
- Roll-up of cost and progress: P6 summarises budgets, actuals and earned value up the WBS hierarchy.
- Reporting: S-curves, earned value metrics and variance reports are usually produced by WBS element.
- Ownership: each WBS element can be given a responsible manager.
Without a sound WBS, the schedule becomes a flat list of activities that is hard to navigate, hard to summarise and prone to errors in cost and progress reporting.
What is the 100% rule in a WBS?
The 100% rule says the WBS must include all of the work defined by the project scope, including project management, and nothing outside it. It applies at every level: the child elements of any WBS element must add up to exactly 100% of the work in that parent, with no gaps and no overlaps.
In practice this means three checks:
- Nothing missing: every scope item in the contract, specification or scope of works maps to a WBS element.
- Nothing extra: no element covers work that is not in scope, such as unapproved variations.
- No double counting: each piece of work sits in one element only, so its cost and progress are counted once.
The rule also applies to cost. If a WBS element has a budget, its children's budgets should sum to it, which is what makes the roll-up in P6 trustworthy.
WBS vs activity codes in Primavera P6
A common confusion is between the WBS hierarchy and activity codes. Both can group activities, but they serve different purposes:
| Feature | WBS | Activity codes |
|---|---|---|
| Purpose | Decompose scope and define the reporting structure | Filter, sort and group activities flexibly |
| Structure | A single fixed tree (parent and child) | Flat or hierarchical, and not tied to scope |
| Used for | Cost roll-up, earned value, progress | Custom layouts, reports and filters |
| Assignment | Mandatory: every activity belongs to exactly one WBS element | Optional: an activity can carry many codes, or none |
Treat the WBS as the official structure for scope and performance measurement. Activity codes are additional tags that let you slice the schedule other ways, for example by area, discipline, phase or contractor. A robust schedule uses both: a solid WBS for integrity, and activity codes for flexibility.
How do you build a WBS in Primavera P6?
1. Start with the project scope
Define the major deliverables before you open P6. A deliverable-oriented WBS (for example Foundation, Superstructure, Finishes) is preferred over a purely phase-oriented one (Design, Procurement, Construction) because it follows what is actually produced. On construction programmes a hybrid often works best: phases at the top level, deliverables below.
2. Limit depth to three to five levels
P6 lets the WBS tree go very deep, but practical schedules rarely need more than five levels. In P6 the project itself is the top node of the WBS. An example for a building project:
- Level 1: Project
- Level 2: Design, Procurement, Construction, Commissioning
- Level 3 (under Construction): Substructure, Superstructure, Finishes
- Level 4 (under Substructure): Excavation, Foundations, Waterproofing
3. Use a consistent coding and naming convention
Keep codes in the WBS code field and descriptions in the name field. Do not put codes such as "WBS.01.02.03" in the name. In P6 you enter each element's own code segment, and P6 builds the full WBS code by joining it to its parents' codes with the code separator set in the admin preferences. For example:
- WBS code C.01.01, name "Excavation"
- WBS code C.01.02, name "Foundations"
Names should be short, unique and descriptive, and codes should follow a logical pattern (1.1, 1.1.1) without skipped numbers or mixed separators.
4. Assign activities to the lowest level
Activities should sit at the leaf nodes (work packages) of the WBS. P6 will still roll up an activity placed on a parent element, but that parent's totals then mix its own work with its children's, which confuses progress, cost and earned value reporting at that level. If you need a summary bar, use a WBS summary activity: its dates span the activities in its own WBS element and the elements below it.
5. Use a WBS category for reporting
P6 lets you define a WBS category (renamed in the admin categories to something like "Phase", "Discipline" or "Area") and give each WBS element a value. This lets you group and report WBS elements consistently across projects, for example every element tagged Design, Build or Test.
How do you create a WBS in Excel?
A spreadsheet is a practical place to draft and agree the WBS before it goes into P6, because the people who own the scope (project managers, engineers, cost controllers) can review it without a P6 licence. A simple WBS template in Excel needs these columns:
| Column | What it holds |
|---|---|
| WBS code | The full code, for example C.01.02 |
| Level | 1 for the project, 2 for the next level, and so on |
| Parent code | The code of the element above, so the tree can be checked |
| WBS name | A short, unique description of the deliverable |
| Description / dictionary | What is in and out of the element, and its completion criteria |
| Responsible manager | Who owns the element |
| Cost account | The finance cost code it maps to |
The description column becomes the WBS dictionary, the document that defines each element so that people agree what belongs where. Check the draft against the 100% rule before building it in P6, and keep the codes identical in both places so reports and data exchanges line up. The agreed WBS and its coding rules belong in the schedule basis memo.
Common WBS mistakes and how to avoid them
Mixing scope and organisation
A WBS should reflect what will be done, not who will do it. Avoid elements such as "Subcontractor A works" or "Engineering team tasks". Group by deliverable (for example Electrical Works) and track responsibility with activity codes, an organisation breakdown structure or resources.
Too many levels
Deep trees are hard to navigate and make roll-up errors more likely. If you are going beyond five levels, ask whether the lower levels could be activity codes instead, or whether the scope is being over-decomposed.
Inconsistent WBS codes
Skipped numbers, non-standard separators and codes in the name field make reports hard to read and data harder to import and export. Fix the convention once and apply it throughout.
Not updating the WBS as scope changes
When scope changes, update the WBS through change control. A new deliverable gets a new element. Deleted scope is removed or closed out, with its history kept where the contract or the cost records need it. A current WBS keeps cost and progress tracking accurate and keeps the 100% rule true.
Ignoring the WBS in cost and resource planning
Because P6 rolls up budgets and costs by WBS, a poorly structured WBS gives misleading cost data. Check that the WBS maps cleanly to the cost account structure used by finance, so that earned value from the schedule can be reconciled with the cost report.
How do you check a WBS in an existing schedule?
The DCMA 14-point assessment does not test the WBS directly, so a schedule review checks it separately. The usual checks are:
- Activities assigned to parent elements rather than work packages.
- Empty WBS elements, or elements holding a single activity that could be merged.
- Elements named after organisations rather than deliverables.
- Scope in the contract that has no WBS element, or elements with no matching scope.
- Codes that do not follow the stated convention or do not map to the cost accounts.
- Milestones placed at the right WBS level, so key deliverables can be tracked.
Involve the team when the WBS is first built, and review it again after the first schedule update, when structural problems are still cheap to fix. Project Assure reviews WBS structure, coding and cost mapping as part of its project planning and schedule review work.
A well-built WBS is the foundation of a reliable programme. It makes scope clear, keeps cost and progress roll-ups honest, and gives every report a structure people recognise, from planning through to closeout.
