Field guide · job readiness
Backflow testing checklist: prepare the visit, document the result, confirm the filing
This is a visit-preparation and documentation checklist—not a replacement for a current approved field-test procedure. The point is to prevent missing identity, credential, gauge, notification, and submission details before a completed result becomes difficult to file.
Before scheduling: establish the local reporting contract
- Identify the water system or cross-connection program that will receive the result and confirm its deadline.
- Confirm the accepted report format, submission route, tester-registration requirement, and whether the program publishes an approved form or portal.
- Confirm whether the service is ordinary domestic, irrigation, fire protection, process, or another use that requires coordination before isolation.
- Confirm that the assignment names the assembly or that enough site information exists to identify it on arrival.
Sources for this section: Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington State Department of Health: Backflow prevention assembly field test report; Austin Water: Backflow Prevention Assembly Tester Information.
Before arrival: verify the equipment and paperwork
| Check | Why it matters | Do not assume |
|---|---|---|
| Current accepted procedure | Why it matters:The test sequence and report criteria are controlled by the accepted program. | Do not assume:That a web summary or prior class handout is still the current local procedure. |
| Gauge documentation | Why it matters:The report may require make, model, serial, and calibration details. | Do not assume:That a credential substitutes for a gauge record. |
| Assembly family and report fields | Why it matters:RP, DCVA, PVB, and SVB records do not use an identical reading set. | Do not assume:That a one-size form captures every required field. |
| Access and notification | Why it matters:Occupants, monitoring, water-system, or fire-service coordination may be necessary. | Do not assume:That closing a valve has no downstream impact. |
Sources for this section: USC Foundation: Field-test training tools; Washington State Department of Health: Backflow prevention assembly field test report; Washington Administrative Code: cross-connection control.
At the site: capture identity before you capture a reading
Start with the tag and the property context. Confirm the assembly type, make, model, serial number, size, location, protected service, and the program's account or facility identifier. A correct reading attached to the wrong serial number creates a filing problem that a clean PDF cannot solve.
A certified tester then follows the current procedure accepted for that assembly and jurisdiction. This page intentionally does not republish a field-test sequence: procedure details change, and USC's current training resources are the right reference for the formal test families.
Sources for this section: USC Foundation: Field-test training tools; Washington State Department of Health: Backflow prevention assembly field test report; EPA: Cross-Connection Control Manual.
After the test: review the record before it leaves the site
- Check that every required assembly-family reading is present and recorded as measured.
- Confirm the result logic is consistent with the accepted local procedure; do not silently treat a missing reading as a pass.
- For a failed initial result, preserve it and follow the program's repair/retest instructions instead of overwriting it.
- Complete required tester, gauge, owner or representative, and date fields before producing the final file.
Sources for this section: Washington State Department of Health: Backflow prevention assembly field test report; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Austin Water: Backflow Prevention Assembly Tester Information.
Filing and retention close the loop
A completed report is not necessarily a filed report. Submit through the receiving program's required channel, retain the submitted version and confirmation, and associate it with the same assembly record for future annual, repair, or replacement work.
For a multi-purveyor tester, keep the local requirements as named profiles rather than relying on memory. That keeps a form, deadline, or calibration-detail change from becoming a batch of rejected reports.
Sources for this section: Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington State Department of Health: Backflow prevention assembly field test report; Austin Water: Backflow Prevention Assembly Tester Information.
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: Cross-Connection Control Manual
Technical background on cross-connections, backpressure, backsiphonage, and mechanical protection.
- USC Foundation: Field-test training tools
Current Foundation materials distinguish the RP, DC, PVB, and SVB field-test families.
- 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.
Cross-connection control program guide
The authority, survey, approved protection, testing, recordkeeping, and corrective-action pieces behind a maintained program.
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.