BackflowVerdict Local backflow requirements
Request help
Menu
Request help
Mission statement

Provider narrative and compliance posture

Official tester listed by Phoenix and also carried on Mesa and Avondale utility rosters for the metro cluster.

This profile does not override the utility's official rules. It exists to make the public provider layer inspectable after the governing workflow is clear.

Before booking this provider

Match Air & Water Factor to the City of Phoenix Backflow Prevention Program workflow

The strongest local provider pages do not stop at a phone number. Confirm the authority source, the utility's tester gate, the report route, and the proof trail before you schedule or send a failed device back for retest.

Official source Officially listed across multiple Phoenix-metro utility tester lists.
Due trigger Upon installation and annually thereafter - Phoenix requires certified testers on the city list to perform testing and repairs, and the approved report has to be forwarded to Planning and Development by the due date shown on the work order.
Notice clue Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
Report proof Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
Submission route Phoenix Backflow Prevention Program
Failed-test branch Ask whether repair, retest, and final submission are all handled under the same utility workflow.
Open utility workflow Official tester route Request local help
Regional coverage map
Jurisdictional coverage

1 mapped metro support page(s).

Coverage

Utility coverage

3 mapped utility pages

Utility count 3
Metro count 1
Guide links 5
  • Official tester listed by Phoenix and also carried on Mesa and Avondale utility rosters for the metro cluster.
  • Authority source
  • Last reviewed 2026-04-05
Service area

Area served across mapped utility pages

States Arizona
Cities Phoenix, Mesa, Avondale
Counties Maricopa County
  • Backflow testing
  • Backflow compliance support
  • Annual testing coordination
  • Failed test follow-up
  • Irrigation backflow testing
  • Fire line backflow testing

Verification basis

  • 3 mapped utility pages
  • 3 mapped utilities with an official tester route
  • 0 mapped utilities using a directory route
  • 3 mapped utilities with structured submission steps
  • Latest mapped utility verification: 2026-06-29
Covered utilities

Utility pages this provider is mapped to

arizona

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.

  • Due basis: Phoenix requires certified testers on the city list to perform testing and repairs, and the approved report has to be forwarded to Planning and Development by the due date shown on the work order.
  • Notice clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission route: Phoenix Backflow Prevention Program
  • Proof to keep: Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
Open utility page Official tester route
arizona

Mesa Water Resources Backflow Prevention

Mesa is a high-value Arizona utility because it publishes the annual cadence, the seven-day submission rule, tester lists, and a city-code layer that covers residential, irrigation, and fire-related hazards.

  • Due basis: Mesa sends annual notices to regulated customers, requires recognized testers to submit results through the backflow portal within seven days of service, and requires immediate retesting after repair or maintenance.
  • Notice clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission route: Mesa Backflow Prevention program
  • Proof to keep: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
Open utility page Official tester route
arizona

City of Avondale Backflow and Cross-Connection Control

Avondale is a strong utility-first page because the city pairs annual testing, approved testers, and specific approved device classes in one public workflow.

  • Due basis: Avondale says annual testing is required, that customers will be notified when results are due, and that only a Certified Backflow Prevention Assembly Tester approved by the City may test devices in the system.
  • Notice clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission route: Avondale backflow and cross-connection page
  • Proof to keep: Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
Open utility page Official tester route
Support guides

Guides that match this provider's utility mix

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.
arrow_forward
How we verify local backflow rules What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
arrow_forward
Backflow reporting portals: BSI, SwiftComply, WEIRS, VEPO, Aqua, Tokay, and SpryBackflow Find how BSI Online, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, and utility customer portals affect backflow test report submission after the field test.
arrow_forward
Backflow test due dates: anniversary date vs calendar deadline Why some utilities track annual backflow tests by anniversary date, while others use a calendar window, notice date, or hard deadline.
arrow_forward
Residential vs commercial backflow rules Why the local trigger is rarely just residential versus commercial, and how utilities actually split hazard, irrigation, multifamily, and managed-property cases.
arrow_forward
Profile maintenance

Need a correction to this profile?

If a phone number, website, or approval source is wrong, report it for manual review. BackflowVerdict updates public provider profiles only after checking the source record.

Report a correction Contact BackflowVerdict