municipal utility · official record
Mesa utility backflow testing requirements
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.
Fast answer
Who, when, and what device?
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.
- 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.
- Covered devices
- Domestic backflow assemblies · Irrigation backflow assemblies · Fire protection assemblies · Point-of-use backflow assemblies
- Risk if missed
- Mesa can keep a regulated customer out of compliance if the test is late, the portal filing misses the seven-day window, or the assembly is repaired without an immediate retest by a recognized tester.
What to do now
Choose the task on your notice
The official rule stays on this record; national guidance explains the task.
Exact workflow
Follow the local sequence
- 01
Identify whether the property or device is already in Mesa's regulated-customer pool.
- 02
Use a recognized tester from the city resources.
- 03
Upload the test through the portal within seven days of service.
- 04
If the assembly was repaired, retest immediately and keep the replacement data aligned with Mesa's record.
Tester gate
Who can produce an accepted result?
Confirm tester eligibility directly with Mesa Water Resources Backflow Prevention before scheduling.
View the official tester listSubmission route
Where the result goes
Use the official program contact and submission method below.
- Mesa Backflow Prevention program program page
- Mesa general tester list official tester list
- Mesa city code on backflow prevention city code
Local detail
Property, device, and enforcement notes
Open the parts that match the property and system. These details stay subordinate to the fast workflow above.
Program and failure notes
- Mesa uses a seven-day result-submission window.
- Repairs trigger an immediate retest expectation.
- Residential irrigation and fire-service contexts both appear in the official program.
- Mesa sends annual notices to regulated customers.
- Repair or maintenance triggers an immediate retest requirement.
- Recognized testers submit results through the city portal within seven days.
Residential notes
- Mesa is stronger than many cities on residential coverage because dedicated landscape meters and other residential cross-connections are called out directly.
- Single-family homes are not automatically outside the program if a hazard exists under the plumbing code or city ordinance.
Commercial notes
- Mesa's seven-day reporting requirement and immediate retest rule make the workflow operationally strict.
- Fire and non-fire work are not identical because Mesa separates general testers from fire-contractor resources.
Irrigation
Mesa explicitly treats dedicated landscape meters and landscape sprinkler systems as backflow-relevant cross-connections.
- Landscape sprinkler and drip systems are listed as cross-connection examples.
- Homes with dedicated landscape meters are directly within Mesa's program.
- Irrigation assemblies still need testing and portal submission through the normal city workflow.
Fire line
Mesa keeps separate resources for fire contractors, which makes the fire-line path stronger than a generic annual-testing page.
- Most fire sprinkler systems are listed as covered cross-connections.
- Mesa distinguishes general testers from fire-contractor resources.
- The annual testing and portal reporting discipline still applies.
Cost and fee context
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.
Evidence ledger
Official sources
Mesa publishes one of the cleaner city workflows: annual notices, seven-day portal reporting, immediate retesting after repairs, and separate resources for general testers and fire contractors.
BackflowVerdict summarizes these records; the governing entity remains the authority.
Open official program page- 01Mesa Backflow Prevention programofficial program pageOpen source ↗
- 02Mesa city code on backflow preventionofficial code pdfOpen source ↗
- 03Mesa general tester listofficial tester list pdfOpen source ↗
Commercial handoff · separate layer
Still need help after reading the rule?
The request keeps this utility ID and source page with the handoff.