Who this article is for: Authority Users
Overview
Locations in SwiftComply represent the physical properties where backflow assemblies are installed — a home, a commercial building, a municipal facility. Every location has address and account info, the contacts associated with it, the assemblies installed there, a communication history, any surveys performed, and a compliance history. This article covers the Locations list and all six tabs on a location's detail flyout.
The Locations List
Click Locations in the left navigation.
The list displays the standard columns: Account Number, Active, Name, Address, City, State / Prov, Postal Code, Phone, Device Count, Overall Compliance, and more.
Use the toolbar to configure the view:
Search — search across locations using the field dropdown in the search bar
Advanced Filter Builder (funnel icon)
Columns (gear icon) — show or hide columns
Export to CSV (download icon)
Click any location row to open its detail flyout on the right side of the page.
Key Columns
Column | What It Shows |
Account Number | The billing account identifier (often matches the external billing system) |
Active | A green check for active locations |
Name | The location name |
Device Count | How many assemblies are installed at the location |
Overall Compliance | Whether the location (via its assemblies and surveys) is in compliance. A red X means something at the location is non-compliant; three dots mean no accepted compliance data yet |
Adding a Location
Click Add Location in the top right of the Locations page.
Fill in the required fields:
Location Name
Address, City, State / Prov, Postal Code
Account Number (optional but recommended — used for billing sync matching)
Primary Contact and Phone (optional, but recommended if you want communications to reach this location)
Notes (free text)
Click Save.
Editing a Location
Click the location in the list to open the detail flyout.
On the Details tab, click the pencil icon (top right of the flyout).
Update the fields.
Click Save.
The flyout stays open after save so you can continue to review or switch to other tabs.
The Six Tabs
The location detail flyout has six tabs across the top:
Details
The core fields: Location Name, Address, City, State/Prov, Postal Code, Account Number, Primary Contact, Phone, Notes. Plus any Custom Properties fields configured for your organization, and state-specific fields if your state requires location-level data.
Assemblies
Every assembly currently linked to this location. Click an assembly to open it. For a walkthrough of assembly management, see Understanding Assemblies.
Contacts
Everyone with a contact record tied to this location. Primary Contact is the default recipient for auto-generated communications; additional contacts can also be configured to receive specific communication types. For the full contact workflow, see Managing Contacts within SwiftComply Backflow.
Comms
The communication history for this location — every notice generated, sent, or logged. For the full picture of how communications flow, see Understanding Communication Status.
Surveys
Hazard surveys submitted for this location, including status and result. For the full workflow, see Understanding Survey Compliance at a Location.
Compliance History
The timeline of compliance state changes for this location's assemblies. Each entry shows which assembly or surveyed attribute changed, the new compliance state, and when. For the full reference, see Understanding Compliance History.
Deleting or Inactivating a Location
Locations with active assemblies generally can't be deleted — you'd lose the assembly history. To take a location out of active management:
Open the location.
Click the pencil icon to edit.
Toggle Active off.
Save.
Inactive locations are hidden from default list views but still accessible via search. Their assemblies remain intact.
FAQ
Q: Why is my location's Device Count zero after I added an assembly?
A: The assembly wasn't linked to this location — it may have been added from the global Assemblies page without a location assignment. Open the assembly and use the Assign Location action in the Location tab of the assembly.
Q: Can I merge two duplicate locations?
A: There's no in-app merge. If you have two duplicate locations with separate assemblies, the cleanest approach is to move all assemblies to one location (using Change Location on each assembly) and then inactivate the empty duplicate.
Q: Why is the Overall Compliance column showing "..." for some locations?
A: Those locations have no compliance data yet — typically because no assembly tests or surveys have been accepted. Once test reports are accepted or surveys completed, the column will populate.
Q: How do I find locations that are missing a primary contact?
A: Use the Advanced Filter Builder and build a rule for Primary Contact is empty. Save the filter if you plan to rerun it regularly.