Backflow Test Report Filing: How to Submit to Your Water Authority
Backflow test report filing is the formal process by which the results of a certified backflow prevention assembly test are transmitted to the local water authority or municipal utility responsible for cross-connection control enforcement. Submission requirements, accepted formats, and filing deadlines vary by jurisdiction, but the underlying compliance obligation is consistent across the United States: tested devices must be documented, and that documentation must reach the authority of record. Failure to file — even when the test itself was completed — constitutes a reporting violation under most utility cross-connection control programs.
Definition and scope
A backflow test report is an official record generated by a certified backflow prevention assembly tester (as listed in the backflow listings) following a field inspection of a backflow prevention assembly. The report captures the device's make, model, serial number, installation location, test conditions, pass/fail readings for each check valve and relief valve component, and the tester's license number and signature.
The obligation to file belongs to different parties depending on how a jurisdiction structures its program. In utility-direct models, the licensed tester submits the report directly to the water authority within a specified window — commonly 10 to 30 days after the test date. In property-owner-responsible models, the property owner or facility manager receives the completed report from the tester and bears responsibility for forwarding it to the utility. A third model, used by larger municipalities including those served by the Los Angeles Department of Water and Power and the Denver Water system, uses web-based portals where certified testers upload reports electronically at point of completion, eliminating secondary filing steps.
The American Water Works Association (AWWA) and the University of Southern California Foundation for Cross-Connection Control and Hydraulic Research (USC FCCCHR) both maintain model cross-connection control program frameworks that specify test report content standards and filing chain-of-custody requirements. Most state drinking water programs reference AWWA's Manual of Water Supply Practices M14 when establishing their own reporting standards.
How it works
The filing process follows a structured sequence from test completion to authority confirmation:
- Test execution — A certified backflow prevention assembly tester performs a field test using calibrated differential pressure gauges (ASSE Standard 1064 specifies gauge requirements). The tester records all readings on a standardized form.
- Form completion — The report form captures device data, service address, meter number, hazard classification, and test results for each testable component. Jurisdictions may require their own proprietary forms; universal forms such as those developed by the California-Nevada Section AWWA are accepted in multiple states.
- Submission to the authority — The completed report is submitted by mail, fax, email, or electronic portal depending on what the local water authority accepts. Paper-based submission remains active in rural and smaller utility systems.
- Authority review and logging — The water authority enters the report into its cross-connection control database, verifies the tester's license status against the state registry, and logs the test date as the compliance benchmark for the next required test cycle.
- Confirmation issuance — Many utilities generate a confirmation notice or update an online property record to reflect compliance. Properties with failed assemblies that were repaired and retested require a separate repair report and retest filing before the compliance record updates.
Late filing — submitting outside the required window after the test was completed — is treated differently from non-testing. Some water authorities assess administrative fees for late reports; the City of Portland, Oregon's Portland Water Bureau cross-connection control program specifies reporting deadlines in its program rules.
Common scenarios
Annual residential service connections — Single-family properties with in-ground irrigation systems, residential fire suppression lines, or booster pumps are commonly required to test annually. The tester files directly with the utility; the property owner receives a copy for records.
Commercial and industrial properties — High-hazard facilities such as hospitals, laboratories, and food processing plants typically operate under local water authority backflow requirements that mandate testing of multiple assemblies. Each assembly generates a separate report; batch filing under a single property account is accepted by some utilities.
New installation testing — When a backflow prevention assembly is installed for the first time, an initial acceptance test report must be filed before the connection is approved for service. This report is distinct from annual compliance testing and triggers a permit close-out in the building department's inspection record.
Failed assembly with repair — If a device fails the field test, the tester documents the failure on the initial report, notes the failed component, and specifies whether the assembly was repaired on-site or requires replacement. A follow-up retest report must be filed after correction. The original failure report and the passing retest report together constitute the compliance record for that cycle.
Tester license discrepancy — If a tester's certification has lapsed at the time of the test, the water authority will reject the report regardless of whether the device passed. The test must be repeated by a currently certified tester and a new report filed.
Decision boundaries
The primary distinction governing filing responsibility is whether the jurisdiction uses a tester-direct or owner-responsible submission model. Tester-direct programs centralize accountability with the licensed professional; owner-responsible programs shift the filing obligation to the property and create a secondary audit risk if the report is not forwarded in time.
A secondary boundary separates pass reports from fail-with-repair reports. Pass reports close the compliance cycle; fail-with-repair reports open a remediation record that remains open until a passing retest report is received. Some utilities notify property owners of an open remediation record via mail or an online portal flag. Failure to close an open remediation record within the utility's cure period — typically 30 to 60 days — can result in service interruption notices under cross-connection control enforcement authority.
The how to use this backflow resource reference explains how to locate jurisdiction-specific filing requirements, including which state drinking water programs have adopted electronic submission mandates versus those still operating paper-based programs. Jurisdictional variation in accepted form types, electronic system compatibility, and tester registry integration means that a report format valid in one state may not satisfy requirements in an adjacent jurisdiction.
References
- U.S. Environmental Protection Agency — Cross-Connection Control Manual
- American Water Works Association (AWWA) — Cross-Connection Control
- USC Foundation for Cross-Connection Control and Hydraulic Research (USC FCCCHR)
- Safe Drinking Water Act, 42 U.S.C. §300f et seq. — U.S. Code
- ASSE International — Standard 1064 (Field Test Equipment)
- Portland Water Bureau — Cross-Connection Control Program
- Denver Water — Cross-Connection Control
- Los Angeles Department of Water and Power — Backflow Prevention