The WBS Dictionary Template is the companion document to the Work Breakdown Structure (WBS) that provides detailed information about each WBS component. In PMBOK 8, the WBS Dictionary is part of the scope baseline and ensures that every team member, contractor, and stakeholder has a shared understanding of exactly what each work package entails.

What's Included in This WBS Dictionary Template?

This free PMBOK 8 WBS Dictionary Template is a structured Excel spreadsheet. For each work package, it includes:

• WBS Code — the unique identifier from the Work Breakdown Structure.
• Work Package Name — the descriptive name of the deliverable or activity.
• Description — a detailed narrative of the work to be performed.
• Deliverable(s) — the specific outputs or outcomes expected.
• Acceptance Criteria — measurable conditions that must be met for the deliverable to be accepted.
• Assumptions — conditions assumed to be true for this work package.
• Constraints — limitations that affect how the work can be done.
• Owner / Responsible — the person or team accountable for this work package.
• Estimated Duration — planned working days.
• Estimated Cost — budgeted amount.
• Dependencies — predecessor and successor work packages.
• Quality Requirements — standards or metrics the deliverable must meet.

WBS Dictionary as Part of the Scope Baseline

In PMBOK 8, the scope baseline consists of three components:

1. Project Scope Statement — defines what is in and out of scope.
2. Work Breakdown Structure (WBS) — hierarchical decomposition of scope into work packages.
3. WBS Dictionary — detailed descriptions for each WBS element.

The WBS Dictionary is what transforms the WBS from a visual hierarchy into an actionable contract between the project team and the stakeholders. Without it, work package boundaries are unclear and scope creep is almost inevitable.

How the WBS Dictionary Prevents Scope Creep

Scope creep — the unauthorised expansion of project scope — is one of the most common causes of project overruns. The WBS Dictionary prevents it by:

• Defining acceptance criteria: When the criteria are clear, there is no room for subjective interpretation of "done".
• Documenting out-of-scope items: Explicitly stating what is NOT included in a work package prevents assumptions.
• Providing a baseline for change control: Any request outside the WBS Dictionary is a formal change that requires a change request.

How to Complete the WBS Dictionary Template

1. Start with your WBS: Every Level 3 work package should have a WBS Dictionary entry.
2. Write clear descriptions: Avoid jargon. The description should be understandable by any team member.
3. Define measurable acceptance criteria: "Approved by the client" is not measurable. "Passes all UAT test cases with zero critical defects" is.
4. Document assumptions explicitly: If you are assuming something is out of scope, write it down.
5. Review with the team: Have SMEs validate the descriptions and criteria before baselining.

Related PMBOK 8 Templates

• Work Breakdown Structure Template — the visual hierarchy that the dictionary describes.
• Scope Baseline Template — the WBS Dictionary is a component of the scope baseline.
• Project Scope Statement — the narrative that the WBS decomposes.
• Deliverables Acceptance Checklist — used at delivery time to confirm acceptance criteria are met.

The Project Management Institute (PMI) includes the WBS Dictionary as a required component of the scope baseline. Projects that invest time in building a detailed WBS Dictionary experience fewer scope disputes, faster acceptance processes, and better stakeholder satisfaction. Download this free PMBOK 8 template to strengthen your scope management today.