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

Submit Mesa 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 Mesa.

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

What to check for Mesa

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

  • 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 or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Who is affected: Commercial, industrial, irrigation, fire-sprinkler, and dedicated-landscape-meter customers, plus residential sites that city code and plumbing rules identify as cross-connection hazards.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 480-644-6462
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority Mesa Water Resources 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 Mesa Backflow Prevention program (program page)
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: Mesa Backflow Prevention program - program page
  • Submission path: Mesa general tester list - official tester list
  • Submission path: Mesa city code on backflow prevention - city code
  • 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: 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.
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

  • Mesa Backflow Prevention program (program page)
  • Mesa general tester list (official tester list)
  • Mesa city code on backflow prevention (city code)
  • 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

Mesa 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: Mesa Backflow Prevention program, Mesa general tester list, Mesa city code on backflow prevention.
  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

Mesa questions before you act

How do I submit a backflow test report for Mesa?

Use the official utility workflow and submission methods listed on this page: Mesa Backflow Prevention program, Mesa general tester list, Mesa city code on backflow prevention. Program phone: 480-644-6462. 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 Mesa 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 Mesa 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 Mesa Water Resources Backflow Prevention.

Who controls the rule for Mesa?

Mesa search demand is routed to Mesa Water Resources Backflow Prevention. Commercial, industrial, irrigation, fire-sprinkler, and dedicated-landscape-meter customers, plus residential sites that city code and plumbing rules identify as cross-connection hazards.

What costs or fees should I expect for Mesa?

Testing is market-priced, but Mesa adds process friction through the portal deadline and annual notice cycle. Repair and retest cost changes with the device class and whether fire-side work is involved. The city does not publish a retail tester fee, so the main value is in the strict operational rules and list of recognized testers.