BackflowVerdict Local backflow requirements
Request help
Menu
Request help
Mission statement

Provider narrative and compliance posture

Official tester listed on Greeley's certified tester PDF and Fort Collins' certified tester page for the Northern Colorado corridor.

This profile does not override the utility's official rules. It exists to make the public provider layer inspectable after the governing workflow is clear.

Before booking this provider

Match AJ's Backflow Testing to the Fort Collins Utilities Backflow Prevention and Cross-Connection Control workflow

The strongest local provider pages do not stop at a phone number. Confirm the authority source, the utility's tester gate, the report route, and the proof trail before you schedule or send a failed device back for retest.

Official source Officially listed across Greeley and Fort Collins tester rosters.
Due trigger Upon installation and annually thereafter - 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.
Notice clue Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
Report proof Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
Submission route Fort Collins backflow program
Failed-test branch Ask whether repair, retest, and final submission are all handled under the same utility workflow.
Open utility workflow Official tester route BSI portal context Request local help
Regional coverage map
Jurisdictional coverage

1 mapped metro support page(s).

Coverage

Utility coverage

2 mapped utility pages

Utility count 2
Metro count 1
Guide links 5
  • Official tester listed on Greeley's certified tester PDF and Fort Collins' certified tester page for the Northern Colorado corridor.
  • Authority source
  • Last reviewed 2026-04-05
Service area

Area served across mapped utility pages

States Colorado
Cities Fort Collins, Greeley
Counties Larimer County, Weld County
  • Backflow testing
  • Backflow compliance support
  • Annual testing coordination
  • Failed test follow-up
  • Irrigation backflow testing
  • Fire line backflow testing

Verification basis

  • 2 mapped utility pages
  • 2 mapped utilities with an official tester route
  • 0 mapped utilities using a directory route
  • 2 mapped utilities with structured submission steps
  • Latest mapped utility verification: 2026-06-29
Covered utilities

Utility pages this provider is mapped to

colorado

Fort Collins Utilities Backflow Prevention and Cross-Connection Control

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

  • 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.
  • Notice clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Submission route: Fort Collins backflow program
  • Proof to keep: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
Open utility page Official tester route BSI context
colorado

City of Greeley Cross-Connection Control Program

Greeley is a strong Colorado utility because it combines annual testing, Spry portal reporting, and an official local tester 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.
  • Notice clue: Look for the utility service address, responsible party or customer record, assembly record, and annual due-date clue before opening SpryBackflow.
  • Submission route: Greeley cross-connection program
  • Proof to keep: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
Open utility page Official tester route SpryBackflow context
Support guides

Guides that match this provider's utility mix

Approved testers vs find a tester Why official tester lists and commercial directories must stay separate, and what each page type is allowed to claim.
arrow_forward
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.
arrow_forward
Backflow reporting portals: BSI, SwiftComply, WEIRS, VEPO, Aqua, Tokay, and SpryBackflow Find how BSI Online, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, and utility customer portals affect backflow test report submission after the field test.
arrow_forward
Backflow test due dates: anniversary date vs calendar deadline Why some utilities track annual backflow tests by anniversary date, while others use a calendar window, notice date, or hard deadline.
arrow_forward
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.
arrow_forward
Profile maintenance

Need a correction to this profile?

If a phone number, website, or approval source is wrong, report it for manual review. BackflowVerdict updates public provider profiles only after checking the source record.

Report a correction Contact BackflowVerdict