Utility pages where SwiftComply or C3Swift appears in the official backflow report submission workflow.
Open the utility page first. It contains the due basis, submission method, program phone, and any tester-list route tied to the property.
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.