BackflowVerdict Local backflow requirements
Request help
Menu
Request help
Portal city route

San Francisco reporting portal backflow reporting portal

Use this page when a notice for San Francisco mentions BSI, SwiftComply, WEIRS, VEPO, Aqua/TrackMyBackflow, Tokay WebTest, a customer portal, or online backflow test report submission.

Open utility submission 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 a notice for San Francisco mentions BSI, SwiftComply, WEIRS, VEPO, Aqua/TrackMyBackflow, Tokay WebTest, a customer portal, or online backflow test report submission.

  • 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

  • San Francisco certified tester list - official tester list
  • SFPUC customer service contact - utility contact
  • Due basis: San Francisco pushes users to a certified tester list through SF.gov and keeps the utility contact path inside SFPUC channels.
  • Program phone: 415-551-4720
Other San Francisco routes

Stay inside the city intent cluster

San Francisco annual backflow testing San Francisco annual backflow testing: verify who must test, the due-date rule, tester requirements, and the official submission workflow.
arrow_forward
Submit San Francisco reporting portal backflow test reports How to submit a backflow test report in San Francisco through reporting portal, including notice clues, tester requirements, and accepted filing proof.
arrow_forward
San Francisco approved backflow testers Find the official San Francisco approved backflow tester route and confirm utility registration, credentials, and report submission requirements.
arrow_forward
San Francisco failed backflow test What to do after a failed backflow test in San Francisco: repair, retest, and confirm accepted report submission with the utility.
arrow_forward
San Francisco irrigation backflow testing Check San Francisco irrigation backflow testing triggers, device rules, tester requirements, and the official utility workflow.
arrow_forward
San Francisco fire-line backflow testing Check San Francisco fire-line backflow testing triggers, assembly rules, tester requirements, and the official utility workflow.
arrow_forward
Workflow

San Francisco workflow order

  1. Confirm the property needs a certified backflow test.
  2. Use the official SF.gov tester list.
  3. Schedule the inspection or test with a certified company.
  4. Stay inside the utility's accepted reporting path.
City FAQ

San Francisco questions before you act

Which backflow reporting portal should San Francisco use?

San Francisco maps to San Francisco Public Utilities Commission Backflow Prevention Program. The stored portal context is reporting portal. Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.

What notice or device ID should I keep for San Francisco?

Look for the utility name, service address, assembly serial number, account or notice ID, and due date.

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.