San Francisco backflow prevention requirements
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
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.
The city term helps discovery. The governing utility still decides the rule, submission method, tester route, and follow-up order.
Start with the utility page to confirm who is affected, accepted submission methods, phone contact, and source evidence.
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.
Use the utility page to confirm whether reports go through BSI, WEIRS, SwiftComply, a city portal, or another official submission path.
This utility has an official tester-list route. Confirm status on the governing list before treating a provider as approved.
Use the failed-test page when the assembly has already failed and the next step is repair, retest, and report submission.
Use this path when the question is tied to sprinkler systems, reclaimed water, outdoor service, or irrigation assemblies.
Use this path when the assembly serves fire protection equipment or a managed commercial site.
City search demand maps directly to SFPUC's certified tester and backflow workflow.
San Francisco is commercially useful because SF.gov exposes a certified tester list with real companies instead of making users guess.
Provider profiles can help after the city and utility workflow is clear. They do not replace the official source trail.
Officially listed on the San Francisco certified tester list
Officially listed on the San Francisco certified tester list
Officially listed on the San Francisco certified tester list
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
How BSI, SwiftComply, and utility customer portals change the real testing workflow after the field work is done.
Why the local trigger is rarely just residential versus commercial, and how utilities actually split hazard, irrigation, multifamily, and managed-property cases.
How to think about annual testing, repair, and retest pricing without confusing a market quote with the compliance rule.