BackflowPath Local backflow requirements
Request help
Evergreen guide

How we verify local backflow rules

The fastest way to publish junk in this category is to paraphrase generic plumbing advice and pretend it applies to every utility. This site works only if the local program page stays canonical.

Last reviewed: 2026-04-04 Reviewer: TL Freshness window: 120 days
Open a mapped utility page Open mapped metro layer
Why this page exists

Support the local pages without blurring the official rule

We verify utility pages against the governing authority first, then use statewide and evergreen sources only to explain the workflow around that local rule.

Mapped utilities 6
Mapped metros 4
State hubs 5
Backflow instrumentation and technical ledger panel
Technical reading path

Guides should reduce interpretation risk, then route the user back down into the exact utility rule and tester workflow.

Guide chapter

Official source beats generic explanation

A city or utility program page, ordinance, tester list, or submission portal beats a generalized article every time. We keep the local page canonical and use guides to support comprehension, not replace the rule.

  • TCEQ establishes the statewide floor, but cities still control notices, portals, and local enforcement.
  • If a utility has a hazard split or a city-specific portal, we use that instead of a one-size-fits-all annual claim.
Guide chapter

Tester pages only open under explicit rules

An approved-tester page only goes live when the governing authority exposes an official list or equivalent official lookup. Non-official directory pages stay separate and do not borrow the authority language.

  • Lewisville and College Station both publish official tester lists.
  • Dallas publishes registration and portal instructions, but that is not the same as an official public list.
Guide chapter

Freshness matters more than page count

If a local rule page goes stale, the safer behavior is to suppress it from public routes and sitemap generation until it is re-verified.

  • Each utility JSON stores its own last-verified date and stale window.
  • A thin but current site is better than a large site filled with expired rules.
Utility layer

Use this guide with local utility pages

City of Phoenix Backflow Prevention Program Phoenix is one of the strongest Arizona utilities because it publishes tester requirements, a current tester list, city code references, and a clear work-order driven reporting workflow.
arrow_forward
City of San Diego Public Utilities Backflow Program San Diego is one of the best California fits because the city publishes annual testing rules, an approved tester list, a tester-orientation gate, and explicit enforcement consequences.
arrow_forward
City of Lafayette Backflow Compliance Program Lafayette is a strong Front Range utility because it publishes clear annual due dates by device type, a BSI workflow, and enforcement language with fees and shutoff risk.
arrow_forward
Lee County Utilities Cross-Connection Control Program Lee County is a strong Southwest Florida utility because it combines annual testing, portal-driven compliance, and county-level cross-connection workflow on public pages.
arrow_forward
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.
arrow_forward
City of Prescott Backflow Prevention Program Prescott is a strong Northern Arizona utility because the city ties annual testing, approved testers, irrigation triggers, and fire-protection assemblies into one clear utility workflow.
arrow_forward
Metro layer

Metro clusters where this guide matters

Central Texas backflow testing Support layer for the Central Texas utility cluster where Austin-area, SAWS, and College Station style workflows create different next-action paths.
arrow_forward
Front Range backflow testing Front Range support page for Colorado utility routes where fire-line, irrigation, date-specific testing, and third-party reporting workflows vary by city.
arrow_forward
Northern Arizona backflow testing Northern Arizona support page for Prescott-area and Flagstaff utility routes where annual testing and tester-routing rules differ by authority.
arrow_forward
Phoenix metro backflow testing Phoenix-area support page for the East Valley and West Valley utility cluster where approved-list and fire-line rules vary by city.
arrow_forward
Guide snapshot

What this guide carries forward

The local utility or district page stays canonical. Statewide and evergreen sources support comprehension, but stale or weakly sourced local pages must be suppressed.

This page exists to make a repeated question legible without pretending to replace utility-specific authority language.

Related guides

Support pages that belong in the same reading path

Reading path

Failed backflow test next steps

What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.

Open guide
Reading path

Approved testers vs find a tester

Why official tester lists and commercial directories must stay separate, and what each page type is allowed to claim.

Open guide
Reading path

Backflow test cost

How to think about annual testing, repair, and retest pricing without confusing a market quote with the compliance rule.

Open guide
Reading path

Who needs a backflow preventer

A practical guide to the property types, hazard classes, and devices that usually trigger backflow assembly requirements.

Open guide
Source trail

Source trail

TCEQ backflow prevention assembly report instructions The local utility or district page stays canonical. Statewide and evergreen sources support comprehension, but stale or weakly sourced local pages must be suppressed.
state baseline
Lewisville backflow testing page The local utility or district page stays canonical. Statewide and evergreen sources support comprehension, but stale or weakly sourced local pages must be suppressed.
utility example
Dallas Water Utilities backflow test reports page The local utility or district page stays canonical. Statewide and evergreen sources support comprehension, but stale or weakly sourced local pages must be suppressed.
utility example
College Station drinking water and backflow page The local utility or district page stays canonical. Statewide and evergreen sources support comprehension, but stale or weakly sourced local pages must be suppressed.
utility example