BSI backflow reporting
Utilities where BSI or Backflow Solutions appears in tester or report submission context.
Use this page when a notice says the tester must submit through a portal, customer account, or utility reporting workflow.
These pages group the strongest recurring portal names without pretending the portal itself replaces the local rule.
Utilities where BSI or Backflow Solutions appears in tester or report submission context.
Utilities where WEIRS appears in the official tester lookup or compliance workflow.
Utilities where SwiftComply or C3Swift appears in the official report submission path.
Open the utility page first. It contains the due basis, submission method, program phone, and any tester-list route tied to the property.
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.
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.
Queen Creek is a strong utility because it combines annual backflow reporting, BSI filing fees, and strict tester credential requirements.
Tucson Water publishes one of the clearer Arizona workflows: annual testing, registered testers, an iBAK portal, and a short shutoff-warning path when compliance is missed.
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.
Sacramento is a useful California utility because city drinking-water pages and county cross-connection operations meet in an actual approved-tester workflow.
San Diego is one of the best California fits because the city publishes annual testing rules, an approved tester list, a tester-orientation gate, and explicit enforcement consequences.
SSWD is a strong district page because approved testers and annual test entry live inside a real utility workflow.
San Francisco is a strong approved-tester utility because SF.gov publishes a genuine certified tester list with contact details.
Aurora Water is a strong supporting Colorado utility because it publishes a clean annual-testing rule, online submission requirement, and ownership-responsibility language.
Aspen is a high-quality Colorado utility because the city publishes BSI-driven annual testing, a certified tester list, and device-level guidance for irrigation, fire systems, and containment assemblies.
Greeley is a strong Colorado utility because it combines annual testing, Spry portal reporting, and an official local tester list.
Lafayette is a strong Front Range utility because it publishes clear annual due dates by device type, a BSI workflow, and enforcement language with fees and shutoff risk.
Longmont is a very strong Colorado utility because it combines annual testing, enforcement timing, irrigation-specific upgrade rules, and a real portal transition.
Thornton is a strong Colorado city because it names the covered classes, publishes annual-testing language, and gives a clean portal-driven reporting path.
Colorado Springs Utilities is a strong Colorado page because it shows how the utility actually runs the testing workflow: portal registration, certification uploads, five-day test entry, and survey-first rules.
Fort Collins is a strong Colorado utility because it combines annual testing, BSI reporting, a local tester list, and explicit water-service suspension risk.
Parker is a strong Colorado utility because annual testing, repair deadlines, and reporting all live on district-run pages instead of a vague contractor follow-up chain.
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.
Tampa is one of the best Florida fits because it publishes a clear cadence split, a seven-day reporting deadline, and a real tester-enrollment workflow instead of generic educational content.
Lee County is a strong Southwest Florida utility because it combines annual testing, portal-driven compliance, and county-level cross-connection workflow on public pages.
Manatee County is one of the strongest Florida county utilities because the testing clock, county-contractor fallback, and portal deadlines are all explicit.
Orange County is a strong Florida county utility because it exposes the real county program, the registered tester search path, and reclaimed-water-specific device rules.
Austin Water runs a stricter ordinance-backed program with annual testing for many assemblies, online WEIRS reporting, and City registration for testers.
College Station is a useful procedural page because it clearly publishes the tester list, report form, 30-day submission rule, and City registration requirements for BPATs.
Fort Worth requires testing at installation, repair, or relocation and then annually, with licensed registered testers submitting reports through VEPO.
Frisco requires installation testing and recurring annual testing for certain testable assemblies, with BSI handling much of the program workflow.
Leander is useful because it publishes hazard-based frequency rules, including annual tests for many residential and commercial hazards and five-year testing for some residences without septic.
Lewisville is strong pilot content because it publishes the annual cadence, official tester list, BSI submission deadline, filing fee, and enforcement language on one page.
McKinney is a paperwork-heavy utility. The main risk is not just failing the field test; it is using the wrong City form, the wrong registration path, or the wrong submission method.
Round Rock splits testing cadence by hazard class: annual for high-hazard devices and every 7 years for low-hazard residential devices.
Sugar Land runs an annual testing program for health-hazard backflow devices and tracks compliance through BSI.
Dallas is a useful edge case because it is not simply annual-for-everything: high-hazard assemblies are annual, irrigation is event-driven, and SwiftComply is mandatory for covered test reports.
San Antonio requires annual backflow testing and routes both customer compliance checks and registered testing company discovery through BSI under the SAWS program.
Talty SUD is a strong district example because it publishes explicit annual testing triggers, deadline months, RPZ rules for OSSF properties, and a hard service-disconnection consequence for noncompliance.
A reporting portal may handle test submission while the utility, county, or separate list controls tester eligibility. Treat the utility page as the canonical workflow before scheduling or submitting a report.