Free Template · Word · Updated March 2026
Free WBS Template
Work Breakdown Structure Word Download
Before you can schedule, budget or assign work, you need to know exactly what the work is. A WBS decomposes the project into every piece of work required — structured hierarchically, numbered with WBS codes, and detailed enough that each work package can be assigned, estimated and tracked. This Word template gives you the structure; your scope fills in the content.
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.
01 — WBS Structure
What's in the Template — The Four-Level Hierarchy
The template uses a four-level hierarchical outline structure with pre-formatted WBS codes. Level 1 is the project itself. Levels 2–4 decompose the scope progressively until each element is a work package — something assignable, estimable and trackable.
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 identifiers. Once assigned, a WBS code stays with that element for the life of the project. If a work package is removed from scope, its code is retired — never re-used for a different element. This prevents confusion in the schedule, budget and risk register, all of which reference WBS codes. The resource plan, risk register and RACI matrix should all use the same WBS codes as the primary reference for scope elements.
02 — WBS Rules
Five Rules for a Good WBS
A WBS that violates these rules creates downstream problems in scheduling, estimating and scope control. These five rules are the quality test for any WBS before it is baselined.
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 (one person-day) and no larger than 80 hours (two person-weeks) of effort. Smaller than 8 hours and you are managing at activity level, not work package level. Larger than 80 hours and the package is too big to estimate reliably or track meaningfully within a reporting period. This rule is a guideline — some work packages in complex technical projects may legitimately exceed 80 hours — but it is a useful check when first decomposing scope.
03 — WBS Dictionary
The WBS Dictionary — Turning Codes Into Scope Definitions
The WBS outline tells you what the work packages are. The WBS dictionary tells you what each one means — precisely enough that two different team members reading it would do the same work. The template includes a companion dictionary table for the first 10 work packages, which you can extend as needed.
| 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 valuable. They prevent the most common WBS dispute: "I thought that was part of work package X" from someone who interpreted the label differently. Being explicit about what is excluded is as important as defining what is included — exclusions are what make scope boundaries defensible.
04 — FAQ
WBS — 4 Common Questions
A Work Breakdown Structure is a hierarchical decomposition of the total scope of work required to complete a project. It breaks the project down from the overall deliverable at the top, through phases and major deliverables, down to work packages — specific pieces of work that can be assigned, estimated and tracked. The WBS is the foundation of project planning: schedule, cost, resource and risk planning all build from it. In PMBOK, creating the WBS is an output of the Create WBS process within the Scope Management knowledge area.
The 100% rule states that a WBS must include 100% of the work defined in project scope — no more and no less. Every deliverable must appear somewhere in the WBS. Work not in the WBS is not in the project. Conversely, work in the WBS that is not in the scope statement represents unauthorised scope. The rule applies at every level: the sum of all child elements must equal 100% of their parent. This rule is the most important quality check for any WBS — and the most commonly violated in practice.
A WBS dictionary is a companion document that provides a detailed description of each work package. For each work package it records: the WBS code, what the work package includes and excludes, acceptance criteria, the responsible party and any dependencies or constraints. The dictionary turns a list of codes and labels into a complete scope reference document — the primary tool for preventing "that's not what I meant" disputes when team members interpret work packages differently. The template includes a WBS dictionary table alongside the hierarchical outline.
Typically 3–5 levels depending on project complexity. Level 1 is the project. Level 2 is major phases or deliverable groups. Level 3 is specific deliverables. Level 4 is work packages — the lowest level at which work is assigned, estimated and tracked. A fifth level may be needed for very complex projects. The practical test: can the work package be assigned to one owner, estimated with reasonable confidence and tracked to completion within one reporting period? If yes, it is at the right level. The 8/80 rule provides a useful size check: work packages should be 8–80 hours of effort.
Explore More Free PM Resources