Program guide · facilities and water systems
Cross-connection control programs: the records and workflows behind backflow prevention
A cross-connection control program is more than annual test notices. EPA guidance describes a system of authority, hazard identification, protection, qualified testing, repair, recordkeeping, communication, and response. The exact legal requirements belong to the state and local program.
The program exists to control risk before a backflow event
Cross-connections can occur wherever potable water can meet a nonpotable source. EPA explains that an effective control program is designed to identify those risks, require appropriate protection, and maintain the records and enforcement structure needed to keep protection working over time.
That makes a report database useful but incomplete by itself. A program also needs clear authority, current hazard information, a way to communicate with premises, and a response path when an assembly fails or an incident is suspected.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; EPA: Cross-Connection Control Manual.
Core elements EPA identifies
| Element | Operational question | Record to maintain |
|---|---|---|
| Authority and policy | Operational question:Who may require survey, protection, testing, and correction? | Record to maintain:Applicable ordinance, policy, authority, and escalation process. |
| Hazard survey and plan review | Operational question:Where are actual or potential cross-connections and how are new services reviewed? | Record to maintain:Survey, plan-review, and hazard-classification history. |
| Approved protection | Operational question:Which method and model are accepted for the documented hazard and service? | Record to maintain:Approval, installation, and assembly identity information. |
| Qualified personnel | Operational question:Who may test, survey, repair, or administer the program? | Record to maintain:Current credential, registration, and scope records. |
| Testing, repair, and recordkeeping | Operational question:How are failed tests, repairs, retests, and due dates reconciled? | Record to maintain:Initial report, corrective-work reference, final report, and filing confirmation. |
| Communication and response | Operational question:How are owners notified and how does the program respond to suspected incidents? | Record to maintain:Notices, correspondence, response log, and follow-up evidence. |
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; EPA: Cross-Connection Control Manual; Washington Administrative Code: cross-connection control.
Records should reconcile a property, an assembly, and an obligation
Every backflow record is easier to use when it can be traced from a property and service to a specific assembly, a tester, a dated result, and a next obligation. Serial numbers and exact locations are especially important where one site has several assemblies or an assembly is replaced.
Local rules decide which fields, retention period, and submission proof are mandatory. Washington field-report guidance and city-specific tester pages are useful examples of the record detail programs can require, but they are not a universal field specification.
Sources for this section: Washington State Department of Health: Backflow prevention assembly field test report; Austin Water: Backflow Prevention Assembly Tester Information; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
A low-regret program review sequence
Confirm authority and owner
Name the public water system, authority, program owner, and policy that govern each property population.
Audit the inventory
Reconcile properties, protected services, assembly identities, known hazards, and open corrective items before sending notices.
Validate the workflow
Test how a new installation, annual test, failed test, repair, retest, and submission confirmation move through the records.
Verify qualified roles
Make credential, registration, and repair-scope checks part of intake, not an exception after a report is rejected.
Review incidents and changes
Keep the policy current after a code change, system change, or incident; do not keep running a form because it worked last year.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Washington Administrative Code: cross-connection control; Washington State Department of Health: Backflow prevention assembly field test report.
This is a program worksheet, not legal or engineering approval
Water-system obligations, enforcement authority, public-notice duties, data retention, and technical selection rules vary by jurisdiction. A facility should obtain its own program requirements from the water system, state primacy agency, plumbing authority, and counsel or engineering professionals where needed.
BackflowPass can help a certified tester prepare a structured field result. It does not provide a public-water-system program, make regulatory filings, approve assemblies, or decide enforcement action.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington Administrative Code: cross-connection control.
Sources and review boundary
This guide was reviewed on August 22, 2026. It links to primary public sources where possible and labels state and local examples as examples. It is educational material, not engineering, legal, installation, certification, or water-system approval advice.
- EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention
Definitions, assembly/device distinction, program elements, and incident-response context.
- EPA: Cross-Connection Control Manual
Technical background on cross-connections, backpressure, backsiphonage, and mechanical protection.
- USC Foundation: Approval Program
Explains USC laboratory plus one-year field-evaluation approval work for assemblies.
- Washington State Department of Health: Backflow prevention assembly field test report
An official example of report guidance; its required and optional fields are specific to Washington.
- Texas Commission on Environmental Quality: Cross-connection control and backflow prevention
Shows that alternate forms and submission requirements are controlled by the receiving water system.
- Austin Water: Backflow Prevention Assembly Tester Information
A current local example of receiving-system report fields and submission workflow.
- Washington Administrative Code: cross-connection control
A state example for hazard assessment, approved protection, certified testing, repair, records, and annual scheduling—not a national rule.
- Washington Administrative Code: field test report content
A detailed official field-report checklist for facilities, assemblies, readings, repairs, test kits, and tester attestation; use as a Washington example, not a national form.
- California State Water Resources Control Board: Cross-Connection Control Policy Handbook (April 2026)
A current statewide example of definitions, assembly limits, testing, repair, recordkeeping, and tester-recognition rules.
Continue with the right next question
Related field references
Backflow prevention assembly guide
The practical distinction between testable assemblies, non-testable devices, air gaps, and the pressure reversals cross-connection programs manage.
RPZ vs. DCVA vs. PVB
A source-led comparison of the major assembly families, their protection limits, and why local hazard approval controls selection.
Backflow test report guide
Common report record blocks, local-form acceptance, failed-test history, and the submission checks a generic PDF cannot answer.
Failed backflow test guide
How to preserve the original result, confirm the local corrective path, document repair or replacement, and retain a complete retest record.
Backflow testing checklist
A job-readiness checklist for procedure, access, assembly identity, gauge records, report review, and filing—not a replacement field procedure.
Backflow testing software checklist
A transparent field-reporting software evaluation checklist, with boundaries around local acceptance and program administration.
Fill this out on the phone instead.
The generator asks for exactly these fields, grades every differential as you type, opens repair and retest fields when something fails, and hands you the finished one-page PDF. No account, no install, works with no signal.