Utility-first support page for the Dallas-Fort Worth cluster. Use it to compare nearby authorities, then drop into the exact utility rule page before acting.
DFW is commercially important because multiple city and district utilities publish different tester-list, annual-testing, and failed-test workflows. This page groups those surfaces without pretending the metro summary is the underlying authority.
Use this metro page to compare nearby utility workflows and commercial options, then drop into the exact utility page before acting on a compliance step.
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.
Fort Worth requires testing at installation, repair, or relocation and then annually, with licensed registered testers submitting reports through VEPO.
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.
Annual testing is required for enrolled backflow prevention assemblies in the Grand Prairie utility program.
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.
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.
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.
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.
Frisco requires installation testing and recurring annual testing for certain testable assemblies, with BSI handling much of the program workflow.
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.
Officially listed on the Talty SUD tester PDF
Officially listed on the Talty SUD tester PDF
Officially listed on the Mesquite tester PDF
Officially listed on the Mesquite tester PDF
Officially listed on the Garland tester PDF
Officially listed on the Mesquite tester PDF
Officially listed on the Mesquite tester PDF
Officially listed on the Talty SUD tester PDF
Officially listed on the Garland tester PDF
Officially listed on the Garland tester PDF
Officially listed on the Garland tester PDF
Officially listed on the Talty SUD tester PDF
Why official tester lists and commercial directories must stay separate, and what each page type is allowed to claim.
What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.
How to think about annual testing, repair, and retest pricing without confusing a market quote with the compliance rule.
What counts as an official source, how local utility pages override generic assumptions, and why stale pages are suppressed.
Why some utilities track backflow tests by anniversary date, while others push owners into a calendar-season or hard-date deadline.