Credential Verification Checklist

An agency fills a caregiver vacancy on a Tuesday. The rota for the following week is built around the new hire. On the Friday before the start date somebody checks the certification and finds it lapsed four months ago.

Nothing illegal has happened. Nothing was neglected in any obvious way. But the role is open again, the schedule has to be rebuilt, and the candidate, who has done nothing wrong either and could have renewed had anyone asked in week one, is now three weeks into a process that produced nothing.

Credential checking is treated as onboarding paperwork and behaves like a sourcing dependency. That misplacement is the whole problem, and it is structural rather than careless: the check sits at the end because it feels administrative, and it belongs near the front because it can invalidate everything after it.

What actually has to be true

Four categories of fact gate the first shift, and they have very different failure characteristics.

Work authorization is the one that ends a process outright. It is binary, it is legally required, and it cannot be worked around by a willing employer. It is also the single most common reason a candidate who looked ideal turns out not to be hireable, which is why it belongs among the very first things established rather than among the last.

Occupational licenses and certifications are the ones with an expiry date. Nursing and care certifications, CDLs, trade tickets, food handling, first aid. The failure mode is not absence but lapse, and lapse is invisible unless someone looks at a date.

Clearances and background checks are the slow ones. They are gated by a third party on a timescale you do not control, and the delay is the risk rather than the outcome. A check begun in week three of a search delays a start date by however long that check takes.

Setting-specific requirements are the ones people forget. Immunisation records for clinical settings, safety training for a site, insurance for anyone driving. They tend to be discovered by the person running the first shift.

Ask early, and ask as a fact rather than a hurdle

The objection to asking early is that it feels like an interrogation before a relationship exists. That objection is real and the answer is framing rather than delay.

A question asked as part of a form is administrative. The same question asked after two interviews is an obstacle. Candidates experience early questions as process and late questions as suspicion, which is the opposite of the intuition that produces the delay.

There is a second reason, less obvious and more expensive. A candidate whose authorization status makes them ineligible for your role is far better served by learning that in the first hour than in the third week, and so are you. The industry's habit of deferring the question protects nobody. It simply moves the cost of the answer to the point where both sides have spent the most.

This is the reasoning behind how Kariaa's candidate profile is built. A candidate completes eight fields once, in a fixed order set by code rather than left to a conversation, and the last of them is work authorization: legal first name, legal last name, phone, location, occupation, email, resume, then authorization. The order is deliberate. It sits at the end of the profile, which is the beginning of everything else, so it is established before an application exists rather than after a shortlist does.

Record the expiry date, not the status

Most credential tracking fails at exactly one point: it records that a certification was seen, and not when it stops being valid.

A field that says verified is true on the day it is written and decays silently. A field that says expires 14 March is true permanently and can be sorted, filtered, and looked at in advance. This is the entire difference between a record that prevents an uncovered shift and one that explains it afterwards.

The minimum viable version needs no compliance system. One row per person, one column per credential, each cell holding a date rather than a tick, sorted by soonest expiry. Reviewed monthly, that spreadsheet catches essentially everything a compliance product catches for an operator of this size, because the hard part was never the storage.

Verify against the source, not the document

A photograph of a certificate proves that a photograph exists.

For most regulated occupations the issuing body publishes a public register, and checking a name or license number against it takes about a minute. That minute is the difference between having a copy and having a verification, and it is the step most often skipped because the document looks convincing. Documents are supposed to look convincing.

This is worth being calm rather than dramatic about. The large majority of candidates are exactly who they say they are. The reason to check the register is not suspicion, it is that the cost of the check is a minute and the cost of not checking is discovered at the worst possible moment, in a setting where a license is a legal precondition rather than a preference.

Where an automated screening step returns a fraud signal, treat it the way Kariaa's own vetting labels it, which is advisory. It is a reason to look more closely, never a verdict, and the same is true of any confidence score attached to an automated check.

The recertification problem is a calendar problem

For an operator with twenty staff carrying certifications that expire on twenty different dates, lapse is not an event. It is a slow leak.

Recertification only ever fails for one reason, which is that nobody read the date until it had passed. There is no sophistication required here and no product needed. There is a sorted column and a recurring calendar entry, and the discipline to look at it when nothing appears to be wrong.

The version that works flags at ninety days rather than at expiry, because a renewal that requires a course, an exam or a third-party appointment cannot be completed in a week. Flagging at expiry produces the same uncovered shift as not flagging at all, and it feels like a process.

Written by the team at Kariaa. Learn more at www.kariaa.com.