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

Submit Fort Collins 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 Fort Collins.

Open utility source workflow Utility requirements Find from notice Request local help
City: Fort Collins Utility: Fort Collins Utilities Backflow Prevention and Cross-Connection Control Cadence: Upon installation and annually thereafter Last verified: 2026-06-29
Local answer

What to check for Fort Collins

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

  • 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 or device clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Who is affected: Commercial, industrial, irrigation, hydrant-meter, and other Fort Collins Utilities customers whose services create actual or potential cross-connections.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 970-416-2249
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority Fort Collins Utilities Backflow Prevention and Cross-Connection Control
Notice trigger Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
Tester gate View the official tester list
Submission route Fort Collins backflow program (program page)
Proof to keep Report acceptance depends on the named portal and the utility-approved tester route; 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: Fort Collins backflow program - program page
  • Submission path: Fort Collins certified tester list - official tester list
  • Notice or device clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Tester gate: Start with the governing authority's published tester list. This utility has an official approved-tester route and it should be treated as the primary source.
  • Report acceptance: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • 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.
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

  • Fort Collins backflow program (program page)
  • Fort Collins certified tester list (official tester list)
  • View the official tester list
After filing

Keep acceptance proof

  • Report acceptance depends on the named portal and the utility-approved tester route; 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

Fort Collins workflow order

  1. Match the utility notice to the service address, device or assembly record, and due date.
  2. Confirm the tester is accepted through the governing tester-list or approval route before the report is filed.
  3. File the result through the stored submission path: Fort Collins backflow program, Fort Collins certified tester list.
  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

Fort Collins questions before you act

How do I submit a backflow test report for Fort Collins?

Use the official utility workflow and submission methods listed on this page: Fort Collins backflow program, Fort Collins certified tester list. Program phone: 970-416-2249. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.

What information should be ready before filing the Fort Collins 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 Fort Collins 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 Fort Collins Utilities Backflow Prevention and Cross-Connection Control.

Who controls the rule for Fort Collins?

Fort Collins search demand is routed to Fort Collins Utilities Backflow Prevention and Cross-Connection Control. Commercial, industrial, irrigation, hydrant-meter, and other Fort Collins Utilities customers whose services create actual or potential cross-connections.

What costs or fees should I expect for Fort Collins?

Testing is market-priced, but Fort Collins narrows the path through a local tester list and utility reporting rules. Repair and retest cost depends on the assembly type and whether the case is irrigation, hydrant meter, or another protected service. The strongest local cost signal is noncompliance risk, not a posted utility fee.