Britain’s £924bn Project Portfolio: Is ‘On Budget’ the Wrong Test?

The number that deserves a better question

Britain’s project leaders should be asking a more demanding question than whether the latest dashboard remains within tolerance. What, exactly, will the country receive for its investment? NISTA’s July 2026 annual report records £924.2 billion in whole-life costs across 189 government major projects at 31 March 2026. Within that portfolio, infrastructure and construction account for 68 projects and £450.0 billion. These are substantial commitments, but precision matters: the figures use 2024/25 real prices and describe costs over project lifetimes, not one year’s spending or money lost. The delivery-confidence snapshot records 29 green, 109 amber, 34 red and 17 exempt projects. Red signals serious delivery concerns; it is not a verdict that a project has failed. Nor does amber make failure inevitable. NISTA’s report provides a reason for sharper scrutiny, rather than a licence for theatrical arithmetic.

For a senior project manager, a council chief executive or the head of project controls in a major contractor, the uncomfortable point is this: a programme can look financially orderly while its intended value becomes steadily harder to realise. A revised scope may protect the approved budget while reducing useful capacity. A successful handover may leave an operating organisation without the people, systems or funding needed to use the asset properly. These are illustrative governance risks, not allegations about the projects in NISTA’s portfolio. They explain why a board should examine the relationship between expenditure, delivery and operational outcomes. Cost discipline remains indispensable. It becomes more valuable when it helps decision-makers protect the purpose of the investment as well as the financial envelope.

What recent research adds to the boardroom

A November 2025 paper by Zhiwen Zheng and Ofer Zwikael in the International Journal of Project Management gives this debate an empirical foundation. The authors examined a survey of 198 US projects and an analysis of 154 World Bank projects. Their reported findings suggest that a minimum level of project-management success is necessary, but insufficient, for long-term success. Quality required a higher threshold than cost or schedule: some delay or overspend could coexist with eventual success, whereas serious defects in the outputs were much less compatible with it. That is a useful challenge to budget-only assessments, not permission to excuse overruns. The research is not a UK infrastructure experiment, and it does not establish a universal acceptable overspend. This commentary draws on the authors’ published abstract and bibliographic record; the paper is available through its DOI.

My practical interpretation is that every proposed saving should carry an explicit account of what changes for the eventual user. Imagine a council considering a cheaper specification for a public building. The decision paper should explain the effect on accessibility, service capacity, running costs and maintenance, alongside the capital saving. For an oil and gas operator or an energy developer, the equivalent questions concern safe commissioning, reliability, operability and the resources required to maintain performance. These examples are prompts for analysis, not calculated business cases. The principle is straightforward: the project director should be able to explain whether the saving removes waste, transfers cost into operations or weakens the outcome the sponsor originally intended. A lower outturn is valuable when the associated trade-off is understood and justified.

Government practice is moving towards a more usable conversation about outcomes. On 30 July 2026, Government Project Delivery released its benefits management collection, bringing together a senior-leader guide, a practitioner workbook, templates and government case studies. Its significance for industry is practical: public clients and their delivery partners have a shared starting point for identifying and tracking benefits. My recommendation is to take one live investment and put its operating owner in the next controls meeting. Ask that person to confirm the measure of success, the starting position, the dependencies and the date on which improvement should become visible. This makes benefits realisation a current management responsibility, rather than a retrospective narrative assembled after completion.

The changes I would ask project leaders to make

First, bring cost, schedule, risk, quality and benefits into the same decision paper. The original approved baseline should remain visible alongside the current authorised baseline and the latest forecast, with material changes explained. A single headline variance can conceal changes in scope or assumptions even when everyone is acting properly. Each significant benefit should have a named owner, an evidence source and a review date. Each major quality requirement should connect to the capability the asset must provide. For consultancies, this is an opportunity to strengthen the advice accompanying a report: explain what a forecast means for the client’s choices and the consequences of waiting. For contractors, it creates a clearer basis for discussing change with the client before expectations diverge.

Second, make every material early warning lead to a decision. Government Project Delivery’s April announcement on GRIP describes a more consistent approach to major-project data and its use across government. Better data should help teams compare, interpret and reuse information. My implication for project controls is that an alert still needs an accountable person: who will investigate, what evidence is missing, what decision is due, and by when? AI in project controls may help identify an unusual movement or draft an explanation, but it cannot establish the truth of an unverified input or take responsibility for an investment decision. Use automation to give professionals more time to challenge assumptions and resolve issues. Measure whether action followed, rather than merely counting the alerts generated.

Third, protect the period after handover. A construction milestone and an operational benefit rarely arrive at exactly the same moment. Agree who will observe performance after the delivery team reduces its involvement, who can correct emerging problems and how the sponsor will hear about them. Councils can make this concrete through service availability, user experience and operating expenditure. Infrastructure owners can use capacity, reliability and commissioning performance. The right measures depend on the business case; an impressive list of indicators is no substitute for an agreed decision. In the next reporting cycle, I would ask each project team to identify one unresolved assumption that could materially change the value of its project, give it an owner and set a date for testing it.

A more confident prospect for British delivery

There is a constructive opportunity here. Britain’s public clients, engineering businesses and project professionals can use the current focus on delivery to make their reporting more useful and their decisions more accountable. Better project controls need not mean another layer of paperwork. They can mean a clearer explanation of the choices, a reliable record of what changed and an earlier conversation with the people who will use the result. Being on budget is an achievement worth pursuing. Knowing that the investment will also work, serve its users and retain its intended value is a stronger ambition still. That is a standard worth building towards, and one that capable project leaders can begin advancing in their very next meeting.