How are cross-connection tests typically scheduled and recorded, and why is documentation important?

• A. Per code, tests done by a certified tester; results are documented for compliance, future maintenance, and inspections.
• B. Tests are optional and not recorded.
• C. Tests are done by any employee and not filed.
• D. Tests are performed only when a complaint is filed.

Answer: (B)

The main idea here is that cross-connection testing is part of a formal backflow prevention program, done on a scheduled basis by a certified tester, with the results documented and kept for record-keeping and inspections. Regular scheduling ensures backflow prevention devices are checked at appropriate intervals and still functioning correctly, rather than waiting for a problem to appear.

Documentation matters because it provides proof that tests were completed, shows the results and any actions taken, and creates a traceable history for future maintenance, upgrades, or regulatory inspections. Keeping thorough records helps confirm ongoing protection of the potable water supply and supports compliance with local codes and authority inspections.

In practice, tests are not performed haphazardly or only in response to complaints. They are scheduled at defined intervals and carried out by someone with the proper certification. The test records typically include the device tested, the measurements taken, whether the device passed or failed, and any corrective steps required. Without this documentation, there’s no verifiable assurance that the system remains protected or that regulatory requirements are being met.

Choosing expectations that testing is optional, performed by any employee, or only done when there’s a complaint doesn’t align with how backflow prevention programs are designed to protect public health and ensure accountability.