Backflow reporting portals: BSI, SwiftComply, WEIRS, and VEPO

Why this page exists

Support the local pages without blurring the official rule

Use the local utility page to confirm the exact portal, timing, fee, and tester status. 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.

Portal lookup

Jump to the portal family named in the notice

These hub pages group utilities by the reporting system named in the public workflow, then send the user back to the exact authority page.

BSI Online

BSI backflow reporting

Use this route when the notice mentions BSI Online, Backflow Solutions, a CCN, or online test report entry through BSI.

Open BSI utilities

SwiftComply

SwiftComply test reports

Use this route when the utility uses SwiftComply or C3Swift for tester registration and report submission.

Open SwiftComply utilities

WEIRS

WEIRS tester and report routes

Use this route when the local workflow references WEIRS for tester lookup, inspection, or report submission.

Open WEIRS utilities

VEPO Envirotrax

VEPO tester registration and reports

Use this route when the utility names VEPO or Envirotrax for BPAT registration, credential verification, approved-list status, or report submission.

Open VEPO utilities

Guide chapter

A portal changes the real next action

Utilities that use BSI, SwiftComply, WEIRS, VEPO, Envirotrax, 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.
Fort Worth shows how VEPO/Envirotrax can combine tester registration, credential verification, approved-list status, and online reporting.
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, a WEIRS route, a VEPO/Envirotrax route, and a utility customer portal each imply different registration, fee, credential, 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 programs block submission if tester license, insurance, or gauge accuracy documents are stale.
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 quote-prep and provider pages, the practical 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 workflow-specific 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, 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

State support

Keep the state layer in view

Review record

How this guide is kept trustworthy

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

Last reviewed: 2026-07-03
Verification code: TL
Freshness window: 120 days
Editorial standards
Report a correction

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

Backflow test notice: what to do next

What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.

Open guide

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.

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

Source trail

Dallas Water Utilities backflow test reports and SwiftComply workflow Many utilities now route compliance through BSI, SwiftComply, WEIRS, VEPO, Envirotrax, 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, WEIRS, VEPO, Envirotrax, 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, WEIRS, VEPO, Envirotrax, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.

utility workflow

Lee County BSI Online tester instructions Many utilities now route compliance through BSI, SwiftComply, WEIRS, VEPO, Envirotrax, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.

official tester reporting instructions

Fort Worth VEPO Envirotrax backflow workflow Many utilities now route compliance through BSI, SwiftComply, WEIRS, VEPO, Envirotrax, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.

official utility workflow

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

portal tester search