Lafayette backflow prevention requirements
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
City backflow route
Lafayette backflow testing routes through City of Lafayette Backflow Compliance Program.
City search demand maps directly to Lafayette's governing BSI-backed compliance workflow. This page keeps the city search term visible while routing the actual compliance work to the governing utility record.
City: Lafayette
Utility: City of Lafayette Backflow Compliance Program
Cadence: Annually
Last verified: 2026-06-29
Next action
Pick the Lafayette 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.
Lafayette annual backflow testing
Annually Lafayette runs backflow compliance through the city utility and BSI Online. The city says annual backflow tests are due by May 31 for irrigation systems and by August 31 for all other backflow devices, with late fees and possible water shutoff if the device stays out of compliance.
Lafayette backflow reporting portal
Use the utility page to confirm whether reports go through BSI, WEIRS, SwiftComply, a city portal, or another official submission path.
Lafayette failed backflow test
Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.
Lafayette irrigation backflow testing
Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.
Why Lafayette maps to City of Lafayette Backflow Compliance Program
City search demand maps directly to Lafayette's governing BSI-backed compliance workflow.
- Lafayette utility customers with irrigation systems or any other city-required backflow devices.
- Lafayette says late tests and failed devices can trigger fines, late fees, and eventual water shutoff if the assembly is not returned to compliance.
- Program phone: 303-661-1272
- City route reviewed: 2026-04-05
Source-backed workflow
Lafayette is a useful Colorado utility because the city publishes separate annual due dates for irrigation and non-irrigation devices, runs the workflow through BSI, and keeps enforcement language visible.
Support guides
Read these before acting on the Lafayette workflow
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.
Backflow reporting portals
How BSI, SwiftComply, and utility customer portals change the real testing workflow after the field work is done.
Anniversary date vs calendar deadline
Why some utilities track backflow tests by anniversary date, while others push owners into a calendar-season or hard-date deadline.
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.