Who this article is for: Authority Users
Overview
Every backflow assembly in SwiftComply has an Overall Compliance status — a single value that summarizes whether the assembly is in good standing. This article walks through the four statuses, where you'll see them in the UI, and exactly what data drives each one.
The Four Statuses
Status | Assembly Detail Page | Assemblies Table | What It Means |
Compliant | Green circle with check | Green check | A passing test is on file and the Next Test Due is in the future |
Overdue | Orange circle with clock | Red X | A passing test is on file, but the Next Test Due has passed |
Non-Compliant | Red circle with X | Red X | The most recent accepted test failed (this status takes priority over Overdue, even if the due date has also passed) |
Unknown | Grey circle with minus | Three dots (...) | No test has ever been accepted for this assembly |
📝 Both Overdue and Non-Compliant display a red X on the Assemblies table's Overall Compliance column — they're collapsed into one icon at the list level. Open the assembly detail page (or look at Last Test Result) to tell them apart.
How to Read That
The two real differentiators between an out-of-compliance assembly are:
Overdue — the last accepted test passed, but the due date has come and gone. The assembly is non-compliant because the test has expired.
Non-Compliant (Failed Testing) — the most recent accepted test was a Fail. This wins over everything else: even if the assembly is also past its Next Test Due, the status stays Non-Compliant.
In other words, "Overdue" *is* a form of non-compliance — it just has its own label so you can tell at a glance whether the issue is an expired test (Overdue) or a failed test (Non-Compliant).
Where to See It
On the Assemblies Table
Click Assemblies in the left navigation.
If the Overall Compliance column isn't visible, click the Table Columns gear icon, check Overall Compliance, and apply.
You can sort and filter on this column from the toolbar.
On the Assembly Detail Page
Click any assembly in the Assemblies table.
The compliance icon and supporting values appear on the Compliance info card at the top of the detail page, alongside Last Test Result, Last Tested On, and Next Test Due.
What Drives the Status
Overall Compliance is derived from two fields on the assembly:
Last Test Result (Pass / Fail)
Next Test Due (date)
📝 Last Tested On is shown on the Compliance card for context, but it does not affect Overall Compliance. Only Last Test Result and Next Test Due are used in the calculation.
The logic, in priority order:
If the most recent accepted test was a Fail → Non-Compliant.
Else, if Next Test Due is in the past → Overdue.
Else, if there's a passing test and Next Test Due is today or in the future → Compliant.
If no test has ever been accepted (so neither field is set) → Unknown.
What Sets These Fields
The Last Test Result and Next Test Due fields are set by either:
Accepted test reports. When an authority user accepts a test report (or auto-accept runs), SwiftComply updates the assembly's compliance fields based on the report.
Manual edits by an authority user. From the assembly's DETAILS tab, click Edit, change the values in Standard Properties, and save.
Every change is recorded on the COMPLIANCE HISTORY tab. See Understanding Compliance History for the audit trail.
FAQ
Q: My assembly's Overall Compliance shows "Unknown." What does that mean?
A: Unknown means no test has ever been accepted for the assembly — Last Test Result and Next Test Due haven't been set. The fix is to accept a test report for it (or, if you have historical data, manually fill in the compliance fields on the DETAILS tab).
Q: The last test passed, but the Assemblies table is showing a red X. Why?
A: The Assemblies table collapses Overdue and Non-Compliant into the same red X. If the test passed but Next Test Due has passed, the assembly is Overdue. Open the assembly to see the actual status (or check Last Test Result on the table).
Q: My assembly failed its last test but is also past due. Which status wins?
A: Non-Compliant wins. A failed test takes priority over an expired due date — both are forms of non-compliance, but the failed test is the one SwiftComply surfaces as the status.
Q: Can I change an assembly's Overall Compliance without a test report?
A: Indirectly. You can't edit "Overall Compliance" itself — it's derived from Last Test Result and Next Test Due. But you can edit those two fields directly on the DETAILS tab; doing so changes the calculated status. (Last Tested On is also editable, but changing it doesn't affect Overall Compliance.)
Q: I accepted a passing test, but Overall Compliance didn't change. Why?
A: The test may not have met all the conditions to update the compliance fields — for example, the test date was older than the current Last Tested On, or the test fell outside the Allowable Window Days when Preserve Date is enabled. See Compliance Rules for how those settings work.