Last Tuesday at 7 a.m., a clerk at a 1,800-connection water system in Kansas took a call from a homeowner. Brown water at the kitchen tap. She wrote it on a sticky note, walked it across the office, and stuck it to the lead operator's monitor. By 9, the operator was in the truck, the note was somewhere on the floorboard, and the original caller was waiting for a return phone call that wasn't coming. That's a paper work order, and it's what small utilities are trying to replace when they go shopping for water utility work order management software.
This post is the 10 features that separate the kind that lives in the truck from the kind that dies in a binder. Each one comes with a plain-language example and one question to ask the next vendor who shows up on a Zoom call.
Features that work in the truck, not just at the desk
If a feature doesn't work on a phone with cold hands and one bar of signal, your crew won't use it. Three features decide whether software lives in your trucks or stays at the office.
1. Mobile-first work orders
The work order opens on a phone or tablet, with the same information you'd see at a desk, and the crew can close it out without coming back to fill out paperwork. A hydrant flushing task gets created at the office. The operator sees it on the phone, drives to the hydrant, fills out the flow readings while standing at it, and hits done. The supervisor gets the closed ticket before the operator has driven back to the shop.
Ask the vendor: "Show me the work order on a phone. Can a tech complete it from the field without going back to the office?"
2. Map-linked work orders
Every work order is tied to a specific asset on a map, a valve or a hydrant or a meter, not a free-text address. This is the single feature that small utilities consistently say changes how they do the work.
"Sometimes it is a scavenger hunt and sometimes we go to check a meter and we can't even find the damn thing." — Chelsea Vialpando, Candlewood Park
When a meter exchange ticket is created, the operator opens it and the meter is already pinned on the map. No "it's by the second tree from the corner," no flipping through a binder. You can also do this the other way around. Tap the valve on the map and see every work order ever done on it. That's the difference between a work order app and a record of your system.
Ask the vendor: "If I tap a valve on the map, can I see every work order ever done on it?"
3. Photo and video documentation
Every work order can carry photos taken on the phone, tagged to the work and the asset. This sounds obvious. It is not obvious in the older software still being sold to small utilities.
"Take a picture, add it. Boom. So when the customer says there's no way, you can pull it up and go, well, here's proof." — skeith, Veolia
The use case is dead simple. A homeowner complains the meter wasn't read. You pull up the work order, you show the photo of the read with a timestamp, and the conversation ends. The same is true for the state inspector who wants to see proof you flushed the hydrant.
Ask the vendor: "Can my crew attach five photos to a single work order without leaving the app?"
Features that match how the work actually flows
Most small utilities run on the same three-step flow. Someone creates a work order. A supervisor assigns it to a crew member. The crew closes it out and the supervisor reviews it. Software has to match that, not redesign the job.
4. Inbox and assignment workflow
You need a single place where new work orders land, get assigned to a person, and disappear once they're done. The Town of Lexington in South Carolina runs exactly this way, and they described it as the test for any software they pick:
"She has a physical box on her desk that says inbox on it. That's where all the completed reviewed work orders by supervisors go." — Woodrow Evans, Town of Lexington SC
The good version of this feature lets a clerk create the work order from her desk in 30 seconds, route it to Bobby's phone in the field, and have it back on her screen the moment Bobby closes it out. No emails. No phone tag.
Ask the vendor: "Can my clerk create a work order in under 30 seconds and assign it without picking up the phone?"
5. Recurring preventive maintenance routines
The software automatically generates the work orders you'd otherwise forget. Monthly hydrant flushes. Weekly generator runs. Quarterly tank inspections. Annual valve exercising.
A hydrant flushing routine creates 47 work orders on the 1st of every May, each pinned to a specific hydrant in the distribution system. Your operator opens the app and there's the list, in order, with the route already on the map. You don't have to remember anything. You also don't have to defend a missed inspection to the state, because the record is right there.
Ask the vendor: "Can I set up a recurring task for one asset, then duplicate it to 200 more in one click?"
6. Asset history per work order
Every work order completed against a valve, a meter, or a pump is appended to that asset's permanent record. This is the feature that matters when a long-tenured operator retires and the knowledge in his head has to stay in the system.
A new operator pulls up a 30-year-old gate valve and sees every repair, every photo, and every note since 2019. The previous operator's "I think we replaced the stem in maybe 2021" becomes the actual date, the actual part, and the actual picture. That's how you track what's in the ground without it living in one person's memory.
Ask the vendor: "If my best operator retires tomorrow, what stays in the system and what walks out the door?"
Features that decide whether your crew, your office, and your board can all use it
Work order software stops being a fight when the part-time clerk, the senior operator, and the council member can all open it and find what they need. These last four features decide whether the software gets used or gets canceled in a year.
7. A crew-friendly interface anyone can learn in under an hour
Simple enough that your weekend on-call operator can use it the first time, without a manual. This is not a low bar. Most software designed for utilities was built for an IT department, and most small utilities don't have one.
"This is perfect. It was just learning the new process, which this is pretty simple." — Samuel Cushman, Bingen WA
The test is a brand new crew member, day one, no training. Can they open a work order, complete it, and close it without help. If the answer is no, the software will get used by two people and the rest will find a way around it.
Ask the vendor: "Can a brand new crew member open a work order, complete it, and close it without help?"
8. Works when the signal doesn't
Out at the lift station, in the well house, or under a manhole, the work order has to keep working when the bars drop to zero. And it has to sync when the signal comes back. This is the difference between software designed for an office and software designed for the field.
An operator opens a tank inspection task on a 4G dead spot at the edge of the district. Fills it out. Takes a photo. Hits done. The phone holds it. When the truck pulls back into town, it uploads, and the supervisor sees the completed work order on her screen.
Ask the vendor: "Show me the app working with airplane mode on. Does it actually open and save?"
9. Board-ready reporting without a spreadsheet exercise
One click to pull the month's completed work orders by district, by operator, or by asset type. Formatted for the council, not for IT. This is the feature decision-makers ask for in nearly every demo, and the one missing from most CMMS tools.
A month-end report shows 312 tasks completed, $14,400 in parts used, 47 hydrants flushed, and 12 emergency repairs by location. One PDF, two clicks, ready to hand to the board on Monday. The contract operators running multiple systems need a version of this per district. Same feature, different scope.
Ask the vendor: "Show me the report I'd hand to my council. Can you build it without exporting to Excel?"
10. Pricing that scales with your system, not your seat count
Unlimited users at one flat price. Every operator needs access, and per-seat pricing punishes you for hiring help or letting your part-time clerk into the system.
A 1,500-connection system with four operators, one clerk, and two contractors all use the same login pool with no surcharge. When you add a summer hire, the bill doesn't change. When the contract operator running your wastewater side needs to see the work orders too, the bill still doesn't change. That's what flat unlimited-user pricing means.
Ask the vendor: "If I add three part-time operators next year, does my bill change?"
What to ask before you buy
The 10 questions above aren't a vendor checklist. They're what to type into your phone before the next demo. Print this list and bring it.
- Show me the work order on a phone. Can a tech complete it from the field without going back to the office?
- If I tap a valve on the map, can I see every work order ever done on it?
- Can my crew attach five photos to a single work order without leaving the app?
- Can my clerk create a work order in under 30 seconds and assign it without picking up the phone?
- Can I set up a recurring task for one asset, then duplicate it to 200 more in one click?
- If my best operator retires tomorrow, what stays in the system and what walks out the door?
- Can a brand new crew member open a work order, complete it, and close it without help?
- Show me the app working with airplane mode on. Does it actually open and save?
- Show me the report I'd hand to my council. Can you build it without exporting to Excel?
- If I add three part-time operators next year, does my bill change?
If a vendor can't answer those 10 questions on a 30-minute demo, the software isn't built for a utility like yours.
For a longer read on the same problem from the mapping side, see From Paper Maps to Digital GIS. For the resource page that goes deeper on the work-order side specifically, see mobile work orders.
How Ziptility helps
Ziptility was built around exactly these 10 features, because they came from 100 plus conversations with operators, clerks, and superintendents at utilities like yours. Not a generic CMMS feature list.
Every work order in Ziptility lives on the map. Tap a valve, see its history. Open a work order, see the asset already pinned. The inbox and assignment flow works the way the Town of Lexington described it, and the photos go on the phone, in the field, at the time the work happens. Preventive maintenance routines run on their own schedule. Asset histories build up on every valve, hydrant, meter, and pump, automatically.
Out in the field, Ziptility works on a phone, with offline support for the dead spots. Back at the office, the board report generates in two clicks. Pricing is flat and includes every user, because a small utility shouldn't be punished for needing help. We work with water utility work order management software customers running systems from a few hundred connections to 10,000. Built for small water and wastewater utilities, not IT departments.
If you want to see the 10 features running on real data, you can request a guided demo and we'll set up a 14-day trial against your actual valves, hydrants, and meters.
