Call

Benefits Realisation Frameworks for Regional Infrastructure Projects

Business cases open with confident numbers; two years later, almost nobody checks whether any of it happened. That is close to the norm, and 'we'll assess the benefits later' should be treated as a planning risk, not an administrative afterthought.

By Dr Tony Irish, CA Business Valuation Specialist 26 August 2026 · 5 min

A regional council opens a new bypass, health precinct, or irrigation upgrade with a business case full of confident numbers: trip-time savings, jobs created, hectares unlocked. Two years later, almost nobody checks whether any of it happened. This is not a hypothetical failure of a few unlucky projects; it is close to the norm, and the evidence for why is now strong enough that “we’ll assess the benefits later” should be treated as a planning risk, not an administrative afterthought.

Ex-ante forecasts and ex-post reality rarely match

The gap between what a business case promises and what a project delivers has been documented for decades. Bent Flyvbjerg’s research (spanning more than 16,000 projects across 20-plus sectors and 136 countries) finds roughly nine in ten large infrastructure projects run over budget, and benefit shortfalls above 50% are not unusual; only around 0.5% of projects come in on budget, on time, and deliver the promised benefits. Optimism bias at the forecasting stage, not just poor construction management, is a primary driver.

Australian data tells the same story. Grattan Institute’s analysis of every transport project over $20 million since 2001 found actual costs exceeded promised costs by 24%, with 90% of the total overrun explained by just 17% of projects that blew their budget by more than half. A later Grattan update found billion-dollar “megaprojects” overran initial cost estimates by 30% on average, and Infrastructure Australia’s own national risk study attributes over a third of transport cost overruns since 2001 to just seven megaprojects that “overestimated benefits and underestimated costs due to optimism bias and project complexity.”

Auditors find the same gap on the assurance side. The Victorian Auditor-General found the Department of Treasury and Finance had claimed at least $1 billion in savings from its Gateway Review Process but “cannot demonstrate that these benefits were reliably measured,” and that no project had completed the full suite of Gateway reviews since the process began in 2003. The ANAO reached a similar conclusion on Commonwealth programs: its audit of the $150 million Streamlined Grants Administration hubs found “insufficient evidence” the promised $400 million in annual savings had materialised, with only one of four key deliverables achieved.

Forecast and outcome are, more often than not, different documents.

Best-practice frameworks already exist: they are just under-used

Australia does not lack the architecture for benefits realisation; it lacks follow-through. Infrastructure Australia’s five-stage Assessment Framework builds benefits tracking in from the start: Stage 3 requires a Benefits Realisation Plan setting out how benefits will be measured as the project proceeds, and Stage 4 requires a Post Completion Review (PCR) demonstrating “whether it delivered the benefits described in the project’s business case.”

The Gateway Review model, imported from the UK and standard across Australian jurisdictions, is designed to make benefits a governance gate, not a retrospective afterthought. NSW’s Gate 6 (Benefits Realisation) is mandatory for capital projects over $10 million and must be completed six to twelve months after operations begin, testing delivery against the state’s Benefits Realisation Management Framework. Victoria’s DTF runs an equivalent six-gate process, with Gate 6 dedicated to benefits analysis, though VAGO found the department had never systematically measured whether the process improved outcomes.

The Managing Successful Programmes (MSP) framework fills the methodological gap these gates assume exists: its benefit profile requires a description of the benefit, the observable outcomes indicating it occurred, clear attribution of who owns it in business-as-usual, and a defined measurement approach and timing. This is the missing link between a business case’s benefit claim and a review’s benefit evidence, built before approval rather than reconstructed afterwards from memory.

Practical benefits register: minimum fields for a business case

  • Benefit description: plain-language statement of the improvement, tied to a specific business case claim.
  • Owner: the named role (not agency) accountable for realising and reporting the benefit post-completion.
  • Measure / KPI: the specific metric, with data source identified.
  • Baseline: the pre-project value, captured before construction begins.
  • Target: the forecast value from the business case, with the underlying assumption stated.
  • Timing: when the benefit is expected to materialise (rarely at opening; often 1–3 years post-completion).
  • Dependencies: other projects, policy changes, or behavioural shifts the benefit relies on.

Why post-completion evaluation usually doesn’t happen, and why regional projects can least afford to skip it

The incentive structure works against follow-through. Funding is exhausted at completion, the project team disbands, and the political reward for evaluation is close to zero: nobody gets credit for confirming an old promise, and there is real downside risk in confirming it fell short. Infrastructure Australia’s Stage 4 process is effectively voluntary for most projects below its threshold, and Victoria shows even a mandatory gate can go unused. No project had completed its full six-gate cycle by the time of the 2013 VAGO audit.

Regional projects have the least margin to absorb this gap. Budgets are smaller relative to fixed review costs, so skipping evaluation looks cheap in isolation. But regional infrastructure is more often one link in a long-run strategy (freight corridor, health network, water security plan), where a benefit shortfall quietly undermines the case for the next project. Commonwealth policy now recognises this risk: the 2021 Commonwealth Evaluation Policy and the newer Australian Centre for Evaluation aim to embed evaluation planning into funding proposals from the outset.

SED’s role

SED Advisory has spent nearly three decades building investment and business cases for regional Australia, and builds the benefits register into the business case itself, not as a compliance exhibit but as the same document used for the post-completion review years later. Where a regional proponent needs independent Stage 4 or Gate 6 evidence they can defend to Treasury or Infrastructure Australia, SED delivers the post-completion evaluation to the same standard. If your project needs a benefits framework that will still hold up at review, get in touch with SED Advisory.

Sources cited

About the author

Dr Tony Irish is a director of SED Regional Advisory. He is a Chartered Accountant, holds a PhD in regional economic development, and is accredited as a CA Business Valuation Specialist by Chartered Accountants Australia and New Zealand.

Read more about Tony → · Start a conversation →

Have a project that needs to stand up to scrutiny?

Bring us the decision and we'll scope the evidence it needs.

Start a conversation