BackflowPath Local backflow requirements
Request help
Menu
Request help
Report submission route

Submit Lafayette BSI backflow test reports

Use this page when the notice or tester workflow is about submitting, uploading, filing, or confirming a backflow test report for Lafayette.

Open utility source workflow Utility requirements Find from notice Request local help
City: Lafayette Utility: City of Lafayette Backflow Compliance Program Cadence: Annually Last verified: 2026-06-29
Local answer

What to check for Lafayette

Use this page when the notice or tester workflow is about submitting, uploading, filing, or confirming a backflow test report for Lafayette.

  • Due basis: 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.
  • Notice or device clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Who is affected: Lafayette utility customers with irrigation systems or any other city-required backflow devices.
  • Acceptance rule: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
  • Program phone: 303-661-1272
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

This is the working path for Lafayette notices: match the authority, confirm the tester gate, use the accepted submission route, and keep proof that the report was accepted.

Authority City of Lafayette Backflow Compliance Program
Notice trigger Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
Tester gate Confirm tester eligibility with the governing utility before scheduling.
Submission route Lafayette backflow compliance support (utility contact page)
Proof to keep Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
Failure branch Open failed-test workflow before treating repair, retest, or resubmission as complete.
Local signals

Signals that matter before you act

  • Submission path: Lafayette backflow compliance support - utility contact page
  • Submission path: Lafayette BSI customer portal - reporting portal
  • Submission path: Lafayette code library - city code
  • Notice or device clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Tester gate: 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.
  • Report acceptance: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
  • Due basis: 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.
Submission packet

What the report needs before it can count

Use this as the working checklist for the owner, tester, or property manager before treating a passed field test as a completed compliance cycle.

Before filing

Match the notice record

  • Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Service address, device type, due date, and utility name must match the notice.
  • Use the utility workflow before relying on a generic tester search.
Filing gate

Confirm the accepted route

  • Lafayette backflow compliance support (utility contact page)
  • Lafayette BSI customer portal (reporting portal)
  • Lafayette code library (city code)
  • Confirm tester eligibility with the utility or portal.
After filing

Keep acceptance proof

  • Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
  • Keep portal confirmation, email receipt, account history, or accepted report record.
  • If the assembly failed, use the failed-test workflow before assuming the case is closed.
Failed-test workflow
Workflow

Lafayette workflow order

  1. Match the utility notice to the service address, device or assembly record, and due date.
  2. Confirm tester eligibility with the utility or portal before treating the report as accepted.
  3. File the result through the stored submission path: Lafayette backflow compliance support, Lafayette BSI customer portal, Lafayette code library.
  4. Keep proof that the report was submitted and accepted; a passed field test alone may not close the compliance cycle.
  5. If the assembly failed, follow the repair, retest, and resubmission sequence before assuming compliance is restored.
City FAQ

Lafayette questions before you act

How do I submit a backflow test report for Lafayette?

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. Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.

What information should be ready before filing the Lafayette report?

Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder. Also keep the due date, service address, tester credential status, device type, and proof of submission.

Does the tester or owner submit the Lafayette report?

The field tester often controls portal entry, but the owner should keep the notice, due date, and proof that the report was accepted by City of Lafayette Backflow Compliance Program.

Who controls the rule for Lafayette?

Lafayette search demand is routed to City of Lafayette Backflow Compliance Program. Lafayette utility customers with irrigation systems or any other city-required backflow devices.

What costs or fees should I expect for Lafayette?

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.