Key takeaways
- Every handoff between tools is a re-keying job. The same facility, device or contact gets typed several times, and each copy can drift from the others.
- Follow-ups fail in the seams. When the notice, the due date and the field finding live in three places, the reminder depends on someone’s memory.
- Audit time exposes the gaps. A complete history of one record becomes a search project, and missing pieces look like missing work.
- The person holding it together is the integration. When they move on, the next coordinator has to rebuild the map of which tab, which inbox and which folder.
- Count the handoffs in one record. Trace it from first contact to last and mark every place it gets typed by hand.
A test result arrives on a form. Someone types it into the tracking spreadsheet, someone else types the contact into the mailing list, and at year end a third person retypes the totals for the annual report. Each of those tools does its own job well enough. The cost of disconnected compliance systems is in the spaces between them, and in most programs it gets paid in small amounts every week.
The same fact gets typed more than once
Every copy is a chance for the copies to disagree.
Disagreement is rarely dramatic. It’s a street address abbreviated two ways, so a search finds one record and misses the other.
It’s a contact updated in the billing system and not in your list, so the next notice goes to a person who left the account months ago. It’s a test date entered a day off, which is enough to push an assembly into the wrong column.
You can measure this for your own program without a stopwatch. Pick one record, a single assembly, facility, industrial user or inspection site, and follow it from the first time it entered your world to the most recent thing that happened to it.
Count how many times a person typed some part of it by hand.
Follow-ups slip in the seams between tools
A follow-up is only as reliable as the thing that remembers it. When the notice is in email, the due date is in a spreadsheet and the deficiency is in a field notebook, nothing connects them, so the reminder depends on someone’s calendar and good intentions.
A second notice goes out late because the first one’s date lived in a different file. A contractor says the problem is fixed and sends photos by text message, and the photos never reach the inspection record. A notice goes to whoever is on the billing account, who turns out to be a tenant, when the person who can act on it is the landlord or property manager.
Our backflow page‘s FAQ covers this one: because contacts are tied to the location or assembly rather than only to the billing record, notices “can be routed to a landlord or property manager independent of who the current tenant or billing customer is.” The problem exists because the contact lives in one place and the assembly lives in another.
For stormwater, the equivalent is the deficiency that gets reported, discussed in three email threads and never formally closed. The inspection and the follow-up both happened, but the record of them is scattered, so on paper the loop never closed.
At audit time, the record is a scavenger hunt
An audit, a state report or a question from your city manager all ask for the same thing: the complete story of one site, device or permittee. If that story is spread across a spreadsheet, a mailbox, a paper file and a GIS layer, assembling it is a project in its own right. The history usually exists somewhere. The question is how many places you have to open to prove it.
The painful part is that gaps in the paper trail look like gaps in the work. A follow-up call that happened, and was logged nowhere, did not happen as far as an auditor can tell. The inspection you did on a tablet and never attached to the permit file is, for practical purposes, an inspection you can’t prove.
Annual reporting feels the same pull. Our stormwater page describes the reporting scramble this way: “Managing data across spreadsheets, emails, and siloed systems turns reporting into a desperate scramble.” Its FAQ notes that inspection data, enforcement actions and outreach tracking often live in separate departments with no shared system, leaving the person responsible for the annual MS4 report “reconstructing it from memory, emails, and multiple spreadsheets.”
Our pretreatment page says limits, reports and enforcement actions “often live in separate systems (or spreadsheets),” which means “extra work just to track what’s due, what’s submitted, and what’s unresolved.”
Billing adds a wrinkle. If your customer accounts live in a billing system and compliance status lives somewhere else, every decision about an account means checking two systems and trusting that someone updated both.
What walks out the door with a person
In most stitched-together programs, one person holds the stitching.
They know which tab is current and which one is last year’s. They know that the “Notes” column means something different for commercial accounts. They know which email search turns up the old correspondence and which folder holds the scanned forms.
That person is the integration. As long as they’re in the building and in a good week, the program runs. When they retire, change roles or take a long leave, the map they never wrote down is gone, and the next coordinator rebuilds it from the artifacts.
The gap tends to surface during a staffing change, when you have the least spare attention to untangle it.
Count the hand-typed handoffs in one record
One record and an afternoon will show you how stitched together your program is.
- Pick one record from the last year, ideally one that had a complication such as a failed test, a late response or a deficiency.
- Write down every tool, inbox and folder that holds something about it, including the ones only one person ever opens.
- Mark each place where someone typed information by hand from one tool into another.
- Ask who knows how each of those handoffs works, and what happens when they’re out.
Keep the list. It’s the map your successor would otherwise have to draw from scratch, and it shows which handoffs are worth fixing first.
What closing the gaps can look like
Your GIS is still the right home for your maps, and your billing system is still the right home for billing. What matters is whether the compliance record, meaning the results, the notices, the field findings and the history, lives in one place.
If you start looking at software, ask each vendor exactly what connects to what, and in which direction.
For comparison, here is how our product pages describe three of the programs. Our stormwater page describes inspections where “the work you do in the field becomes the finished report, notice, and compliance record,” with a PDF published and deficiency notices emailed “in the same step.” In pretreatment, the page says the system “connects every part of your program” from permitting and sampling to violations and enforcement, “So any updates are reflected across the workflow.” And for FOG, the product page describes an online pump-out module that lets “FSEs, service providers, and city users” upload pump out documents “to your database.”
Get a demo for a walkthrough of the software, tailored to how your program works.
