San Francisco backflow prevention requirements
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
City backflow route
San Francisco backflow testing routes through San Francisco Public Utilities Commission Backflow Prevention Program.
City search demand maps directly to SFPUC's certified tester and backflow workflow. This page keeps the city search term visible while routing the actual compliance work to the governing utility record.
Open utility requirements
Find from notice
Annual testing
Submit report
San Francisco approved tester route
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
Next action
Pick the San Francisco backflow path that matches the problem
The city term helps discovery. The governing utility still decides the rule, submission method, tester route, and follow-up order.
San Francisco annual backflow testing
On the local certification cycle for protected assemblies San Francisco pushes users to a certified tester list through SF.gov and keeps the utility contact path inside SFPUC channels.
San Francisco backflow reporting portal
Use the utility page to confirm whether reports go through BSI, WEIRS, SwiftComply, a city portal, or another official submission path.
San Francisco approved backflow testers
This utility has an official tester-list route. Confirm status on the governing list before treating a provider as approved.
San Francisco failed backflow test
Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.
San Francisco irrigation backflow testing
Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.
San Francisco fire-line backflow testing
Use this path when the assembly serves fire protection equipment or a managed commercial site.
City intent map
San Francisco pages linked from this hub
These routes keep local searches connected to the exact city, while each page still routes back to the governing utility record.
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
San Francisco reporting portal backflow reporting portal
Find the San Francisco reporting portal backflow report route, notice or device identifiers, tester gate, and proof of accepted submission.
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
Check the local rule before treating this as a generic tester search
- Cadence: On the local certification cycle for protected assemblies
- 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.
- Submission: San Francisco certified tester list
- Acceptance rule: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
- Cost signal: Testing is market-priced, but the local advantage is the public certified tester list.
San Francisco action split
Why San Francisco maps to San Francisco Public Utilities Commission Backflow Prevention Program
City search demand maps directly to SFPUC's certified tester and backflow workflow.
- SFPUC customers and protected San Francisco properties whose assemblies need a certified tester from the city's accepted list.
- Missing the certified-tester workflow makes the property owner more likely to stay in a vague, non-compliant state instead of an accepted SFPUC path.
- Program phone: 415-551-4720
- City route reviewed: 2026-04-05
Source-backed workflow
San Francisco is commercially useful because SF.gov exposes a certified tester list with real companies instead of making users guess.
Provider layer
Public provider profiles mapped to this utility
Provider profiles can help after the city and utility workflow is clear. They do not replace the official source trail.
1 Backflow Plumbing
Officially listed on the San Francisco certified tester list
415 Backflow Testing
Officially listed on the San Francisco certified tester list
AA Precision Backflow
Officially listed on the San Francisco certified tester list
Support guides
Read these before acting on the San Francisco workflow
Backflow test notice: what to do next
What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.
How we verify local backflow rules
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
Backflow reporting portals: BSI, SwiftComply, WEIRS, VEPO, Aqua, Tokay, and SpryBackflow
Find how BSI Online, SwiftComply, WEIRS, VEPO, Envirotrax, Aqua Backflow, TrackMyBackflow, Tokay WebTest, SpryBackflow, and utility customer portals affect backflow test report submission after the field test.
Residential vs commercial backflow rules
Why the local trigger is rarely just residential versus commercial, and how utilities actually split hazard, irrigation, multifamily, and managed-property cases.