The Week That Was: There's Nothing Like a War to Scare the Horses
Back to Insights
The Week That Was

The Week That Was: There's Nothing Like a War to Scare the Horses

There are weeks where the industry concerns itself with pipeline sequencing, procurement reform, productivity gains and the steady, almost procedural rhythm of nothing happening — and then there are weeks like this one, where all of that dissolves into the background and something more instinctive takes over, where the conversation sharpens, contracts, and returns to fundamentals: cost, risk, and the uncomfortable awareness that the conditions underpinning delivery are shifting again. This week, the contractors awoke from their sleep.

Because while one of many conflicts sits geographically distant in Iran, its influence on infrastructure is now anything but distant; it is immediate, mechanical and working its way through the system with a familiarity that the industry has seen before, even if it would prefer not to acknowledge it.

Oil moves first. Then diesel. Then freight. Then materials. Then contractor and subcontractor risk pricing. And finally — inevitably — contractual stress.

And once it begins, it does not move in isolation; it cascades. It's like termites — it eats everything from the inside out.

What is most telling about weeks like this is not what appears in the headlines, but what changes underneath them.

You see it in the way conversations with contractors become suddenly shorter, the way the ringtone sounds in your ear when the subbie's name flashes up. It's in the way confidence becomes conditional and in the way suppliers begin to introduce a newly created language that wasn't there even a fortnight ago. It's not because they are reacting to a known outcome, but because they are positioning themselves against a risk they cannot yet fully define — a risk that the client will need to find money to pay for, or another reason to create delay, uncertainty and an overarching lack of progress.

Contractors — particularly subcontractors — price uncertainty, and they love it. It's a safe space, creating noise, disruption and confusion. It's a professional QS's holy grail.

And right now, uncertainty is re-entering the system in a big way that is both rapid and difficult to quantify: energy inputs are volatile and exposed, freight routes are under scrutiny, programme durations are becoming less predictable, insurance and financing conditions are tightening, and supply chain reliability is once again being questioned.

And when that happens, pricing does not simply increase — it evolves. Margins widen. Contingencies grow, and assumptions multiply. Or in some cases, the market simply pauses.

Because the greatest commercial risk in this environment is not being expensive — it is being wrong. It's a project manager's nightmare.

For some time now, the industry has treated cost escalation as a technical issue, something that can be understood through indices, benchmarked against historic data, and managed through structured commercial mechanisms, and now we have another dynamic to contend with. Something new that sits outside of that framework.

This is not escalation in the traditional sense but is actually behavioural pricing under uncertainty and it presents differently: subcontractors reducing the validity of their pricing, suppliers pushing risk upstream through exclusions and qualifications, packages being delayed, restructured or selectively released, early works becoming more attractive than full contractual commitment, and lump sum models becoming increasingly exposed.

What is often interpreted as a cost increase is, in reality, a live reallocation of risk across the supply chain and it is this distinction that matters.

This is now all too familiar — we saw it through COVID and through the impacts of the war in Ukraine and now, we are watching it re-establish itself once more. This time, it is layering into a market already carrying structural pressure.

Which leads to a more confronting question than most procurement strategies aren't currently set up to answer: are projects still being priced for delivery — or are they now being priced for protection?

For projects currently moving through planning, procurement or early delivery, this is not an abstract consideration — it is immediate, as these are the phases where assumptions are being formed, risk is fluid and where there is often a tendency to proceed on the basis that conditions will stabilise.

The projects that will navigate this phase successfully will not be those that attempt to preserve yesterday's commercial structures in today's conditions; they will be those that adapt early, and deliberately, to how the market is actually behaving.

That means: establishing a known position early, where assumptions, risks and interfaces are explicitly defined and agreed; structuring early works packages to create momentum while limiting exposure to broader uncertainty; selecting delivery models that enable risk to be understood and managed collaboratively, rather than simply transferred; engaging the market continuously, not episodically; and building real-time cost and risk intelligence that reflects current behaviour, not historic data.

In moments like this, the distinction between projects that hold together and those that drift is rarely about technical capability but about clarity.

Increasingly, the value sits with those who can interpret what the market is doing beneath the surface — who can translate shifting behaviours into defensible strategies, and who can support decisions that remain robust even as conditions continue to move.

There's nothing like a war to scare the horses.

But the real question is not whether they react — it is how the system responds to that reaction.

Because in infrastructure, outcomes are rarely defined by the shock itself. They are defined by what happens next.