Field guide · reports and filing
Backflow test reports: the fields, records, and local submission rules that matter
A backflow test report is the evidence trail for one identified assembly on one date. There is no universally accepted U.S. form: the water system or local program decides the report layout, required fields, recipient, deadline, and whether an alternative form is accepted.
Why a generic test report is not automatically compliant
An official form is not merely a piece of paper. It is the receiving program's data contract: it ties a property, assembly, qualified tester, gauge, readings, result, and sometimes an online submission workflow to that program's records. Texas guidance says alternate forms that differ from the official form need approval; Washington publishes specific field-test-report guidance; Austin publishes its own tester submission information.
Use a general form or software workflow only after confirming that the receiving water system accepts its fields and delivery method. Do not relabel a generic PDF as a 'universal certificate' or assume a template accepted in one city will be accepted in another.
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.
The record blocks most reviewers need to reconcile
| Record block | Why it matters | Local verification question |
|---|---|---|
| Property and service | Why it matters:Matches the report to the correct customer, service, and program record. | Local verification question:Which account, meter, parcel, or facility identifier does the program require? |
| Assembly identity | Why it matters:Separates one device from another at the same address. | Local verification question:Are type, make, model, serial, size, and location all mandatory? |
| Test context | Why it matters:Explains date, test type, local procedure, and measured conditions. | Local verification question:Does the program require line pressure, reason for test, or a specific procedure reference? |
| Tester and gauge | Why it matters:Lets a reviewer validate the person and instrument behind the reading. | Local verification question:Which certification, registration, gauge serial, and calibration details are required? |
| Readings and result | Why it matters:Preserves the actual evidence and distinguishes an initial result from a retest. | Local verification question:Which readings, tightness checks, signatures, and dates must be reported? |
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; Washington Administrative Code: field test report content.
A failed initial test and a passing retest are not the same record
When an assembly fails, preserve the original as-measured result rather than overwriting it with the final result. The next record should identify the repair or replacement work and retain the complete retest readings. That gives an owner and program reviewer a coherent timeline instead of a report that appears to have passed without explanation.
Whether a separate repair report, a separate retest form, an outage notice, or a deadline applies is local. Washington code is a useful example of the rule pattern: defective or inoperative assemblies must be repaired or replaced, with testing carried out by a certified tester. It is not a national substitute for your own program's instructions.
Sources for this section: Washington Administrative Code: cross-connection control; Washington State Department of Health: Backflow prevention assembly field test report; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention; Washington Administrative Code: field test report content; California State Water Resources Control Board: Cross-Connection Control Policy Handbook (April 2026).
Confirm the submission path before the first job in a service area
Find the actual receiving program
Use the water bill, water-system website, or local cross-connection office—not a search result for a similarly named city.
Confirm the accepted form and delivery method
Ask whether the program accepts its PDF only, an approved alternative, a portal upload, email, mail, or direct tester submission.
Confirm tester registration
A valid credential may still need local registration before a report will be accepted.
Retain the submitted version
Keep the final file, the submission confirmation, and any correction request with the assembly record.
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.
Where a reporting tool can help—and where it cannot decide
A reporting workflow can make the field record easier to complete: identify the assembly, collect the right readings for its family, retain initial and final readings, capture signatures, and generate a legible PDF. BackflowPass provides that field-report workflow for the supported assembly families.
It does not approve an alternative form, determine a site's hazard classification, validate a tester's credential, submit to every water system, or replace review by the receiving authority. Those boundaries are intentional: the authority's current program rules stay in control of acceptance.
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: Protecting Water Quality through Cross-Connection Control and Backflow Prevention
Definitions, assembly/device distinction, program elements, and incident-response context.
- 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.
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.
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.