Why a compliance check from three weeks ago isn't proof

Ask any AI recruitment platform whether they verify compliance, and the answer is almost always yes. Ask when, and the answer narrows fast: at screening. Once. Then a renewal reminder gets set, a calendar entry gets created, and everyone moves on to the next requisition.

That's not a criticism of any one platform — it's the industry standard. Right to work status, DBS certificates, professional registrations, mandatory training: the established best practice is to check these at onboarding and flag them for periodic review. Compared to not checking at all, that's real progress. Compared to actually knowing whether a candidate is compliant on the day they turn up to work, it's a guess dressed up as a fact.

The gap nobody prices in

Here's the problem in concrete terms. A candidate is screened on a Monday. Right to work is confirmed, DBS comes back clear, registration is current. Everyone signs off. The placement is booked for three weeks out.

In those three weeks, several things could change without anyone in the recruitment process finding out: a visa condition shifts. A DBS update-service flag appears. A professional registration lapses or is suspended pending an unrelated investigation. None of these are rare edge cases in regulated sectors — they're exactly the kind of status changes compliance frameworks exist to catch. And in a system that checks once, none of them get caught until something goes visibly wrong.

The question worth asking isn't "did we check compliance." It's "do we actually know this is still true today."

We looked closely at how the major AI recruitment and staffing-tech platforms — the ones agencies are already evaluating — talk about compliance publicly. Almost universally, what gets marketed as "compliance" is platform governance: SOC 2 certifications, GDPR statements, responsible-AI frameworks, bias audits. All genuinely useful. None of it answers the actual operational question a compliance manager needs answered: is this specific person, in this specific role, still cleared to be here, today.

What re-verification actually changes

The fix isn't complicated to describe, even if it's non-trivial to build properly: check again, live, immediately before the placement is confirmed as starting. Not a renewal reminder that someone has to act on manually. A structural checkpoint that the placement cannot pass without.

This is the model we built SOS Global Recruitment around — every candidate is verified once at screening, and again, live, against the current authoritative source, on the actual day the placement starts. If anything has changed since screening, the placement halts until it's resolved by a named human with the authority to do so. No override on urgency. We'd rather lose a fill than paper over a gap. We've written up the full mechanics of how the two checkpoints work on our How We Verify page.

Why this matters more than it sounds like it should

Agencies don't lose contracts over a single missed check very often. They lose them over the pattern that a missed check reveals — that compliance was treated as a box ticked once, rather than a standard maintained continuously. Frameworks and auditors increasingly ask not "do you check compliance" but "can you show me it was true on the day." A screening file from six weeks ago answers the first question. Only a timestamped, live re-verification answers the second.

That's the entire argument for verifying twice instead of once. It's not a marginal improvement on an already-solved problem. It's closing the actual gap that causes placements to fail compliance audits after the fact.