Who this article is for: Authority Users
Overview
Every assembly in SwiftComply has three fields that drive its compliance: Next Test Due, Last Test Result, and Last Tested On. These fields update automatically when accepted test reports are processed, and they can be edited manually by an authority user. This article explains what each field means, when it updates, and how to find assemblies that need attention.
The Three Fields
Field | What It Shows |
Next Test Due | The date the next backflow test is due for the assembly |
Last Test Result | The result of the most recent accepted test — Pass or Fail |
Last Tested On | The date the most recent accepted test was performed |
All three appear on the Compliance info card at the top of the assembly detail page, and are available as columns on the Assemblies table (add them from the Table Columns gear icon if they aren't visible).
How Next Test Due Is Calculated
SwiftComply calculates Next Test Due using your organization's compliance rule settings. The key settings are Compliance Period, Preserve Date, Allowable Window Days, and End of Month Expiration. These are configured by SwiftComply — authority users cannot change them directly. If you need a setting changed, contact your CSM to submit a PPCR.
Without Preserve Date, Next Test Due is calculated from the test date plus the Compliance Period.
With Preserve Date on, Next Test Due stays on the same month and day and advances by the Compliance Period from the existing due date — as long as the test falls within the Allowable Window Days (more on this below).
For the full details on each setting and how they interact, see Compliance Rules.
📝 The End of Month Expiration setting moves the calculated due date to the last day of the month during the calculation. It only affects dates that are calculated after the setting is enabled — it does not retroactively move due dates that were set before.
When Last Test Result and Last Tested On Update
Last Test Result and Last Tested On update when:
A test report is accepted and the test date is newer than the current Last Tested On, OR
An authority user manually edits these fields on the assembly's DETAILS tab.
A failing test still updates these two fields as long as the test date is newer than the existing Last Tested On. The difference is that a failing test does not advance Next Test Due — only a passing test does.
📝 Accepting an older test report (one with a test date earlier than the current Last Tested On) does not change any of these fields. The report is accepted and recorded, but it will not overwrite newer data.
When Next Test Due Updates
Next Test Due advances only when all three of these conditions are met:
A test report is accepted.
The test's Tested On date is newer than the current Last Tested On.
The test result is Pass. (A failing test will not advance Next Test Due.)
How Allowable Window Days Affects This
If your compliance rule has Preserve Date enabled, Allowable Window Days (AWD) comes into play — but only when the test date is before the assembly's current Next Test Due:
Test date is before Next Test Due AND within AWD → Next Test Due advances using Preserve Date logic.
Test date is before Next Test Due AND outside AWD → The test is still accepted, but Next Test Due stays where it was. These tests show up on the Assemblies Passing Test Didn't Update Due Date report.
Test date is on or after Next Test Due → AWD doesn't apply at all. Next Test Due advances normally.
In other words, AWD is the rule for "how early before the due date a test can happen and still preserve that date." Tests on or after the due date are evaluated without AWD.
Next Test Due can also be changed manually by an authority user — see below.
Editing These Fields Manually
An authority user can edit Last Test Result, Last Tested On, or Next Test Due directly on the assembly's DETAILS tab:
Open the assembly from the Assemblies table.
Click Edit.
In the Standard Properties section, update the field you need to change.
Click Save.
Each manual change is logged in the COMPLIANCE HISTORY tab with the authority user's name.
Finding Assemblies That Are Due Soon or Past Due
Past Due
On the Assemblies table, the cleanest way to find past-due assemblies is to filter by Next Test Due directly:
Click the Advanced Filter Builder icon in the Assemblies toolbar.
Build a rule: Next Test Due is less than today's date.
Click Apply Advanced Filter.
You can also filter by Overall Compliance status to see all non-compliant assemblies (Overdue and Failed together). See Understanding Assembly Compliance Status for how Overall Compliance is determined.
💡 If you find yourself running the same filter often, save it. Apply your filters, click the Save Filters icon, and name the view. It will appear in the saved filter selector at the top-left of the table.
Due Soon
Use the Advanced Filter Builder to find assemblies with Next Test Due in an upcoming window — for example, Next Test Due greater than today AND Next Test Due less than 60 days from today. This gives you a working list for upcoming notices or scheduling.
FAQ
Q: I accepted a passing test, but Next Test Due didn't change. Why?
A: The most common reason: your compliance rule has Preserve Date enabled, the test date was before the assembly's current Next Test Due, and the test fell outside the Allowable Window Days. The test is accepted and recorded, but Next Test Due stays where it was. Run the Assemblies Passing Test Didn't Update Due Date report to find these assemblies.
If the test date was on or after the current Next Test Due, AWD isn't the cause — check that the Tested On date on the report is newer than the assembly's existing Last Tested On.
Q: A newly accepted test report has Last Test Result set to Fail, but my Last Tested On didn't change. What happened?
A: Last Tested On only updates when the accepted test's date is newer than the existing Last Tested On. If the failing report was older than the current Last Tested On, the fields stay as they are.
Q: Can I change Next Test Due without entering a test report?
A: Yes. An authority user can edit Next Test Due on the assembly's DETAILS tab by clicking Edit, updating the field, and clicking Save. The change is logged in the Compliance History tab.
Q: Who configures the settings that control how Next Test Due is calculated?
A: SwiftComply configures the compliance rule settings (Compliance Period, Preserve Date, Allowable Window Days, End of Month Expiration) for your organization. Authority users can't change them from the UI. To request a change, contact your CSM to submit a PPCR.