When Utilities Coordination Breaks: How We Prevented 8 Week Schedule Slippage

The Newington Green project almost slipped 8 weeks because Thames Water's sewer relocation timeline ran in parralel with our main delivery schedule instead of ahead of it. This is how we fixed it. The specific coordination failure that nearly cost the programme 8 weeks and £2.8M is a case study in why utilities coordination has to be treated as a first-order delivery problem, not a background task.

The Problem: Standard Coordination Wasn't Working

Thames Water had committed to a major sewer relocation that affected the entire pedestrianisation scheme. The original programme assumed Thames Water would complete the relocation on a schedule that ran concurrently with our main civils works. That assumption was wrong. Thames Water's internal approval and mobilisation timelines were operating independently of our programme schedule. By the time we identified the misalignment, the risk had already propagated into the critical path.

The standard coordination approach, monthly progress meetings and email updates, wasn't producing the visibility we needed. Thames Water's delivery team was managing their programme internally without integration into ours. We were receiving status updates that described activity, not outcomes. The distinction matters. Activity updates tell you what someone is doing. Outcome updates tell you whether the programme is on track.

The Approach: Embedded Governance

We changed the coordination model. Instead of running parallel programmes with occasional touchpoints, we embedded Thames Water's delivery team in our weekly governance meetings. This wasn't a meeting addition. It was a governance restructure. Thames Water's critical path items became visible as constraints on our programme, not as external dependencies managed by someone else.

We also created a utility coordination protocol that explicitly mapped Thames Water's mobilisation sequence against our construction phases. Each phase had a Thames Water dependency identified, with a lead time requirement and an escalation trigger. If Thames Water's progress fell below the lead time threshold, the escalation protocol activated automatically. No manual monitoring required.

Negotiating Accelerated Timelines

The permit acceleration process required direct engagement with Thames Water's permit team, not just their project management function. We identified the specific approval bottlenecks in their internal process and worked with them to compress the timeline through pre-submission consultation. Pre-submission consultation means engaging with the approval body before formal submission to identify and resolve issues that would otherwise delay approval.

The result was a Thames Water relocation completed 4 weeks ahead of the original critical path, with zero schedule impacts to the main civils works. The 8-week risk became a 4-week benefit. That 12-week swing was the difference between a programme that delivered on schedule and one that would have required a contract extension.

Lessons for Multi-Stakeholder Coordination

The lesson from the Newington Green utilities coordination failure and recovery is that parallel programme management doesn't work when stakeholders have genuine interdependencies. Interdependent programmes need shared governance, shared visibility, and shared accountability for critical path outcomes. Embedded coordination is the governance mechanism that creates that shared accountability.

This approach applies directly to customer success management in infrastructure. When a client's implementation depends on a third-party vendor delivering a specific component on schedule, the customer success manager can't manage that dependency through status updates. They need embedded visibility into the vendor's programme and a coordination protocol that surfaces schedule risks before they cascade. The Newington Green documentation at olamapped.com/newington-green-programme shows the full utilities coordination framework.