BackflowVerdict Local backflow requirements
Request help
Menu
Request help
Failed-test city route

Tempe failed backflow test

Use this page when the assembly already failed and the next step is repair, retest, and accepted report submission.

Open failed-test workflow Utility requirements Find from notice Request local help
City: Tempe Utility: City of Tempe Backflow Prevention Program Cadence: At installation and annually on the anniversary date Last verified: 2026-06-29
Local answer

What to check for Tempe

Use this page when the assembly already failed and the next step is repair, retest, and accepted report submission.

  • 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.
  • Who is affected: Tempe customers with contained cross-connection hazards, including irrigation, fire-line, multifamily, commercial, and other assemblies tracked by the Water Utilities Division.
  • Acceptance rule: Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
  • Program phone: 480-350-2678
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

This is the working path for Tempe notices: match the authority, confirm the tester gate, use the accepted submission route, and keep proof that the report was accepted.

Authority City of Tempe Backflow Prevention Program
Notice trigger Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
Tester gate View the official tester list
Submission route Tempe backflow prevention program (program page)
Proof to keep Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
Failure branch Open failed-test workflow before treating repair, retest, or resubmission as complete.
Local signals

Signals that matter before you act

  • Tempe publishes a 45-day reminder and overdue notice sequence.
  • Water service termination is on the table for unresolved noncompliance.
  • Fire lines are explicitly called out as double-check assembly use cases.
Other Tempe routes

Stay inside the city intent cluster

Tempe annual backflow testing Tempe annual backflow testing: verify who must test, the due-date rule, tester requirements, and the official submission workflow.
arrow_forward
Tempe approved backflow testers Find the official Tempe approved backflow tester route and confirm utility registration, credentials, and report submission requirements.
arrow_forward
Tempe irrigation backflow testing Check Tempe irrigation backflow testing triggers, device rules, tester requirements, and the official utility workflow.
arrow_forward
Tempe fire-line backflow testing Check Tempe fire-line backflow testing triggers, assembly rules, tester requirements, and the official utility workflow.
arrow_forward
Workflow

Tempe workflow order

  1. Confirm the due date from Tempe notice or city record.
  2. Hire a Tempe-registered tester.
  3. Complete the annual test on the anniversary cycle.
  4. Post the result before enforcement moves toward shutoff.
City FAQ

Tempe questions before you act

What should I do after a failed backflow test in Tempe?

Tempe publishes a 45-day reminder and overdue notice sequence.

Does a failed test still need report submission in Tempe?

Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.

Who controls the rule for Tempe?

Tempe search demand is routed to City of Tempe Backflow Prevention Program. Tempe customers with contained cross-connection hazards, including irrigation, fire-line, multifamily, commercial, and other assemblies tracked by the Water Utilities Division.

What costs or fees should I expect for Tempe?

Testing is market-priced, but Tempe adds notice timing and tester-registration discipline. Repair and retest cost rises if the assembly was stolen, relocated, or tied to a fire line. The strongest local cost driver is avoiding Tempe enforcement and repeat site visits.