Work Breakdown Structure (WBS) Guide
How to Build One, Step by Step
Before you can schedule, budget or assign work, you need to know exactly what the work is. A Work Breakdown Structure (WBS) breaks the whole project into smaller pieces of work. It is laid out as a hierarchy, numbered with WBS codes, and broken down until each piece (a work package) can be given to one owner, estimated and tracked. This guide shows you what a WBS is, the rules for a good one and how to build one, with a worked construction example.
Just want the file? Download the ready-made Word version from my free WBS template page. This page is the guide: it explains how to think through a WBS and build your own, so the template actually fits your project.
No email required. Instant Word download.
What's in the Template: The Four-Level Hierarchy
A WBS usually has four levels, each with its own WBS code. Level 1 is the project itself. Levels 2 to 4 break the scope down step by step until each element is a work package: something you can assign, estimate and track.
| Level | Name | Content | Example |
|---|---|---|---|
| 1 | Project | The entire project: all scope in one node. WBS code: 0 | "CRM Implementation Project" |
| 2 | Phase / Major Deliverable | Major phases or deliverable groups. WBS codes: 1.0, 2.0, 3.0… | "1.0 Initiation", "2.0 Planning", "3.0 Development" |
| 3 | Deliverable | Specific deliverables within each phase. WBS codes: 1.1, 1.2, 2.1… | "2.1 Project Charter", "3.1 Database Design" |
| 4 | Work Package | The lowest level: assignable, estimable, trackable. WBS codes: 1.1.1, 1.1.2… | "1.1.1 Draft charter", "1.1.2 Stakeholder review" |
How to Build a WBS: A Worked Construction Example
Build a WBS in four steps. First, write the final deliverable at the top. Second, split it into the major parts (Level 2). Third, split each part into deliverables you could hand over or inspect (Level 3). Fourth, stop when each piece can go to one owner and be estimated with confidence. Here is a simple example for a two-storey villa:
- 1.0 Villa (Level 1: the whole project)
- 1.1 Substructure: 1.1.1 Excavation, 1.1.2 Foundations, 1.1.3 Waterproofing, 1.1.4 Backfill
- 1.2 Superstructure: 1.2.1 Ground floor columns and slab, 1.2.2 First floor columns and slab, 1.2.3 Roof slab, 1.2.4 Blockwork
- 1.3 MEP: 1.3.1 Electrical, 1.3.2 Plumbing and drainage, 1.3.3 HVAC, 1.3.4 Fire safety
- 1.4 Finishes: 1.4.1 Plaster and paint, 1.4.2 Flooring and tiling, 1.4.3 Doors and joinery, 1.4.4 Sanitary fittings
- 1.5 Project management and approvals: 1.5.1 Permits, 1.5.2 Consultant submittals, 1.5.3 Authority inspections, 1.5.4 Handover and snag list
Notice that 1.5 is in the WBS too. Approvals, inspections and handover are real work with real effort. If they are not in the WBS, they will not be in the schedule or the budget.
From my experience: On my projects in the UAE, the items most often missing from a first WBS were not the concrete or the steel. They were the approvals, authority inspections, testing and commissioning, and the handover paperwork. When I teach this to my PMP students, the mistake I see most is a WBS full of construction trades and no project management branch. Add it from day one.
Five Rules for a Good WBS
A WBS that breaks these rules causes problems later in scheduling, estimating and scope control. Use these five rules as a quality check before you baseline your WBS.
The WBS Dictionary: Turning Codes Into Scope Definitions
The WBS shows what the work packages are. The WBS dictionary explains what each one means, clearly enough that two people reading it would do the same work. Here is a sample for the first three work packages.
| WBS Code | Work Package Name | Includes | Excludes | Acceptance Criteria | Owner |
|---|---|---|---|---|---|
| 1.1.1 | Draft Charter | First draft of project charter incorporating scope, objectives, PM authority and initial stakeholder list | Stakeholder sign-off (1.1.3), budget approval | Draft reviewed by sponsor and two business owners before advancing | PM |
| 1.1.2 | Stakeholder Review | Circulation of draft charter to all Level 2 stakeholders, collation of feedback, incorporation of changes | Final sign-off: that is 1.1.3 | Feedback received from all named reviewers; all material comments resolved or deferred with documented rationale | PM |
| 1.1.3 | Sponsor Sign-Off | Formal signature of final project charter by project sponsor | Distribution to full stakeholder list (separate comms activity) | Signed charter on file; version 1.0 baselined in document management system | Sponsor |
The Includes and Excludes columns are the most useful. They stop the most common WBS argument: "I thought that was part of work package X." Writing down what is excluded matters as much as what is included, because exclusions make the scope boundary clear.