Cost Breakdown Structure in Construction: A Guide for Commercial Project Teams

By

Josh Krissansen

Last Updated Jul 2, 2026

By

Josh Krissansen

How costs are structured at tender determines how accurately they can be tracked through delivery. A poorly designed hierarchy makes variation tracking inconsistent, and progress claims harder to substantiate than they should be.

A cost breakdown structure (CBS) is the hierarchical framework that organises every project cost into trackable categories, from preliminaries and subcontract packages through to contingency and escalation. 

We cover what a CBS includes, how to build one for a commercial project, how it connects to the WBS, and how to use it as a live cost control instrument from tender through to final account.

What is a cost breakdown structure in construction?

A cost breakdown structure is a hierarchical framework that organises every project cost into trackable categories, each tied to a specific scope of work or cost type.

Categories cover the full spread of project expenditure: 

• Subcontract packages
• Preliminaries
• Plant and equipment
• Materials
• Indirect costs

A CBS is not the same as a project budget. The budget sets the total amount to be spent, while the CBS defines how that total is divided and tracked through delivery.

Take a $12 million commercial fitout, for example. The budget tells you the total approved cost. The CBS breaks that figure into $4.2 million across trade packages, $1.1 million in preliminaries, $480,000 in head contractor-supplied materials, $350,000 contingency, and $120,000 escalation, each under its own cost code.

Unlike a high-level budget, the CBS gives project teams visibility into where costs are moving, which packages are under pressure, and how variations and procurement outcomes are affecting the overall financial position as delivery progresses.

In the above example, the CBS is what lets you see, mid-delivery, that the joinery package is tracking $60,000 over budget while contingency is still intact, rather than only knowing that total project cost is under pressure.

A CBS runs the full life of the project. The estimator builds the CBS during tender pricing, and the commercial manager maintains and reconciles it from mobilisation through to final account.

What does a construction CBS include?

A CBS is organised hierarchically, with broad cost categories sitting at the top level, and individual packages and line items nested beneath them. Each package at the lowest level carries its own cost code, against which budget, variations, and forecast are tracked.

The categories below reflect how those top-level divisions are typically structured on a commercial project.

Preliminaries

Preliminaries are the site-level costs that support construction activity but cannot be attributed to a specific trade package. They include site establishment, site management, temporary works, amenities, and insurances.

They are also among the least consistently structured elements of a CBS, which is why a clear coding structure needs to be defined early on. Otherwise, preliminaries become a catch-all. Costs get posted to whichever code is most convenient rather than the correct one, and by the time the project is in full delivery, the preliminaries line is carrying expenditure that belongs elsewhere, making cost-to-complete forecasting unreliable at the category level.

Trade packages

Trade packages are the discrete scopes of work left to subcontractors, and they typically make up the bulk of cost on a commercial project.

Each package carries its own cost code, with awarded subcontract value, approved variations, committed cost, and forecast final cost tracked separately. During delivery, this structure allows project teams to monitor how individual packages are performing against budget as procurement, variations, and site progress evolve.

Provisional sums and PC sums

Provisional sums cover work where the scope or cost is not fully defined at contract execution, while PC sums cover supply items where the final purchase cost has not been confirmed.

Both are carried as discrete line items so they can be updated as the project progresses without distorting the original budget structure.

Contingency

Contingency is a budget reserve held separately from package allocations to absorb unforeseen costs as they arise. It sits outside package budgets and is managed through a drawdown process, not an open allocation.

Escalation

Escalation is a provision for cost increases driven by market movement over the project programme, and is most relevant on projects with long programmes or where material price volatility is a live commercial risk.

Indirect costs and overheads

Indirect costs and overheads are expenses that sit above the direct construction cost structure and cannot be assigned to a specific package. They include head office recovery, project management costs, and permits, each requiring its own cost code.

On many projects, these categories are reported separately during monthly cost reviews because they do not move in the same way as subcontract package costs through delivery.

CBS vs WBS in construction: How they connect

The WBS (work breakdown structure) and CBS serve different but complementary purposes. 

The WBS breaks the project down into discrete work packages, each with defined scope and assigned responsibility. The CBS takes those same work packages and attaches a cost code to each one, carrying budget, committed cost, and forecast against that scope. 

That shared structure is what makes cost reporting traceable.

When every work package in the WBS maps directly to a cost code in the CBS, any cost movement can be traced back to a specific scope of work. When a variation comes in, or a package goes over budget, the project team can identify exactly where in the project it originated rather than hunting across an inconsistent structure.

The most common problem is when the two are built independently. The project manager builds the WBS for programme purposes, and the QS builds the CBS separately, with no consistent mapping between them.

When variations occur, scope and cost tracking diverge, and project teams lose the ability to understand which work packages are driving cost movement or whether programme changes are affecting the forecast.

How to build a CBS for a commercial construction project

The steps below cover how to structure a CBS for a commercial project, from establishing the cost code hierarchy through to confirming reporting requirements before delivery begins.

1. Start with the WBS

Build the CBS directly from the project WBS. Work through the WBS systematically, using it to assign a cost code to each package.

Where a work package covers multiple cost types, such as both subcontract labour and head contractor-supplied materials, split it into separate cost codes at the lowest level of the hierarchy so each component can be tracked independently.

2. Define the cost code hierarchy

Three levels of cost codes are standard on a commercial project: 

