A lot of agencies have bought a modern platform in the last few years, and many of them are the same thing underneath: a CRM with government branding. Contacts, accounts, activities, tasks. CRM is fine software for managing relationships. The trouble starts when it's asked to run a cross-connection control program, because the program isn't a relationship. It's hardware on a service line under a regulation.
The Assembly Named Like a Person
Open a CRM that's been forced to hold a backflow program and you'll find a contact whose first-name field reads "RPZ #2 - rear irrigation" and whose last name is the service address. The mailing address belongs to the property owner, who is a different contact, related to the assembly through a field originally meant for "employer." The tester's certification number lives in a notes box, with no expiration date the system can check. None of this is anyone's fault. The system offered exactly one noun — a person — and staff did what people do with the wrong tool: they made it fit.
The person changes; the assembly stays. CRM gets that backwards, because in CRM the person is the record. Everything that goes wrong downstream goes wrong because of this one inversion.
The Deadline That Got Snoozed
An annual test date set by the state is not a to-do item, but in a CRM it becomes one: a task, assigned to the utility clerk, due June 30. Tasks can be snoozed. During a busy week, somebody snoozes it — reasonably, because forty other tasks are due the same day — and the system treats that as handled. No escalation fires. The certified-mail shutoff notice that should follow a missed test never gets queued, because the notice was never wired to the deadline. It was wired to the task, and the task is asleep. The regulation doesn't know the task is asleep.
The Merge That Ate the History
Then the property sells. The new owner calls in, the billing clerk creates a contact, and the CRM's duplicate detection helpfully suggests merging it with the existing record at that address. Someone clicks yes. Now three years of passing test reports — attached as PDFs to the old owner's contact — hang off a person who bought the place in March. When the new owner disputes a non-compliance letter, the file says she's been receiving notices since 2022. She hasn't. The asset has. But the asset was never a record, so its history had to live on whoever was standing nearest.
The Report Built by Hand Every Month
The state wants a monthly compliance summary, and the water system's own engineer wants it broken out by pressure zone. The CRM cannot say "compliance rate by pressure zone" because pressure zone was never a field — there was nowhere natural to put it. So each month the clerk exports contacts to Excel, matches addresses against a parcel list from the county assessor, hand-tags zones, and rebuilds the percentages. The export has duplicate addresses and a few assemblies filed under the tester's name instead of the owner's. The official system of record is, functionally, that spreadsheet. The CRM is where the spreadsheet's inputs are stored, badly.
None of these incidents shows up on the invoice. They arrive as friction, a few hours and one bad letter at a time, which is why nobody totals them. Totaled, they cost more than the license.
What the Right Model Looks Like
Software fit for this work starts from the program's own nouns:
- Assemblies and service addresses as first-class records, with people attached in their actual roles — owner, tenant, tester, responsible party
- Compliance status computed from test dates and rules, not typed into a status field
- Deadlines that generate notices and escalate on their own, with no snooze button between the regulation and the mail
- History that belongs to the asset and survives every change of owner
- Reporting that can answer the question the state actually asks
Before signing for a platform, take one real record — an RPZ at a sold property with a snoozed test and a disputed letter — and ask the vendor to show you where each piece lives. If the answer involves a contact, a task, and a notes field, the system isn't wrong yet. But it will be, and your staff will be the ones absorbing the difference.