Escalate and resolve a customer account's non-compliance for a missed or failed annual backflow test
domain: Water utility cross-connection control program · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send an initial notice to the account holder when the annual test becomes due or overdue
Issue a follow-up/final notice if the account remains non-compliant after the initial notice period, typically specifying a shorter final deadline
Assess administrative fees or fines for continued non-compliance per the purveyor's own ordinance
Escalate to service restriction or disconnection (shutting off and locking the meter) if the final deadline passes without a compliant test on file
Restore service only after a passing test report is received and any outstanding fees are resolved
Document the full compliance timeline in the account's cross-connection control record for audit purposes
Known gotchas
Disconnection authority and fee schedules are set by local ordinance, not a national standard — the escalation timeline and dollar amounts differ significantly between utilities and shouldn't be assumed to match a typical figure
Some programs disconnect service for a missing test report even when the underlying assembly is functioning fine — compliance tracking is about the paperwork being on file, not just physical device condition
Reconnection after a compliance-related shutoff often requires both a passing retest and payment of accumulated fees/penalties — resolving only one of the two won't restore service
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?