A WBS dictionary template is a companion document to the Work Breakdown Structure that provides detailed deliverable, activity, scheduling, cost, and resource information for each component of the WBS. According to the Project Management Institute (PMI), the WBS dictionary is a component of the scope baseline in PMBOK 8, alongside the project scope statement and the WBS itself. Without a WBS dictionary, team members and contractors may interpret work packages differently, leading to scope gaps, disputes, and rework that could have been prevented with clear definitions upfront.

What is a WBS Dictionary?

A WBS dictionary template is a structured document where each WBS work package is described in enough detail that the team member or contractor responsible for it understands exactly what work is included, what the acceptance criteria are, what resources are required, and what the schedule constraints are. In PMBOK 8, the WBS dictionary is part of the scope baseline and ensures that the WBS is not just a graphic hierarchy, but a fully defined, unambiguous decomposition of the project scope. The dictionary prevents scope creep by making explicit what is — and what is not — included in each work package.

What's Included in This WBS Dictionary Template?

• WBS Code and Work Package Name - The unique WBS identifier and name for each work package, matching exactly the structure in the WBS diagram to ensure one-to-one traceability.
• Work Package Description - A detailed narrative of the work to be performed, written with enough specificity that someone unfamiliar with the project can understand what is required without asking follow-up questions.
• Deliverable and Acceptance Criteria - A description of the output produced by the work package and the specific, measurable criteria that must be met for the deliverable to be formally accepted.
• Scope Inclusions and Exclusions - Explicit statements of what work is within the scope of the work package and what is explicitly excluded, preventing misunderstandings at delivery time.
• Responsible Organization or Person - The team, department, or named individual accountable for completing the work package, linked to the responsibility assignment matrix (RAM).
• Schedule Milestones - The key dates associated with the work package, including the planned start date, planned finish date, and any intermediate milestones.
• Cost Budget - The budget allocated to the work package, serving as the control account-level budget for earned value measurement.
• Quality Requirements - Any quality standards, inspection requirements, test procedures, or regulatory compliance obligations that apply specifically to this work package.

How to Use This WBS Dictionary Template (PMBOK 8)

1. Complete the dictionary in parallel with WBS development - The WBS dictionary is most effective when written at the same time the WBS is developed, while the team's understanding of each work package is freshest. Retrofitting the dictionary after the fact produces superficial entries.
2. Write acceptance criteria that are measurable and testable - Vague criteria like "satisfactory quality" are unenforceable. Write criteria that specify exactly what will be measured, how, and by whom — so there is no ambiguity at the time of delivery.
3. Use the exclusions section actively - This is often the most valuable part of the dictionary. Explicitly stating what is NOT included prevents scope creep and contractor disputes. If a stakeholder asks for something not in the WBS, the exclusion statement is the first line of defense.
4. Link the dictionary to the responsibility assignment matrix - Every work package must have a single accountable owner. The dictionary reinforces this by naming the responsible party, ensuring no work package is orphaned.
5. Review and update the dictionary when scope changes are approved - The WBS dictionary is part of the scope baseline. Any approved change to scope must be reflected in the dictionary — otherwise the baseline becomes misleading.
6. Use the dictionary as the basis for contract statements of work - When work packages are contracted out, the WBS dictionary entry is the starting point for the statement of work, ensuring contract scope aligns precisely with project scope.

When to Create This Document (PMBOK 8)

The WBS dictionary is created during the Develop Scope Structure process (part of the Scope Performance Domain planning activities), after the WBS has been decomposed to the work package level. In PMBOK 8, the WBS dictionary becomes part of the scope baseline alongside the scope statement and WBS, and must be formally approved before the baseline is established. It is updated through formal change control whenever approved scope changes affect work package definitions.

Related Templates

• Work Breakdown Structure Template
• Scope Baseline Template
• Scope Management Plan Template
• Project Scope Statement Template
• Statement of Work Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• WBS Dictionary in PMBOK 8 - Complete Guide - Understand the purpose, key elements, and best practices before filling in the template.
• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.