May 28, 2026 · For Authority Users
We've made approving testers faster and simpler. No more expiration dates to set, track, or remember — just one click to approve, and you're done.
What's new
Approving a tester used to mean picking an expiration date every single time. Now it's a single click: Approve.
From here on, a tester's eligibility is based on what actually matters — their approval status and their valid certifications. When their certifications are current, they can submit. When those certifications expire, the system steps in automatically. Nothing for you to track by hand.
Why you'll love it
A little backstory: the “Approved Until Date” dates back to when a tester could only carry one certification, so some teams used it to hand-track extra requirements. Now that SwiftComply supports multiple certifications with built-in expiration tracking, that field was just creating busywork — so we retired it. Here's what that means for you:
One click, done. Approve a tester and move on. No date pickers, no extra steps.
Fewer surprise lockouts. Testers with current credentials can submit right away — no more being blocked by a date that quietly lapsed.
One simple rule. Eligibility comes down to approved status + valid certifications. That's it.
Less back-and-forth. Fewer “why can't I submit?” calls, fewer manual updates, more time back in your day.
What this looks like
Before | After |
Approve Until Specific Date — open a date picker, set an expiration | Approve — one click, no date |
Deny User | Deny |
The old “Approved Until Date” column is now tucked away in your tables and reports. And don't worry — none of your existing data was deleted. It's all safely stored if you ever need it.
Good to know
Now that the date is off, a few testers who were previously blocked by an expired “Approved Until Date” — but whose certifications and approval status were actually current — can submit again. For most teams, that's exactly right.
Want to keep the old behavior for now, or have a question about your specific setup? Our team is happy to help — just reach out to help@swiftcomply.com or start a chat right inside SwiftComply.
A little housekeeping to set you up for success
Here's the good part: some testers who were previously stuck behind an expired “Approved Until Date” — even though their certifications and approval were current — can now submit again. Take five minutes to confirm the right people have access:
Go to Reporting and run the Service Provider Tester Certification Info report.
Export the report to CSV.
Filter for: Certification Status = Compliant and Approval Status = Approved.
Sort by Approved Until Date.
Review testers whose Approved Until Date is in the past.
For each tester on that list, decide: should they remain eligible, or should you Deny them now?
💡 If someone genuinely shouldn't be submitting — say, their city registration hasn't been renewed — just set their status to Denied. The old date no longer blocks anyone, but a Denied status will.
Learn more
We've updated the Help Center to walk you through everything:
🆕 New
✏️ Updated
Questions?
The SwiftComply Support team can review your specific tester configuration, walk through the impact for your program, and help you decide on the right path forward.
Reach us at help@swiftcomply.com or start a chat from within SwiftComply.