Work breakdown structure (WBS) template
A free work breakdown structure (WBS) template in Excel and CSV — WBS codes with automatic levels, work packages, WBS dictionary description, owner, acceptance criteria and estimates.
What's inside
| Column | What goes in it |
|---|---|
| WBS code | 1, 1.1, 1.1.1 … each level adds a number |
| Name | A noun: the deliverable, not the activity |
| Level | Worked out from the code · calculated |
| Work package? | Yes for the lowest level you estimate and assign · drop-down Yes, No |
| Description | What is included (WBS dictionary) |
| Owner | One person accountable |
| Acceptance criteria | How you will know it is done |
| Cost estimate | Work packages only; parents roll up |
| Effort (days) | Work packages only |
The Excel file has three sheets: the blank register, a filled example from the Coral Ridge Resort sample project, and how to use each column. The CSV is the blank header row only.
What a WBS is
A work breakdown structure breaks the project's total scope into smaller and smaller pieces, until each piece is small enough to estimate, assign and check. The lowest pieces are work packages. Together, the WBS and its dictionary (what each piece includes) are part of the scope baseline.
A WBS is about deliverables, not activities: "Raft foundation & basement", not "pour concrete". The activities come later, in the schedule.
When to use it
- After the scope statement, before estimating cost and time: estimates are made per work package.
- Whenever someone asks "is that in scope?" The WBS is where you check.
How to fill it in
- Code each row 1, 1.1, 1.1.1 … The Level column works itself out from the code.
- Name each row with a noun: the thing being delivered.
- Stop decomposing when a piece can be estimated with confidence and given to one owner. Mark it Work package: Yes.
- Write acceptance criteria for each work package: how you'll know it's done. "Flood test passed, no wet spots" is checkable; "basement finished" isn't.
- Estimate only the work packages; parents are the sum of their children (the 100% rule: the children of any item cover all of its work, and nothing more).
The Example sheet shows part of the Coral Ridge Resort WBS: the substructure branch down to its piling and basement work packages.
Common mistakes
- Activities instead of deliverables. Verbs belong in the schedule.
- Breaking down too far. Work packages of a few hours turn the WBS into a to-do list.
- Missing project-management work. Reporting, procurement and closing are work too; give them a branch.
- Gaps or overlaps. If two branches both include "site security", one will be paid twice; if neither does, nobody does it.
See it used on a real project: Pr2 · Develop and manage project scope