Cross-connection control is the least visible program in most water utilities. It runs at the meter, the hose bib, and the boiler room, and it draws attention only when a test fails or a customer turns up in the wrong file. The paperwork that keeps it honest is simple to describe and easy to lose: a device, a tester, a date, and a register that ties them together.
Four records, one device
A backflow prevention assembly is a mechanical barrier, commonly a reduced pressure or double check device, installed where a service connection could allow non-potable water to flow back into the public system. The barrier depends on its check elements and relief valves working when a pressure drop reverses flow. A test at installation and at set intervals is how a utility learns whether that barrier still works.
The test is only one of four records a complete file needs. The first is device identity: make, model, size, serial number, and location on the premises. The second is the hazard classification the utility assigned, which sets how strict the protection must be. The third is the tester's credential and the test report, which should show the gauge calibration date and the recorded readings. The fourth is the register entry that links all three to a due date and a status. When any one of these lives only in a contractor's inbox, the program has a gap that will not appear until a test is missed.
Where the chain breaks
Most breaks happen at handoffs. A property changes owners and the new occupant does not know a device exists. A tester leaves a firm and the reports stay filed under the firm's name. A device is replaced and the register keeps the old serial number. A utility that moves to new billing or work-order software may import the device list without the test history attached. None of these failures requires bad faith. They come from records that were never designed to travel with the asset.
Rules differ by state. Requirements for who may test, how often, and which hazard classes trigger mandatory protection are set in state codes and local ordinances, and they change. Utilities should confirm the current version with their state drinking water agency rather than rely on a template borrowed from a neighboring jurisdiction.
Funding pressure reaches the register
Budget pressure often lands on staffing first. In a recent report, Abigail Mihaly of Circle of Blue describes communities facing a "federal water infrastructure funding cliff," and the summary identifies the State Revolving Funds as supporting projects such as lead pipe replacement and sewer repairs. Capital programs are the most visible part of that picture. Cross-connection control is an operating obligation funded from rates or general accounts, so it is less likely to be cut outright. It is more likely to slow down. A vacant inspector position goes unfilled, a notice mailing waits for a clerk, and a test list gets reconciled once a year instead of quarterly.
That slowdown is hard to see in a monthly report. The number of tests completed may look steady while the number of devices with no current test drifts upward. A useful check is to compare the active device count in the register against the count of devices with a passing test in the most recent reporting period, and to flag the difference by zone.
A working file
A workable file answers five questions for each device: where it is, what hazard it guards against, who tested it last and under what credential, when the next test is due, and who the utility will contact if that date passes. The last question is the one most often left blank. Assigning a named owner to each overdue notice turns a list into a schedule.
Utilities with thin staff can start with the highest hazard classes and any device that has failed a prior test. Those files merit a monthly review. The rest can be reconciled quarterly, provided the register remains the single source and tester reports are scanned into it when they are filed. The standard is not complicated. The real question is whether the record can still account for a device after the people who installed and tested it have moved on.