Facility guide · testing coordination
Backflow testing for facility managers: coordinate access without guessing the procedure
A facility manager does not need to perform a field-test procedure to make the visit successful. The practical job is to match the right assembly to the notice, arrange safe access and service coordination, provide accurate site context, and retain the completed record for the next cycle.
The facility role is coordination and traceability
EPA identifies building managers among the people who share responsibility for safe cross-connection control practices. In day-to-day terms, that usually means knowing where assemblies are, what service they protect, who must authorize access, and which water program receives the result.
A commercial site can have multiple assemblies for irrigation, fire sprinklers, water reuse, or boilers. Portland uses those examples in its public guidance, which is why one calendar entry called 'backflow' is often not enough for a large facility.
Sources for this section: EPA: Cross-Connection Control Best Practices Guide; Portland Water Bureau: Testing backflow prevention assemblies; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention.
Give the tester the context that changes the visit
- The notice or program reference, required deadline, and the correct report recipient.
- A current list of assembly locations, services, serial numbers where known, and access contacts.
- Occupant, kitchen, production, irrigation, security, or fire-protection coordination that may be affected by access or isolation.
- Prior reports, repair/retest records, and any site changes that may mean the saved identity needs a field check.
Sources for this section: EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Portland Water Bureau: Testing backflow prevention assemblies; Washington Administrative Code: field test report content.
After the test, make the handoff traceable
Review the asset match
Check that the report identifies the assembly and service the visit was intended to cover.
Ask about the required next action
If the result needs repair, retest, or local follow-up, confirm the responsible owner and the receiving program's deadline.
Retain the completed record
Keep the report, delivery evidence, and any repair/retest sequence with the same asset record.
Refresh the next-cycle details
Update access contacts and program instructions without converting an old report into a guessed new requirement.
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; Portland Water Bureau: Testing backflow prevention assemblies.
A field report is useful when it stays tied to the visit
BackflowPass helps a certified tester document the inspection details, readings, signatures, and a PDF report at the jobsite. That can give a facility team a clearer handoff than an unstructured note.
The app does not replace the facility's site-safety procedures, a fire-system impairment plan, an authority's compliance system, or a qualified tester's judgment.
Sources for this section: EPA: Cross-Connection Control Best Practices Guide; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
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
Program elements, including records for testing, repair, personnel, and assemblies in service.
- EPA: Cross-Connection Control Best Practices Guide
EPA guidance on cross-connection-control program responsibilities, testing, and records.
- Portland Water Bureau: Testing backflow prevention assemblies
A current public-water-system example of annual notices, owner coordination, tester reporting, and a submission timeline.
- City of Fort Worth: Backflow and cross-connection control
A current utility example covering irrigation, certified tester registration, and reports for new, altered, replacement, and removed assemblies.
- Washington State Department of Health: Backflow prevention assembly field test report
An official example of a state field-report resource; its requirements are not a national form.
- Washington Administrative Code: field test report content
A detailed state example of report fields covering identity, readings, repair, tester, and gauge information.
- Texas Commission on Environmental Quality: Cross-connection control and backflow prevention
A state example of a receiving authority's program and report materials; do not treat it as a national procedure.
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.
Cross-connection control program guide
The authority, survey, approved protection, testing, recordkeeping, and corrective-action pieces behind a maintained program.
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.