Cost Escalation

Most infrastructure cost blowouts are locked in before delivery begins.

Projects rarely become unaffordable because construction suddenly failed. Cost escalation usually begins much earlier — when organisations commit before authority, evidence, sequencing and delivery conditions are fully resolved.

Budgets appear stable at approval because uncertainty has not yet surfaced through the governance system. Once delivery begins, those unresolved assumptions harden into variation, rework, delay and contractual exposure.

By the time the variance appears financially, the structural decisions that created it are already embedded in the project.

XD Thinking™ examines the governance conditions underneath cost escalation — before delivery risk becomes operationally irreversible.
How cost escalation starts

Cost blowouts rarely begin as cost problems.

They begin when commitment moves faster than evidence, authority and delivery readiness. The budget looks controlled because the uncertainty has not yet been forced into view.

What sits underneath
Assumptions are not tested before approval
Evidence thresholds are applied inconsistently
Authority is unclear when risk emerges
Delivery constraints are identified too late
→
Decision failure
Commitment occurs before uncertainty is resolved
Risk is accepted rather than escalated
The original decision is not retested when conditions change
Escalation occurs after exposure is financially embedded
→
What you see
Variations increase once delivery begins
Budgets move after approval rather than before
Contingency is consumed earlier than expected
Executives inherit decisions they can no longer unwind
The visible cost overrun is usually the late-stage expression of an earlier governance failure.

Where the Cost Actually Enters

Financial exposure

Once commitments are made, cost escalation cannot be contained without trade-offs. Overruns flow directly into capital budgets, contingencies, or reduced scope elsewhere in the program.

Political and assurance exposure

Escalation triggers scrutiny from audit, executives and elected members. At that point, the ability to change the outcome is limited, but accountability remains.

Program disruption

Overruns do not stay isolated. They affect sequencing, delay other projects, and reduce confidence in the broader capital program.

What this calculates to
Most organisations do not measure the cumulative cost of unresolved uncertainty across the capital program. A simple model shows why it matters.
  • If 3 in 10 capital projects exceed their approved contingency
  • and average overrun on those projects is 18–25% of approved project value
  • on a capital program of $100M annually
In most organisations, this pattern begins at business case approval or budget sign-off — when projects are committed at 20–30% design maturity. From that point, uncertainty is not reduced. It is carried forward and paid for later.
This represents $5M–$7.5M in unplanned expenditure per year — reducing effective capital available and limiting how many projects can be approved and delivered each year.
Recent public reporting shows how this sequence unfolds in practice. A local government infrastructure project, initially approved at approximately $3 million, escalated to around $20 million after early environmental risks were not resolved before commitment, contractor termination and legal costs followed, and design changes were introduced under delivery pressure.

This is the recognisable sequence: uncertainty accepted at approval, carried forward into delivery, and paid for at a multiple of the original estimate.
Similar escalation patterns are visible across major national infrastructure programs where uncertainty, interface complexity and delivery conditions were not fully resolved before commitment. Snowy 2.0 is one public example where evolving geotechnical conditions and delivery complexity materially changed cost and delivery assumptions after approval.
Cost of doing nothing
Unresolved uncertainty does not diminish between approval cycles. Without structural change to how projects are committed, each program year carries the same exposure — accumulating in overruns, contingency draw-downs, and scope reductions that constrain what the organisation can deliver.
Over three years without structural change, the same exposure repeats — compounding unplanned expenditure, program disruption, audit risk and reduced delivery capacity.
All figures are illustrative, not benchmarks. They are a way to test whether the pattern and its cost are present in your environment.

The overrun shows up in delivery. The cost was locked in at approval.

The recurring sequence

Cost escalation follows a recognisable governance pattern.

When infrastructure overruns are examined closely, the same structural sequence appears repeatedly — regardless of project size, sector or delivery model.

  • 1 Projects are approved before key assumptions are tested against delivery reality.
  • 2 Risk and assurance processes inform decisions but do not stop commitment when uncertainty remains material.
  • 3 Contracts, procurement pathways and delivery commitments become locked in before the cost of change is fully understood.
  • 4 Scrutiny increases only after variance becomes financially visible — when the opportunity to unwind the original decision has largely passed.

Cost escalation is rarely just a delivery problem. In most infrastructure environments, it is the downstream result of how commitment, authority and uncertainty are structured before delivery begins.

XD Thinking™ focuses on the governance conditions underneath these sequences before escalation becomes operationally irreversible.
What Most Organisations Try First

Why normal controls fail to stop escalation

More reporting and variance analysis

Improves visibility after escalation occurs. It does not change the decisions that created the exposure, nor show what needs to change.

Stronger assurance after commitment

Provides oversight once risk is already embedded. It does not stop commitment when uncertainty remains material.

Tighter procurement controls

Acts at contract stage. Cost escalation often begins earlier, before procurement is engaged.

More contingency

Turns contingency into a buffer for unresolved uncertainty instead of a controlled response to defined risk.

These responses improve oversight. They do not change when or how commitment becomes binding.

What XD Thinking™ Changes

What becomes possible when commitment is governed earlier

Exposure is visible before commitment

Cost, uncertainty and delivery conditions are surfaced before obligations harden into contracts, scope or public commitments.

Evidence thresholds are explicit

Commitment depends on defined evidence, authority and readiness conditions — not confidence alone.

Contingency is preserved and controlled

Contingency is used against defined risk, not drawn down early to absorb uncertainty that should have been resolved.

Escalation occurs before cost locks in

Material changes trigger formal review while options still exist, not after variance is already financially visible.

This is not about removing all risk. It is about controlling when exposure becomes irreversible.

Next step Before the next overrun becomes unavoidable If this pattern is familiar, the issue is rarely isolated to estimating or delivery performance alone. In most organisations, escalation begins earlier — when uncertainty, authority and commitment timing drift out of alignment.

The earlier this becomes visible, the more options still exist. Discuss Your Situation or Check Your Cost Escalation Risk A 5-minute capital program stress test. No commitment. Results shown immediately.