Who this article is for: Authority Users
Overview
When a tester submits a test report, it appears in your Test Reports To Review queue on the Notifications tab. From there you can open each report, review the results and uploaded documents, and accept or reject it. If you later need to make a change to an already-processed report, you can reset it back to In Progress so the tester can correct and resubmit. This article walks through each action and where it lives in the UI.
Where to Start: The Notifications Tab
The Notifications tab in the left navigation is your central queue for items that need authority attention. It displays counts for each type of review work, with a shortcut link to open each queue as a filtered list.
For test reports specifically:
Click Notifications in the left navigation.
Find the Test Reports To Review row. The number next to it is your current backlog of submitted reports waiting on review.
Click the open icon next to the number to jump straight to the Test Reports list, pre-filtered to show only reports in Submitted status.
💡 You can also get to the same list by clicking Test Reports in the left navigation and filtering the status column to Submitted. The Notifications tab is just the faster shortcut for day-to-day queue work.
Reviewing a Test Report
From the filtered Test Reports list, click a report to open it.
The report opens in a flyout or full-page view showing:
The assembly the test was performed on
The tester and the tester's certification
The test kit and its calibration
Test date and overall result (Pass / Fail)
Valve readings and any repair information
Tester comments
Any attached documents (the test report PDF, field photos, etc.)
Review the readings, confirm the documents look reasonable, and decide whether to accept or reject.
📝 If the tester added a comment to the report, that's a strong signal the report needs human review. Comments are one of the reasons Auto Accept skips a report and routes it to your queue. See Auto Accept Overview for the full list.
Accepting a Report
In the open report, click Accept.
SwiftComply runs a final compliance check and, if it passes, updates the assembly's compliance fields:
Last Test Result and Last Tested On update if the test date is newer than the existing values.
Next Test Due advances if the test passed and (for compliance rules with Preserve Date) the test date is within the Allowable Window Days.
A new entry is written to the assembly's Compliance History tab.
The report's status changes to Accepted.
You can accept a failing test — it will update Last Test Result to Fail and Last Tested On, but Next Test Due will not move.
For details on how compliance calculations work (and why a passing test sometimes doesn't advance Next Test Due), see Compliance Rules and Understanding Test Due Dates and Last Test Results.
Rejecting a Report
Reject a report when the data is wrong or something is missing that the tester needs to correct.
In the open report, choose the rejection action.
Enter a reason so the tester understands what to fix.
The report's status changes to Rejected. The tester is notified and can correct the information and resubmit.
Rejecting does not update the assembly's compliance record — the assembly stays in the state it was before the submission.
Resetting a Report (Unsubmitting)
Use Reset to In Progress when a report has already been accepted or submitted and you need it sent back to the tester for correction.
Open the report from the Test Reports list.
Click Reset to In Progress.
The report returns to In Progress status. The tester can re-open the report, edit it, and resubmit.
If the report was already Accepted, resetting it also reverses the compliance changes: Last Test Result, Last Tested On, and Next Test Due revert to what they were before the report was accepted. A Compliance History entry is written to record the reset.
📝 Reset to In Progress is not available for imported reports or, depending on your organization's configuration, reports accepted more than a set window ago (for example, 90 days). If the button isn't available, contact SwiftComply support if you need to make a correction.
What Auto Accept Does in the Background
Many submitted reports never hit your queue — Auto Accept handles them automatically. Your Test Reports To Review queue only contains reports that Auto Accept either couldn't process or chose not to. Common reasons a report lands in your queue:
The tester added a comment
The assembly or location is flagged Needs Review
The assembly or location is inactive
The compliance check didn't pass (for example, the test fell outside the Allowable Window Days)
Your organization's Auto Accept rules intentionally excluded it for manual review
See Auto Accept Overview for the full criteria.
FAQ
Q: My Test Reports To Review count on the Notifications tab seems high. What can I do?
A: Ask your CSM about widening your Auto Accept rules so more passing, straightforward tests can auto-accept. Your manual review queue is meant for the reports that actually need human attention — comments, flags, or unusual situations.
Q: Can I accept a test that failed?
A: Yes. Accepting a failed test records the failure on the assembly (Last Test Result becomes Fail) but does not advance Next Test Due. This is the right move when the tester's failed result is legitimate and you want the record to reflect that the test happened.
Q: I accepted a test by mistake. What should I do?
A: Click Reset to In Progress on the report. That reverses the compliance changes and returns the report to the tester. If the reset action isn't available (for example, if too much time has passed per your org's configuration), contact SwiftComply support.
Q: I rejected a report but now I realize I should have accepted it. Can I reverse the rejection?
A: The tester will need to resubmit. Let them know, and they can open the report, make any corrections (if needed), and submit it again — it will return to your queue as Submitted.