Why this page exists
Support the local pages without blurring the official rule
Use this page as the top-of-funnel checklist, then open the exact utility page before scheduling or submitting a report.
Evergreen guide
Backflow test notice: what to do next
A backflow test notice is not just a reminder to call the nearest plumber. It usually tells you which utility is enforcing the rule, when the test is due, who can test, how the report must be filed, and what happens if the device fails.
Notice funnel
Turn the notice into the right next page
Start with the word or problem named in the notice. Then open the exact utility page before scheduling or filing.
Notice says annual test or due date
Use the due-date guide when the notice is about timing, annual testing, a calendar window, or an anniversary date.
Notice names BSI, SwiftComply, WEIRS, or VEPO
Use the portal guide when the report has to be entered through a named online system or tester account.
Notice says certified, registered, or approved tester
Use the tester guide when the issue is whether the provider is accepted by the city, county, utility, or portal.
Device failed or needs repair
Use the failed-test guide when the next step is repair, retest, report correction, or a short compliance window.
Notice creates a pricing question
Use the cost guide when the owner needs to separate tester pricing, filing fees, repair exposure, and retest costs.
Notice names a city or water provider
Use the mapped utility page for the exact phone, source trail, submission method, tester route, and local rule.
Read the notice like a workflow
The notice usually contains more than a due date. Look for the utility name, property address, assembly serial number, due date, portal name, tester requirement, and fee language before choosing the next action.
- If the notice names BSI, SwiftComply, VEPO, Envirotrax, or a local portal, the tester may need a registered account before the report can be accepted.
- If the notice references a hard deadline, the useful question is not just test price; it is whether the tester can complete and file before the due date.
Match the tester to the filing path
Good commercial pages win because they promise the full chain: certified testing, repair if needed, report filing, proof to the owner, and reminders. BackflowPath keeps that chain tied to the governing utility instead of turning it into a generic provider claim.
- Registered tester, certified tester, approved tester, and county-certified tester can mean different things.
- A passed test still leaves the owner exposed if the report is filed late, filed through the wrong portal, or rejected for missing credentials.
Plan for failure before it happens
Many official pages treat failed tests differently from passed tests. Some require faster notice, a repair and retest window, or different fee handling. The right tester is the one who can close the failed-test loop, not only run the first test.
- Ask whether the tester can repair, retest, and submit the corrected report.
- Keep the failed-test timeline on the same utility workflow as the original notice.
Use this guide with local utility pages
City of Avondale Backflow and Cross-Connection Control
Avondale is a strong utility-first page because the city pairs annual testing, approved testers, and specific approved device classes in one public workflow.
arrow_forward
City of Anaheim Cross Connection Control
Anaheim is a strong Southern California utility because it publishes annual testing rules, approved-list gating, online submission, and utility specifications for irrigation and proposed fireline work.
arrow_forward
Aurora Water Backflow Prevention
Aurora Water is a strong supporting Colorado utility because it publishes a clean annual-testing rule, online submission requirement, and ownership-responsibility language.
arrow_forward
Broward County Water and Wastewater Services Backflow Certification
Broward County is a high-value Florida utility because it publishes due-date notices, filing-fee handling, and separate tester qualification rules for domestic, irrigation, and fire-service assemblies.
arrow_forward
Arlington Water Utilities
Arlington is a code-driven city: annual testing is tied to health-hazard assemblies, but installation, moves, repairs, replacement, irrigation permits, and fire line work all have separate ordinance triggers.
arrow_forward
City of Buckeye Environmental Compliance and Backflow Program
Buckeye is a useful Arizona utility because it publishes annual due notices, clear required assembly classes, and direct owner responsibility for annual testing.
arrow_forward
Metro clusters where this guide matters
Dallas-Fort Worth backflow testing portals and tester lists
Utility-first Dallas-Fort Worth backflow testing page covering city portals, registered tester routes, annual testing, and failed-test workflows.
arrow_forward
Front Range backflow testing
Front Range support page for Colorado utility routes where fire-line, irrigation, date-specific testing, and third-party reporting workflows vary by city.
arrow_forward
Phoenix metro backflow testing, portals, and tester lists
Phoenix-area backflow testing page for Mesa, Chandler, Tempe, Queen Creek, and nearby utilities with BSI, approved-list, annual-test, and fire-line workflows.
arrow_forward
South Florida backflow testing
South Florida support page for county and city utility backflow routes across Miami-Dade, Broward, Jupiter, and Palm Beach.
arrow_forward
Keep the state layer in view
How this guide is kept trustworthy
Strong official examples show the same notice workflow: confirm the utility, use an accepted tester, submit through the required portal or report path, handle failed tests quickly, and keep proof of filing.
- Last reviewed: 2026-07-03
- Verification code: TL
- Freshness window: 120 days
- Editorial standards
- Report a correction
Related guides
Support pages that belong in the same reading path
How we verify local backflow rules
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
Failed backflow test next steps
What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.
Approved testers vs find a tester
Why official tester lists and commercial directories must stay separate, and what each page type is allowed to claim.
Backflow test cost: annual testing, repairs, and portal fees
How annual backflow test cost changes when the utility requires registered testers, repairs, retests, BSI fees, or online reporting.
Source trail
Source trail
Dallas Water Utilities SwiftComply backflow reports
Strong official examples show the same notice workflow: confirm the utility, use an accepted tester, submit through the required portal or report path, handle failed tests quickly, and keep proof of filing.
official utility example
Tampa backflow testing and SwiftComply enrollment
Strong official examples show the same notice workflow: confirm the utility, use an accepted tester, submit through the required portal or report path, handle failed tests quickly, and keep proof of filing.
official utility example
Queen Creek BSI filing fee and credential rules
Strong official examples show the same notice workflow: confirm the utility, use an accepted tester, submit through the required portal or report path, handle failed tests quickly, and keep proof of filing.
official utility example
Hillsborough County backflow BMP portal and failed-test notice
Strong official examples show the same notice workflow: confirm the utility, use an accepted tester, submit through the required portal or report path, handle failed tests quickly, and keep proof of filing.
official county example
Fort Worth VEPO and registered BPAT workflow
Strong official examples show the same notice workflow: confirm the utility, use an accepted tester, submit through the required portal or report path, handle failed tests quickly, and keep proof of filing.
official utility example