Rollercoaster Budget: The Ups, Downs, and Loop-the-Loops of Infrastructure Spending
Fasten your seatbelts. The infrastructure budget rarely travels in a straight line.
They climb during business-case development, pause at the top while everyone admires the approved funding envelope, and then plunge when design, procurement and delivery introduce themselves. Somewhere along the route come a few sharp bends, an unexpected tunnel, a change-order corkscrew and the inevitable budget inflation loop-the-loop.
Unlike a theme-park ride, nobody queues willingly for this experience. At the end, there is usually only a revised forecast and an estimator being asked why the number has “changed again”.
Infrastructure budgets do not usually become unstable because arithmetic stopped working. They move because the project is moving: scope develops, assumptions expire, risks materialise, markets change, and decisions arrive late. What looked like a firm number was often an early estimate, wearing a suit and pretending to be a commitment.
The Budget Initial Climb: When Everything Still Looks Affordable
Every rollercoaster begins with a reassuring climb.
At the earliest stage of a project, the concept is clean, the drawings are limited and edited, and the delivery narrative is wonderfully uncomplicated. The route is clear. Ground conditions are described as “typical”. Existing utilities are assumed to be somewhere else. Access appears straightforward. Stakeholders are supportive—at least the three who have been consulted.
The estimate is prepared from incomplete information, often under pressure to fit a business case or funding limit. A single figure is extracted from a much wider range of outcomes and soon appears in presentations, investment papers and public announcements.
The problem is not that an early estimate contains uncertainty. That is unavoidable. The problem begins when the uncertainty disappears from the conversation, but the number remains.
HM Treasury guidance recognises optimism bias as a systematic tendency to underestimate project costs and duration or overestimate benefits. The answer is not simply to add a random percentage and hope for the best, but to make uncertainty explicit and use evidence from comparable projects. Government project-delivery guidance also recommends expressing uncertain early forecasts as ranges, with suitable provision for risk.
The Budget Surprise Dip: Scope and Design Maturity
Then comes the first drop.
The project team conducts surveys. The site is not as simple as expected. Utilities appear exactly where the foundations need to go. Environmental commitments become design requirements. Temporary works grow from a footnote into a significant package. Access restrictions affect productivity. The “minor interface” turns out to involve three asset owners and a possession strategy.
None of this necessarily means that the original estimator failed. It may mean that the project now knows more than it did before.
As design develops, quantities become clearer, construction methods become more realistic, and exclusions are challenged. Yet organisations often describe every movement as a “cost increase” without distinguishing between the following:
- a genuine rise in the price of delivering the same scope;
- the discovery of a scope that was always required but not previously understood;
- The addition or enhancement of scope after the original estimate.
These are not interchangeable. Placing them in one large bucket labelled “overrun” destroys the audit trail and teaches the organisation very little.
The Change-Order Chaos Car
When the track seems to level out, the changes arrive.
Some are unavoidable: safety requirements evolve, site conditions demand a different solution, or a stakeholder identifies a legitimate need. Others are less heroic—late preferences, unresolved decisions or the rediscovery of excluded scope.
Each change carries more than its visible direct cost. It can affect design, procurement, logistics, sequencing, testing and commissioning. After a contract award, it may also bring disruption, prolongation, and commercial consequences.
This is why change control cannot be reduced to updating a spreadsheet after a meeting. It must establish what changed, why it changed, who authorised it, which assumptions are affected, and what the time, risk and commercial consequences may be.
Without that discipline, the budget becomes a passenger rather than a control mechanism.
The Loop-the-Loop of Inflation and Escalation
Inflation is one of the most familiar villains in infrastructure budgeting, but it is often treated too casually.
Published indices can move historical costs to a common price base. That is useful, but it does not automatically predict what a particular project will experience. Labour availability, energy prices, commodities, manufacturing capacity, regional demand, exchange rates and tender appetite can all affect outturn cost.
Long programmes are especially exposed because packages are procured at different times. If the base date, current price, forecast escalation, and outturn price are conflated, apparently similar figures may represent entirely different points on the ride.
Escalation, therefore, needs an explicit methodology, stated dates, appropriate indices and scenario testing. It should not be an invisible formula hidden in the final tab of a workbook maintained by the only person who understands it.
The Supply-Chain Corkscrew
Even a well-developed estimate can be thrown sideways by the market.
Infrastructure projects compete for specialist labour, plant, materials, manufacturing slots and competent suppliers. A programme may be technically feasible but commercially difficult because several projects need the same resources at the same time.
The cheapest theoretical construction method is not always the most deliverable one. Historic benchmarks may need adjustment where the supply chain is constrained, the geography is difficult, the programme is compressed, or the packaging strategy transfers risk inefficiently.
Market engagement is, therefore, part of cost intelligence. A model developed without understanding how the work will be bought and delivered is an elegant description of an imaginary project.
The Schedule-and-Cost Helix
Time and cost are not separate rides.
A delay can extend overheads, design resources, supervision, plant hire and traffic management. It can move procurement into an unfavourable market window. Acceleration can also be expensive, requiring extra shifts, parallel working or premium logistics.
Yet schedules are sometimes developed independently from estimates, as though the programme can slip while the budget remains politely stationary.
A credible estimate must be connected to a credible schedule—the timing of procurement, expenditure and risk matters.
Cash flow is not simply the total cost divided by the number of project years; it is the financial expression of the delivery strategy.
Contingency Is a Safety Bar, Not a Magic Wand
Every rollercoaster has restraints. Infrastructure projects have contingency—or at least they should.
But contingency is often misunderstood. It is not a decorative percentage added to make executives feel safer. Nor is it spare money for additional scope, known costs that nobody wanted to show, or design development that should already have been included.
A useful contingency assessment should be linked to uncertainty and risk. It should reflect scope maturity, data quality, interfaces and the organisation’s chosen confidence level. It should also be reviewed as the project changes.
Most importantly, contingency does not compensate for poor estimating.
Adding 20 per cent to a weak model produces a weak model with a larger total.
How to Make the Ride Less Terrifying
Infrastructure budgets will never be perfectly flat. The goal is not to eliminate movement but to make it explainable, controlled and proportionate.
A stronger approach starts with a clear Basis of Estimate recording:
- scope and design maturity;
- assumptions and exclusions;
- quantities and rates;
- price base and escalation methodology;
- construction and procurement strategy;
- programme assumptions;
- risk and contingency treatment;
- responsibilities and approval status.
The estimate should use ranges where knowledge is limited and narrow them as the evidence improves. It should separate base cost, risk, contingency, escalation and scope change so decision-makers can understand why the forecast is moving.
Historical data and benchmarking are valuable only when normalised for scope, location, time, procurement route and complexity. A £/m², £/km or £/asset benchmark may look reassuringly scientific, but it is only useful when the comparison is genuinely comparable.
An independent review should test the logic, not merely recalculate the total. A spreadsheet can be arithmetically correct while the scope, assumptions, quantities and delivery strategy behind it are fundamentally wrong.
Early collaboration should also bring delivery disciplines together before the project is committed to a headline number. Estimators need information from designers, planners, procurement specialists, operators, risk managers and construction teams. Cost planning is not a solo performance conducted after everybody else has made the important decisions.
The Infrastructure and Projects Authority’s cost-estimating guidance describes the need for estimates that are robust, transparent and assured, enabling better project decisions. That is the real objective: not a number that never changes, but a forecast whose movement can be traced, challenged and understood.
Budget Reporting Without the Theatre
Clear reporting also matters.
A budget update should not simply announce that the forecast has risen by £20 million. It should explain the movement.
How much resulted from inflation? How much came from scope development? What was caused by an approved change? Which risks materialised? Has contingency been drawn down? Has the completion date moved? Are there new assumptions that could affect the next forecast?
Without this breakdown, every change appears to be an estimating failure. With it, decision-makers can distinguish genuine cost pressure from better information, changed requirements and deliberate investment decisions.
Budget reporting should not be designed to defend yesterday’s numbers. It should help the project make better decisions today.
Final Stop: Budget Confidence, Not Budget Theatre
The metaphor feels familiar because budgets rise, fall and occasionally appear to defy gravity. The ride becomes dangerous when uncertainty is hidden, scope movement is poorly controlled, and early estimates are presented as promises.
A changing estimate is not automatically evidence of failure.
An unexplained estimate is.
Projects need fewer theatrical declarations that “the budget is fixed” and more disciplined conversations about what the budget includes, what it excludes, how mature it is, what could move it and who owns the decisions behind it.
So fasten the safety bar, keep the Basis of Estimate nearby and resist treating every early number as the final fare.
Infrastructure delivery may always contain twists and turns. Good cost planning ensures that, even when the project enters a loop-the-loop, everyone knows why—and nobody has to pretend it was a straight track all along.
