Use this hub when the field test is done but the compliance cycle still depends on BSI, WEIRS, SwiftComply, VEPO, Envirotrax, Aqua/TrackMyBackflow, Tokay WebTest, or a utility online submission path.
Start here for searches like submit backflow report, upload backflow test, BSI report submission, Austin WEIRS, Dallas SwiftComply, TrackMyBackflow Hazard ID, Tokay WebTest report, or VEPO Envirotrax tester submission.
Open the city submission route when the notice names a city. Open the utility workflow when the notice names only the governing water authority.
| Utility and cities | Portal or submission route | Notice clue | Acceptance proof | Open route |
|---|---|---|---|---|
| City of Flagstaff Backflow Prevention Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| Mesa Water Resources Backflow Prevention | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Town of Queen Creek Backflow Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Tucson Water Backflow Prevention | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Anaheim Cross Connection Control | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Buena Park Water Backflow Reporting | Aqua/TrackMyBackflow | Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Oxnard Water Division Backflow Prevention | Tokay WebTest | Look for the Tokay/WebTest entry, tester login context, device record, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Pleasanton Cross-Connection Control Plan | Aqua/TrackMyBackflow | Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Sacramento Department of Utilities Cross-Connection Control | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of San Diego Public Utilities Backflow Program | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Dublin San Ramon Services District Backflow Testing | Tokay WebTest | Look for the Tokay/WebTest entry, tester login context, device record, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Sacramento Suburban Water District Cross-Connection Control Program | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| San Francisco Public Utilities Commission Backflow Prevention Program | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Aurora Water Backflow Prevention | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Aspen Cross Connection Control AKA Backflow Prevention Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Greeley Cross-Connection Control Program | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Lafayette Backflow Compliance Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Longmont Backflow Prevention and Cross-Connection Control | SwiftComply | Look for the SwiftComply or C3Swift account, device, address, or notice record. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Thornton Cross Connections and Backflow Prevention | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| Colorado Springs Utilities Backflow Prevention | SwiftComply | Look for the SwiftComply or C3Swift account, device, address, or notice record. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| Fort Collins Utilities Backflow Prevention and Cross-Connection Control | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Parker Water and Sanitation District Backflow and Cross-Connection Control | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Fort Lauderdale Backflow and Cross-Connection Control | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Tampa Water Department Backflow Prevention | SwiftComply | Look for the SwiftComply or C3Swift account, device, address, or notice record. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| Lee County Utilities Cross-Connection Control Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| Manatee County Utilities Cross Connection Control Program | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Orange County Utilities Cross Connection Control | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Austin Water Cross-Connection Control | WEIRS | Look for the WEIRS route, service address, tester record, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Baytown Backflow Information | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Bedford Cross Connection and Backflow | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Buda Cross-Connection Control | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Cleburne Backflow Prevention Program | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of College Station Backflow Prevention | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Euless Cross-Connection Control Program | Aqua/TrackMyBackflow | Look for the Hazard ID, Site ID, device record, or TrackMyBackflow customer record. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Fort Worth Water Backflow Program | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Frisco Backflow Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Irving Cross Connections and Backflow | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of League City Backflow Testing Program | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Leander Cross-Connection Control | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Lewisville Backflow Testing | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Mansfield Water Utilities Backflow Testing | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Marble Falls Backflow Prevention and Cross Connection | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of McKinney Cross Connection Prevention | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Round Rock Backflow Prevention | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Southlake Cross Connection Control | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| City of Sugar Land Water Utilities | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| City of Taylor Cross Connection Control Backflow | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Dallas Water Utilities Backflow Prevention Program | SwiftComply | Look for the SwiftComply or C3Swift account, device, address, or notice record. | Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted. | |
| Liberty City Water Supply Corporation Backflow Program | VEPO/Envirotrax | Look for the BPAT/tester registration context, Envirotrax record, service address, or assembly identifier. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| San Antonio Water System Backflow Prevention | BSI | Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. | |
| Talty Special Utility District Backflow Testing | reporting portal | Look for the utility name, service address, assembly serial number, account or notice ID, and due date. | Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted. |
Start with the city or utility named on the notice, then match the portal name, device or account clue, accepted tester route, and report acceptance rule before filing.
No. Many utilities require the report to be entered through a named portal or online submission path. Keep proof that the report was submitted and accepted.
BackflowPath currently groups source-backed routes for BSI, WEIRS, SwiftComply, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, and utility-run online submission workflows.
Keep the notice, due date, service address, device identifier, tester name, portal confirmation, accepted report receipt, or account history showing the submission was accepted.
A portal can collect reports, but the utility still controls who must test, which tester is accepted, what identifier is required, and whether a failed test needs repair, retest, or resubmission.