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

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

Open utility source workflow Utility requirements Find from notice Request local help
City: Frisco Utility: City of Frisco Backflow Program Cadence: Upon installation and annually thereafter for certain testable assemblies Last verified: 2026-06-29
Local answer

What to check for Frisco

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

  • Due basis: Certain backflow prevention assemblies with test ports must be tested upon installation and thereafter annually by a licensed backflow tester. Frisco administers annual inspection fees through BSI.
  • Notice or device clue: Look for the CCN, account number, BSI record, device ID, or assembly serial from the reminder.
  • Who is affected: Properties where the hazard review requires a testable backflow assembly, including irrigation-related installations and other inspected hazards.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 972-292-5000
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority City of Frisco Backflow Program
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 Frisco backflow program page (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: Frisco backflow program page - program page
  • Submission path: BSI tracking - submission portal
  • 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: Certain backflow prevention assemblies with test ports must be tested upon installation and thereafter annually by a licensed backflow tester. Frisco administers annual inspection fees through BSI.
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

  • Frisco backflow program page (program page)
  • BSI tracking (submission portal)
  • 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

Frisco 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: Frisco backflow program page, BSI tracking.
  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

Frisco questions before you act

How do I submit a backflow test report for Frisco?

Use the official utility workflow and submission methods listed on this page: Frisco backflow program page, BSI tracking. Program phone: 972-292-5000. 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 Frisco 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 Frisco 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 Frisco Backflow Program.

Who controls the rule for Frisco?

Frisco search demand is routed to City of Frisco Backflow Program. Properties where the hazard review requires a testable backflow assembly, including irrigation-related installations and other inspected hazards.

What costs or fees should I expect for Frisco?

Private tester pricing varies, plus a City-administered per-device annual inspection fee. Repair and retest costs vary with assembly type and installation conditions. Frisco is one of the clearer cities on the existence of a City fee layered on top of private testing charges.