Work breakdown structure: A guide for Australian construction teams

By

Josh Krissansen

Last Updated Jul 2, 2026

By

Josh Krissansen

On a large commercial project, dozens of subcontractors are pricing and delivering work simultaneously, each responsible for a defined scope.

What sits at the boundary between those scopes is often what gets missed, and teams usually do not discover the gap until it surfaces as a variation request or a dispute over responsibility. By that point, the impact is already affecting cost, programme, and commercial position.

A work breakdown structure (WBS) is the tool used to prevent that from happening. It breaks the full project scope into a hierarchy of components, from major deliverables down to discrete work packages that can be assigned, costed, and tracked. 

Built correctly, a WBS becomes the scope baseline from which the cost plan, construction programme, and subcontract packages are derived. It defines where cost and programme risk sits before delivery begins.

In this article, we explain what a WBS is, how it is structured, and how to build one for a construction project so the scope is clearly defined before delivery begins and variations can be assessed against a documented baseline.

What is a work breakdown structure?

A work breakdown structure (WBS) is a hierarchical map of everything a project must deliver, organised from the overall project at the top down to individual work packages at the bottom. Each level adds more detail until every element of scope has been broken into components specific enough to be assigned, costed, and tracked for progress.

A WBS is not a programme, organisational chart, or cost plan. It defines what needs to be delivered, while those tools define when it will happen, who is responsible, and what it will cost. The WBS becomes the scope baseline from which those systems are built.

In construction, the WBS drives subcontract package definitions, the cost breakdown structure, and the construction programme. This is where scope boundaries are set, and where cost and programme exposure begin to take shape. If the WBS is incomplete or poorly structured, those same gaps flow through into every downstream document.

How a WBS supports better delivery

On a well-run commercial project, the WBS becomes the reference point for how scope, cost, and accountability are managed from award through to handover, providing a consistent structure that connects what is planned to what is delivered.

• Scope definition

  The WBS captures every element of project scope in a single structured framework, making it the definitive record of what needs to be delivered and within what boundaries. Because each element is assigned to a responsible party, there is less risk of unowned work sitting between packages, which is where scope creep and coordination gaps typically emerge.

• Cost management

  Breaking scope into discrete work packages makes it possible to build a cost plan that maps directly to deliverables rather than to broad categories.
  During delivery, teams can track expenditure against specific packages, compare actual spend against forecast positions at a granular level, and identify which areas are absorbing cost ahead of programme. This gives the project team earlier visibility into emerging budget pressure.

• Accountability

  Because each work package has a named owner, responsibilities are visible across the project team.
  On a fitout project, the WBS makes explicit where the head contractor's own labour scope ends and where the hydraulics subcontractor's begins. That clarity extends to the client as well, reducing ambiguity about responsibility when issues arise during delivery and lowering the likelihood of scope disputes between packages.

• Phasing and sequencing

  On projects with staged delivery or early turnovers, the WBS provides the structure needed to sequence work logically across multiple packages.
  On a data-centre project with a live cutover date, the WBS helps identify which mechanical and electrical packages must be completed before fitout can begin. The project team can then map those dependencies against the programme and confirm that the sequencing is achievable before work starts on site, rather than discovering conflicts during delivery.

• Variation assessment

  When a subcontractor submits a variation claim, the first question is whether the work was already included in the original scope.
  On projects without a documented WBS, that question is answered by reading contract documents, cross-referencing drawings, and arguing about what was implied. On projects with a well-structured WBS, the project team can locate the relevant work package, confirm what was included, and assess the claim against a documented baseline rather than recollection or interpretation. That creates a clearer basis for assessing both cost and programme impact.

Types of work breakdown structures

There are two primary ways to structure a WBS in construction, and most commercial projects draw on elements of both, depending on how the project is staged and reported through delivery.

1. Phase-based WBS

   A phase-based WBS is organised around key stages of the project lifecycle, such as:
   
   • Design
   • Procurement
   • Construction
   • Commissioning
   • Handover
   
   This structure is useful where stage gates and client approvals drive the sequence, as is common on staged masterplanned developments where funding, planning conditions, or presales determine when each phase proceeds, and where reporting and cost control are tied to those milestones.

2. Deliverable-based WBS

   A deliverable-based WBS is organised around the physical components of the project rather than the stages used to deliver them. Major elements such as structure, envelope, fitout, and services form the upper levels of the hierarchy, with individual subcontract packages sitting beneath them.
   
   This is generally the preferred approach for most commercial construction projects because it alignes with how work is procured, contracted, and managed on-site.
   
   In practice, most commercial projects use a combination of both approaches.
   The upper levels of the WBS follow a phase structure, particularly where staged delivery or programme milestones are contractually significant. Within each phase, the structure then becomes deliverable-based, mapping directly to subcontract packages and trade scopes.

Key components of a WBS

A WBS is made up of several interconnected elements, each serving a specific function in how scope is defined, assigned, and controlled during delivery.

Hierarchy

The WBS is organised in levels, from the overall project at the top down to individual work packages at the bottom. The upper levels break the project into major components, while the lower levels decompose those components into manageable and assignable scopes.

For most commercial projects, three to four levels are sufficient. Adding more detail than the project requires increases administrative complexity without improving control.

Work packages

