Field guide · initial installation
Initial backflow test reports: document the assembly that was actually installed
The first test record after installation needs more than a passing result. It creates the identity that future notices, schedules, repairs, and reports may rely on. Confirm the installed assembly and the local acceptance process before you treat an initial-test PDF as complete.
An initial test records a new asset, not just a new date
For an initial report, read the installed tag and capture the type, manufacturer, model, serial number, size, service, and precise location from the assembly in front of you. Do not copy an expected model from a proposal or old equipment list.
Fort Worth is one current example of a water utility that calls for test results on new and altered assemblies. The particular approval, inspection, test, and submittal sequence is local, so confirm it with the program serving the site.
Sources for this section: City of Fort Worth: Backflow and cross-connection control; Washington Administrative Code: field test report content; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
Confirm four facts before creating the initial record
- The receiving authority accepts the assembly type, model, installation, and service application; a web guide cannot make that approval.
- The tester holds the credential or registration the program requires for this work and assembly family.
- The correct local form, inspection record, and filing destination are known before a field record is finalized.
- The site has the access, drainage, isolation coordination, and any required service-specific procedures for the test.
Sources for this section: EPA: Cross-Connection Control Best Practices Guide; City of Fort Worth: Backflow and cross-connection control; Texas Commission on Environmental Quality: Cross-connection control and backflow prevention.
What to preserve with the first test
| Record | Purpose | Future use |
|---|---|---|
| Nameplate and location | Purpose:Establishes the identity of the installed assembly. | Future use:Matching future notices and annual reports. |
| Initial readings and result | Purpose:Shows what the tester observed under the accepted procedure. | Future use:Comparing a repair or future test with the starting record. |
| Tester, gauge, and signature details | Purpose:Preserves who made the record and the instrument context required by the program. | Future use:Reviewing the record for completeness. |
| Approval or filing reference | Purpose:Connects the report to the actual recipient's process. | Future use:Resolving questions without guessing months later. |
Sources for this section: Washington Administrative Code: field test report content; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; Washington State Department of Health: Backflow prevention assembly field test report.
Use the same field discipline on the first report
BackflowPass supports an Initial Installation test type, family-specific readings, signatures, and a one-page PDF. It can help a tester capture the field record in one workflow rather than rebuilding it from scattered notes.
It does not approve an installation, inspect code compliance, validate the accepted model, or submit the record to a water program. Those decisions stay with the authorities and professionals responsible for the site.
Sources for this section: City of Fort Worth: Backflow and cross-connection control; 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.