Who this article is for: Authority Users
Overview
SwiftComply builds your state's backflow report automatically. There's no separate "generate" step — once you pick a year from the dropdown, the full report renders on the page using your current SwiftComply data. This article walks through viewing the report, resolving the data issues it flags, and saving a copy when you submit to your regulator.
Before You Run It
Your state must be configured in SwiftComply. SwiftComply currently supports CA, CO, FL, MA, MI, and WA. If you don't see State Reports in the left navigation, your state may not be configured yet — contact your CSM.
Your state report fields should be filled in. Each state's report pulls from specific fields on assemblies (and sometimes locations). Missing fields can cause categories to undercount. See Setting Up State-Specific Report Requirements and Using Custom and State Report Fields on Assemblies.
Viewing Your State Report
Click State Reports in the left navigation.
Click the Select a Year dropdown at the top of the page.
Pick the year you want to view. The dropdown lists every year from 2020 through the current year.
The report renders on the page. It's titled with your state and year — for example, 2025 Washington (WA) State Report.
Switching years re-renders the report instantly; there is no progress bar or separate generate button.
Reading the Report
The report is laid out to match the structure your state uses on its submission form. For example, the Washington report is organized into Parts (Part 3B, Part 3C, and so on), each containing tables that count assemblies by category and protection status.
Each state's layout is different. Once you've pulled your report for the first time, spend a few minutes orienting to its structure so you know which SwiftComply fields feed which section — that'll make future fixes much faster.
Data Quality Flags
At the top of the report, SwiftComply surfaces any issues that could affect accuracy. The header reads:
💡 *There were some issues that could affect the accuracy of this report:*
Followed by a bulleted list of specific problems. Common examples:
Serial number is used by multiple assemblies
A bypass assembly doesn't indicate which assembly it bypasses
An assembly and its reported bypass are not in the same location
Each flagged issue ends with a (view) link. Clicking it opens the specific record causing the problem so you can correct the underlying data. Once you've fixed it, re-select the year on the State Reports page and the report re-renders with the updated numbers.
💡 Run your state report well before your regulatory deadline. These flags often take research to resolve — you don't want to discover them the day the report is due.
Saving a Copy of the Report
State reports pull live data every time they render. If anything in SwiftComply changes after you run the report — a late test acceptance, a corrected field, a new assembly — re-running the same year will show the new numbers. SwiftComply does not store a snapshot of past runs.
That means whenever you submit a report to your regulator, save a point-in-time copy of what you submitted:
Print / Save as PDF — Use your browser's print dialog (File → Print → Save as PDF) to capture the full rendered report.
Screenshot — Capture individual tables if you just need a section for internal review.
Store the saved file outside SwiftComply (your regulatory records folder is a good place). This gives you a record of exactly what was reported, which is what you'll need if your regulator ever asks questions later.
FAQ
Q: I picked a year and nothing happened — is the report still generating?
A: The report renders immediately after you pick a year. If you don't see it, scroll down — the dropdown is at the top, but the report table can be below the fold. If the page is genuinely blank, refresh and select the year again.
Q: A data quality flag is unclear. What do I do?
A: Click the (view) link next to the flagged issue — it takes you directly to the record. If the fix still isn't obvious after looking at the record, email help@swiftcomply.com with the exact flag text and we'll walk through it with you.
Q: Can I edit what appears in the report?
A: You can't change the report layout or which fields it uses — those are set by your state's template. You can change the numbers by correcting the underlying SwiftComply data (assembly fields, location fields, accepted test reports, accepted surveys). Re-run the report after your corrections to see the updated numbers.
Q: Last year's numbers no longer match what I submitted. What happened?
A: State reports always pull current data — they're not locked after submission. If records were added, edited, or removed since you submitted, the numbers will have changed. That's why saving a PDF at submission time matters: it's your snapshot of what you actually reported.
Q: My state isn't in the dropdown. Can we add it?
A: State report templates are configured on the back end. Contact your CSM to start the conversation — adding a new state involves SwiftComply setting up the template structure to match what your state requires.