Every compliance system demos with the same tidy status list: Compliant, Non-Compliant, Due. Three states, three colors, one clean dashboard. Then the software meets a real cross-connection control program, and the tidy list stops describing anything.
Here is what an actual backflow program looks like inside a year. A double check valve assembly was removed during a kitchen remodel in 2022, and the system is still mailing annual test-due notices to that address because there is no way to mark a device gone without deleting it — and deleting it erases six years of test history the state auditor will want. A vacant property with the service off gets a shutoff warning by certified mail, which is an interesting threat to send about water that is already off. A test report sits in pending review for eight months because the reviewer position was vacant, while the dashboard counts that assembly as compliant. And the utility clerk knows a particular property is exempt — she has known it for years, there was a letter — but the system has no field for why, so the exemption lives in her memory and a sticky note.
The States Nobody Demos
Run a backflow program, or inspections, or code enforcement, and these are the statuses you actually need:
- Pending — a test report was submitted but no one has reviewed it yet
- Inactive — the property is vacant, the service is off, the requirement is suspended but not gone
- Historical — the assembly was removed, but its record has to survive
- Replaced — an RPZ went in where the double check was; the new device inherits the location but not the history
- Manual override — staff made a judgment call against the default, with a reason
- Approved but not advanced — passed review, waiting on a fee, a second sign-off, a season
- Exempt, disputed, deferred, grandfathered — each with its own paper trail
None of these are edge cases. They are the program. The clean statuses are just the cases that didn't need anyone's attention.
What Staff Do When the Software Won't
When the system only offers clean statuses, staff improvise, and the improvisations always follow the same pattern. The removed assembly gets parked as Due, because Due is the least wrong option — and Due quietly stops meaning anything. The exemption letter gets summarized in a notes field no report can search. A side spreadsheet appears for the exceptions, which is to say, for the actual work. And the notice batch keeps including the kitchen-remodel address and the vacant lot, which trains everyone — staff and property owners alike — to ignore notices.
The dashboard stays green the whole time. The gap between the dashboard and the program is invisible until an audit, an appeal, or a contamination incident finds it.
Exceptions Are What Gets Examined
Nobody appeals a routine passing test. The records request, the audit finding, the angry call to the council member — those land on the override, the exemption, the report that sat in pending for eight months. The cases your system represents worst are precisely the ones that will be pulled and read later, which means each one needs a status, a reason, a date, and a name. "Marked exempt 3/14, per 2019 engineering letter, J. Alvarez" is a defensible record. A blank field and the clerk's memory is not.
Ask to See the Override
Software built for a real program lets exceptional states carry their reason and their author, shows exceptions in reports instead of hiding them, and teaches the automation the difference — inactive services do not get shutoff warnings, historical assemblies do not get test reminders. How long reports sit in pending is a program health number, not trivia.
So when you evaluate compliance software, skip the dashboard demo. Ask to see the inactive property, the replaced asset, and the override. That is where you find out what the system is made of.