A passed test is not the same thing as a completed compliance cycle. Many utilities now care as much about BSI, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, or a customer portal as they do about the field result.
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.
These pages are selected from the utility records most relevant to this guide and ranked by structured evidence.
These hub pages group utilities by the reporting system named in the public workflow, then send the user back to the exact authority page.
Use this route when the notice mentions BSI Online, Backflow Solutions, a CCN, or online test report entry through BSI.
Use this route when the utility uses SwiftComply or C3Swift for tester registration and report submission.
Use this route when the local workflow references WEIRS for tester lookup, inspection, or report submission.
Use this route when the utility names VEPO or Envirotrax for BPAT registration, credential verification, approved-list status, or report submission.
Use this route when the notice mentions Aqua Backflow, TrackMyBackflow, a filing fee, or a hazard/site ID for online report entry.
Use this route when the utility requires Tokay WebTest, tester credentials, test kit calibration records, or online report entry through a Tokay portal.
Use this route when the official workflow names SpryBackflow or a utility-specific Spry backflow site for online test result submission.
These routes carry concrete local intent: portal names, annual notices, inspection language, tester gates, and utility-specific report acceptance.
Austin search demand already shows WEIRS language, so the city route should carry the portal, tester, and report-submission path directly.
Use this path when the notice or tester workflow is about SwiftComply report entry, device records, failed tests, or accepted submission proof.
Fort Worth has separate annual-testing, portal, failed-test, and report-submission intent. Do not flatten those into one generic backflow page.
GSC shows VEPO backflow demand landing on Southlake. Keep the annual letter, VEPO records, registered tester search, paperless submission, and device fee close together.
Aurora already has search visibility. Keep the utility workflow, inspection language, and portal path close together.
Anaheim has installation and prevention impressions, so the route should make the official program and tester path easy to reach.
Hillsborough is already getting impressions and clicks. Keep annual-testing, cost, and utility source context linked from the guide layer.
Utilities that use BSI, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, 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.
A BSI route, a SwiftComply route, a WEIRS route, a VEPO/Envirotrax route, an Aqua/TrackMyBackflow route, a Tokay WebTest route, a SpryBackflow route, and a utility customer portal each imply different registration, fee, credential, due-date, and tester-enrollment assumptions. Treating them as one generic online submission step is how people lose time.
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.
Many utilities now route compliance through BSI, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, or utility-managed customer portals. The practical mistake is assuming the field test alone closes the loop.
What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.
Why official tester lists and commercial directories must stay separate, and what each page type is allowed to claim.