1. Cost category at the top (subcontract, preliminaries, contingency)
2. Trade or package in the middle (structural steel, hydraulics, facade)
3. Cost element at the lowest level (awarded subcontract value, variations, materials supplied by head contractor).

That said, it's always smart to match the number of levels to project complexity. On a straightforward commercial fitout, for example, two levels is often sufficient: cost category at the top, and individual packages beneath it. On a complex D&C hospital build, you might run four: cost category, building system, trade package, and cost element. 

More levels produce finer visibility but increase administrative overhead, so the structure should reflect what the project team can realistically maintain through delivery.

3. Allocate the contract sum

Distribute the contract sum across cost codes at the package level at project commencement. Preliminaries, contingency, and escalation should sit as discrete line items, not inside package budgets.

Where subcontracts haven't been awarded at the point you’re setting up the CBS, carry the budget against the relevant cost code as an estimate and update to the awarded value once the subcontract is executed. For instance, if the facade package was estimated at $2.4 million but awarded at $2.75 million, that $350,000 variance needs to be recorded against the facade cost code immediately and a drawdown contingency flagged.

Confirm that all cost codes reconcile to the contract sum, and hold any unallocated balance as an explicit line item rather than leaving it unaccounted for.

4. Set up variation tracking

Give each package cost code four distinct fields:

1. Original budget
2. Approved variations
3. Pending variations
4. Forecast final cost

Once a variation is approved, record it against the relevant cost code. Until it is, carry it in the pending column rather than leaving it unrecorded. Maintaining both figures gives the commercial manager a clear picture of the full variation exposure at any point in the project, not just the portion that has been formally signed off.

The CBS should mirror the variation register in real time.

This means that if a variation is raised on site, it goes into the pending column the same day. When updates are left to accumulate, the CBS stops reflecting the actual commercial position, and cost surprises become harder to explain at monthly reporting.

5. Align with the programme

Map each cost code to the corresponding activity or milestone in the construction programme. 

When cost codes are tied to programme activities, the CBS can project not just what each package will cost in total, but when that expenditure will fall.

For a subcontract package that runs across three programme stages, spend doesn’t necessarily happen evenly across them, and linking the cost code to the programme lets the commercial manager forecast spend in line with actual site progress rather than spreading it arbitrarily across the project duration.

6. Confirm reporting requirements

Before finalising the CBS structure, confirm how costs will be reported to the client, to ownership, and internally across the project team.

Where possible, structure the cost code hierarchy to mirror those reporting categories directly.

For example, if the client requires costs reported by building element, organise the relevant cost codes under building element categories from the start. If ownership requires a summary by cost type, make sure the top level of the hierarchy produces that view without manual aggregation.

The goal is a CBS that generates each reporting format as a natural output rather than a reconciliation exercise at the end of every reporting cycle.

Using the CBS throughout the project lifecycle

The CBS moves through four distinct phases across the project, and what it needs to do at each stage is different. Here’s how to manage it from tender through to final account.

At tender: Establish the structure before subcontracts are awarded

Build the CBS as part of the tender pricing exercise. Establish cost codes against the tender WBS, allocate the contract sum estimate across packages, and set contingency and escalation as discrete line items from the start.

At this stage, the CBS reflects the head contractor's view of project cost based on subcontractor quotes, estimating data, and Rawlinsons or AIQS benchmarks where package pricing is incomplete.

The structure established here should carry through to delivery without being rebuilt. A CBS that is reconstructed at mobilisation means you lose the audit trail on how the original estimate was put together, so when budget pressure emerges mid-delivery, there's no clear reference point for where it started.

At mobilisation: Transition from tender document to live cost control tool

Replace tender estimates with subcontract awards at the package level. The difference between the two is the first real read on budget performance for each package.

If the programme has been updated since tender, confirm that cost code mapping reflects the current activity structure before site works begin. A mismatch between the CBS and the live programme at mobilisation creates forecasting problems that compound through delivery.

During delivery and progress claims: Maintain the CBS as a live instrument

Update the CBS at each cost reporting cycle (typically monthly). Post approved variations to the relevant cost codes, update cost-to-complete forecasts, and record contingency drawdowns against the contingency line.

Cost-to-complete forecasting at the package level is the most operationally important function of the CBS during delivery because it is the only figure that tells the commercial manager whether the project will finish within budget before it actually does. 

The forecast final cost for each package should reflect the commercial manager's best current assessment of where the package will land, not the original budget plus approved variations. Those two figures will rarely be the same on a project of any complexity.

A CBS maintained through delivery also provides the cost substantiation trail for variations included in progress claims. That record is built progressively through monthly updates, not reconstructed at claim time.

At final account: Reconcile and retain

At practical completion, the CBS transitions from a forecasting tool into a reconciliation document. Reconcile the original contract sum against the final certified cost, with every approved variation, provisional sum adjustment, and contingency drawdown accounted for line by line.

Retain the final CBS as a project benchmark.

Cost data at the package level, particularly the relationship between tender estimate, awarded subcontract value, and final cost, is the most useful input available when estimating future projects of a similar type.

A cost breakdown structure helps teams keep project costs visible

A CBS built at tender and maintained through delivery gives commercial teams a live read on cost movement, variation exposure, and forecast final cost at the package level.

Set it up from the WBS, keep it current through every reporting cycle, and the numbers in your monthly cost report will reflect where the project actually stands.

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