The records your water utility’s systems were never built to keep

Water utilities run dozens of field programs generating water utilities field data that regulators, clients, and auditors will eventually demand to see. Most of it lands in spreadsheets or disconnected apps that were never built to produce defensible records. A dedicated field platform closes that gap, producing geolocated, timestamped, attributable records across every program a crew runs.

Key insights

• The systems water utilities rely on were built for the office, not the crew in the field.
• When field tools are painful enough that crews cut corners, data quality problems compound across every program.
• Lead service line inventory, fire hydrant inspection, sanitary surveys, and multi-phase repair work all demand airtight, attributable records.
• Engineering and inspection firms running distribution programs on client-mandated apps turn costly field engineers into clerks.
• A field platform built for distribution work integrates with existing systems and gets a program capturing records fast.

Your public water system records show a fire hydrant at the corner of 4th and Main. None of your systems can answer those questions with certainty. They can’t tell you whether it still flows, when a crew last flushed it, or who signed off. And when someone asks for proof, doubt is expensive.

A water distribution system runs on programs that put a crew in the field on a schedule and come back with records someone will eventually ask to see: valve exercising, fire hydrant inspection and flushing, leak surveys, main and manhole inspection, backflow and cross-connection control, and the lead service line inventory the federal rule now demands. Every one generates water utilities field data, and most of it sits in a spreadsheet or a different app bought for that one program.

Your systems serve the office, not the field

The asset and mapping systems most water utilities run are good at what they were built for. Cityworks, now Trimble Unity Maintain, manages the asset; ArcGIS holds the map; Maximo, Infor, or Oracle runs the enterprise side. All of them serve the asset manager, the GIS manager, and the planner. None of them were built for the crew in the truck.

The crew pays for the gap. To finish one inspection or data capture task they open the asset app, a separate safety form, and the map, then re-key the whole thing at a desk that night. If they skip it, the record becomes a guess. Every program change, tightened regulation, and new piece of equipment means the field form has to change with it. Keeping those forms current falls to the GIS or IT queue, a team that never signed up to build and babysit field workflows for every distribution program you run.

The friction has a cost beyond the lost record. When the field tool is painful enough that crews cut corners or miss their quotas, the data quality problem compounds itself. When someone has to validate and manually feed mountains of captures into the system, the team carrying that load burns out fast.

Built for the truck instead of the back office

Crews need a platform built around their work and the water utilities field data those programs generate. The right one runs every distribution program the same way, stays current without IT intervention, and feeds clean data into the systems the office already uses. The right platform for this work must:

• Run every program the same way. Built-in safety checks and required steps make sure nothing gets skipped or invented on the fly.
• Put workflow changes in your team’s hands. When the rule, route, or equipment changes, field teams make the updates without vendors or an IT queue.
• Attach location to every record at capture. The position logs automatically as the crew works, with no re-keying step required.
• Feeds clean data into the systems you already run. Built-in process guardrails enforce inputs at capture so the data reaching ArcGIS, Cityworks, and your EAM is clean and ready to use.

The record behind the work

A record that holds up captures the geolocation, timestamp, and crew member who did the work. When someone asks, the export is ready in minutes.

Four programs where that record has to be airtight:

Lead service line inventory. The initial lead service line inventory deadline passed in October 2024. What remains is a continuous workflow of physical verification, replacement tracking, and ongoing updates. A comprehensive baseline inventory is due in 2027, and the live record has to be ready for regulators at any point.

Fire protection rating. Fire hydrant inspection records feed the ISO Public Protection Classification which sets property insurance costs across an entire service territory. Gaps in those records cost the whole community money.

Sanitary surveys and consent decrees. EPA and state reviews, along with CMOM reporting on the wastewater side, require proof that every program ran in sequence and on schedule, with each step tied to a crew member and a date.

Multi-phase work. When a temporary repair gets replaced by a permanent one, the record of the first has to survive the second. Spreadsheets and disconnected apps can’t maintain that continuity.

A record system built for the office was never going to hold up to this kind of scrutiny.

Contract firms have the same problem (and a bigger opportunity)

Engineering, environmental, and inspection firms running distribution programs for water utilities live or die on the quality of their field records. Running each client’s mandated app and re-keying the output into their own reports undermines that quality, turns costly field engineers into clerks, and drags out billing.

Instead, a single platform built around firm workflows transforms field data capture. It keeps programs running consistently and protects the margin.

The records the client receives drop straight into their ArcGIS or Cityworks, clean and located, without a re-entry step on their end. Cleaner deliverables win bids. When an invoice or audit gets questioned, the answer is already in the record: proof of work by crew, by location, by date.

Up and running without a stack project

A field platform built for this work integrates with your existing Esri, Cityworks, and EAM systems and passes enterprise security and IT review. Field process and data flow across those systems runs automatically. Crews run it on the phones and tablets they already carry, and it works offline at the far end of the service territory, syncing when they’re back in range. A single program can be up and capturing records in as little as a day, and many teams are running full workflows within their first week in the field.

Moving field operations onto a platform built for the work doesn’t have to be a big project. A utility can start with the programs already running and add workflows and system connections at its own pace, without waiting on a full rollout to see results.

Field operations built on proof

Water utilities have spent years managing field programs with systems built for the office, and the records those programs produce reflect that. They live in spreadsheets, disconnected apps, and GIS queues, incomplete and impossible to defend when a regulator, a client, or an auditor asks for proof.

A platform built for field work improves data quality. The system geolocates and timestamps every record. It also attributes the work to the specific crew member. Clean data reaches the office before anyone touches it.

The utilities and firms that get this right stop paying the cost of doubt. Better records mean fewer revisits, cleaner audits, and field programs that hold up to scrutiny. For utilities running critical infrastructure, that standard has always been the expectation. Field operations are finally in a position to meet it.

See what defensible field records look like in practice

Water utilities and the firms that serve them are already running the programs that generate field data every day. A free custom demo shows exactly how a platform built for that work captures, locates, and delivers records that hold up when someone asks for proof. Contact us today to get started!