Routes for "colorado-springs"
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.
Colorado Springs backflow notice route
Colorado Springs maps to Colorado Springs Utilities Backflow Prevention. Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
- Portal: SwiftComply
- Due basis: Colorado Springs Utilities requires customers to hire a backflow tester for the annual compliance test and expects test results to be entered within five days through SwiftComply.
- Fee clue: The value is in understanding the portal and survey gate, not in a public price schedule.
- Failed-test clue: Colorado Springs uses a five-day result-entry expectation.
Colorado Springs Utilities Backflow Prevention workflow
Colorado Springs Utilities is a strong Colorado page because it shows how the utility actually runs the testing workflow: portal registration, certification uploads, five-day test entry, and survey-first rules.
- Portal: SwiftComply
- Due basis: Colorado Springs Utilities requires customers to hire a backflow tester for the annual compliance test and expects test results to be entered within five days through SwiftComply.
- Fee clue: The value is in understanding the portal and survey gate, not in a public price schedule.
- Failed-test clue: Colorado Springs uses a five-day result-entry expectation.
Arvada backflow notice route
Arvada maps to City of Arvada Backflow and Cross-Connection Control Program. Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
- Tester gate: official list
- Due basis: Arvada says all assemblies must be tested annually, moved every assembly to a July 31 deadline, and added a non-compliance fee schedule.
- Fee clue: The biggest local pressure is the deadline plus fee-backed non-compliance, not a flat city testing rate.
- Failed-test clue: Arvada gives a hard annual deadline.
Aspen backflow notice route
Aspen maps to City of Aspen Cross Connection Control AKA Backflow Prevention Program. 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: Aspen says initial notifications now come directly from BSI and testers are required to submit reports online through BSI. The city also says containment devices are tested at least annually and residents receive a reminder before the anniversary of the test date.
- Fee clue: Aspen's strongest commercial signal is the utility's operational discipline around reminders, list-based routing, and BSI reporting.
Aurora backflow notice route
Aurora maps to Aurora Water Backflow Prevention. Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
- Due basis: Aurora says operational tests by a certified technician must be conducted upon installation and at least annually thereafter, and results must be submitted online before the annual test due date.
- Fee clue: Aurora's value is the clear annual workflow and owner-responsibility language, not a published test-price table.
- Failed-test clue: Aurora requires online submission before the due date.
Castle Rock backflow notice route
Castle Rock maps to Castle Rock Water Cross-Connection and Backflow Program. Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
- Tester gate: official list
- Due basis: Castle Rock says annual testing is required, compliance is managed by Castle Rock Water, and only certified testers may work in town.
- Fee clue: Castle Rock's main commercial advantage is a clean certified-tester workflow plus list freshness.
- Failed-test clue: Castle Rock says annual testing is required.
Denver backflow notice route
Denver maps to Denver Water Cross-Connection Control and Backflow Prevention Program. Use the listed submission method and keep proof that the report was filed with the utility.
- Due basis: Denver Water sends a testing reminder 30 days before the annual test is due, expects certified testers to report results to the Cross-Connection Control office, and can assess a $250 penalty after repeated ignored notices.
- Fee clue: The financial risk is not just the tester invoice; it is also Denver Water's penalty and service-interruption exposure.
- Failed-test clue: Denver Water sends reminder letters and can assess a $250 penalty.
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.
- 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.
Englewood backflow notice route
Englewood maps to City of Englewood Backflow Prevention and Cross-Connection Control Program. Use the listed submission method and keep proof that the report was filed with the utility.
- Due basis: Englewood's program centers on surveys, inspections, and utility notification whenever customers add new cross-connections or change protected water uses.
- Fee clue: The strongest local advantage is the city's clear change-of-use logic, not a posted fee.
- Failed-test clue: Englewood names specific hazard triggers instead of generic annual copy.
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.
Grand Junction backflow notice route
Grand Junction maps to City of Grand Junction Backflow Prevention Program. Use the listed submission method and keep proof that the report was filed with the utility.
- Due basis: Grand Junction says backflow preventers are required under Colorado drinking-water regulations and city resolution, and that PVBAs must be tested at installation, annually, and when moved or repaired.
- Fee clue: The main local value is clear device-specific rules for sprinkler-heavy properties.
- Failed-test clue: Grand Junction names sprinkler and fire-sprinkler systems directly.
Greeley backflow notice route
Greeley maps to City of Greeley Cross-Connection Control Program. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
- Tester gate: official list
- Due basis: Greeley requires all containment backflow prevention assemblies to be tested upon installation, after repairs or relocation, and annually. The city moved testing notifications and report submission into its Spry Backflow portal.
- Fee clue: The local value comes from the operational workflow and tester routing, not a published city rate.
- Failed-test clue: Greeley uses a real portal workflow instead of phone-only backflow management.