Free Template · Word · Updated March 2026
Free WBS Template: Work Breakdown Structure Word Download
You cannot schedule, budget or assign work until you know what the work is. A WBS breaks the project into every piece of work, in levels, with a WBS code for each item. Go down until each work package can be given to one owner, estimated and tracked. This Word template gives you the structure. Your scope fills it in.
4-level hierarchical outline
Project → Phases → Deliverables → Work Packages. Each with a pre-formatted WBS code (1.0, 1.1, 1.1.1) and description field.
WBS dictionary table
A companion table defining each work package. What's included, what's excluded, acceptance criteria and responsible party.
5 sample phases pre-populated
Initiation, Planning, Execution, Monitoring and Closure: replace the sample content with your project's actual deliverables.
WBS Template
Free Word template: instant download
Format
Word (.docx)
Levels
4-level hierarchy
WBS codes
Pre-formatted numbering
Dictionary
Work package table included
Compatible
Word, Google Docs, LibreOffice
Price
Free: no signup needed
No email required. Instant Word download.
Quick answer
A work breakdown structure (WBS) is a hierarchical breakdown of all the work needed to deliver a project, with each item given a WBS code. This free Word template uses a four-level hierarchy and includes a WBS dictionary, aligned with PMBOK.
If you want to learn how to build a WBS from scratch, with the theory and PMP exam angle, read my work breakdown structure guide. This page is for doing it: download the template, see a filled-in example and avoid the mistakes I see most.
01 · WBS Structure
What's in the WBS template?
The template is a four-level outline with WBS codes already formatted. Level 1 is the whole project. Levels 2 to 4 break the scope down step by step until each item is a work package: something you can assign, estimate and track.
✦
From my experience: On my UAE construction projects, the WBS was the backbone. The schedule, the cost plan and the subcontract packages all hung from the same codes. When a subcontractor claimed extra work, the first thing we checked was which work package it sat in. When I teach this to my PMP students, the mistake I see most is a WBS full of activities like "install" and "review" instead of deliverables. Break the work down until each package has one owner and you can estimate it with confidence.
0 [Project Name] Level 1: The Project
1.0 Initiation Level 2: Phase
1.1 Project Charter Level 3: Deliverable
1.1.1 Draft charter Level 4: Work Package
1.1.2 Stakeholder review Level 4: Work Package
1.1.3 Sponsor sign-off Level 4: Work Package
1.2 Stakeholder Register Level 3: Deliverable
1.2.1 Identify stakeholders Level 4: Work Package
1.2.2 Power/interest analysis Level 4: Work Package
2.0 Planning Level 2: Phase
2.1 Project Management Plan Level 3: Deliverable
2.1.1 Scope management plan Level 4: Work Package
2.1.2 Schedule development Level 4: Work Package
2.1.3 Risk register Level 4: Work Package
3.0 Execution ··· 4.0 Monitoring ··· 5.0 Closure
| 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" |
WBS codes are permanent. Once a code is given, it stays with that item for the whole project. If a work package is removed, retire its code. Never reuse it for something else. Your schedule, budget, risk register, resource plan and RACI matrix all point to these codes, so changing them causes confusion everywhere.
02 · WBS Rules
What makes a good WBS?
A WBS that breaks these rules causes problems later in the schedule, the estimates and scope control. Use these five rules as a check before you baseline it.
1
The 100% Rule
The WBS must include 100% of the work: no more, no less. Every deliverable must appear somewhere. Work not in the WBS is not in the project. The sum of all child elements equals 100% of their parent at every level.
2
Deliverables, Not Activities
WBS elements are deliverables or outputs: nouns, not verbs. "Project Charter" not "Draft the project charter". "Test Report" not "Conduct testing". Activities belong in the schedule, not the WBS.
3
Mutually Exclusive Elements
No work should appear in more than one WBS element. Overlapping scope leads to double-counting in budgets and schedule confusion. Each piece of work belongs to exactly one work package.
4
Work Package Test
Each work package at the lowest level should be: assignable to one owner, estimable with reasonable confidence, completable within one reporting period (8/80 rule: 8 hours to 80 hours of effort), and verifiable when complete.
5
Consistent Decomposition
All elements at the same level should be decomposed to a similar level of detail. Having some work packages at 8 hours and others at 200 hours at the same WBS level creates unbalanced planning. If one element at Level 3 needs breaking down further, all should be evaluated at the same decomposition standard.
The 8/80 rule for work packages: A work package should be no smaller than 8 hours of effort and no bigger than 80 hours. Smaller than 8 and you are managing tasks, not work packages. Bigger than 80 and it is hard to estimate or track in one reporting period. It is a guide, not a law. On construction jobs, some packages are much bigger, and that is fine as long as you can still measure progress on them.
Worked example
Example: filling in the WBS for an office fit-out
The sample in the template uses generic project phases. Here is how one branch looks on a real kind of job, an office fit-out in the UAE. This is an example only. Notice that every line is a deliverable (a noun), and the work packages have one owner each.
| WBS code | Element | Level | Owner and notes |
|---|---|---|---|
| 3.0 | MEP Works | 2: Phase / group | MEP manager |
| 3.2 | Fire Alarm System | 3: Deliverable | MEP coordinator |
| 3.2.1 | Fire alarm devices and cabling, Level 3 | 4: Work package | Fire alarm subcontractor. Includes supply, install and testing. Excludes ceiling access panels (sits in 4.1). |
| 3.2.2 | Civil Defence approval certificate | 4: Work package | MEP coordinator. Done when the approval is received, not when the inspection is booked. |
Mistakes I see when people fill this in
- Verbs instead of deliverables. "Install fire alarm" is an activity for the schedule. "Fire alarm system" belongs in the WBS.
- Authority approvals left out. Permits and inspections take real time and effort. If they are not in the WBS, they will not be in the schedule either.
- Work in two places. Ceiling access panels in both the MEP and the ceiling packages means you pay or plan for them twice.
- Codes changed halfway. Renumbering after the baseline breaks the link to your schedule and cost reports.
03 · WBS Dictionary
What is a WBS dictionary?
The WBS outline tells you what the work packages are. The WBS dictionary tells you what each one means, clearly enough that two people reading it would do the same work. The template has a dictionary table for the first 10 work packages. Add rows as you need them.
| 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 matter most. They stop the classic argument: "I thought that was part of package X." Writing what is excluded is as important as writing what is included. Exclusions are what make your scope boundary hold up when someone pushes.
04 · FAQ
WBS: 4 Common Questions
A Work Breakdown Structure breaks the total scope of a project into smaller parts. It goes from the whole project at the top, through phases and main deliverables, down to work packages that can be assigned, estimated and tracked. Your schedule, cost, resource and risk planning all build on it. In PMBOK 6, the WBS is created in the Create WBS process in the Scope Management knowledge area. That older structure is still useful for learning.
The 100% rule says the WBS must contain all the work in the project scope: no more and no less. Work not in the WBS is not in the project. Work in the WBS that is not in the scope statement is unapproved scope. It applies at every level: the children of an item must add up to 100% of their parent. It is the most important check on any WBS and the one I see broken most often.
A WBS dictionary is a table that describes each work package in detail: its code, what it includes and excludes, acceptance criteria, who is responsible and any dependencies. It turns a list of codes and labels into a proper scope reference, and it is your best tool against "that's not what I meant". This template includes a dictionary table next to the outline.
Usually 3 to 5 levels, depending on how complex the project is. Level 1 is the project, Level 2 the main phases or deliverable groups, Level 3 the deliverables and Level 4 the work packages. Very complex projects may need a fifth level. The test is simple: can you give the package to one owner, estimate it with reasonable confidence and track it to the end within a reporting period? If yes, you have gone deep enough. The 8/80 rule is a handy size check.
Explore More Free PM Resources
Keep learning
- Free Gantt Chart Template: Excel Download
- Free Project Budget Template: Excel Download
- Free Communication Plan Template: Excel Download
- Free Change Management Plan Template: Word Download
- Free Procurement Plan Template: Word Download
- Free Quality Management Plan Template: Word Download