City backflow route

Durango backflow testing routes through City of Durango Backflow Prevention.

City search demand maps directly to Durango's official backflow prevention and tester-list workflow. This page keeps the city search term visible while routing the actual compliance work to the governing utility record.

City: Durango Utility: City of Durango Backflow Prevention Cadence: Upon installation, after repair, and annually Last verified: 2026-06-29
Next action

Pick the Durango backflow path that matches the problem

The city term helps discovery. The governing utility still decides the rule, submission method, tester route, and follow-up order.

Requirements

Durango backflow prevention requirements

Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.

Annual notice

Durango annual backflow testing

Upon installation, after repair, and annually 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.

Tester route

Durango approved backflow testers

This utility has an official tester-list route. Confirm status on the governing list before treating a provider as approved.

Repair or failure

Durango failed backflow test

Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.

Irrigation

Durango irrigation backflow testing

Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.

Fire line

Durango fire-line backflow testing

Use this path when the assembly serves fire protection equipment or a managed commercial site.

Before scheduling in Durango

Check the local rule before treating this as a generic tester search

  • Cadence: Upon installation, after repair, and annually
  • 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.
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission: Durango backflow prevention
  • Acceptance rule: Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
  • Cost signal: Testing is market-priced, but Durango's five-day report deadline changes how quickly owners need to act after a test.
Owner vs tester

Durango action split

Authority mapping

Why Durango maps to City of Durango Backflow Prevention

City search demand maps directly to Durango's official backflow prevention and tester-list workflow.

  • Customers with a city water service where Durango identifies a potential cross connection, including irrigation, heating, beverage, and fire suppression uses.
  • Durango ties the program directly to the city code and expects test reports within five days. Owners are also expected to keep test records for three years, which makes backflow compliance part of the utility's formal record trail.
  • Program phone: 970-375-4882
  • City route reviewed: 2026-04-05
Support guides

Read these before acting on the Durango workflow

Guide

Backflow test notice: what to do next

What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.

Guide

How we verify local backflow rules

What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.

Guide

Residential vs commercial backflow rules

Why the local trigger is rarely just residential versus commercial, and how utilities actually split hazard, irrigation, multifamily, and managed-property cases.

Guide

Backflow test cost: annual testing, repairs, and portal fees

How annual backflow test cost changes when the utility requires registered testers, repairs, retests, BSI fees, or online reporting.