Inside Construction Delivery: Lessons from major infrastructure projects: What every project team should know

  • Opinion

    16 June 2026

Inside Construction Delivery: Lessons from major infrastructure projects: What every project team should know Desktop Image Inside Construction Delivery: Lessons from major infrastructure projects: What every project team should know Mobile Image

Major infrastructure projects are among the most complex commercial undertakings in any market. They involve multiple parties, significant capital, long delivery timeframes, and an inevitable degree of uncertainty. While every project is different, the same patterns of underperformance, dispute, and avoidable cost recur across distressed projects. These outcomes typically reflect predictable issues with how project teams prepare, communicate, administer their contracts, and respond when issues arise.

Across this series, those themes have been explored individually. This final article draws them together. Rather than revisiting each topic in isolation, it focuses on what consistently separates projects that perform well from those that don’t when these factors interact in live delivery. Project delivery  pressure-tests whether a project team’s systems, behaviours, and assumptions can hold under strain. Where they can’t, relatively minor issues tend to compound into material consequences.

The contract is not a reference document but a live management tool

On most distressed projects, contract administration is underestimated as a discipline. It is often treated as a compliance exercise – forms filled, notices sent, boxes ticked – rather than as the primary mechanism for managing commercial risk in real time. That distinction matters. The contract does not pause during delivery. Rights are lost through inaction. Obligations not enforced early become difficult to enforce later. Information gaps and incomplete records cannot reliably be reconstructed.

Project teams should treat the contract as an active commercial management system. That requires a clear understanding of key rights and obligations, how core processes operate (variations, EOTs, payment), and ensuring those administering them have both the capability and authority to act. Treating contract administration as a commercial discipline, rather than a clerical one, is one of the highest-return investments a project team can make.

These disciplines only work if they are embedded early and they are often the first things to break down when pressure builds.

Set the tone early: The first phase sets the operating conditions

The issues that cause the most damage later in delivery almost always originate early. Misunderstood risk allocation, unresolved scope, and weak documentation practices compound over time. Matters that could have been resolved in weeks become entrenched months later, when the factual record is incomplete and the cost of resolution is far higher.

Common examples include:

  • Failing to clearly identify the interface and any scope-gap between designers and/or between principal design and design & build elements in the contract documents. This invariably gives rise to additional cost and time and can quickly escalate into formal disputes and relationship breakdowns. 
  • Failing to keep accurate, unambiguous and complete meeting minutes and project records during delivery. This often leads to things being missed and miscommunications between project participants. Vague and/or incomplete project records also commonly creates uncertainty and risk in formal disputes where decision makers are ever focussed on the contemporaneous record. 

The early phase is where the project actually establishes how it will operate: communication, escalation, record keeping, programme management, variation processes, and documentation standards. This is not process for its own sake. It creates the clarity and discipline needed to deal with issues as they arise.

A practical delivery strategy, agreed before delivery begins, effectively sets the project’s operating conditions. Expectations around commercial management, behaviour, and escalation are much harder to establish once pressure builds. When the foundations are weak, delivery exposes it quickly.

Behaviour under pressure determines outcomes

Behaviour under pressure, particularly how people communicate, escalate issues, and make decisions has a significant impact on whether disputes arise and how severe they become.

Communication gaps, unclear authority, overconfidence in one’s position, and reluctance to escalate early are recurring contributors to disputes. Over time, this leads to informal practices, loss of discipline, and erosion of trust.

Project leads can mitigate this by:

  • creating an environment where raising issues (and acknowledging mistakes) early is required;
  • managing risk objectively and bringing in specialist input where needed; and
  • ensuring clear and consistent communication across the project.
Know what a distressed project looks like before it becomes one

When commercial pressure hits, behaviour changes. The patterns are predictable: increased claim volumes, shifting delay narratives, arguments over risk allocation, and more positional negotiation. These behaviours are often rational responses to pressure. They are also the point at which the project is being pressure-tested in real time.

A project’s commercial position can shift quickly. Counterparties that previously collaborated well may adopt more adversarial positions as losses emerge. Goodwill can dissipate faster than most teams expect. While some disputes are unavoidable, they can often be managed effectively through:

  • strong programme governance;
  • robust contemporaneous records; and
  • consistent, disciplined contract administration.

These are the same disciplines established early in the project and this is where they either hold or fall away. Maintaining a clear separation between entitlement and relationship management is also critical. Blurring the two tends to produce inconsistent positions and avoidable risk.

Managing claims is a discipline, not just a response

Claims are a normal feature of major projects. Some are well-founded; others reflect commercial pressure rather than clear entitlement. Understanding that distinction matters. A common pattern is that parties adopt positions early for tactical reasons, then become commercially or reputationally committed to them, even where the underlying entitlement is weak. Effective claims management requires more than process. It requires:

  • honest assessment of factual and contractual foundation;
  • clear separation of entitlement and quantum; and
  • measured analysis that prioritises accuracy over speed.

Poor early assessments often create positions that are difficult to unwind.

Teams also need to actively manage their own claims. Legitimate entitlements must be identified early, properly notified, and supported by contemporaneous evidence. Entitlements that are real but poorly evidenced can be just as difficult to recover as those never raised.

What good looks like

Across the series, the practices most consistently associated with well-performing projects are:

  • Discipline
    • Treat the contract as an active management tool
    • Maintain strong documentation from day one
    • Approach claims with structure, evidence, and rigour
  • Clarity
    • Establish delivery strategy and communication protocols early
    • Understand how programme, risk allocation, and obligations interact
    • Revisit that understanding as the project evolves
  • Behaviour under pressure
    • Align contractual discipline with relationship management
    • Create a culture of early escalation
    • Anticipate how behaviours will shift under commercial strain
Conclusion

The lessons from major infrastructure projects are consistent. They do not require complex systems or specialist capability beyond what experienced teams already have. They require early attention, sustained discipline, and a willingness to manage commercial and behavioural risk with the same rigour as technical delivery.

Project directors and managers sit at the centre of these pressures. Their role is not just to report on programme or facilitate process, but to create the conditions in which the team can respond effectively as challenges arise. What makes these lessons notable is not their novelty, but their consistency. The same patterns emerge across projects. That consistency means outcomes are more controllable than they often appear. Projects can but often don’t fail because of a single issue, they underperform when smaller issues are left unresolved and then tested under pressure.

Applied early and maintained throughout delivery, that discipline is one of the clearest predictors of projects that remain on track commercially, contractually, and relationally.

Read more from the Inside Construction Delivery series