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

Submit Colorado Springs SwiftComply backflow test reports

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

Open utility source workflow Utility requirements Find from notice Request local help
City: Colorado Springs Utility: Colorado Springs Utilities Backflow Prevention Cadence: Annually after the assembly is in the program Last verified: 2026-06-29
Local answer

What to check for Colorado Springs

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

  • Due basis: Colorado Springs Utilities requires customers to hire a backflow tester for the annual compliance test and expects test results to be entered within five days through SwiftComply.
  • Notice or device clue: Look for the SwiftComply or C3Swift account, device, address, or notice record.
  • Who is affected: Customers and testers working on assemblies that Colorado Springs Utilities has already surveyed into the program, including external and irrigation assemblies.
  • Acceptance rule: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
  • Program phone: 719-668-4388
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority Colorado Springs Utilities Backflow Prevention
Notice trigger Look for the SwiftComply or C3Swift account, device, address, or notice record.
Tester gate Confirm tester eligibility with the governing utility before scheduling.
Submission route Colorado Springs Utilities backflow professionals portal (tester portal guidance)
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: Colorado Springs Utilities backflow professionals portal - tester portal guidance
  • Submission path: Colorado Springs Utilities rules and regulations - rules and tariff document
  • Notice or device clue: Look for the SwiftComply or C3Swift account, device, address, or notice record.
  • 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: Colorado Springs Utilities requires customers to hire a backflow tester for the annual compliance test and expects test results to be entered within five days through SwiftComply.
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 SwiftComply or C3Swift account, device, address, or notice record.
  • 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

  • Colorado Springs Utilities backflow professionals portal (tester portal guidance)
  • Colorado Springs Utilities rules and regulations (rules and tariff document)
  • 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

Colorado Springs 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: Colorado Springs Utilities backflow professionals portal, Colorado Springs Utilities rules and regulations.
  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

Colorado Springs questions before you act

How do I submit a backflow test report for Colorado Springs?

Use the official utility workflow and submission methods listed on this page: Colorado Springs Utilities backflow professionals portal, Colorado Springs Utilities rules and regulations. Program phone: 719-668-4388. 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 Colorado Springs report?

Look for the SwiftComply or C3Swift account, device, address, or notice record. Also keep the due date, service address, tester credential status, device type, and proof of submission.

Does the tester or owner submit the Colorado Springs 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 Colorado Springs Utilities Backflow Prevention.

Who controls the rule for Colorado Springs?

Colorado Springs search demand is routed to Colorado Springs Utilities Backflow Prevention. Customers and testers working on assemblies that Colorado Springs Utilities has already surveyed into the program, including external and irrigation assemblies.

What costs or fees should I expect for Colorado Springs?

Testing is market-priced, but the portal registration and survey-first rule create real workflow cost. Repair and retest costs vary depending on whether the assembly record is already accurate in the utility system. The value is in understanding the portal and survey gate, not in a public price schedule.