BackflowPath Local backflow requirements
Request help
Menu
Request help
Report submission route

Submit Tucson reporting portal backflow test reports

Use this page when the notice or tester workflow is about submitting, uploading, filing, or confirming a backflow test report for Tucson.

Open utility source workflow Utility requirements Find from notice Request local help
City: Tucson Utility: Tucson Water Backflow Prevention Cadence: Upon installation and annually thereafter Last verified: 2026-06-29
Local answer

What to check for Tucson

Use this page when the notice or tester workflow is about submitting, uploading, filing, or confirming a backflow test report for Tucson.

  • Due basis: Tucson Water requires annual testing and can issue a four-day shutoff notice if the compliance date passes without the required test results. Registered testers submit through the iBAK system.
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Who is affected: Commercial and multifamily customers, reclaimed-water users, irrigation users with protected connections, and any Tucson Water customer that the utility flags as requiring backflow protection.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 520-791-2650
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority Tucson Water Backflow Prevention
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 Tucson Water iBAK results entry (online submission)
Proof to keep Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
Failure branch Open failed-test workflow before treating repair, retest, or resubmission as complete.
Local signals

Signals that matter before you act

  • Submission path: Tucson Water iBAK results entry - online submission
  • Submission path: Tucson backflow ordinance - utility ordinance
  • Submission path: Tucson reclaimed water page - irrigation and reclaimed context
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Tester gate: Start with the governing authority's published tester list. This utility has an official approved-tester route and it should be treated as the primary source.
  • Report acceptance: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Due basis: Tucson Water requires annual testing and can issue a four-day shutoff notice if the compliance date passes without the required test results. Registered testers submit through the iBAK system.
Submission packet

What the report needs before it can count

Use this as the working checklist for the owner, tester, or property manager before treating a passed field test as a completed compliance cycle.

Before filing

Match the notice record

  • Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Service address, device type, due date, and utility name must match the notice.
  • Use the utility workflow before relying on a generic tester search.
Filing gate

Confirm the accepted route

  • Tucson Water iBAK results entry (online submission)
  • Tucson backflow ordinance (utility ordinance)
  • Tucson reclaimed water page (irrigation and reclaimed context)
  • View the official tester list
After filing

Keep acceptance proof

  • Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Keep portal confirmation, email receipt, account history, or accepted report record.
  • If the assembly failed, use the failed-test workflow before assuming the case is closed.
Failed-test workflow
Workflow

Tucson workflow order

  1. Match the utility notice to the service address, device or assembly record, and due date.
  2. Confirm the tester is accepted through the governing tester-list or approval route before the report is filed.
  3. File the result through the stored submission path: Tucson Water iBAK results entry, Tucson backflow ordinance, Tucson reclaimed water page.
  4. Keep proof that the report was submitted and accepted; a passed field test alone may not close the compliance cycle.
  5. If the assembly failed, follow the repair, retest, and resubmission sequence before assuming compliance is restored.
City FAQ

Tucson questions before you act

How do I submit a backflow test report for Tucson?

Use the official utility workflow and submission methods listed on this page: Tucson Water iBAK results entry, Tucson backflow ordinance, Tucson reclaimed water page. Program phone: 520-791-2650. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.

What information should be ready before filing the Tucson report?

Look for the utility name, service address, assembly serial number, account or notice ID, and due date. Also keep the due date, service address, tester credential status, device type, and proof of submission.

Does the tester or owner submit the Tucson report?

The field tester often controls portal entry, but the owner should keep the notice, due date, and proof that the report was accepted by Tucson Water Backflow Prevention.

Who controls the rule for Tucson?

Tucson search demand is routed to Tucson Water Backflow Prevention. Commercial and multifamily customers, reclaimed-water users, irrigation users with protected connections, and any Tucson Water customer that the utility flags as requiring backflow protection.

What costs or fees should I expect for Tucson?

Testing is market-priced, but Tucson adds operational risk through the compliance-date and shutoff-warning structure. Repair and retest costs vary by device and whether reclaimed or irrigation equipment is involved. The utility value here is the iBAK workflow and registered tester structure, not a published flat fee.