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

Submit San Diego 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 San Diego.

Open utility source workflow Utility requirements Find from notice Request local help
City: San Diego Utility: City of San Diego Public Utilities Backflow Program Cadence: Upon installation and annually thereafter Last verified: 2026-06-29
Local answer

What to check for San Diego

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

  • Due basis: San Diego says all backflow devices are tested annually and points customers to the approved tester list when the Public Utilities Department contacts them for compliance.
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Who is affected: Multi-family, commercial, industrial, dedicated irrigation, and fire-protection services that the Public Utilities Department identifies as requiring backflow protection.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 858-292-6329
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority City of San Diego Public Utilities Backflow 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 San Diego 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: San Diego Backflow Program - program page
  • Submission path: San Diego Request for Test form - faq and submission context
  • Submission path: San Diego approved tester list - 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: San Diego says all backflow devices are tested annually and points customers to the approved tester list when the Public Utilities Department contacts them for compliance.
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

  • San Diego Backflow Program (program page)
  • San Diego Request for Test form (faq and submission context)
  • San Diego approved 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

San Diego 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: San Diego Backflow Program, San Diego Request for Test form, San Diego approved 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

San Diego questions before you act

How do I submit a backflow test report for San Diego?

Use the official utility workflow and submission methods listed on this page: San Diego Backflow Program, San Diego Request for Test form, San Diego approved tester list. Program phone: 858-292-6329. 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 San Diego 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 San Diego 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 San Diego Public Utilities Backflow Program.

Who controls the rule for San Diego?

San Diego search demand is routed to City of San Diego Public Utilities Backflow Program. Multi-family, commercial, industrial, dedicated irrigation, and fire-protection services that the Public Utilities Department identifies as requiring backflow protection.

What costs or fees should I expect for San Diego?

Testing is market-based, but the city's approved-list constraint shapes the quote more than a public fee schedule. Repair and retest pricing depends on assembly size and whether fire or meter-protection constraints apply. The commercial value is in the approved-list funnel and the enforcement pressure, not in a published retail rate.