Skip to content
GanttPal
Log in Get started

How to create a work breakdown structure that captures the full scope

A work breakdown structure, or WBS, turns a broad project goal into a hierarchy of outcomes. Used well, it exposes missing work before scheduling begins, gives stakeholders a shared picture of what is included, and makes later estimates more credible. The method below combines the core concepts with a practical checklist for building, reviewing and handing the structure over to a schedule.

What a WBS does

A WBS is a top-down map of everything a project must produce. It starts with the final outcome and repeatedly divides that outcome into smaller deliverables until each remaining item is a work package: a concrete result that can be estimated, assigned and tracked without further decomposition into deliverables. The hierarchy shows parent and child relationships, so a reader can move from the overall goal to the components that support it.

That structure serves several planning purposes. It creates one agreed inventory of deliverables, clarifies what sits inside and outside the scope, reveals connections between parts of the work, and gives the team a basis for matching skills, time and cost to each package. Because hidden deliverables are a common cause of scope growth, missed dates and budget pressure, spending time on decomposition early can reduce surprises later.

Levels, dictionary and control accounts

Level 1: Final deliverable. This is the project goal or ultimate result. Every lower level should trace back to it.

Level 2: Major deliverables or phases. These are the broad categories that together cover the whole project. If a sub-deliverable does not fit anywhere, the category set is incomplete.

Level 3: Sub-deliverables. Each major category is divided into smaller outcomes. Items at this level remain deliverables rather than actions.

Level 4: Work packages. These are the lowest deliverables in the structure. They may be broken into tasks and subtasks for execution, but they are not decomposed further as deliverables.

Two supporting elements make the hierarchy easier to use. A WBS dictionary explains each element in words, typically covering its name, description, budget, risks, milestones, acceptance criteria and tracking measures. Control accounts mark groups of work packages that need closer progress and risk monitoring; they can be highlighted by colour, outline or a symbol so they stand out during reviews.

Decomposition should stop when additional detail would make the structure harder to maintain. Extra explanation belongs in the dictionary, not in endless extra levels.

Deliverable-based or phase-based?

Deliverable-based WBS: Major categories are outcomes. This suits projects where separate teams produce distinct results and rarely need to coordinate step by step, such as some construction work. It keeps attention on the complete scope and avoids early arguments about sequence, but timing and dependencies remain hidden until the structure is converted into a schedule.

Phase-based WBS: Major categories are stages of work. This suits cross-functional efforts where people must collaborate closely, such as building a mobile application, and it is often easier for newcomers because it follows the natural order of progress. It converts more readily into a timeline and makes early priorities visible. The risk is drifting into process detail, with approvals and meetings replacing the outcomes they support.

A quick decision check: if the main question is "what must exist when this is done?", start with deliverables. If the main question is "what must happen first, and what depends on it?", start with phases. Either way, keep naming focused on nouns that describe results, and return to outcomes whenever the discussion slips into activity.

Six-step build process, with a worked example

  1. Start from the charter. Confirm the goals and objectives in writing before decomposing anything, so the hierarchy has a stable target.
  1. Bring in the people who will do the work. Their knowledge is how missing deliverables surface; a structure built alone rarely reaches complete coverage.
  1. Name the major deliverables. Ask the group to stay at outcome level first. Capture lower-level ideas as they arise, but park them until the top categories are settled.
  1. Decompose each category. Work through one major deliverable at a time, using actions only as prompts to discover the sub-deliverables those actions produce. Smaller groups can draft separate branches, then reconvene to merge and order them.
  1. Review for completeness and granularity. Look for gaps, duplicates, items that are still too broad, and branches that have gone too deep. Decide at this point whether a dictionary will be created and who will maintain it.
  1. Share the finished structure. Make sure everyone can access the same version, link it from the project plan, and update it when scope changes so it remains the reference for deliverables.