Work packages are the lowest level of the WBS and the unit around which everything else is organised.

Each work package needs a single owner, a cost and duration that can be estimated, and a clear enough scope that progress can be measured against it.

In construction, work packages typically align with subcontract trade packages, making them the natural connection point between the WBS, the cost plan, and the construction programme.

WBS dictionary

The WBS dictionary provides a written description of each element in the hierarchy, covering scope boundaries, responsible party, cost, and key milestones. It is most useful where package boundaries are not self-evident from the element name alone, particularly on complex projects where trade interfaces require explicit definition to avoid disputes later.

Coding structure

Each element in the WBS is assigned a numeric or alphanumeric identifier that allows it to be cross-referenced with the cost plan, construction programme, and subcontract documentation. A consistent coding structure is what makes the WBS functional as a management tool rather than just a scope map, supporting alignment between scope, cost, and programme as the project progresses.

The 100% rule

The WBS must capture 100% of the project scope. If an item of work does not appear in the WBS, it will not be tracked, costed, or managed, and when it surfaces during delivery, it will arrive as a variation, a programme impact, or a dispute.

On commercial construction projects, failures of the 100% rule most commonly occur at trade interfaces, where work sits between packages and responsibility has not been clearly assigned.

How to build a WBS for a construction project

On a typical commercial project, the WBS is built in a sequence that reflects how scope, cost, and delivery will ultimately be managed. The starting point is always the contract documentation.

Step 1: Gather project documentation

Start by collecting the full set of contract documents: drawings, specifications, the head contract scope of works, and any annexures that define deliverables, milestones, or constraints.

Review the documentation for staging requirements, early turnover obligations, and authority conditions. For example, a project with a contractual requirement to hand over a tenancy on level 10 before the rest of the building is complete will need that stage reflected as a discrete component within the WBS from the outset.

Material lead times, procurement dependencies, and subcontractor engagement timelines should also be identified early. On a project where structural steel carries a 16-week lead time, the steel package must be defined and procured well before the downstream packages that depend on it. That sequencing should already be visible in how the WBS is structured.

Step 2: Define the top-level structure

Set Level 1 as the project itself, typically identified by the contract name or project number.

At Level 2, break the project into its major components. On a commercial building project, this will often include civil and structure, building envelope, mechanical and electrical services, fitout, and external works. On staged developments, Level 2 may instead follow project phases rather than physical building elements.

The Level 2 hierarchy determines how the rest of the WBS is organised and how the project will ultimately be tracked and reported during delivery.

If monthly cost reports and progress claims are structured around building elements, the WBS should follow the same logic. If reporting is organised by project stage, the WBS should align with that structure instead.

Alignment at this level ensures that scope management, cost reporting, and programme tracking operate within the same framework rather than being managed independently.

Step 3: Break down to work package level

Break each Level 2 element into subcontract packages or trade scopes at Level 3. Continue decomposing the structure until each element can be assigned to a single responsible party, with a cost and duration that can be estimated and tracked for progress.

Each work package should reflect a genuine scope boundary, such as a subcontract trade, a self-perform scope for the head contractor, or a supplier package.

Once that level is reached, further decomposition rarely improves control and often increases administrative effort.

On a commercial office fitout, for example, the hydraulics package is typically treated as a single work package. Breaking it further into above-ceiling pipework, below-floor pipework, and fixtures adds detail that the project team is unlikely to manage or report against separately, while also creating documentation that becomes difficult to maintain throughout delivery.

Step 4: Apply the 100% rule

Work through the contract documents systematically and confirm that every element of scope is captured somewhere in the WBS. Where gaps are identified, add the missing elements to the WBS, assign them to a responsible party, and update the cost plan to reflect the additional scope before subcontracts are executed.

If the gap sits at a trade interface where ownership is genuinely unclear, resolve that question explicitly in the subcontract documentation rather than leaving it ambiguous, as unresolved interfaces are a common source of variations and disputes during delivery.

Step 5: Confirm alignment with the cost plan and programme

Each work package should map to a line in the cost breakdown structure. Where the WBS and cost plan do not reconcile, work through the discrepancy before contracts are awarded. Alignment at this stage ensures that scope, cost reporting, and programme tracking are all operating from the same framework.

Step 6: Maintain the WBS through delivery

The WBS should be treated as a living document throughout delivery. When scope changes are approved, the structure needs to be updated so the baseline reflects what has actually been agreed.

When a subcontractor submits a claim for additional work, the scope baseline tells the project team whether that work was already included in the package, and if not, what the contractual basis for the variation is.

The same logic applies to progress assessment and payment claims. Clearly defined work packages give both parties a more objective basis for measuring completed work, reducing the likelihood of disputes during claim assessment.

A WBS is the scope baseline every commercial project needs

A work breakdown structure gives the project team a single, structured view of everything that must be delivered, with each element assigned, costed, and traceable through the cost plan and construction programme.

Built before subcontracts are executed and maintained throughout delivery, the WBS is one of the clearest tools available for preventing scope gaps, managing variations, and keeping cost and programme performance under control.

Written by

Josh Krissansen

96 articles

Josh Krissansen is a freelance writer with two years of experience contributing to Procore's educational library. He specialises in transforming complex construction concepts into clear, actionable insights for professionals in the industry.

View profile