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

Submit Flagstaff 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 Flagstaff.

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

What to check for Flagstaff

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

  • Due basis: Flagstaff requires annual testing for assemblies in the city program, sends courtesy notices when testing is due, and routes tester result submission through BSI Online or city compliance staff.
  • Notice or device clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Who is affected: Flagstaff businesses and protected services with contamination risk, plus irrigation and fire sprinkler assemblies that fall inside the city cross-connection program.
  • Acceptance rule: Report acceptance depends on using the named portal or online submission path; keep proof that the report was submitted.
  • Program phone: 928-213-2475
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority City of Flagstaff Backflow Prevention 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 Flagstaff backflow prevention page (program 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: Flagstaff backflow prevention page - program page
  • Submission path: Flagstaff cross-connection ordinance - ordinance
  • 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: Flagstaff requires annual testing for assemblies in the city program, sends courtesy notices when testing is due, and routes tester result submission through BSI Online or city compliance staff.
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

  • Flagstaff backflow prevention page (program page)
  • Flagstaff cross-connection ordinance (ordinance)
  • 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

Flagstaff 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: Flagstaff backflow prevention page, Flagstaff cross-connection ordinance.
  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

Flagstaff questions before you act

How do I submit a backflow test report for Flagstaff?

Use the official utility workflow and submission methods listed on this page: Flagstaff backflow prevention page, Flagstaff cross-connection ordinance. Program phone: 928-213-2475. 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 Flagstaff 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 Flagstaff 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 Flagstaff Backflow Prevention Program.

Who controls the rule for Flagstaff?

Flagstaff search demand is routed to City of Flagstaff Backflow Prevention Program. Flagstaff businesses and protected services with contamination risk, plus irrigation and fire sprinkler assemblies that fall inside the city cross-connection program.

What costs or fees should I expect for Flagstaff?

Testing is market-priced, but mountain-climate installation details can increase service complexity. Repair and retest cost rises when the assembly needs enclosure or variance work. The strongest local value is clarity around waiver, variance, and repair-retest rules.