Find utilities using BSI Online or Backflow Solutions for tester enrollment and backflow test report submission.
Most portal searches start after a notice, failed test, or tester upload problem. Match the portal name to the city or utility, then confirm the exact acceptance gate before filing.
Use these phrases as the practical clue set from a notice, tester upload screen, or property manager handoff.
These links prioritize city routes backed by structured portal, tester, fee, deadline, and report-acceptance facts.
Use this table to spot the acceptance gates that usually decide whether a backflow report is actually complete: portal submission, notice or device identifiers, approved tester status, report acceptance, and failed-test handling.
| Utility and city | Portal evidence | Notice or device ID | Tester gate | Report acceptance | Timing or fee clue | Failed-test clue |
|---|---|---|---|---|---|---|
| City of Flagstaff Backflow Prevention Program |
Flagstaff backflow prevention page
Flagstaff cross-connection ordinance
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Confirm accepted tester status with the utility. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | Annually | Flagstaff requires immediate retest after repair. |
| Town of Queen Creek Backflow Program |
BSI Online reporting cycle
Queen Creek backflow information
Queen Creek contractor information
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Current tester license, Current test kit calibration certificate | Accepted BSI report with current tester credentials and the required filing fee. | Annually after installation and on the BSI filing cycle | Queen Creek has a real filing-fee workflow, not a vague city page. |
| Dublin San Ramon Services District Backflow Testing |
DSRSD backflow testing page
DSRSD Tokay test entry website
|
Look for the Tokay/WebTest entry, tester login context, device record, or assembly identifier. | Open DSRSD approved backflow tester list route | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | Existing backflow devices use Tokay test entry; damaged, leaking, or failed assemblies must be repaired and retested without delay | Failed, damaged, or leaking assemblies must be repaired and retested without delay. |
| City of Aspen Cross Connection Control AKA Backflow Prevention Program |
Aspen BSI Online backflow assembly test reporting
Aspen cross connection control program
BSI Online tester portal
Aspen flyer and tester list
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Certified backflow prevention assembly tester status, Aspen certified tester list status, BSI Online tester portal access | Keep the BSI Online submission record or customer portal report copy for the Aspen assembly. | At least annually, plus on installation and after repair | Aspen uses BSI for notification and tester reporting. |
| City of Lafayette Backflow Compliance Program |
Lafayette backflow compliance support
Lafayette BSI customer portal
Lafayette code library
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Confirm accepted tester status with the utility. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | Annually | Lafayette separates irrigation and non-irrigation annual due dates. |
| City of Thornton Cross Connections and Backflow Prevention |
Thornton cross connections and backflow prevention
Thornton backflow brochure
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Confirm accepted tester status with the utility. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | At installation and at least annually after that | Thornton publicly names its covered customer classes. |
| Fort Collins Utilities Backflow Prevention and Cross-Connection Control |
Fort Collins backflow program
Fort Collins certified tester list
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Open the Fort Collins local certified backflow tester list | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | Upon installation and annually thereafter | Fort Collins keeps a public local tester list. |
| Broward County Water and Wastewater Services Backflow Certification |
Broward backflow certification program
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Confirm accepted tester status with the utility. | Use the listed submission method and keep proof that the report was filed with the utility. | Annually | Broward uses explicit 60-day and 30-day reminders. |
| City of Fort Lauderdale Backflow and Cross-Connection Control |
Fort Lauderdale BSI backflow compliance workflow
Fort Lauderdale backflow and cross-connection page
Fort Lauderdale annual backflow report form
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Certified tester status, Annual report form completion | Keep the submitted annual report form and BSI compliance confirmation before the 90-day fine window is reached. | Annually for commercial and hazardous assemblies; every two years for residential irrigation | Fort Lauderdale publishes a real annual report form. |
| Lee County Utilities Cross-Connection Control Program |
Lee County CCC portal reporting workflow
Lee County Utilities cross-connection control policy
Lee County BSI Online tester instructions
Lee County Utilities customer portal
Lee County CCC portal login
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Lee County BSI Online tester instructions, CCC portal access for the county reporting workflow | Keep the accepted county portal record so the utility account stays current. | At installation and annually thereafter | Lee County says devices are tested at installation and annually thereafter. |
| City of Frisco Backflow Program |
Frisco BSI Online backflow administration
Frisco backflow program page
BSI tracking
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Licensed backflow tester status, BSI registered tester access, Frisco-registered plumber or irrigator status when installation work applies | Keep the BSI/Frisco device record or submission confirmation showing the required installation or annual test workflow was completed. | Upon installation and annually thereafter for certain testable assemblies | Frisco separates tester cost from the City's annual inspection fee. |
| City of League City Backflow Testing Program |
BSI Online Backflow Tracking System
League City backflow testing program page
BSI Online Backflow Tracking System
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Certified tester status, League City tester registration, BSI Online access | Keep the BSI Online submission record tied to the CCN so an overdue notice can be resolved quickly. | Upon installation and at least annually | Retest and accepted report submission are part of the closeout path. |
| City of Leander Cross-Connection Control |
Leander BSI backflow report submission workflow
Leander cross-connection program
BSI submission portal
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Licensed backflow tester status, BSI registered testing agency route, Signed TCEQ-20700 form for new installations | Keep the signed TCEQ-20700 form for new installations or the BSI submission record for existing assemblies. | Annual for many hazards; every five years for some residences without septic | Leander's cadence depends heavily on hazard type, so using the wrong local assumption can over- or under-test. |
| City of Lewisville Backflow Testing |
BSI Online submission portal
Lewisville backflow testing program page
Lewisville tester registration portal
BSI Online submission portal
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Texas tester license, City of Lewisville tester registration | Electronic BSI Online submission within ten days of the test date. | Report due within 10 days after testing. | Retest and accepted report submission are part of the closeout path. |
| City of Round Rock Backflow Prevention |
BSI Online tracking
Round Rock backflow program page
BSI Online tracking
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Registered BPAT status, City tester registration | Keep the BSI Online submission confirmation and repair/retest evidence if the device fails. | Annual for high-hazard devices; every 7 years for low-hazard devices | Repair or correction due within 30 days. |
| City of Sugar Land Water Utilities |
Sugar Land BSI Online backflow tracking system
Sugar Land backflow testing program
BSI Online backflow tracking system
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Current TCEQ tester license, Annual pressure-gauge calibration within the expiration period, BSI online entry registration, State-licensed fireline tester employment by a fireline testing company when fireline devices apply | Keep the BSI Online report entry showing the annual test was submitted within 48 hours of the test date. | Report due within 2 days after testing. | The owner remains responsible for compliance even if testing work is delegated. |
| San Antonio Water System Backflow Prevention |
SAWS BSI customer and tester tracking workflow
SAWS backflow prevention program
BSI customer portal
BSI submission portal
|
Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Registered testing company in the SAWS BSI workflow, Licensed BPAT status, Licensed fireline tester status when testing fireline assemblies | Keep the BSI customer compliance record showing the passing result reached the SAWS workflow. | Annual | Retest and accepted report submission are part of the closeout 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.
Queen Creek is a strong utility because it combines annual backflow reporting, BSI filing fees, and strict tester credential requirements.
DSRSD is a strong Bay Area Tokay page because district-approved testers enter existing backflow device tests electronically through the Tokay workflow.
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.
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.
Thornton is a strong Colorado city because it names the covered classes, publishes annual-testing language, and gives a clean portal-driven reporting path.
Fort Collins is a strong Colorado utility because it combines annual testing, BSI reporting, a local tester list, and explicit water-service suspension risk.
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.
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.
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.
Frisco requires installation testing and recurring annual testing for certain testable assemblies, with BSI handling much of the program workflow.
League City is a strong BSI page because it combines annual testing, CCN-based notice lookup, a one-time device registration fee, online tester reporting, and water-service enforcement.
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.
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.
San Antonio requires annual backflow testing and routes both customer compliance checks and registered testing company discovery through BSI under the SAWS program.
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.
No. The portal may handle report submission, but the city, county, water district, or utility still controls deadlines, tester acceptance, fees, and failed-test handling.
Compare the utility name, service address, notice or device identifier, approved tester gate, report acceptance rule, filing fee, due window, and failed-test instructions.
This portal view currently groups 17 mapped utilities with source-backed portal or online submission evidence.
Do not assume that. Many portals still require accepted tester credentials, current certification, license, insurance, gauge calibration, or separate utility approval before reports are accepted.