Operations guide · asset inventory
Backflow assembly inventory: connect every report to the physical asset
An address list is not a backflow assembly inventory. One property can have multiple assemblies with different services, locations, serial numbers, schedules, and receiving-program instructions. The inventory's job is to make each field report traceable to the asset that was actually tested.
Use the tag as the starting point, not prior memory
At the assembly, record its type, manufacturer, model, serial number, size, service, and specific location. The exact fields a local program requires vary, but Washington's official report-content rule is a useful example of why identity and location are more than optional notes.
EPA's cross-connection guidance identifies records associated with assemblies in service, testing, repair, and personnel as part of a functioning program. A practical inventory is the link between those records over time.
Sources for this section: Washington Administrative Code: field test report content; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention; EPA: Cross-Connection Control Best Practices Guide.
Fields that make an inventory usable in the field
| Field | Use | Refresh trigger |
|---|---|---|
| Physical identity | Use:Matches the report to the actual tag and assembly family. | Refresh trigger:Replacement, relabeling, or corrected nameplate reading. |
| Service and location notes | Use:Separates domestic, irrigation, fire, boiler, or process work at the same site. | Refresh trigger:Tenant, remodel, access, or service change. |
| Receiving-program information | Use:Keeps the correct notice, deadline, and recipient with the asset. | Refresh trigger:New notice, utility change, or current-program confirmation. |
| Test, repair, and retest history | Use:Explains what was observed over time without overwriting prior evidence. | Refresh trigger:Each completed field event. |
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.
Verify an inventory during every visit
A saved record is a starting point, not a substitute for reading the assembly tag. Compare it with the physical unit before entering readings. If a component has been replaced or the location description no longer gets a tester to the asset, correct the record and preserve the reason for the correction.
That small habit prevents a common operational error: producing an accurate test record for a real assembly, but attaching it to the wrong historical identity.
Sources for this section: Washington Administrative Code: field test report content; EPA: Protecting Water Quality through Cross-Connection Control and Backflow Prevention.
Use BackflowPass records as a field-facing inventory layer
BackflowPass lets testers save device and customer information alongside report history so a repeat visit can begin from known details. The record should still be checked against the physical tag at the jobsite.
BackflowPass is not a substitute for a water system's authoritative inventory, approval list, or compliance system. Verify program data with the relevant authority.
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.
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.