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

Submit Greeley reporting portal backflow test reports

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

Open utility source workflow Utility requirements Find from notice Request local help
City: Greeley Utility: City of Greeley Cross-Connection Control Program Cadence: Upon installation and annually thereafter Last verified: 2026-06-29
Local answer

What to check for Greeley

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

  • Due basis: Greeley requires all containment backflow prevention assemblies to be tested upon installation, after repairs or relocation, and annually. The city moved testing notifications and report submission into its Spry Backflow portal.
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Who is affected: Commercial, industrial, irrigation, fire sprinkler, and other Greeley services that need a containment backflow prevention assembly.
  • 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-350-9811
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority City of Greeley Cross-Connection Control Program
Notice trigger Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
Tester gate View the official tester list
Submission route Greeley cross-connection 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: Greeley cross-connection program - program page
  • Submission path: Spry Backflow portal - submission portal
  • Submission path: Greeley backflow testers - official tester list
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • 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: Greeley requires all containment backflow prevention assemblies to be tested upon installation, after repairs or relocation, and annually. The city moved testing notifications and report submission into its Spry Backflow portal.
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 utility name, service address, assembly serial number, account or notice ID, and due date.
  • 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

  • Greeley cross-connection program (program page)
  • Spry Backflow portal (submission portal)
  • Greeley backflow testers (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

Greeley 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: Greeley cross-connection program, Spry Backflow portal, Greeley backflow testers.
  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

Greeley questions before you act

How do I submit a backflow test report for Greeley?

Use the official utility workflow and submission methods listed on this page: Greeley cross-connection program, Spry Backflow portal, Greeley backflow testers. Program phone: 970-350-9811. 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 Greeley report?

Look for the utility name, service address, assembly serial number, account or notice ID, and due date. Also keep the due date, service address, tester credential status, device type, and proof of submission.

Does the tester or owner submit the Greeley 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 Greeley Cross-Connection Control Program.

Who controls the rule for Greeley?

Greeley search demand is routed to City of Greeley Cross-Connection Control Program. Commercial, industrial, irrigation, fire sprinkler, and other Greeley services that need a containment backflow prevention assembly.

What costs or fees should I expect for Greeley?

Testing is market-priced, but the local tester list and Spry portal shape the workflow more than generic Colorado guidance. Repair and retest cost depends on the assembly type and whether the job is a relocation or a standard annual test. The local value comes from the operational workflow and tester routing, not a published city rate.