Article
Why smart water meter rollouts lose momentum at scale – and how to prevent it
Summary
Large-scale smart water meter rollouts rarely slow down because installation is inherently difficult. They slow down when the complexity behind scale is underestimated. This article explains the main challenges water companies face as programmes move from procurement into live delivery, and why protecting pace depends on proven technology, stakeholder readiness, continuous feedback and delivery models built to absorb change.
Understanding the delivery challenge at scale
Smart water metering is moving quickly across AMP8. Water companies are under pressure to improve leakage performance, support demand management and strengthen visibility across their networks, all while mobilising large infrastructure programmes at pace.
From my perspective, the biggest delivery risks do not usually appear on paper during procurement. They appear when a programme moves into reality. That is when assumptions are tested, internal teams begin to engage more closely, field conditions become more varied, and the difference between a pilot and a scalable solution becomes clear.
Large-scale rollout is not just an installation challenge. It is a programme challenge. That means technology, governance, stakeholder readiness, performance management and partner coordination all need to work together if pace is going to hold as volume increases.
In this article, I want to explain the main challenges I see in large-scale smart water meter rollout, and why getting delivery right depends on much more than installation capacity alone.
Smart water meter rollouts slow down when programmes are designed for pilots, not for scale
One of the most common risks in smart water metering is selecting technology that performs well in a pilot, but struggles once rollout reaches more difficult environments.
At a small scale, many solutions can look effective. The real test comes later, when programmes move beyond the easiest installations and into basements, hard-to-reach properties, dense urban areas, rural locations and mixed geographies. That is where performance ceilings start to appear.
The question is not simply whether the technology works. It is whether it can scale to the full requirement of the programme.
That means working backwards from the end goal. Water companies need to understand not just how many meters they want to install, but what connectivity rates, data performance levels and success rates they expect across the hardest parts of the estate as well as the easiest.
If that thinking does not happen early, programmes can end up heavily invested in a technology before discovering that performance cannot move beyond a certain point. That is exactly the kind of avoidable mistake large programmes need to protect against.
Evidence matters more than novelty
For rollouts to succeed, technology selection needs to be built around evidence. In practice, that means asking:
- Has the solution been deployed at a meaningful scale?
- Has it been used in environments similar to the target geography?
- Is the technology proven, or is it still too close to the bleeding edge?
- Does it create resilience, or lock the programme into one supplier approach?
The fact is, there is also no single solution that suits every water company. Different environments create different technical demands, and some programmes may require a combination of approaches rather than one uniform answer. The goal is not to buy the most interesting technology. It is to buy the most suitable one.
Read more: For smart metering to succeed, water companies need to look beyond AMP8 – Tanya Dady
Rollout pace depends on aligning stakeholders, systems and ways of working early
Technology is only one part of the challenge. Large-scale rollout is also a people, process and systems integration exercise.
What often happens is that a water company runs procurement through a relatively focused internal team, sometimes supported by external advisers. The programme is defined, contracted and mobilised at pace. Then, once delivery becomes real, wider operational stakeholders start engaging more directly.
At that point, network teams, billing teams, customer teams and operational leaders may begin raising additional requirements or challenging assumptions that were not fully surfaced earlier. None of that is unreasonable. In fact, it is often exactly the right input. The problem is timing.
If those stakeholders are brought in too late, rollout can quickly lose momentum. Decisions may need to be revisited. Processes may need to change. Governance can become more complex. A programme that looked stable on paper can start to drift before it has built real pace.
That is why early stakeholder engagement is so important. The strongest programmes identify who carries influence, where integration points sit across the organisation, and what support is needed on both sides before delivery ramps up.
Structured mobilisation protects momentum
At Horizon Water Infrastructure, structured mobilisation is critical to how we work. Effective delivery demands:
- The right subject matter experts on both sides
- Clear governance and escalation routes
- Defined integration points across systems and teams
- A mobilisation methodology that can be adapted to each customer’s environment
The point of outsourcing is not to remove complexity. It is to place delivery risk with a partner better equipped to manage it. That only works, however, when the operating model, governance and relationships are set up properly from the start – which is exactly how our “do it once, do it right” approach works.
Delivery at scale only works when performance, change and improvement are built in from day one
Another lesson from large-scale rollout is that pace is not created simply by asking installation teams to do more.
Real pace comes from momentum. Momentum comes from confidence. And confidence comes from knowing, every day, whether performance is holding up as the programme scales.
That means delivery needs proving points. Water companies and delivery partners need to agree what “good” actually looks like, how it will be measured, and what evidence will show that the programme is ready to move into the next gear.
At programme level, that requires close monitoring of issues such as:
- Installs attempted
- Installs completed
- Failed installs and the reasons behind them
- Connectivity and network readiness
- Patterns in field conditions that may affect performance
The detail matters. If a meter cannot be installed because a boundary box is too shallow, for example, that needs to be captured accurately and consistently. Only then can teams analyse failure trends properly, identify what sits within their control, and work with the customer to remove wider constraints.
This is where daily and weekly feedback loops become so important. They allow programmes to improve continuously rather than waiting for problems to accumulate. Just as importantly, performance monitoring needs to stay ahead of rollout, because a programme can appear to be moving quickly while actually storing up later problems.
Change needs a delivery mechanism
Large infrastructure programmes always evolve once they move from procurement into live delivery. The challenge is not whether change will happen. It is whether the programme is structurally ready to absorb it.
That means putting mechanisms in place early to capture new requirements, assess impact, agree decisions, manage commercial consequences and keep delivery moving. Without that, relatively reasonable changes can destabilise the whole programme.
One practical example from our work on Southern Water’s smart meter upgrade programme illustrates the point. An early approach to meter replacement could have followed a relatively low-profile model, where teams simply arrived on the day and completed the replacement. Southern Water decided instead that customers should be engaged in advance through letters or emails, reflecting the importance of customer communication within the wider programme.
That change mattered operationally. It required communications processes, artwork approval, print and distribution capability, and system controls to make sure each step happened in the right order. Because the change was addressed quickly and built into the programme properly, it was accommodated without delaying rollout.
That is the difference between a programme that treats change as disruption and one that treats it as a normal condition of delivery.
Read more: Water Infrastructure: Why water companies need integrated advisory, delivery and funding
Strong partner ecosystems turn programme complexity into delivery momentum
Large-scale smart water metering is rarely delivered by one organisation acting alone.
Even where a prime contractor leads the programme, delivery still depends on a wider ecosystem of partners, specialists and platforms. That makes partner alignment a major delivery issue in its own right.
The strongest programmes build resilience by selecting partners with real expertise in their own domain, then creating enough transparency, trust and communication to surface issues early and solve them quickly.
That matters because the right partner ecosystem does more than provide capacity. It broadens capability. When delivery partners are aligned to outcomes, open about problems and able to contribute real subject matter expertise, programmes become stronger. Teams can draw on a much wider pool of knowledge, solve problems faster and optimise continuously as the rollout matures.
That is especially important in smart water programmes, where technical, operational and customer requirements intersect all the time.
Talk to Horizon Water Infrastructure about your smart water meter rollout
Ultimately, large-scale smart water metering is not a repetition exercise. It is a programme that combines technology selection, systems integration, stakeholder readiness, operational governance, continuous improvement and structured change. When that complexity is underestimated, rollout loses pace. When it is designed from day one, programmes become far more stable, scalable and resilient.
For water companies in AMP8, that distinction matters. The challenge is not just to mobilise quickly. It is to build a delivery model that can sustain performance as complexity increases.
At Horizon Water Infrastructure, that is what we focus on: proven technology choices, structured mobilisation, strong governance, real-time performance management and delivery ecosystems designed to keep moving.
