The American Society of Civil Engineers gave US drinking water infrastructure a C- in its 2021 Report Card. Wastewater scored a D+. Behind those grades are aging pipes, understaffed control rooms, billing systems that bleed revenue, mounting compliance mandates, and a cybersecurity exposure most small and mid-sized utilities have not yet fully reckoned with. For utility directors responsible for keeping the water flowing while managing tight budgets and lean teams, these are not abstract problems, they show up every week.
This guide breaks down the five most significant challenges facing US water utilities right now, what each one costs operationally, andwhat forward-looking utilities are doing to get ahead of them.
The five biggest challenges currently facing US water utilities are aging infrastructure, a retiring workforce, billing inaccuracies and revenue leakage, regulatory compliance pressure, and cybersecurity vulnerabilities. Each challenge compounds the others: aging pipes increase emergency work orders, which strain a shrinking workforce; manual billing systems fail to capture non-revenue water losses from those same aging mains; and compliance reporting consumes staff time that could otherwise go toward capital planning. Utilities that address these challenges in isolation rarely move the needle. Those that address them through connected, modern operational systems make measurable progress.
Water infrastructure in the United States was largely built inthe mid-20th century. Pipes designed for a 50-to-75-year service life are now exceeding that lifespan in cities across the country, and the investment required to replace them has accumulated faster than most utility budgets can address.
According to the American Water Works Association (AWWA), US water systems experience approximately 240,000 water main breaks per year. Each break triggers an emergency response, crew dispatch, road disruption, service interruption, customer complaints, and repair costs that consistently run higher than equivalent preventive maintenance would have. The ASCE's 2021Infrastructure Report Card assigned drinking water a C- and wastewater a D+, reflecting the scale of the deferred investment problem.
Non-revenue water (NRW) is the term water utilities use to describe treated water that is produced and distributed but never billed —primarily because it is lost through leaks in aging distribution networks before it reaches a customer meter. NRW is defined as the difference between the volume of water entering a distribution system and the volume billed to customers. AWWA data places the US average NRW rate at approximately 16%, meaning roughly one in six gallons of treated water generates no revenue. For a utility producing 10 million gallons per day, that is a significant and ongoing financial loss.
The core infrastructure challenge is not simply that pipes are old, it is that most utilities lack the visibility to know which assets are most at risk, in what condition, and in what order they should be prioritized for replacement. Spreadsheet-based asset registers and paper-based inspection records make condition-based capital planning nearly impossible.
Utility asset management software that maps infrastructure to GIS coordinates, tracks condition ratings over time, and connects asset data to work order history gives utility directors the visibility to move from reactive emergency repairs toward planned, prioritized replacement.
The workforce challenge facing water utilities is not a future problem. It is already here.
AWWA has projected that a significant portion of the current water sector workforce, estimates have placed this figure at up to one-third in some regional analyses, will be eligible for retirement within the next decade. In many utilities, the operators who know where buried infrastructure runs, which pump tends to fail at high temperature, and how to navigate a pressure zone during a main break are the same ones approaching the end of their careers.
When those individuals retire, they do not hand over a manual.The knowledge transfers informally, through years of working alongside colleagues, and when it leaves, it tends to leave completely. What remains is a newer crew, often smaller due to budget constraints, working from incomplete documentation in systems that were not built to capture operational history.
The operational impact shows up in slower response times, higher rates of repeat work orders, and increased risk during emergency events.The safety impact is harder to quantify but real: institutional knowledge includes knowing what not to do in specific infrastructure configurations, and that kind of knowledge does not appear in standard operating procedures.
Digitizing field operations is the most direct response utilities have available. Work order management for utilities that requires field crews to log every action, attach photos, and recordasset-specific notes creates a living institutional knowledge base that persists when individuals retire. Mobile dispatch that routes work efficiently and enables crews to access service history in the field reduces the dependence on any single operator's memory.
Billing is the financial engine of a water utility. When it runs poorly, every other operational priority becomes harder to fund.
Billing inaccuracies in water utilities arise from several interconnected sources: meter reads that are estimated rather than actual, rate structures applied incorrectly to customer classes, manual data entry errors inthe meter-to-cash process, and billing exceptions that sit unresolved in queues for days or weeks. Each of these represents revenue that was earned, water was delivered, metered, and should have been billed, but was not collected at the correct amount or on schedule.
For billing managers, this manifests as a reconciliation problem that consumes significant staff time each billing cycle. For utility directors, it shows up in rate-setting conversations: if a utility cannot demonstrate billing accuracy, it cannot make a credible case for rate adjustments to a city council or public utility commission.
The relationship between aging infrastructure and billing accuracy is direct. Older meters read less accurately over time. AMI systems that feed interval meter data into billing platforms reduce the estimation problem, but only when the billing software is built to receive and process that data correctly. Utilities running legacy Customer Information Systems(CIS) that were not designed for AMI data find themselves with modern metersfeeding inaccurate legacy billing processes, the worst of both worlds.
SMART360 has documented a 50% improvement in billing accuracy among utilities that have migrated from legacy CIS platforms to its unified billing and meter data management environment. That improvement reflects fewer estimated reads, fewer billing exceptions requiring manual resolution, and tighter integration between what the meter records and what the customer is billed.
Water utilities in the United States operate under one of the most extensive regulatory frameworks of any sector. The Safe Drinking Water Act (SDWA) establishes federal minimum standards for drinking water quality and requires regular monitoring, testing, and reporting to state primacy agencies and ultimately to the EPA. The scope and frequency of that reporting has grown substantially over the past decade.
The Lead and Copper Rule Revisions (LCRR), finalized by the EPA in 2021, introduced new requirements for lead service line inventories,accelerated replacement timelines, and more rigorous public notificationobligations. For utilities with older distribution systems, complying with theLCRR has required simultaneous investment in inventory documentation, customer communication infrastructure, and physical replacement programs, all with limited incremental funding.
The Infrastructure Investment and Jobs Act (IIJA), enacted in 2021, allocated $55 billion for water and wastewater infrastructure, including specific funding streams for lead service line replacement. Accessing thosefunds requires utilities to demonstrate compliance readiness and maintainaccurate asset documentation, which is itself a systems and data challenge.
The operational burden of regulatory compliance falls disproportionately on small and mid-sized utilities. A large metropolitan water authority has compliance officers, dedicated legal counsel, and enterprise reporting systems. A 30,000-meter municipal utility typically does not. The staff member responsible for SDWA reporting is often the same person managing billing disputes and fielding council inquiries. Manual reporting processes in that environment are a reliability risk.
In February 2021, an operator at the City of Oldsmar, Florida's water treatment facility noticed an intruder had remotely accessed the plant's SCADA system and increased sodium hydroxide levels to more than 100 times the normal concentration. The operator caught it in real time and reversed the change. The incident became a national reference point for cybersecurity risk in water infrastructure.
The EPA has since made water system cybersecurity a formal inspection priority. Its assessments have found significant rates of non-compliance with basic cybersecurity protocols across water systems of varying sizes, inadequate access controls, unpatched software, no incident response plans, and operational technology connected to networks without appropriate segmentation.
Water systems are designated critical infrastructure under federal frameworks, and the threat environment has not improved. Ransomware attacks on municipal systems have increased, and water utilities , often running legacy on-premise software with limited IT staff, represent a target with historically low security maturity.
Cloud-native SaaS platforms carry an inherent security advantage over on-premise legacy systems in this context. They are maintained by the vendor, patched on a regular cadence, and do not require a utility's internal IT team to manage server-level security. SMART360 is built as cloud-native infrastructure with no on-premise components, which removes the most common attack surface vectors that legacy utility systems present.
The five challenges above are distinct in their causes, but they share a common structural problem: they are all significantly harder to manage when a utility's billing system, asset records, work orders, meter data, and customer information live in separate, disconnected systems.
A utility director trying to understand their true NRW rate needs data from the meter platform, the billing system, and the asset register, simultaneously. If those systems do not talk to each other, producing that analysis is a manual project. Meanwhile, the next main break is already being dispatched on paper.
The utilities making the most measurable progress against these five challenges have moved to unified, cloud-based operational platforms that connect billing, customer information, meter data management, work order dispatch, and asset management in a single environment. The data produced by field crews feeds asset condition records. Meter reads flow directly into billing without manual entry. Compliance reports pull from a single source of record rather than being assembled from multiple spreadsheets.
SMART360 is built specifically for small and mid-sized US water utilities, systems ranging from 5,000 to 500,000 meters, that have been underserved by large enterprise vendors whose implementation timelines and licensing costs assume a very different organizational scale. SMART360's 25+ pre-built integrations cover the AMI systems, GIS platforms, and payment gateways that US water utilities already operate, which means migration does not require replacing an entire technology ecosystem. Learn more about water utility management software built for the scale and constraints of small and mid-sized US utilities.
Implementation runs in 8 to 12 weeks, compared with the12-to-18-month industry average for enterprise utility software, because the platform is built for lean utility teams, not dedicated implementation departments. Island Water Authority went live on SMART360 in 8 weeks. Utilities that have made the transition have reduced operational expenditure by approximately 50% and improved billing accuracy by 50%.
For a utility director who has watched modernization projects fail or stall, the barrier to starting again is real. The 9-week free trial is designed to remove that barrier: full platform access, no upfront commitment, and a timeline that fits within a single budget cycle.
The five most significant challenges US water utilitiescurrently face are aging distribution infrastructure, a retiring workforce andinstitutional knowledge loss, billing inaccuracies and non-revenue waterlosses, growing regulatory compliance requirements under the Safe DrinkingWater Act and Lead and Copper Rule Revisions, and increasing cybersecurityvulnerabilities. These challenges compound each other and are significantlyharder to manage in fragmented, legacy technology environments.
According to the American Water Works Association (AWWA), USwater systems experience approximately 240,000 water main breaks per year. Eachbreak triggers emergency crew dispatch, service disruptions, and repair coststhat consistently exceed equivalent planned maintenance expenditure.Accumulated deferred investment in aging distribution networks is the primarydriver of this figure.
Non-revenue water (NRW) is defined as treated water thatenters a distribution system but is never billed to customers — primarily dueto physical losses through leaking or broken pipes. The American Water WorksAssociation places the US average NRW rate at approximately 16%. For mostutilities, NRW represents a direct and ongoing revenue loss that compounds thefinancial pressure of aging infrastructure investment.
Water utilities are designated critical infrastructure under federalframeworks and face growing exposure to ransomware attacks, unauthorized remoteaccess attempts, and SCADA system intrusions. The EPA has flagged cybersecuritydeficiencies through its inspection program. The 2021 Oldsmar, Florida incident— in which an intruder remotely accessed a water treatment plant and alteredchemical dosing levels — is the most widely cited real-world example of theoperational risk. Utilities running on-premise legacy systems with limited ITstaff face the highest exposure.
Enterprise utility software implementations typically run 12to 18 months. SMART360 implements in 8 to 12 weeks for small and mid-sizedwater utilities, including data migration, AMI integration, and staff training.Island Water Authority completed its full implementation in 8 weeks. Thedifference reflects a platform built for lean utility teams rather thandedicated implementation departments.
