At installation, move, repair or replacement; annually for health-hazard assemblies
Arlington Water Utilities
Arlington is a code-driven city: annual testing is tied to health-hazard assemblies, but installation, moves, repairs, replacement, irrigation permits, and fire line work all have separate ordinance triggers.
At least once a year for many listed assemblies, plus initial testing on installation
Austin Water Cross-Connection Control
Austin Water runs a stricter ordinance-backed program with annual testing for many assemblies, online WEIRS reporting, and City registration for testers.
Installation testing plus ordinance-driven ongoing reporting
City of College Station Backflow Prevention
College Station is a useful procedural page because it clearly publishes the tester list, report form, 30-day submission rule, and City registration requirements for BPATs.
Upon installation, repair, or relocation; and annually thereafter
City of Fort Worth Water Backflow Program
Fort Worth requires testing at installation, repair, or relocation and then annually, with licensed registered testers submitting reports through VEPO.
Upon installation and annually thereafter for certain testable assemblies
City of Frisco Backflow Program
Frisco requires installation testing and recurring annual testing for certain testable assemblies, with BSI handling much of the program workflow.
Prior to permanent activation and annually thereafter
City of Garland Water Supply Protection
Garland is a strong pilot utility because it publishes the annual cadence, 10-day report rule, tester-registration workflow, irrigation permit details, and fire line registration requirements on official pages.
Annual for many hazards; every five years for some residences without septic
City of Leander Cross-Connection Control
Leander is useful because it publishes hazard-based frequency rules, including annual tests for many residential and commercial hazards and five-year testing for some residences without septic.
At installation and at least once per year thereafter
City of Lewisville Backflow Testing
Lewisville is strong pilot content because it publishes the annual cadence, official tester list, BSI submission deadline, filing fee, and enforcement language on one page.
As required by the City workflow using McKinney test forms
City of McKinney Cross Connection Prevention
McKinney is a paperwork-heavy utility. The main risk is not just failing the field test; it is using the wrong City form, the wrong registration path, or the wrong submission method.
Upon installation and annually thereafter, excluding residential assemblies that require testing on installation
City of Mesquite Backflow Prevention
Mesquite is a strong pilot utility because it clearly publishes annual-vs-residential cadence, inspector-witnessed testing, the official tester list, and separate commercial, irrigation, and fire line assembly rules.
Annual for high-hazard devices; every 7 years for low-hazard devices
City of Round Rock Backflow Prevention
Round Rock splits testing cadence by hazard class: annual for high-hazard devices and every 7 years for low-hazard residential devices.
Annual for devices protecting against health hazards
City of Sugar Land Water Utilities
Sugar Land runs an annual testing program for health-hazard backflow devices and tracks compliance through BSI.
Annual for high-hazard assemblies; irrigation only on install, repair, or replacement
Dallas Water Utilities Backflow Prevention Program
Dallas is a useful edge case because it is not simply annual-for-everything: high-hazard assemblies are annual, irrigation is event-driven, and SwiftComply is mandatory for covered test reports.
Annual
Grand Prairie Water Utilities
Annual testing is required for enrolled backflow prevention assemblies in the Grand Prairie utility program.
Annual
San Antonio Water System Backflow Prevention
San Antonio requires annual backflow testing and routes both customer compliance checks and registered testing company discovery through BSI under the SAWS program.
Upon installation and annually for health-hazard or commercial properties
Talty Special Utility District Backflow Testing
Talty SUD is a strong district example because it publishes explicit annual testing triggers, deadline months, RPZ rules for OSSF properties, and a hard service-disconnection consequence for noncompliance.
