When a longtime Public Works Director retires, the loss isn’t obvious right away. The crews keep working. The trucks keep rolling. Then, somewhere in the first month, someone asks a question nobody can answer. Which lift stations are overdue for service? When was that stretch of road last patched? Where are the water shutoffs on the east side of town?
The answer, if it exists at all, usually lives in a spreadsheet, a filing cabinet, or the memory of the person who just left. This sort of systems-based problem shows up in municipalities and counties across the country.
For a Public Works Director, the software market is full of systems claiming to fix this sort of issue, many of them short on clarity. Most were built for large cities with IT departments and enterprise budgets that a lean department doesn’t have. Knowing what matters before you sit through a single demo helps make the whole evaluation feel manageable. Here’s a plain-language breakdown of what actually counts.
| Feature | What It Should Do | Red Flag to Avoid |
| Asset tracking | Log condition, location, and maintenance history for each asset | Records that only update when a crew member re-keys field notes at a desk, or that sit disconnected from work orders |
| Work order management | Create, assign, and close work orders from a mobile device | Orders you can open and close at the office but not in the field |
| GIS and mapping | A visual map of assets tied to work history and location data | A map that plots locations but not work history or condition, or that needs a GIS specialist to update |
| 811 / utility locate compliance | Built-in locate request workflow and state compliance reporting | Locate requests bolted on through a generic integration, with state reporting you assemble by hand |
| FEMA documentation | Asset condition records that support reimbursement claims | Condition and maintenance records you can enter but can’t export in a form that supports a Public Assistance claim |
| Support and onboarding | Named contact, same-day acknowledgment, setup handled by the vendor | Anonymous ticket queues and setup left to your staff |
Sources: gWorks Operations [1]; FEMA Public Assistance Program [3]; Common Ground Alliance [4]
For most Public Works Directors, the tipping point isn’t one dramatic failure. It’s the slow pile-up of workarounds. Work orders written on paper and entered into a spreadsheet later, if they get entered at all. Asset records split between a shared drive, a binder in the back office, and the memory of the crew member who installed the line fifteen years ago. A quiet, daily sense that critical information is one retirement away from being gone forever.
The real cost of that setup shows up on the worst possible day. When a contractor hits a utility line, a pipe fails without warning, or a flooding event triggers a FEMA claim, the question is always the same. Do we have a record? If the answer depends on who was working that day and whether they wrote it down, the current system is already failing you.
State 811 mandates are expanding, and penalties for non-compliance are set by state law, reaching into the tens of thousands of dollars per violation in some jurisdictions [4]. FEMA reimbursement after a disaster requires documented asset condition and maintenance history [3]. These aren’t future concerns. They’re requirements departments face right now.
What to Look for in Public Works Asset Management Software
For a lean team without a full-time GIS coordinator or a dedicated IT department, the most important features are rarely the ones at the top of a vendor's marketing page. They’re the ones that make daily work manageable for a crew that’s already stretched thin.
Every asset a department manages, from fire hydrants and stormwater infrastructure to fleet vehicles and roads, should have a record attached to it: condition rating, maintenance history, location, and the last time someone worked on it. That record should be reachable from the field, not just from a workstation in the office.
Look for: cloud-based records with mobile access, GPS or GIS-linked locations, and the ability to attach a photo straight from a phone. With Esri's ArcGIS Desktop now retired, this is also the moment many departments are replacing aging desktop GIS. It’s worth confirming a vendor's mapping is cloud-based rather than tied to legacy software.
Avoid: systems where the asset database lives behind a specialized login only one person on staff knows how to use.
A work order system is only useful if the people doing the work can use it where the work happens. That means creating, assigning, updating, and closing orders from a phone or tablet, without a trip back to the office to log results.
Look for: mobile work order creation and close-out, crew assignment, photo documentation, and real-time status for supervisors.
Avoid: systems that are billed as mobile but really just mirror the desktop, so a crew still logs results at a workstation after the fact.
811 compliance is not optional, and the documentation requirements are specific [4]. The right system should manage locate requests from intake through response and close-out, without a separate spreadsheet or a manual call to the one-call center for every ticket.
Look for: integrated locate ticket management, field crew status tracking, and state-specific compliance reporting built in. Ask vendors directly whether the system produces the documentation your state requires.
Avoid: a general work order tool with 811 treated as an afterthought, where locate tickets live in their own silo and the compliance report is something you still build by hand. If the answer to that documentation question involves an Excel export, keep looking.
FEMA reimbursement after a declared disaster requires documented evidence: asset condition before the event, maintenance history, and repair records [3]. The right system captures these things as a natural output of daily work. Condition ratings updated in the field. Orders closed with notes and photos. Maintenance cycles logged over time. When FEMA calls, the records are already there.
Look for: asset condition logs that build incrementally, work history exportable by asset, and records formatted to support Public Assistance submissions without a major data project.
Avoid: a system that stores condition and maintenance data but can’t export it in a form a Public Assistance claim actually needs, so you’re still rebuilding the record by hand when it counts most.
Ask any vendor's references one question: what happens when something goes wrong the week before a council meeting? The answer tells you more than any SLA document.
Look for: named support contacts, same-day acknowledgment, and onboarding the vendor handles rather than one that lands on your department.
Avoid: support that amounts to a ticket number and a queue, with no way to see who has your issue or when you'll hear back.
A lot of the software marketed to public works departments was built for large cities, with IT staff, GIS departments, and implementation timelines measured in years. For a smaller team it arrives with more complexity than the department can absorb, and with a price tag that includes modules no one will ever open.
Purpose-built software looks different in practice: an interface a crew member can navigate on their first day without an extended training course; setup handled by the vendor, not handed to a department that is already stretched; pricing built around a government budget cycle, not an enterprise contract. gWorks is the top-ranked cloud software platform built exclusively for municipalities, counties, and utility districts under 50,000 population.
gWorks Operations was built for exactly this. More than 2,000 local governments across 48 states use gWorks today, from small towns to counties serving large populations [1, 2]. gWorks handles the setup, and most departments are typically operational within 60 to 90 days [1]. Support is a named person who knows your account inside and out. Departments that have been through the switch consistently describe it as smoother than expected, because the heavy lifting stays with the vendor rather than landing on your staff.
A System That Fits How Your Department Works
The right software doesn’t need to do everything for every city. It needs to do the right things well: track your assets in the field, keep you compliant with 811 requirements, build the documentation you will need for FEMA, and put a real person on the line when something goes wrong.
That’s what to look for in public works asset management software. And the right system delivers it from the first week of use, not after a year of tweaking.
gWorks Operations was built for municipalities and counties that need modern, field-ready tools without enterprise-level complexity. If you want to see what a more capable system looks like for your department, we’re ready to help.
Schedule a gWorks Operations Demo
At a minimum, it should track each asset's condition, location, and maintenance history in one place; let crews create and close work orders from the field; and produce the compliance and FEMA documentation your department needs. If any of that lives in a separate spreadsheet, the software is not doing its job.
Yes, if it’s built for lean teams. Purpose-built systems are set up by the vendor and designed so a crew member can use them on day one, without a VPN, a specialized login, or an in-house IT department to keep them running.
FEMA reimbursement requires documented asset condition and maintenance history from before a disaster event [3]. Software that logs condition ratings and closes work orders with notes and photos as part of daily work builds that record automatically, so the documentation is already in place when a claim is filed.
Share your thoughts about this article.
Be the first to post a comment!
