Mission statement

Provider narrative and compliance posture

County-certified tester directory entry used for Pasadena routing and also listed on IRWD and San Diego official tester rosters.

This profile does not override the utility's official rules. It exists to make the public provider layer inspectable after the governing workflow is clear.

Before booking this provider

Match BAVCO to the Pasadena Water and Power Cross-Connection Control Program workflow

The strongest local provider pages do not stop at a phone number. Confirm the authority source, the utility's tester gate, the report route, and the proof trail before you schedule or send a failed device back for retest.

Regional coverage map
Jurisdictional coverage

1 mapped metro support page(s).

Coverage

Utility coverage

3 mapped utility pages

  • County-certified tester directory entry used for Pasadena routing and also listed on IRWD and San Diego official tester rosters.
  • Authority source
  • Last reviewed 2026-04-05
Service area

Area served across mapped utility pages

  • Backflow testing
  • Backflow compliance support
  • Annual testing coordination
  • Failed test follow-up
  • Irrigation backflow testing
  • Fire line backflow testing

Verification basis

  • 3 mapped utility pages
  • 2 mapped utilities with an official tester route
  • 1 mapped utilities using a directory route
  • 3 mapped utilities with structured submission steps
  • Latest mapped utility verification: 2026-06-29
Covered utilities

Utility pages this provider is mapped to

california

Pasadena Water and Power Cross-Connection Control Program

Pasadena is a strong Los Angeles-area page because the utility publishes real annual-testing and failed-test workflow, but the tester route is county-certified rather than city-approved.

  • Due basis: Pasadena Water and Power says each backflow prevention assembly is tested at least once a year by the due date on the PWP notice. The utility tells customers to use a Los Angeles County certified backflow prevention testing business and to send the passing report plus any repair documentation back to PWP.
  • Notice clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission route: Pasadena Water and Power backflow program
  • Proof to keep: Use the listed submission method and keep proof that the report was filed with the utility.
california

Irvine Ranch Water District Backflow Prevention

IRWD is a good California district page because it clearly explains when the district will require an assembly, what assembly types it recognizes, and where customers can find certified testers.

  • Due basis: IRWD says customers will be notified when a backflow assembly is required and points them to a partial list of certified testers who can perform testing in the district.
  • Notice clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission route: IRWD Backflow Prevention
  • Proof to keep: Report acceptance depends on the governing tester route and the utility's submission method; confirm status before scheduling.
california

City of San Diego Public Utilities Backflow Program

San Diego is one of the best California fits because the city publishes annual testing rules, an approved tester list, a tester-orientation gate, and explicit enforcement consequences.

  • Due basis: San Diego says all backflow devices are tested annually and points customers to the approved tester list when the Public Utilities Department contacts them for compliance.
  • Notice clue: Look for the utility name, service address, assembly serial number, account or notice ID, and due date.
  • Submission route: San Diego Backflow Program
  • Proof to keep: Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
Profile maintenance

Need a correction to this profile?

If a phone number, website, or approval source is wrong, report it for manual review. BackflowVerdict updates public provider profiles only after checking the source record.