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

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

Open utility source workflow Utility requirements Find from notice Request local help
City: San Francisco Utility: San Francisco Public Utilities Commission Backflow Prevention Program Cadence: On the local certification cycle for protected assemblies Last verified: 2026-06-29
Local answer

What to check for San Francisco

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

  • Due basis: San Francisco pushes users to a certified tester list through SF.gov and keeps the utility contact path inside SFPUC channels.
  • Notice or device clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Who is affected: SFPUC customers and protected San Francisco properties whose assemblies need a certified tester from the city's accepted list.
  • Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
  • Program phone: 415-551-4720
Notice-to-closeout map

Source-backed procedure before the record is treated as closed

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

Authority San Francisco Public Utilities Commission Backflow Prevention 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 Francisco certified tester list (official tester list)
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 Francisco certified tester list - official tester list
  • Submission path: SFPUC customer service contact - utility contact
  • 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 Francisco pushes users to a certified tester list through SF.gov and keeps the utility contact path inside SFPUC channels.
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 Francisco certified tester list (official tester list)
  • SFPUC customer service contact (utility contact)
  • 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 Francisco 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 Francisco certified tester list, SFPUC customer service contact.
  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 Francisco questions before you act

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

Use the official utility workflow and submission methods listed on this page: San Francisco certified tester list, SFPUC customer service contact. Program phone: 415-551-4720. 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 Francisco 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 Francisco 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 San Francisco Public Utilities Commission Backflow Prevention Program.

Who controls the rule for San Francisco?

San Francisco search demand is routed to San Francisco Public Utilities Commission Backflow Prevention Program. SFPUC customers and protected San Francisco properties whose assemblies need a certified tester from the city's accepted list.

What costs or fees should I expect for San Francisco?

Testing is market-priced, but the local advantage is the public certified tester list. Repair and retest cost depends on device class and scope of follow-up work. The strongest local signal is accepted tester routing, not a published city fee.