Notice finder

Turn a backflow notice into the right next page.

Search the city, utility, portal name, notice ID clue, or failed-test phrase. BackflowPath will route you to the most specific source-backed page it has.

Notice guide
City and utility matching Portal family routing Failed-test and tester intent Official-source pages first
Best matches

Routes for "fort-worth"

Open the most specific city or utility route first. Portal hubs help when the notice names a software system but the local utility still controls the rule.

City route

Fort Worth backflow notice route

Fort Worth maps to City of Fort Worth Water Backflow Program. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.

  • Portal: VEPO/Envirotrax
  • Tester gate: official list
  • Due basis: All backflow protection assemblies must be tested on installation, repair, or relocation and annually after that. Commercial-class irrigation backflows are also tested annually.
  • Fee clue: Fort Worth's public materials are clearer on tester registration and inspection sequencing than public retail pricing.
Utility workflow

City of Fort Worth Water Backflow Program workflow

Fort Worth requires testing at installation, repair, or relocation and then annually, with licensed registered testers submitting reports through VEPO.

  • Portal: VEPO/Envirotrax
  • Tester gate: official list
  • Due basis: All backflow protection assemblies must be tested on installation, repair, or relocation and annually after that. Commercial-class irrigation backflows are also tested annually.
  • Fee clue: Fort Worth's public materials are clearer on tester registration and inspection sequencing than public retail pricing.
City route

Fort Collins backflow notice route

Fort Collins maps to Fort Collins Utilities Backflow Prevention and Cross-Connection Control. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.

  • Portal: BSI
  • Tester gate: official list
  • Due basis: Fort Collins Utilities requires test reports on all devices annually, requires new and replacement assemblies to be entered into BSI Online or sent to the city's cross-connection email, and warns that customers can face water-service suspension for noncompliance.
  • Fee clue: The strongest local cost signal is noncompliance risk, not a posted utility fee.
City route

Fort Lauderdale backflow notice route

Fort Lauderdale maps to City of Fort Lauderdale Backflow and Cross-Connection Control. Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.

  • Portal: BSI
  • Due basis: Fort Lauderdale routes annual compliance through BSI and says failure to submit a backflow test report can lead to a $250 fine after 90 days, with annual testing for commercial, industrial, and hazardous sites and biennial testing for residential irrigation devices.
  • Fee clue: The strongest local cost pressure is the risk of fines and missed reporting windows.
  • Failed-test clue: Fort Lauderdale publishes a real annual report form.
City route

Sugar Land backflow notice route

Sugar Land maps to City of Sugar Land Water Utilities. Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.

  • Portal: BSI
  • Due basis: Testing is due on the same date every month and not one year from the last test date. Test reports for existing and replacement devices must be submitted through the BSI tracking system.
  • Fee clue: The City page is stronger on workflow and enforcement than public pricing, so use local quotes rather than assuming a statewide rate.
  • Failed-test clue: The owner remains responsible for compliance even if testing work is delegated.
Utility workflow

Broward County Water and Wastewater Services Backflow Certification workflow

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.

  • Portal: BSI
  • Due basis: Broward notifies customers 60 days and 30 days before the annual compliance due date and requires passing test results plus filing fees through Backflow Solutions Incorporated.
  • Fee clue: The main local cost signal is not a flat county test fee; it is the annual compliance plus filing workflow.
  • Failed-test clue: Broward uses explicit 60-day and 30-day reminders.
Utility workflow

City of Fort Lauderdale Backflow and Cross-Connection Control workflow

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.

  • Portal: BSI
  • Due basis: Fort Lauderdale routes annual compliance through BSI and says failure to submit a backflow test report can lead to a $250 fine after 90 days, with annual testing for commercial, industrial, and hazardous sites and biennial testing for residential irrigation devices.
  • Fee clue: The strongest local cost pressure is the risk of fines and missed reporting windows.
  • Failed-test clue: Fort Lauderdale publishes a real annual report form.
Utility workflow

City of Sugar Land Water Utilities workflow

