municipal utility · official record
Anaheim utility backflow testing requirements
Anaheim is a strong Southern California utility because it publishes annual testing rules, approved-list gating, online submission, and utility specifications for irrigation and proposed fireline work.
Fast answer
Who, when, and what device?
Anaheim says backflow prevention devices must be tested annually, and repaired and retested if defective. The annual tests must be performed by an Orange County Health Care Agency certified tester carrying a valid City of Anaheim business license.
- Who is affected
- Water users at locations where Anaheim requires a backflow prevention device, especially commercial, multi-family, irrigation, and fireline-related services.
- Covered devices
- Approved backflow prevention devices · Fireline backflow devices · Irrigation backflow devices · Cross-connection control assemblies
- Risk if missed
- Anaheim only accepts approved testers from the city workflow, no longer accepts mailed or emailed reports, requires SwiftComply electronic submission with a photo of the assembly during the test, and requires defective devices to be repaired and retested before they can be treated as compliant.
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 whether the issue is annual testing, a repair, or a relocation.
- 02
Choose an approved Anaheim tester with the required county certification and city license.
- 03
Complete the test and submit the result plus assembly photo through SwiftComply.
- 04
Continue sending test reports to the Orange County Public Health Care Agency when required by Anaheim's public instructions.
- 05
If the device is defective, repair or replace it and retest before treating the matter as closed.
Tester gate
Who can produce an accepted result?
Orange County Health Care Agency tester certification, City of Anaheim business license, Anaheim approved tester status, SwiftComply tester registration
View the official tester listSubmission route
Where the result goes
Anaheim SwiftComply electronic report submission
Report packet: Anaheim approved tester status, Orange County Health Care Agency certification, Valid City of Anaheim business license, Photo of the assembly during the test
Tester credentials: Orange County Health Care Agency tester certification, City of Anaheim business license, Anaheim approved tester status, SwiftComply tester registration
Look for the SwiftComply or C3Swift account, device, address, or notice record.
Report acceptance depends on the named portal and the utility-approved tester route; keep proof that the report was submitted.
- Anaheim cross connection control program page
- Anaheim SwiftComply tester registration SwiftComply tester registration
- Anaheim standard specifications standards page
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
- Anaheim only accepts approved testers from the city's list.
- The city no longer accepts mailed or emailed reports.
- SwiftComply submission requires test report information and a photo of the assembly during the test.
- Defective devices must be repaired and retested.
- Only testers on the city's approved list may be used.
- The tester must hold Orange County certification and a valid Anaheim business license.
- Test results are submitted through SwiftComply, and the city requires a photo of the assembly during the test.
Residential notes
- Anaheim's strongest public language is utility-wide rather than single-family-only, so residential intent usually shows up through irrigation or other protected services.
- The city points users to county certification and approved-tester requirements instead of leaving the workflow generic.
Commercial notes
- Anaheim has real commercial next-action value because it couples annual testing with approved-list and electronic-submission rules.
- The city's standards make fireline and development-phase questions commercially relevant rather than filler.
Irrigation
Anaheim's published irrigation standards explicitly require backflow protection to keep irrigation systems from contaminating the public water supply.
- Anaheim's landscape and water standards call for backflow devices on irrigation projects.
- The city routes irrigation users into the broader cross-connection control rules instead of treating irrigation as separate filler content.
- Annual testing still sits inside the same approved-tester workflow.
Fire line
Anaheim's utility standards and required-forms index show that proposed fireline work sits inside the backflow compliance workflow rather than outside it.
- Anaheim maintains required forms for proposed fireline backflow devices.
- Development-phase services cannot leave backflow devices in an unmanaged state.
- The same city approval and testing requirements apply before the utility treats the installation as complete.
Cost and fee context
Testing is market-priced, but Anaheim's approved-list gate and electronic reporting matter more than a published retail price.
Repair and retest cost depends on the device type and whether the issue arose during annual testing, relocation, or installation.
The real Anaheim friction is the approved-tester requirement plus the city's submission rules.
Evidence ledger
Official sources
Anaheim publishes annual testing rules, approved-list gating, SwiftComply electronic submission, assembly-photo evidence, and utility specifications for irrigation and fireline work.
BackflowVerdict summarizes these records; the governing entity remains the authority.
Open official program page- 01Anaheim cross connection controlofficial program pageOpen source ↗
- 02Anaheim SwiftComply tester registrationofficially linked submission registrationOpen source ↗
- 03Anaheim standard specificationsofficial standards pageOpen source ↗
- 04Anaheim water services standard specificationsofficial specification pdfOpen source ↗
Commercial handoff · separate layer
Still need help after reading the rule?
The request keeps this utility ID and source page with the handoff.