Greeley backflow prevention requirements
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
City search demand maps directly to Greeley's governing cross-connection and Spry workflow. This page keeps the city search term visible while routing the actual compliance work to the governing utility record.
The city term helps discovery. The governing utility still decides the rule, submission method, tester route, and follow-up order.
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
Upon installation and annually thereafter 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.
Use the utility page to confirm whether reports go through BSI, WEIRS, SwiftComply, a city portal, or another official submission path.
This utility has an official tester-list route. Confirm status on the governing list before treating a provider as approved.
Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.
Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.
Use this path when the assembly serves fire protection equipment or a managed commercial site.
City search demand maps directly to Greeley's governing cross-connection and Spry workflow.
Greeley is a strong Colorado utility because it publishes annual testing, a Spry Backflow submission workflow, and a local certified tester list rather than leaving the customer with generic state-rule text.
Provider profiles can help after the city and utility workflow is clear. They do not replace the official source trail.
Officially listed across Greeley and Fort Collins tester rosters.
Officially listed across Greeley and Fort Collins tester rosters.
Officially listed on the Greeley certified tester PDF.
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
How BSI, SwiftComply, and utility customer portals change the real testing workflow after the field work is done.
Why some utilities track backflow tests by anniversary date, while others push owners into a calendar-season or hard-date deadline.
Why the local trigger is rarely just residential versus commercial, and how utilities actually split hazard, irrigation, multifamily, and managed-property cases.