How often does a commercial backflow preventer need testing in Arizona?

At least once a year, and again after the assembly is installed, relocated, or repaired. This is the baseline across Arizona. State rule sets it, not your plumber's preference. The Arizona Administrative Code R18-4-215 is the state cross-connection control rule. It requires that each backflow assembly be tested when it is installed and then at least annually after that. The test must be done by a person who is certified for the work. Any time the assembly is moved or worked on, it has to be retested before it goes back into service. A repair can change how the device seals.

The annual cycle is the floor, not the ceiling. A water provider can require testing more often for a high-hazard connection. A facility that handles chemicals, medical waste, or process water is one example. The City of Phoenix sets its own schedule under City Code, and its baseline matches the state: test every year by a certified tester. If your provider sends a notice with a shorter interval, that notice controls your site. The annual test is different from the water provider's cross-connection survey, which decides whether you need an assembly at all; see cross-connection survey vs backflow test.

For most commercial properties the rule is simple. Put the test on an annual calendar. Schedule it before the due date, and never let a repair or relocation go un-retested.

Arizona Administrative Code R18-4-215 makes backflow testing a condition of keeping a cross-connection in service. The rule is titled cross-connection control. The Arizona Department of Environmental Quality runs it, and it applies to public water systems across the state. Under R18-4-215, an approved backflow assembly must be tested when it is installed and at least annually by a certified tester. The results have to be kept on record.

The rule states that each required assembly "shall be tested at least annually," and "Each assembly shall also be tested after installation, relocation, or repair." The tester must hold a current certification that the water provider recognizes. Arizona ties its test methods to the USC Foundation Manual of Cross-Connection Control. That manual is the industry reference for how a tester checks that valves and relief vents are holding. Records of each test are kept for about three years. That way a water provider or inspector can confirm the device has stayed in compliance.

A few points that trip people up:

• The water provider, not the state, enforces day to day. ADEQ writes the rule; your city or water company runs the testing program, keeps the assembly list, and sends the notices. To see which businesses each Valley city requires to have an assembly, see backflow assembly requirements by city.
• Certification matters. A general handyman cannot sign off on a test. The tester needs a current backflow tester certification, and the gauge they use must itself be calibrated.
• Repairs reset the clock. A new annual due date does not erase the requirement to retest after any repair or relocation.

For the underlying definitions of what backflow and a cross-connection are, see our pages on what-is-backflow-in-plumbing and what-is-a-cross-connection.

Phoenix City Code Section 37-144 requires annual testing by a certified tester and puts the results and the cost on the customer. This is the city layer that sits on top of the state rule. It adds reporting and recordkeeping steps that R18-4-215 leaves to the provider.

Under Section 37-144, the customer must have each backflow assembly tested at least once a year by a certified backflow assembly tester. The results go to the city by the date the Planning and Development Director sets (Section 37-143). For Class 1 and 2 fire systems, results go to the Director and the City Fire Marshal within 30 days of the inspection. The code puts it this way: "The customer shall test and submit all testing results to the Planning and Development Director" (Section 37-143). The city also expects the customer to keep the test records. The assembly must be repaired or replaced if it fails the test. A replacement after theft or damage needs its own permit and a passing test before it goes back in service; see backflow preventer stolen or damaged: what now?.

What this means in practice for a Phoenix business:

• You own the deadline. The customer must submit test records "by the date specified by the Planning and Development Director" (City Code 37-143). Results for Class 1 and 2 fire systems go to the Director and the Fire Marshal within 30 days of the inspection. A passing test that never gets filed can still leave you out of compliance.
• Fire lines get extra attention. Backflow assemblies on a fire-protection system are reported to the Fire Marshal, not only the water department. A fire line is its own cross-connection hazard. Many fire services carry a double detector check assembly, whose bypass meter shows leaks on a line with no billing meter. Phoenix also requires a full flow test on fire lines, which differs from the gauge test; see how the NFPA 25 flow test compares to a backflow test.
• A failed test is not closed by reporting it. A device that fails has to be fixed or replaced and then retested before it counts.

