The five communications mistakes that derail water infrastructure projects — and how to avoid them.

After three decades of guiding water projects through permitting, construction, and operations, we have seen the same communications failures repeat themselves. They are not failures of strategy, exactly. They are failures of discipline — of doing the hard, unglamorous work of community engagement consistently, even when the project team is exhausted and the schedule is slipping.

The stakes are high. A water infrastructure project that loses community support mid-permitting can face years of delay, litigation, and cost overruns that dwarf any savings from cutting the communications budget. We have seen it happen. We have also seen projects that should have been controversial sail through permitting because the communications program was built on a foundation of genuine transparency and consistent engagement.

Here are the five mistakes we see most often — and what to do instead.

1. Starting communications after the decision is already made.

This is the most common and most costly mistake. A project team spends two years in engineering and planning, makes the fundamental decisions about alignment, technology, and design, and then hires a communications firm to "get community buy-in." The problem is that community buy-in is not something you get after the fact. It is something you build throughout the process.

When communities feel that their input is being solicited as a formality — that the real decisions were made in a conference room without them — they are right. And they respond accordingly. Opposition that could have been addressed through early engagement becomes entrenched. Concerns that could have shaped the project design become lawsuits.

The fix is to involve communications professionals from the earliest stages of project planning — not to manage messaging, but to help the project team understand the community landscape before decisions are made. Who are the stakeholders? What are their concerns? What information do they need to understand the project? What forums exist for genuine dialogue? These questions should be answered before the first shovel of dirt is turned, not after.

2. Treating public meetings as the primary engagement mechanism.

Public meetings are a regulatory requirement, not a communications strategy. They are adversarial by design — a format that rewards the loudest voices and discourages the kind of genuine dialogue that builds understanding and trust. Yet many project teams treat the public meeting as the centerpiece of their community engagement program.

The communities most affected by water infrastructure projects — the landowners near a new pipeline, the neighborhoods downstream of a treatment facility, the rural counties that will host a new reservoir — are not well-served by a two-hour meeting in a school gymnasium where they get three minutes at a microphone. They need sustained, accessible, two-way communication over the life of the project.

Effective engagement programs use public meetings as one tool among many: small group meetings with affected landowners, regular project updates via email and project websites, one-on-one conversations with community leaders, and presence at existing community events. The goal is to be accessible and consistent, not to check a regulatory box.

3. Using technical language with non-technical audiences.

Water infrastructure projects are technically complex. The engineering is sophisticated, the regulatory framework is dense, and the science of hydrology, water quality, and environmental impact is not intuitive. Project teams spend years developing deep expertise in these areas, and that expertise shapes how they communicate — often in ways that are inaccessible to the communities they need to reach.

We have reviewed public comment documents that read like engineering reports. We have sat through public meetings where project managers presented slides full of technical data to audiences of concerned landowners who left more confused — and more suspicious — than when they arrived. Technical complexity is not a communications strategy. It is a barrier.

The discipline of plain-language communication is not about dumbing things down. It is about respecting your audience enough to translate complex information into terms they can evaluate and act on. What does this project mean for my water supply? For my property? For my community? Those are the questions that matter to the people most affected by your project, and they deserve clear, honest answers.

4. Going dark during construction.

The permitting phase gets all the communications attention. The construction phase is where community relationships are actually won or lost — and where many project teams go quiet.

Construction is disruptive. Traffic is diverted. Noise and dust affect neighboring properties. Schedules slip. Unexpected conditions are encountered. Communities that were supportive during permitting can turn hostile when the reality of construction does not match the promises made in public meetings.

The solution is proactive, consistent construction communications: regular project updates that acknowledge disruptions honestly, clear information about what to expect in the coming weeks, and accessible channels for community members to report concerns and get responses. A project hotline that is actually answered. A project website that is actually updated. A community liaison who is actually present in the affected area.

The communities that feel informed and respected during construction become the project's advocates. The communities that feel ignored become its opponents — and they remember.

5. Treating communications as a cost center, not a risk management tool.

Communications budgets are among the first to be cut when project costs escalate. This is a false economy. The cost of a communications program — even a robust one — is a fraction of the cost of a single year of project delay caused by community opposition or regulatory challenge.

We have worked on projects where the communications investment was measured in hundreds of thousands of dollars and the cost of the opposition it helped prevent was measured in tens of millions. The math is not complicated. What is complicated is making the case for communications investment before the crisis happens — before the opposition coalition forms, before the media story runs, before the regulatory agency receives the petition.

The most effective project teams treat communications as a risk management discipline with the same rigor they apply to engineering risk, environmental risk, and financial risk. They identify the stakeholders who can affect the project, they assess the concerns that could derail it, and they build communications programs designed to address those concerns proactively — not reactively.

The bottom line.

Water infrastructure projects are among the most consequential investments communities make. They are also among the most complex to communicate — technically, politically, and emotionally. The projects that succeed are not necessarily the ones with the best engineering. They are the ones with the most consistent, transparent, and genuine community engagement.

That is not a soft skill. It is a discipline. And it requires the same level of professional expertise and sustained commitment as any other critical element of project delivery.