Worked example: for a trip, the final deliverable could be "prepare for vacation". Major deliverables might be decisions, transportation, lodging and a packing list. Under decisions sit travel dates, destination and budget; under transportation sit flights and a rental car; under lodging sit a hotel reservation and pet sitter. The pet sitter branch can end in work packages such as keys, instructions, emergency contact details and a prepared guest bedroom. The same hierarchy can then be drawn as a tree diagram, written as an indented outline, or laid out in spreadsheet columns, depending on who will read and reuse it.

Choosing a format and moving to a schedule

Flowchart or tree diagram: Best for visual presentations and slide decks. Colour and boxes can separate levels or groups, and the whole scope is visible at a glance. It is less convenient when the structure must be edited frequently or imported into another tool.

Outline or indented list: Best when space is tight or the structure will move into project software later. Numbering preserves hierarchy in plain text and survives copying between documents.

Spreadsheet or table: Best when estimates, owners or other fields need to sit beside each deliverable. Columns can represent levels, and extra columns can hold time or cost figures. This format also travels well into scheduling tools without retyping the hierarchy.

Once the WBS exists, a Gantt chart adds what the WBS deliberately leaves out: dates, dependencies, milestones and resource assignments. Work packages become schedulable items, while the hierarchy remains the scope reference. Keeping the two connected matters, because changes made in one should be reflected in the other.

Best practices and when to skip it

Do cover the entire scope, stay focused on deliverables, name items with nouns, keep the hierarchy simple, involve every relevant team, update the structure as work progresses, and consider building it inside a scheduling tool so estimates and assignments attach directly.

Do not turn the WBS into a task list, a process map or a status report. Avoid verbs as deliverable names, excessive granularity, and building the structure without input from the people who will deliver it. For projects with firm deadlines and dependencies, do not rely on a purely deliverable-based view without adding timing afterwards.

Finally, recognise the limits of the method. A repeat project with little change may need only a review of an earlier structure. A project with a single deliverable may need sequencing more than decomposition. And when unknowns outnumber known deliverables, as in early product discovery, goal-focused tools may serve the team better until the scope firms up. In all other cases, a complete WBS gives the project a clearer foundation for estimates, resources and change control.

WBS levels at a glance
LevelWhat it containsTest for a good entry
Level 1Final deliverable or project goalEvery lower item traces back to it
Level 2Major deliverables or phasesTogether they cover 100% of the scope
Level 3Sub-deliverablesStill an outcome, not an action
Level 4Work packagesCan be estimated and assigned without further deliverable breakdown

Levels describe deliverables; work packages are the lowest deliverable level and may contain tasks below the WBS.

Deliverable-based versus phase-based WBS
ConsiderationDeliverable-basedPhase-based
Top levelDeliverablesProject phases
Best fitSeparate teams with distinct outputsCross-functional teams working in sequence
TimelineNeeds extra work to add timing and dependenciesConverts more readily into a timeline
Main riskEarly priorities stay hiddenProcess detail crowds out outcomes

Neither type is universally better; the choice depends on team structure, experience and how the structure will be used.

Frequently asked questions

Is a work breakdown structure the same as a task list?

A WBS is not a task list. It names the outcomes that must exist, grouped from the final goal down to work packages that are small enough to schedule and assign. Tasks, dates and dependencies belong in the plan that follows.

Should I organise a WBS by deliverables or by phases?

Choose deliverables when separate groups can define their outputs independently and timing is secondary. Choose phases when a cross-functional team must move in sequence and early work determines what can start next.

What belongs in a WBS dictionary?

A dictionary entry can record the name, description, budget, risks, milestones, acceptance criteria and tracking measures for each element. Keeping that detail beside the hierarchy prevents the main chart from becoming cluttered.

When can a team skip building a new WBS?

A familiar repeat project may only need a quick review of the earlier structure. A single-deliverable effort may need sequencing more than decomposition. When most deliverables are still unknown, goal-setting tools may work better until the scope becomes clearer.