Expiry is invisible at the moment it matters
The registration lapsed between roster publication and shift start. Nothing in the rostering tool knows, nothing in payroll cares — the work happens anyway.
Solutions / Credentialing
A credential that expired last Tuesday doesn't announce itself — the shift gets rostered, worked, and paid anyway. Smartta checks eligibility at the moment of assignment, flags what's expiring, and gates what's already lapsed.
Checked at rostering, shift start, and payroll recognition · evidence of qualification per shift
The problem
Qualifications live in one system, shifts in another. Between them sits a manual check that happens sometimes, at some sites, when someone remembers — and an exposure that compounds every time it doesn't.
The registration lapsed between roster publication and shift start. Nothing in the rostering tool knows, nothing in payroll cares — the work happens anyway.
Spreadsheet audits and expiry-date eyeballing across sites and agencies miss exactly the cases that matter — and consume hours every week doing it.
After an incident or at audit, the question is specific: was this person eligible for this work on this day? Without a per-shift record, the answer is a search party.
The governed check
Smartta runs the credential check inside the workflow — at rostering, at shift start, and at payroll recognition — with the same pass / flag / gate boundary as every other workforce decision:
What's at stake
An expired credential discovered at rostering is a swap. Discovered after an incident, it's liability. With the check in the workflow:
Workforce eligibility
We can show how Smartta helps make eligibility visible where workforce decisions actually happen.