When you need it
Use this dictionary when the work breakdown structure needs descriptions detailed enough for package owners to plan, price, deliver, and accept their work without relying on ambiguous hierarchy labels alone.
DOCX /
AI tools and documents for engineering and project management.
Work Breakdown Structure and Dictionary
Define the project work hierarchy and the scope, ownership and completion criteria of its packages.
How to use this templateThis Word template contains prepared headings, tables, project fields and completion notes. Add your information, review the completed document and remove the notes before issue.
The form prepares a separate brief; it does not fill the Word or Excel file.
Read product descriptions in your language. The Word and Excel template files are in English.
Only selected pages are shown. This is not the complete template. The full editable Word or Excel file is supplied with purchase.
Learning
How to use this template
What it helps you decide
It explains each work package's boundary, outputs, acceptance requirements, and planning interfaces, helping teams prevent gaps and duplication while maintaining a consistent connection between scope, ownership, schedule, cost, and control records.
How to complete it
- Define WBS scope and coding convention and Work breakdown hierarchy so package identifiers represent an understandable and consistent decomposition of the actual project scope.
- Complete Work package identity and boundary and Package outputs and acceptance, using source requirements to distinguish included work, interfaces, and the evidence of completion.
- Record Package planning interfaces and Package control and references, linking each package to relevant owners, planning information, and controlled source records without duplicating scope.
Who prepares and reviews it
The planning or scope lead usually coordinates package definitions with engineering, construction, commercial, and quality contributors. Package owners validate boundaries, while the project authority controls the approved scope structure and changes to its baseline.
A mistake to avoid
Repeating the package title as its definition leaves the scope boundary unresolved and gives planners, estimators, and delivery teams room for incompatible assumptions.
Illustrative example
Illustrative example: a substation programme includes a transformer-installation work package. The dictionary clarifies equipment positioning, termination interfaces, and acceptance evidence while distinguishing supplier testing from site work. Estimators and planners use that same boundary, avoiding duplicate crane allowances and an omitted earthing interface.
Document contents
- WBS scope and coding convention
- Work breakdown hierarchy
- Work package identity and boundary
- Package outputs and acceptance
- Package planning interfaces
- Package control and references
Required inputs
- Project name, location, company, document number and revision
- Actual project scope, source records and responsible roles
Practical tools.
Professional judgment.
Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.
Prepare project brief