City code language can be amended. Confirm the current Section 37-144 text and your reporting addresses with City of Phoenix Water Services and ADEQ before you rely on this for a deadline.

A backflow preventer is a valve assembly that stops water from reversing direction and carrying contaminants into the clean drinking supply. Water systems are built to flow one way, from the public main into your building. When that flow reverses, dirty water can get pulled or pushed back into the pipes everyone drinks from. That reversal is backflow. The point where clean and dirty water can meet is a cross-connection.

The federal EPA Cross-Connection Control Manual describes the two ways backflow happens. Back-siphonage happens when supply pressure drops, such as during a water-main break or heavy firefighting demand. The suction then pulls non-potable liquid backward through a connection. Backpressure happens when a downstream system pushes water back toward the main at higher pressure than the supply. A boiler, booster pump, or elevated tank can do this. A backflow assembly is built to block both. It is usually a double check valve or a reduced-pressure principle device.

Testing matters because these devices fail silently. The internal valves and relief vents wear, scale up, or stick, and you cannot see it from the outside. The water keeps flowing the right way under normal use, so a worn assembly looks fine right up until pressure reverses. The annual test is the only routine check that the seals still hold. Debris on a check valve seat is one cause of a failed test; here's whether a strainer belongs ahead of the backflow preventer. It catches the problem before a real backflow event puts a contaminant into the drinking water. The EPA manual documents real cases. Pesticides, boiler chemicals, and other contaminants entered potable systems through untested or missing assemblies.

Any commercial connection with a cross-connection hazard needs a tested assembly. This covers most businesses, irrigation systems, and fire-protection lines. If your property has a backflow preventer installed, the water provider almost certainly found a hazard there. That means the annual test applies to you.

The test has to be done by a certified tester your water provider recognizes (see who can test backflow assemblies in Arizona), and the report has to reach that provider on time; where to send backflow test reports in the Phoenix area lists each provider's address and deadline. If the assembly fails, here's what happens next. Keep every report you get back; how long to keep backflow test records covers the three-year Phoenix rule and what to file.

Connections that commonly require testing:

• Businesses and commercial buildings with boilers, chemical feed, process water, soda or beverage carbonation, or commercial dishwashing. For restaurant equipment specifically, see backflow rules for soda and ice machines.
• Apartment and condo complexes on a master meter, which usually have several assemblies; see annual backflow testing for apartment complexes.
• Irrigation and sprinkler systems, where fertilizer, pesticide, or standing pond water can be siphoned back into the supply.
• Fire-protection lines, where stagnant water and any antifreeze or additives sit against the potable system.
• Restaurants and food service, where mop sinks, hose connections, and equipment create multiple cross-connection points.

If you miss the test, the consequences grow. The water provider can issue a non-compliance notice with a deadline to test. If the assembly is not tested or repaired, the provider can shut off water service to the connection until you fix it. This authority comes from the state cross-connection rule and city code. Phoenix can also pursue the penalties its code allows for violations; what happens if you miss a Phoenix backflow test deadline lays out the notice periods and the penalty. There is also liability. An untested assembly that fails during a backflow event can send contaminated water to other customers, and that is on you. The annual test is far cheaper than an emergency shutoff or a contamination cleanup.

This page explains general Arizona and Phoenix requirements and is not legal advice. Confirm the current rules, deadlines, and reporting contacts with the City of Phoenix Water Services Department, your local water provider, and ADEQ before acting. Code sections and testing intervals can change.

Associations face the same rule on shared irrigation. See HOA common-area irrigation backflow testing.

The annual test is also how worn parts get caught; see how long a backflow preventer lasts.

For what a tester has to know, see the Arizona certification exam. Some businesses, such as dental offices, have their own questions; see whether a dental office needs a backflow preventer.