What Is a WBS Dictionary?

A WBS Dictionary is a document that provides detailed information about each component in the Work Breakdown Structure (WBS). In PMBOK 8, the WBS Dictionary complements the WBS graphic (which shows structure) with the narrative detail needed to define, execute, and control each work package. For every WBS element — phase, deliverable, or work package — the dictionary includes: a code of accounts identifier, scope description, assumptions and constraints, responsible organization or person, scheduled milestones, resources required, cost estimates, quality requirements, acceptance criteria, and references to technical specifications. Together, the WBS and WBS Dictionary form the scope baseline.

What's Inside This WBS Dictionary Example

This WBS Dictionary example covers Project Phoenix — MCG's $72,250 website launch, March 17 to June 13, 2025. The spreadsheet contains one row per WBS work package (32 work packages across 5 phases), with columns for:

• WBS Code — hierarchical numbering (e.g., 3.2.1 = Execution / Development / Homepage Build)
• Work Package Name — clear, noun-phrase title
• Scope Description — what is included and explicitly what is excluded
• Deliverable — the tangible output of the work package
• Acceptance Criteria — specific, measurable conditions for completion
• Owner — primary responsible team member
• Estimated Hours — hours allocated from Cost Estimates
• Estimated Cost — labor and material cost from Cost Estimates
• Start / Finish — planned dates from the Schedule Baseline
• Dependencies — predecessor work packages
• Quality Standards — applicable standards (WCAG, Core Web Vitals, etc.)

How Alex Morgan Used This WBS Dictionary

Alex Morgan used the WBS Dictionary as the primary reference for work package handoffs. When the Lead Developer received a new work package assignment, the WBS Dictionary entry for that package was the first document shared — it defined exactly what "done" meant before a single line of code was written.

Three WBS Dictionary entries proved especially valuable during execution:

• WP 3.4.1 (Content Migration): The scope description explicitly stated "migration of core website pages defined in the approved content inventory" with an "excludes blog archive and legacy press releases" carve-out. When the content audit revealed 180 pages, this exclusion language provided the contractual foundation for CR-002's scope reduction — it was not a PM judgment call, it was a scope boundary that had been agreed at project start.
• WP 2.1.1 (UX Wireframes): The acceptance criteria specified "wireframes approved by MCG Marketing Manager and Riley Park in writing before development begins." This criterion prevented the development team from starting homepage coding before design was fully approved — a common source of rework in web projects.
• WP 4.2.3 (UAT Execution): The quality standards section referenced the 143-test-case UAT script as the required evidence of completion. When Riley Park needed to approve UAT sign-off remotely (ISS-007), Alex provided the completed test case spreadsheet as the formal evidence — because the WBS Dictionary had specified it as the required deliverable.

Download and Customize

This WBS Dictionary example is available as a free download. Use it as a reference to build your own WBS Dictionary, or start with the blank template and complete it alongside your WBS development.

• Download the WBS Dictionary Template — PMBOK 8 (blank, ready to use)
• Read the article: WBS Dictionary in PMBOK 8 — Guide and Best Practices

WBS Dictionary Example: Key Takeaways

The WBS Dictionary's "excludes" language in WP 3.4.1 (Content Migration) is the most consequential sentence in Project Phoenix's entire document set. When the content audit revealed twice as many pages as assumed, the exclusion clause turned a potential scope dispute into a clean change request. That clause did not write itself — it was the result of Alex asking "what could be interpreted as included that we do not intend to include?" during WBS Dictionary development. The WBS Dictionary earns its value not from describing what will be done, but from explicitly stating what will not be done. The out-of-scope boundary is where scope creep begins; the WBS Dictionary is where it ends.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.