What should I paste into the BackflowVerdict 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.

Backflow notice finder | BackflowVerdict

Best matches

Routes for "durango"

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.

Your likely next steps

Open the local workflow

Open the local utility workflow to confirm the rule before scheduling work.

When Durango says backflow preventers are required to be tested upon installation, after any repairs, and once annually. All test reports must be emailed to [email protected] within five days…

Where to submit Use the submission method listed on the governing utility page.

Who can test it Tester status: official list.

Open the local workflow Still unsure? Request help

Best first

Durango backflow notice route

Durango maps to City of Durango Backflow Prevention. Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.

Open top route Request help

Tester gate: official list
Due basis: Durango says backflow preventers are required to be tested upon installation, after any repairs, and once annually. All test reports must be emailed to [email protected] within five days, and property owners must keep reports for three years.
Fee clue: Durango's real value is the specificity of the compliance surface and the official tester route, not a published city price list.
Failed-test clue: Durango publishes a five-day reporting deadline.

If the first match is not it

Try the next closest route

Notices often mix a city, portal vendor, tester credential, and due-date clue. These are the next strongest matches without scrolling through the full page.

City of Durango Backflow Prevention workflow

Show all matched routes 1 more

City of Durango Backflow Prevention workflow Utility workflow · Durango is an unusually actionable Colorado local page because it publishes the annual cadence, five-day reporting deadline, and direct certified-tester list alongside explicit examples like irrigation, fire suppression, and beverage dispensers.

arrow_forward

Turn a backflow notice into the right next page.

Routes for "durango"

Open the local workflow

Durango backflow notice route

Try the next closest route

Use the next safest step

When the notice only names software

Turn a backflow notice into the right next page.

Routes for "durango"

Open the local workflow

Share this notice route

Durango backflow notice route

Try the next closest route

Use the next safest step

When the notice only names software