Lead service line inventory: get the fieldwork done, and come out with a map you keep.

Use something that gives your crew a record they can fill in from the field. It needs to turn into a living map, not a spreadsheet that goes stale. For a small system that means an app built for water, with the lead service line fields already in it, something you can run yourself with the crew you already have. No per-seat fee.

Ziptility is built for exactly that. Your service lines start as points on a map. Each one carries the fields the inventory needs: material, lead status, ownership, diameter, year installed, and where the location came from. As your crew verifies lines, they fill those in, and the inventory builds itself out of the work.

The lead status field is the one the rules care about. It is already there with the right options: lead service line, lead-free, galvanized requiring replacement, and unknown. You are not configuring a blank database. You are starting from a form a water operator already shaped for this exact job.

The real fields, not a generic asset record. Fields include: material (copper, galvanized steel, lead, PVC, HDPE, PEX, and more), lead status, ownership (utility-owned, customer-owned, split, or unknown), diameter, year installed, burial depth, and condition.

It also tracks where the data came from. The location source field records whether a line was GPS-collected in the field, placed from an as-built record, or placed from memory. That matters for a defensible inventory. A regulator and your own crew should be able to tell a verified line from an assumed one.

When a crew does a service line repair or replacement, the task updates the line's material and lead status right on the asset. So the day you dig up a line and find out what it really is, the record changes with the work. No second system to update later.

Yes. This is the part that makes us different. Along with the templates built for lead service lines, we have staff who have gone out in the field and inventoried lines. You get specific domain expertise plus a human you can call.

That second part is what sells most small operators in the first place. You call and get a person who has done this work, not a ticket queue. The rules are confusing and a moving target. Someone who has stood at the curb stop and worked through it with a utility is worth more than another login.

To be clear about scope: the software is the inventory, the map, and the field forms, and that is what a standard subscription gets you. The hands-on help (working through your records, the verification approach, the reporting) is help we provide alongside the tool, not a magic button inside it. The engineering and regulatory judgment stays with your people and your state.

You get an interactive map with a color-coded status for each service address. Anyone can see at a glance what is verified, what is assumed, and what still needs a field visit. That beats a spreadsheet because the whole crew can look at the same map and know what is left.

The Cordry-Sweetwater Conservancy District in Indiana built their inventory this way and described it plainly. The digital forms were easy to use for any skill level, so every employee could input data. The color-coded map made it easy to keep track of the whole project. They finished ahead of schedule.

The "any skill level" part is the point. Field-first design shows up even in a compliance job. If the person at the curb stop can use it standing there with a phone, the inventory gets done. If they cannot, it sits.

It is ongoing, and that is actually the good news. The rules require you to keep the inventory current, so the lines you verify are not a checkbox you tick and forget. They become permanent asset records on a map you keep using.

That is the difference between a compliance bolt-on and something worth keeping. The service line work you are forced to do anyway becomes the first layer of the system of record you have been meaning to build. Every line you verify is one more asset on the same map your crew already pulls up for main breaks, valve work, and 811 locates. The inventory does not die in a binder the day the mandate is met. It is the start of your map.

We have watched this play out. A utility that uses us only for the one-time inventory and then walks away got a compliance deliverable. A utility that lets the verified lines live on the map got a working system of record for a few thousand a year. We would rather you get the second thing.

Verify fast, verify cheap, and get back to work. The obligation lands on every system the same way, but what you find depends entirely on where you sit.

Arizona spent something like 12 million dollars inventorying for lead service lines and found about six in the whole state. It is the Copper State. For a low-lead system, the inventory is mostly proving a negative. That money would have done real good somewhere with an actual lead problem.

The lesson for a small system: verify fast, verify cheap, get defensible, and get back to work. Do not turn a mandate into a forever project with a price tag to match. Our job is to get you compliant and leave you with a map you keep, not to bill the rule for everything it is worth.

The service line inventory is one piece of the compliance workload. For the rest (sampling, reporting, the recurring work your state expects), start at compliance software for small water utilities.

Rather talk it through first? Talk to someone who has done an inventory. You will get a person who has stood at the curb stop and worked through the records, not a ticket queue.