Somebody has to say yes. On the record.
A background check, a diploma, a clearance: each one ends in a judgement somebody makes. Vetting holds that judgement together with the evidence behind it, the reasoning that led to it, and the date it stops being valid.
When the check lives in someone's head
A check that was done and never recorded is, on the day somebody asks, the same as a check that never happened. This is what that costs.
The check is part of joining
Right to work, a valid ID, a background check, a professional registration where the role demands one. Each is captured as part of joining and gated, so a hire into a sensitive role does not start with the check still open.
The check is part of joining. With a name and a date on it.
Evidence, a decision, and a date it expires
Three things sit on every vetting record, and the middle one is a judgement somebody made.
Evidence
Where it came from, who collected it, a checksum that proves it is the file that was filed, and when it must be destroyed.
Decision
Approved or refused by a named person, with the reasoning, a risk rating, and conditions where the yes comes with strings.
Validity
From one date to another, with the next review already scheduled, and a reason recorded when it ends early.
The ones that expire
A work permit, a driving licence where a company car is involved, a nursing licence, a security clearance: many roles carry something with a date on it, and an expired one is a live exposure.
When one nears expiry a re-verification fires through Employee lifecycle; when one lapses the Validation Framework can raise a blocking rule, so nobody is scheduled or paid against an invalid credential. Things you issue and want back live in Asset management.
An expired credential is a live exposure. The date is watched for you.
Put the check on the record
Collect the evidence, record who decided and why, and let the expiry date do the remembering.
Book a demo →