Annual testing
Open the annual page when the utility notice is about routine testing, timing, and accepted submission methods.
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.
This page is the rule hub. Use it to confirm the governing utility workflow, then open the focused page that matches the actual situation on site.
Open the annual page when the utility notice is about routine testing, timing, and accepted submission methods.
Open the failed-test page when the device already failed and you need the repair, retest, and reporting order.
Open the irrigation page when the question is tied to sprinkler systems, reclaimed water, or landscape devices.
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.
Every focused page on this utility still runs through this authority sequence. Confirm the rule here before you branch into repair, testing, or provider routing.
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.
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 utility customers with irrigation systems or any other city-required backflow devices.
Use the official utility workflow and submission methods listed on this page: Lafayette backflow compliance support, Lafayette BSI customer portal, Lafayette code library. Program phone: 303-661-1272.
No public tester directory is live for this utility yet. Use the official utility page first and do not infer approval from a generic directory.
No public tester route is live for this utility yet. Stay on the authority workflow and submission methods before treating any outside provider directory as reliable.
Typical testing and repair pricing used to frame next-action decisions in the metro around this utility.
Provider routing stays clearly labeled below the official workflow. This block exists to frame public provider discovery without implying authority status.