Sugar Land runs an annual testing program for health-hazard backflow devices and tracks compliance through BSI.

  • Portal: BSI
  • Due basis: Testing is due on the same date every month and not one year from the last test date. Test reports for existing and replacement devices must be submitted through the BSI tracking system.
  • Fee clue: The City page is stronger on workflow and enforcement than public pricing, so use local quotes rather than assuming a statewide rate.
  • Failed-test clue: The owner remains responsible for compliance even if testing work is delegated.
Utility workflow

East Bay Municipal Utility District Backflow Prevention workflow

EBMUD supports trustworthy utility pages because it publishes an approved tester list, official policy links, and fire-flush rules that make the program operationally concrete.

  • Tester gate: official list
  • Due basis: EBMUD requires tests to be performed by testers on the district's approved list and keeps separate scheduling rules for fire flushes and related field operations.
  • Fee clue: The district's commercial value is in approval gating and project sequencing, not in a public retail fee sheet.
  • Failed-test clue: EBMUD keeps its own approved tester exam and public list.
Utility workflow

Fort Collins Utilities Backflow Prevention and Cross-Connection Control workflow

Fort Collins is a strong Colorado utility because it combines annual testing, BSI reporting, a local tester list, and explicit water-service suspension risk.

  • Portal: BSI
  • Tester gate: official list
  • Due basis: Fort Collins Utilities requires test reports on all devices annually, requires new and replacement assemblies to be entered into BSI Online or sent to the city's cross-connection email, and warns that customers can face water-service suspension for noncompliance.
  • Fee clue: The strongest local cost signal is noncompliance risk, not a posted utility fee.
Utility workflow

Lee County Utilities Cross-Connection Control Program workflow

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.

  • Portal: BSI
  • Due basis: Lee County Utilities says required devices are tested at installation and every year after that. The county uses a cross-connection portal, gives customers portal access tied to the account, and expects approved reports to keep the account in compliance.
  • Fee clue: Lee County's local friction is the portal-driven compliance step, not just getting a device tested.
  • Failed-test clue: Lee County says devices are tested at installation and annually thereafter.
Portal shortcuts

Jump to a named portal family

BSI

Find utility pages where BSI Online or Backflow Solutions appears in the official backflow test report, tester enrollment, or submission workflow.

WEIRS

Find utility pages where WEIRS appears in the official backflow tester lookup, water inspection, or report submission workflow.

SwiftComply

Find utility pages where SwiftComply or C3Swift appears in the official backflow report submission workflow.

VEPO/Envirotrax

Find utility pages where VEPO or Envirotrax appears in the official backflow tester registration, credential verification, or report submission workflow.

Aqua/TrackMyBackflow

Find utility pages where Aqua Backflow or TrackMyBackflow appears in the official backflow test reporting, filing-fee, or tester registration workflow.

Tokay WebTest

Find utility pages where Tokay or Tokay WebTest appears in the official backflow tester approval, credential, or online test report entry workflow.

Notice clue routes

Use the exact clue instead of a broad search

These shortcuts mirror the repeated winning pattern: city plus portal, city plus tester gate, city plus failed-test or annual notice.

Tester

Approved tester wording

Use this when the notice says approved, certified, registered, credential, license, insurance, or gauge calibration.

Urgency

Due date or failed-test wording

Use this when the notice mentions annual, due, deadline, anniversary, failed, repair, or retest.

Popular notice routes

Open source-backed routes without searching

These are the priority notice and portal paths to crawl first because they combine city, portal, tester, and report-submission intent.

Featured utility records

Open a utility workflow when the notice names the authority

Notice FAQ

What to read from a backflow notice

What should I paste into the BackflowPath notice finder?

Paste the city, utility, portal name, notice identifier, account clue, device clue, approved-tester wording, due-date wording, or failed-test phrase from the notice.

Which portal names can the notice finder route?

The finder recognizes BSI, Backflow Solutions, SwiftComply, C3Swift, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay, and Tokay WebTest when those terms match source-backed pages.

What notice identifiers matter before scheduling a tester?

Keep the due date, service address, account number, CCN, Hazard ID, Site ID, device ID, assembly serial, or portal record visible so the tester can match the utility workflow.

What should I do if the notice says failed backflow test?

Open the failed-test route first. A failed assembly usually needs repair, retest, and accepted report submission, not only a generic annual testing appointment.