Find utilities using SwiftComply or C3Swift for official backflow report submission, device records, and accepted filing proof.
Most portal searches start after a notice, failed test, or tester upload problem. Match the portal name to the city or utility, then confirm the exact acceptance gate before filing.
Use these phrases as the practical clue set from a notice, tester upload screen, or property manager handoff.
These links prioritize city routes backed by structured portal, tester, fee, deadline, and report-acceptance facts.
Use this table to spot the acceptance gates that usually decide whether a backflow report is actually complete: portal submission, notice or device identifiers, approved tester status, report acceptance, and failed-test handling.
| Utility and city | Portal evidence | Notice or device ID | Tester gate | Report acceptance | Timing or fee clue | Failed-test clue |
|---|---|---|---|---|---|---|
| City of Anaheim Cross Connection Control |
Anaheim SwiftComply electronic report submission
Anaheim cross connection control
Anaheim SwiftComply tester registration
Anaheim standard specifications
|
Look for the SwiftComply or C3Swift account, device, address, or notice record. | Orange County Health Care Agency tester certification, City of Anaheim business license, Anaheim approved tester status, SwiftComply tester registration | Keep the SwiftComply electronic submission record and assembly photo evidence from the test. | Immediately after installation, relocation, or repair, and at least annually thereafter | Retest and accepted report submission are part of the closeout path. |
| City of Longmont Backflow Prevention and Cross-Connection Control |
Longmont SwiftComply backflow test submission workflow
Longmont backflow prevention program
|
Look for the SwiftComply or C3Swift account, device, address, or notice record. | Certified tester status | Keep the accepted SwiftComply or city submission record before the enforcement ladder advances. | Annually with utility due dates between April and September | Repair or correction due within 60 days. |
| Colorado Springs Utilities Backflow Prevention |
Colorado Springs Utilities SwiftComply workflow
Colorado Springs Utilities backflow professionals portal
Colorado Springs Utilities rules and regulations
|
Look for the SwiftComply or C3Swift account, device, address, or notice record. | Certification information, Test-kit information | Test result entered into the Colorado Springs Utilities workflow within five days. | Report due within 5 days after testing. | Colorado Springs uses a five-day result-entry expectation. |
| City of Tampa Water Department Backflow Prevention |
Tampa SwiftComply portal
Tampa backflow prevention program
Tampa SwiftComply portal
|
Look for the SwiftComply or C3Swift account, device, address, or notice record. | Certified tester status, SwiftComply enrollment | Certified result delivered to the Water Department within seven calendar days. | Report due within 7 days after testing. | Tampa uses different cadences for commercial and residential properties. |
| Dallas Water Utilities Backflow Prevention Program |
Dallas SwiftComply backflow reporting workflow
Dallas Water Utilities backflow test reports page
Dallas printable backflow report form
|
Look for the SwiftComply or C3Swift account, device, address, or notice record. | City of Dallas registered tester status, Backflow tester license | Keep the accepted SwiftComply submission or accepted city form when the Building Inspections path applies. | Annual for high-hazard assemblies; irrigation only on install, repair, or replacement | Repair or correction due within 30 days. |
Open the utility page first. It contains the due basis, submission method, program phone, and any tester-list route tied to the property.
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.
Longmont is a very strong Colorado utility because it combines annual testing, enforcement timing, irrigation-specific upgrade rules, and a real portal transition.
Colorado Springs Utilities is a strong Colorado page because it shows how the utility actually runs the testing workflow: portal registration, certification uploads, five-day test entry, and survey-first rules.
Tampa is one of the best Florida fits because it publishes a clear cadence split, a seven-day reporting deadline, and a real tester-enrollment workflow instead of generic educational content.
Dallas is a useful edge case because it is not simply annual-for-everything: high-hazard assemblies are annual, irrigation is event-driven, and SwiftComply is mandatory for covered test reports.
A reporting portal may handle test submission while the utility, county, or separate list controls tester eligibility. Treat the utility page as the canonical workflow before scheduling or submitting a report.
No. The portal may handle report submission, but the city, county, water district, or utility still controls deadlines, tester acceptance, fees, and failed-test handling.
Compare the utility name, service address, notice or device identifier, approved tester gate, report acceptance rule, filing fee, due window, and failed-test instructions.
This portal view currently groups 5 mapped utilities with source-backed portal or online submission evidence.
Do not assume that. Many portals still require accepted tester credentials, current certification, license, insurance, gauge calibration, or separate utility approval before reports are accepted.