Office guide
How to Use Work Breakdown Structure Builder
A work breakdown structure decomposes a project into deliverables and manageable work packages. Numbering, levels, owners, and notes make scope visible before dates and dependencies are added elsewhere.
Open the Work Breakdown Structure BuilderWhat to prepare
A few reliable inputs make the first result easier to review.
- The project’s final deliverables and boundaries
- A consistent definition of the lowest useful work package
- Owners and notes for major components
How to Use Work Breakdown Structure Builder
- Name the project
- Add top-level deliverables, then add lower-level components with the correct level
- Build the work breakdown and inspect numbering and hierarchy
- Check for complete scope without overlap, then export the outline
Worked example
For a conference, top-level deliverables might be Venue, Program, Registration, and Communications. Under Venue, include Contracted space, Room setup, and Accessibility arrangements.
Review the result
Apply the 100 percent rule: children should account for all work represented by their parent without adding unrelated scope. Stop decomposing when a package can be estimated and owned.
Practical tips
- Use deliverable nouns rather than activity verbs at higher levels
- Keep sibling items at similar detail
- Assign ownership after the structure is coherent
Common mistakes to avoid
- Turning the WBS into a chronological task list
- Mixing outcomes and departments at the same level
- Creating work packages too large to estimate
Build it in your browser
The free Work Breakdown Structure Builder processes entries locally in your browser. Review the generated draft against source information and any policy that applies before sharing it.