This guide covers everything you need to know about the WBS dictionary in PMBOK 8. The WBS dictionary is the detailed reference document that provides a description, definition, and acceptance criteria for each element of the Work Breakdown Structure — it transforms the WBS from a visual structure into a complete, unambiguous scope specification.
What Is the WBS Dictionary?
The WBS dictionary is a document that provides detailed information about each component in the Work Breakdown Structure. For every work package in the WBS, the dictionary describes what work is included, what the deliverable is, what the acceptance criteria are, who is responsible, what the estimated cost and duration are, and what quality requirements apply. It is the reference document that answers “what exactly does this WBS element include?”
The WBS alone is a visual hierarchy of boxes and labels — it shows the structure but not the detail. The WBS dictionary fills in the detail that makes the WBS truly useful for planning, execution, and control. Together, the WBS and its dictionary form the primary component of the scope baseline.
Without a WBS dictionary, work packages are subject to interpretation. Two team members looking at “1.3 Development” in the WBS may have completely different ideas about what it includes. The dictionary eliminates that ambiguity by providing an authoritative written definition that everyone can reference.
WBS Dictionary in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the WBS dictionary belongs to the Scope Performance Domain and is produced during the Develop Scope Structure process. Along with the project scope statement and the WBS, the WBS dictionary is one of the three components of the scope baseline.
The WBS dictionary feeds into cost estimation (providing the scope definition needed to estimate each work package accurately), resource planning (identifying what skills and resources each work package requires), and scope verification (providing the acceptance criteria for deliverable inspection).
Key Elements of the WBS Dictionary
A well-structured WBS dictionary entry typically includes:
- WBS Code — the unique identifier for the WBS element (e.g., 1.3.2)
- Work Package Name — the descriptive title matching the WBS label
- Scope Description — detailed description of what work is included and excluded
- Deliverable — the specific output produced by completing this work package
- Acceptance Criteria — measurable conditions the deliverable must satisfy
- Responsible Party — the team member or vendor accountable for this work package
- Schedule and Cost Summary — planned duration and estimated cost for planning reference
WBS Dictionary Example — Project Phoenix
The Project Phoenix WBS dictionary contained entries for all 23 work packages. Work Package 1.3.1 — “Frontend Development” — was defined as: develop all HTML, CSS, and JavaScript for the 12 approved page templates using the BrightFrame design mockups as specifications, including responsive breakpoints at 1440px, 768px, and 375px. The deliverable was a fully functional frontend codebase committed to the GitHub repository. Acceptance criteria: all 12 pages render correctly in Chrome, Firefox, Safari, and Edge; Google Lighthouse performance score above 85 on all pages; zero CSS errors in W3C validator.
Work Package 1.4.1 — “Hosting Infrastructure Setup” — included precise acceptance criteria for HTTPS enforcement, SSL certificate validity, nginx HTTP/2 configuration, and a load test passing at 200 concurrent users. These precise definitions enabled Maria Santos to write all QA test cases directly from the WBS dictionary without additional specification documents — saving approximately four hours of test planning time and eliminating the scope ambiguity that typically requires mid-sprint clarification.
You can download the complete filled-in example below — it shows exactly how the WBS dictionary was built for a real project.
Download Free WBS Dictionary Template and Example
We have prepared two free resources to help you build a WBS dictionary for your own projects:
- Download the WBS Dictionary Template — PMBOK 8 (blank, ready to fill in)
- Download the WBS Dictionary Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
WBS Dictionary — Best Practices and Common Mistakes
Write the scope description to the level of detail needed to prevent scope boundary ambiguity. The acceptance criteria section is the most important and the most commonly underdeveloped; vague acceptance criteria make deliverable acceptance a negotiation rather than a verification. Have the responsible party review and sign off on their work package dictionary entry before the scope baseline is approved.
The WBS dictionary is most effective when it is developed collaboratively with the team members who will do the work, ensuring that the scope description reflects operational reality. Teams that skip or rush the dictionary often discover mid-project that their WBS boxes contain very different amounts of work than they expected.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Project Management