BackflowPath Local backflow requirements
Request help
Evergreen guide

Backflow reporting portals

A passed test is not the same thing as a completed compliance cycle. Many utilities now care as much about the portal workflow as they do about the field result.

Last reviewed: 2026-04-05 Reviewer: TL Freshness window: 120 days
Open a mapped utility page Open mapped metro layer
Why this page exists

Support the local pages without blurring the official rule

Use the local utility page to confirm the exact portal and timing. This guide exists to make those portal patterns easier to recognize before you act.

Mapped utilities 6
Mapped metros 4
State hubs 5
Backflow instrumentation and technical ledger panel
Technical reading path

Guides should reduce interpretation risk, then route the user back down into the exact utility rule and tester workflow.

Guide chapter

A portal changes the real next action

Utilities that use BSI, SwiftComply, or county customer portals shift risk from the wrench work to the reporting sequence. Owners and testers can still fall out of compliance even when the assembly passes if the result is not entered correctly.

  • Dallas and Colorado Springs push testers into portal-first result submission workflows.
  • Lee County and Tampa show how customer or contractor portals become part of the actual compliance path.
Guide chapter

Portal workflows are not interchangeable

A BSI route, a SwiftComply route, and a utility customer portal each imply different registration, fee, and tester-enrollment assumptions. Treating them as one generic online submission step is how people lose time.

  • Some programs want the tester enrolled before the report can be accepted.
  • Some county and utility portals tie the record to an existing account or hazard ID.
Guide chapter

Quote pages should reflect the reporting burden

For lead and sponsor pages, the marketable angle is not just test price. It is whether the tester can handle the reporting system the utility actually uses.

  • Portal-driven utilities often justify stronger commercial messaging than a simple annual reminder page.
  • This is one reason metro and provider profiles need to point back down into the exact utility workflow.
Utility layer

Use this guide with local utility pages

City of Flagstaff Backflow Prevention Program Flagstaff is a utility-first page because the city program clearly explains who is exempt, who needs annual testing, and how testers must route reports.
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
City of Fort Lauderdale Backflow and Cross-Connection Control Fort Lauderdale is a strong Florida utility because it combines BSI reporting, city forms, residential versus commercial testing cycles, and an explicit fine for missing reports.
arrow_forward
Austin Water Cross-Connection Control Austin Water runs a stricter ordinance-backed program with annual testing for many assemblies, online WEIRS reporting, and City registration for testers.
arrow_forward
Mesa Water Resources Backflow Prevention 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.
arrow_forward
Metro layer

Metro clusters where this guide matters

Central Texas backflow testing Support layer for the Central Texas utility cluster where Austin-area, SAWS, and College Station style workflows create different next-action paths.
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
Northern Arizona backflow testing Northern Arizona support page for Prescott-area and Flagstaff utility routes where annual testing and tester-routing rules differ by authority.
arrow_forward
Phoenix metro backflow testing Phoenix-area support page for the East Valley and West Valley utility cluster where approved-list and fire-line rules vary by city.
arrow_forward
Guide snapshot

What this guide carries forward

Many utilities now route compliance through BSI, SwiftComply, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.

This page exists to make a repeated question legible without pretending to replace utility-specific authority language.

Related guides

Support pages that belong in the same reading path

Reading path

How we verify local backflow rules

What counts as an official source, how local utility pages override generic assumptions, and why stale pages are suppressed.

Open guide
Reading path

Failed backflow test next steps

What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.

Open guide
Reading path

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.

Open guide
Reading path

Backflow test cost

How to think about annual testing, repair, and retest pricing without confusing a market quote with the compliance rule.

Open guide
Source trail

Source trail

Dallas Water Utilities backflow test reports and SwiftComply workflow Many utilities now route compliance through BSI, SwiftComply, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.
utility workflow
Tampa SwiftComply portal Many utilities now route compliance through BSI, SwiftComply, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.
official portal
Colorado Springs Utilities backflow professionals Many utilities now route compliance through BSI, SwiftComply, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.
utility workflow
Lee County customer portal Many utilities now route compliance through BSI, SwiftComply, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.
official portal