Contingency in Construction: How Much Is Enough?

Every construction budget includes a contingency allowance. Most people understand that contingency exists to cover unexpected costs. Fewer understand what "unexpected" actually means in a construction context — and how the right contingency amount changes depending on the stage of design and the type of project.

What contingency is for

Construction contingency is a financial allowance for costs that are reasonably foreseeable but not yet quantified. It is not a buffer for poor estimating, scope creep, or client-directed changes.

There are typically two types of contingency in a well-structured cost plan:

Design contingency: allowances for aspects of the design that haven't been fully resolved at the time of the estimate. As the design develops, this contingency should reduce — because the uncertainty it was covering has been resolved.

Construction contingency: allowances for risks during the construction phase — unforeseen site conditions, latent defects in existing structure, minor scope additions. This contingency sits in the project budget and is managed by the project manager.

How much contingency at each stage

Contingency requirements vary with design development. A rough guide:

| Stage | Contingency range | |-------|-------------------| | Concept / feasibility | 20–30% | | Developed design | 10–15% | | Construction documentation | 5–10% | | Post-tender (contract awarded) | 3–5% |

These ranges are guides, not rules. Renovation and alteration projects typically carry higher contingency than new builds at equivalent design stages, because the existing conditions introduce more uncertainty. Heritage projects carry more again.

Why too little contingency is a problem

When contingency is underestimated, the first unforeseen cost event exceeds it. The project manager then has to go back to the client for additional budget — often at a point when it's too late to recover the cost through value management.

Clients who've been told a project will cost $X and then receive a variation notice that pushes it to $X + 15% lose confidence in the cost management process, regardless of whether the contingency shortfall was the PM's fault or not.

Why too much contingency is also a problem

Contingency that's too high gives a false signal of cost certainty. A client told their project budget is $5M with 25% contingency is really being told the estimate has very low confidence — but that signal is often lost in the headline number.

Excess contingency also has a way of being spent. When there's headroom in the budget, the discipline around variation control relaxes. The contingency isn't available for genuine unforeseen risks; it's been absorbed by approved scope additions that should have been value-managed.

Managing contingency drawdown

Contingency should be tracked like any other cost. Each drawdown should be authorised by the project manager, recorded in the cost plan with the reason for the drawdown, and reconciled against the remaining contingency balance.

A cost plan that shows "contingency remaining: $0" three months before practical completion is a warning sign — either the contingency was too small to begin with, or it wasn't managed properly during the project.

---

Contingency tracking is part of every cost plan we prepare. Contact us if you'd like us to review your current project budget.