municipal utility · official record
Lafayette utility backflow testing requirements
Lafayette is a strong Front Range utility because it publishes clear annual due dates by device type, a BSI workflow, and enforcement language with fees and shutoff risk.
Fast answer
Who, when, and what device?
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.
- Who is affected
- Lafayette utility customers with irrigation systems or any other city-required backflow devices.
- Covered devices
- Backflow prevention devices · Irrigation assemblies · City-monitored testable assemblies
- Risk if missed
- Lafayette says late tests and failed devices can trigger fines, late fees, and eventual water shutoff if the assembly is not returned to compliance.
What to do now
Choose the task on your notice
The official rule stays on this record; national guidance explains the task.
Exact workflow
Follow the local sequence
- 01
Confirm the device type and its annual due date.
- 02
Complete the annual test through Lafayette's utility workflow.
- 03
Post the result through the BSI-side process.
- 04
Do not let late fees or shutoff escalation start.
Tester gate
Who can produce an accepted result?
Confirm tester eligibility directly with City of Lafayette Backflow Compliance Program before scheduling.
Submission route
Where the result goes
Use the official program contact and submission method below.
- Lafayette backflow compliance support utility contact page
- Lafayette BSI customer portal reporting portal
- Lafayette code library city code
Local detail
Property, device, and enforcement notes
Open the parts that match the property and system. These details stay subordinate to the fast workflow above.
Program and failure notes
- Lafayette separates irrigation and non-irrigation annual due dates.
- Late fees and water shutoff are part of the city's enforcement path.
- The workflow is utility-plus-BSI, not generic contractor routing.
- Irrigation systems are due by May 31.
- Other backflow devices are due by August 31.
- Late fees and shutoff risk are part of the city workflow.
Residential notes
- Residential demand is strongest for irrigation assemblies because Lafayette gives irrigation its own due date.
- The BSI workflow makes this more actionable than a general educational page.
Commercial notes
- Commercial value comes from the separate due-date rules, late fees, and shutoff risk.
- Users need the city utility and BSI workflow, not just a contractor recommendation.
Irrigation
Lafayette is a good irrigation page because the city publishes a separate irrigation due date rather than flattening everything into one generic annual deadline.
- Irrigation assemblies come due earlier than the rest of the city's devices.
- The BSI workflow still controls the reporting path.
- Late fees and shutoff risk apply if the irrigation device stays out of compliance.
Cost and fee context
Testing is market-priced, but Lafayette's date-specific enforcement matters more than a generic Colorado average.
Repair and retest cost depends on assembly type and whether the device is already running into late fees.
The strongest local pressure is meeting the right due date and avoiding late-fee or shutoff escalation.
Evidence ledger
Official sources
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.
BackflowVerdict summarizes these records; the governing entity remains the authority.
Open official program page- 01Lafayette backflow compliance supportutility contact pageOpen source ↗
- 02Lafayette BSI customer portalofficial reporting portalOpen source ↗
- 03Lafayette code librarycity code contextOpen source ↗
Commercial handoff · separate layer
Still need help after reading the rule?
The request keeps this utility ID and source page with the handoff.