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.
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.
Credentialing view
Required registration check
Current, role-matched, site-eligible
Expiring certification
4 upcoming — renewal paths routed
Role mismatch exception
1 open — assignment held until resolved
Decision evidence
Check and any override recorded per shift
Shift assignment
Held until the lapsed credential is resolved or overridden by named authority.
An expired credential discovered at rostering is a swap. Discovered after an incident, it's liability.
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, or gate boundary as every other workforce decision.
Current, role-matched, site-eligible. The assignment proceeds, evidence written.
The shift proceeds with the renewal path routed to the right person, weeks ahead of the lapse.
The assignment holds until resolved — or overridden by named authority, with the reason attached.
Every check — and every override — is recorded against the shift it governed.
Most checks pass silently. Your team only sees the eligibility decisions that need them.
The plan
Identify where decisions move between roster, time, HR, payroll, credentialing, and care systems.
Here: where eligibility is decided — rostering, shift start, payroll recognition.
Configure checks that pass, flag, or gate high-risk workforce decisions before they move downstream.
Here: assignments checked the moment they're made; lapsed credentials held.
Keep decision evidence ready for payroll review, compliance checks, incident response, and operational governance.
Here: the check, the credential state, and any override — per shift, on record.
Evidence
After an incident or at audit, "was this person eligible for this work on this day?" should be a lookup — not a search party.
What's at stake
Eligibility answered at assignment time — no side-system lookup, no relying on memory.
Expiries become renewal workflows weeks ahead — not floor incidents on the day.
"Was the worker qualified for this shift?" — answered per shift, with the check and any override on record.
Workforce eligibility
A short review of how credentials, rosters, and payroll connect today — and where checking eligibility at assignment would remove exposure, rework, and audit scramble.