Cost breakdown structure: A guide for Australian construction teams

By

Josh Krissansen

Last Updated Aug 30, 2026

By

Josh Krissansen

A cost breakdown structure (CBS) is a hierarchical structure that organises a project's total costs into categories such as labour, materials, equipment, subcontractor packages, overheads, and contingency.

A well-built CBS at the tender stage becomes the backbone of cost control during delivery. 

Designed poorly, though, the CBS forces the project team into manual re-mapping every time a variation, progress claim, or cost report is due.

We cover what a CBS includes, how it differs from a schedule of rates and WBS, and how to build one that holds up from estimate through to final account so that you can set up cost coding your project team can actually use.

What is a cost breakdown structure?

A cost breakdown structure (CBS) organises a project's total costs into a hierarchy of defined categories: 

• Labour
• Materials
• Equipment
• Subcontractor packages
• Overheads
• Contingency

By providing a structure under which costs are organised, the CBS makes cost tracking, forecasting, and reporting possible at every level of a project, not only at the total budget figure. That means a project team can interrogate cost performance at a single trade package as readily as across the whole job.

The CBS is built using the cost estimate, which is a separate pricing exercise. The CBS gives that estimate structure.

What a CBS includes

A complete CBS accounts for every dollar the project will spend, sorted so that each cost sits in a category the team can track and report against. Five components make up that structure.

1. Direct costs

   Direct costs attach to a specific work package. Labour is broken down by trade, materials and plant are split by category, and subcontractor packages are priced individually rather than lumped under a single trade heading. Pricing each subcontract package on its own line keeps committed costs traceable once the packages are let.

2. Indirect costs

   Indirect costs support the project without attaching to any one work package. They cover site establishment, supervision and management salaries, temporary services, and insurances.

3. Overheads and margin

   Head office cost allocation, company overheads, and profit margin sit here, kept separate from project delivery costs. Blending margin into delivery line items hides true project performance, leaving the team unable to tell whether the job itself is making or losing money.

4. Contingency

   Contingency is a risk allowance held against defined cost categories rather than a single blanket percentage across the job. Tied to specific risk exposure, such as latent conditions or authority-driven scope, the allowance lets the team track each risk and draw down against it as the exposure resolves.
   

5. Cost code hierarchy

   Most CBS hierarchies run three to four levels deep. The top level holds broad categories such as labour, materials, and subcontractors. Lower levels reach individual trade packages or cost items. Building the hierarchy this way lets any stakeholder report at whichever level suits their decision.

How to build a CBS that survives estimate to execution

A CBS earns its value in delivery, but it gets built during the tender, when the pressure is on winning the job rather than running it. The five steps below set the structure up at tender stage so it carries through commitment, tracking, and payment without a rebuild after award.

Step 1: Set cost codes at tender stage with execution in mind

Estimating teams typically build cost codes around pricing logic, grouping items in whatever way makes the tender easiest to assemble. That produces a structure suited to winning the job, but it falls apart once delivery starts, and costs need to be tracked against committed packages rather than estimate line items.

Before you finalise the tender, confirm that every cost code maps to how costs will actually be committed and tracked during delivery. If a code cannot be linked to a specific trade package, subcontract, or purchase order, plan on re-mapping it after award.

Step 2: Map cost codes to trade packages

Give every trade package the project requires a directly corresponding cost code or group of codes in the CBS. When that mapping is clean, committed costs, actual costs, variations, and progress claims all reference the same structure.

Where a single cost code covers multiple trade packages, overspend in one package gets hidden by underspend in another. The project team loses visibility until the aggregate position is already over budget.

Step 3: Set cost code depth to match project complexity

A CBS set too high-level aggregates cost risk into categories too broad to act on, but a CBS set too granular creates reporting overhead without improving any decision.

Three to four levels of depth suit most commercial construction projects:

• The top level covers major categories such as labour, materials, subcontractors, and preliminaries
• The second level breaks these into trade groupings
• The third and fourth levels reach individual trade packages or cost items where the value warrants it

Let the value and risk of the cost item decide where to add depth, rather than applying a uniform rule across the whole project.

Step 4: Sense-check rates against published benchmarks

Rawlinsons or AIQS rate data can confirm whether category-level cost assumptions sit within a reasonable range at setup. This helps most with indirect costs and preliminaries, where teams often carry allowances forward from previous projects without adjusting for the conditions of the current one.

Treat published benchmarks as a sense-check, not a substitute for project-specific pricing. Site conditions, procurement strategy, and market conditions all move actual rates away from any published reference.

Step 5: Align the CBS to the contract schedule of values before the first progress claim

The contract schedule of values is the document the principal uses to assess progress claims. If the CBS cost codes do not map cleanly to it, every claim needs manual reconciliation between two structures.

Confirm alignment before the first claim goes in, as fixing a misalignment once claims are already in progress creates rework, delays payment, and opens disputes over line items that do not match.

Common CBS failure points and how to fix them

Four failure points show up repeatedly on commercial projects, and each has a fix that costs far less to apply at setup than to retrofit mid-delivery.

Estimate and execution use different cost structures

When the estimating team builds cost codes for tendering convenience and hands over a structure the delivery team cannot use to track committed costs and actuals, it causes several problems at once.

Variations can’t be coded consistently, cost reports need manual re-mapping, and forecasts become unreliable because the baseline they reference does not match how money is actually being spent.

The fix is to require the estimating and commercial teams to agree on a single cost code structure before contract award. Treat the CBS as a handover item reviewed between preconstruction and delivery, not as the estimator's document alone.

Portfolio reporting breaks down across projects

When each project sets up its own CBS from scratch, cost categories end up named differently and structured at different levels of depth, which leaves them impossible to compare meaningfully across a portfolio.

The fix is a standardised CBS template at business level that every project adopts as its starting framework. Individual projects can add depth where needed, but the top two levels of the hierarchy stay consistent across the business.

Progress claims are disputed because they do not match the contract schedule of values

Cost categories need to align with how the construction contract structures payment.

When they don’t, because the CBS is built around internal cost categories, the principal or superintendent assesses claims against the schedule of values and queries or rejects the line items that do not match.

The fix is to map CBS cost codes to the contract schedule of values at project setup, before the first claim is submitted. Where the contract groups costs differently to the internal CBS, build a reconciliation layer rather than forcing the CBS to match a structure that doesn’t serve internal reporting.

Cost overruns are hidden in aggregated categories

When cost codes sit too high-level and multiple trade packages or cost items share a single code, overspend in one area is masked by underspend in another until the aggregate position tips over budget. The project team can’t intervene early, because the reporting structure does not show where the problem actually sits.

The fix is to set a minimum level of cost code granularity for any trade package or cost item above a defined value threshold. The threshold varies by project size, but the principle is the same at any level: 

Any cost item large enough to materially affect the budget should appear as its own line in the CBS.

A well-built cost breakdown structure stays intact from estimate to final account

A cost breakdown structure only earns its value when the same categories carry through tender, commitment, tracking, and payment without a rebuild after award. Set the codes up at tender stage with delivery in mind, map them to trade packages and the contract schedule of values, and the CBS becomes the one structure your project team reports against for the life of the job.

Written by

Josh Krissansen

122 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