public utilities commission · official record
San Francisco utility backflow testing requirements
San Francisco is a strong approved-tester utility because SF.gov publishes a genuine certified tester list with contact details.
Fast answer
Who, when, and what device?
San Francisco pushes users to a certified tester list through SF.gov and keeps the utility contact path inside SFPUC channels.
- Who is affected
- SFPUC customers and protected San Francisco properties whose assemblies need a certified tester from the city's accepted list.
- Covered devices
- Backflow assemblies · Certified testable devices · Protected service assemblies · Fire and larger commercial assemblies
- Risk if missed
- 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.
What to do now
Choose the task on your notice
The official rule stays on this record; national guidance explains the task.
Exact workflow
Follow the local sequence
- 01
Confirm the property needs a certified backflow test.
- 02
Use the official SF.gov tester list.
- 03
Schedule the inspection or test with a certified company.
- 04
Stay inside the utility's accepted reporting path.
Tester gate
Who can produce an accepted result?
Confirm tester eligibility directly with San Francisco Public Utilities Commission Backflow Prevention Program before scheduling.
View the official tester listSubmission route
Where the result goes
Use the official program contact and submission method below.
- San Francisco certified tester list official tester list
- SFPUC customer service contact utility contact
Local detail
Property, device, and enforcement notes
Open the parts that match the property and system. These details stay subordinate to the fast workflow above.
Program and failure notes
- San Francisco publishes a real certified tester list.
- The list includes direct tester contact information.
- This route is stronger as a high-intent approved-tester page than as a generic city explainer.
- The official list includes company names and contact details.
- The route is an authority-first list, not a private directory.
- SFPUC contact remains the support layer behind the tester routing.
Residential notes
- Residential demand is strongest where an irrigation or other protected assembly already exists.
- The city value is not generic homeowner education but clear tester routing.
Commercial notes
- Commercial value is strong because the SF.gov list behaves like a real utility-approved next step.
- This is a good example of official guidance and directory content staying separate while still monetizable.
Irrigation
San Francisco is useful for irrigation only when a real protected assembly exists and the owner needs a certified tester.
- The official tester list is the strongest public asset.
- This page captures high-intent routing better than generic irrigation advice.
- The city utility contact remains available when details are unclear.
Fire line
The official list is already geared toward certified testers rather than generic plumbers.
- The certified tester list is public and specific.
- Commercial and larger protected services are a natural fit for this route.
- Official routing stays separate from directory inventory.
Cost and fee context
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.
Evidence ledger
Official sources
San Francisco is commercially useful because SF.gov exposes a certified tester list with real companies instead of making users guess.
BackflowVerdict summarizes these records; the governing entity remains the authority.
Open official program page- 01SF.gov certified tester listofficial tester listOpen source ↗
- 02SFPUC customer service contactofficial utility contactOpen source ↗
Commercial handoff · separate layer
Still need help after reading the rule?
The request keeps this utility ID and source page with the handoff.