City backflow route

Tempe backflow testing routes through City of Tempe Backflow Prevention Program.

City search demand maps directly to Tempe's governing backflow program and registered tester workflow. This page keeps the city search term visible while routing the actual compliance work to the governing utility record.

City: Tempe Utility: City of Tempe Backflow Prevention Program Cadence: At installation and annually on the anniversary date Last verified: 2026-06-29
Next action

Pick the Tempe backflow path that matches the problem

The city term helps discovery. The governing utility still decides the rule, submission method, tester route, and follow-up order.

Requirements

Tempe backflow prevention requirements

Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.

Annual notice

Tempe annual backflow testing

At installation and annually on the anniversary date Tempe uses annual anniversary-date testing by a City-registered certified tester, sends reminders before the due date, and can escalate unresolved noncompliance to termination of water service.

Tester route

Tempe approved backflow testers

This utility has an official tester-list route. Confirm status on the governing list before treating a provider as approved.

Repair or failure

Tempe failed backflow test

Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.

Irrigation

Tempe irrigation backflow testing

Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.

Fire line

Tempe fire-line backflow testing

Use this path when the assembly serves fire protection equipment or a managed commercial site.

Before scheduling in Tempe

Check the local rule before treating this as a generic tester search

  • Cadence: At installation and annually on the anniversary date
  • Due basis: Tempe uses annual anniversary-date testing by a City-registered certified tester, sends reminders before the due date, and can escalate unresolved noncompliance to termination of water service.
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission: Tempe backflow prevention program
  • Acceptance rule: Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
  • Cost signal: Testing is market-priced, but Tempe adds notice timing and tester-registration discipline.
Owner vs tester

Tempe action split

Authority mapping

Why Tempe maps to City of Tempe Backflow Prevention Program

City search demand maps directly to Tempe's governing backflow program and registered tester workflow.

  • Tempe customers with contained cross-connection hazards, including irrigation, fire-line, multifamily, commercial, and other assemblies tracked by the Water Utilities Division.
  • Tempe warns that unresolved overdue tests can move toward water-service termination and that stolen assemblies must be replaced with the same type of device.
  • Program phone: 480-350-2678
  • City route reviewed: 2026-04-05
Provider layer

Public provider profiles mapped to this utility

Provider profiles can help after the city and utility workflow is clear. They do not replace the official source trail.

Support guides

Read these before acting on the Tempe workflow

Guide

Backflow test notice: what to do next

What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.

Guide

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.

Guide

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.

Guide

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.