Healthcare staffing agencies stop scheduling on lapsed credentials by moving the check from a calendar to the moment of assignment. Instead of auditing expiration dates monthly, the system tests every required credential against the date of the shift each time a clinician is assigned, offered, or swapped in, and blocks the assignment when one is expired, missing, or unverified.
Why do lapsed credentials still reach the schedule?
Almost every agency tracks expiration dates. Most still get caught. The reason is that tracking and scheduling happen in different places, at different times, by different people.
The expiration date lives in a spreadsheet or a field in the ATS. The schedule lives somewhere else. The coordinator filling a Friday night shift at 4pm is looking at who is available, not at a compliance report that someone ran at the start of the month. The check depends on a person remembering to do it, under time pressure, for every single placement.
A credential lapse you catch next month is a shift you lost today. Or worse, a shift that was worked by someone who should not have been there.
What is the difference between tracking and enforcement?
Tracking answers the question "when does this expire?" Enforcement answers the question "may this person work this shift?"
They sound close. They are not. Tracking is a reminder system, and reminders fail quietly. Credential enforcement is a gate in the workflow itself. The assignment does not complete unless the credentials hold.
In Workforce & Compliance, the check has three outcomes:
- Compliant. The assignment proceeds. Nobody sees anything.
- Expiring soon. A required credential expires within 30 days. The assignment proceeds with a warning, so someone starts the renewal.
- Blocked. A required credential is expired, missing, or still waiting for review. The assignment is refused, with the specific credential named.
Every refusal is recorded, so there is a trail of what was stopped and why.
Why does the shift date matter more than today's date?
Here is the scenario that catches careful teams. It is the 3rd of the month. An RN's state license expires on the 12th. A coordinator books her for six shifts between the 8th and the 20th.
A check against today's date passes all six. She is compliant today. But three of those shifts fall after the 12th, and unless the renewal lands in time, she will walk onto a unit with a lapsed license.
A check against the shift date handles this correctly. The shifts on the 8th, 10th, and 11th pass, with a warning that the license is expiring. The shifts on the 14th, 17th, and 20th are blocked until the renewal is uploaded and verified. The coordinator finds out on the 3rd, with nine days to fix it, not on the 14th with a client on the phone.
Mach 1 checks each required credential against the start of the shift being assigned.
Where does the check need to fire?
Anywhere a person can end up on a shift. Most home-grown processes cover the front door and leave the side doors open. In Mach 1 the same gate runs on:
- a coordinator assigning a clinician by hand
- bulk and draft assignments when a schedule is published
- a clinician accepting an open shift offer from the mobile app
- offers being created in the first place, so non-compliant clinicians are never invited
- shift swaps between two clinicians
- recurring order series
Non-compliant clinicians also drop out of the ranked lists coordinators choose from, so the block is rarely the first time anyone hears about it.
It is worth being precise about the boundary. The gate runs at assignment. It does not run again at clock-in, and hours recorded after the fact, such as paper timesheets, are not re-checked. The gate exists to stop a bad assignment, not to refuse to record work that already happened.
What should you require, and where?
Requirements belong on the job, not on the person. An ICU RN role at one hospital and a school nurse role in a district need different stacks.
Mach 1 starts from a catalog of credential types that an agency can edit: professional licenses including compact nursing licenses, certifications such as BLS, ACLS, PALS, and TNCC, vaccinations, TB and drug screens, N95 fit tests, background checks, identity documents, liability insurance, skills checklists, and references. Each job lists the credentials it requires, and the gate checks exactly that list.
If you run Bullhorn, certification types and each job's required certifications import from it, and candidate certifications sync both ways with their files. The Bullhorn integration page has the detail.
How do you keep credentials current without chasing people?
Put the clinician in the loop. The person with the most reason to keep a license current is the person who cannot work without it.
Each credential type has a renewal reminder lead time, and the clinician gets a push notification before the credential lapses. They upload the renewal from the web or mobile app. The upload lands in a verification queue, where a reviewer approves it or rejects it with a reason, and the clinician can resubmit.
Until a reviewer approves it, the credential counts as unverified, which blocks assignment. That matters. An uploaded photo of a license is a claim, not a verification.
Ops sees the whole pool in compliance analytics: overall compliance rate, status distribution, expiration risk, the verification queue, and coverage by job. That turns "who do we chase this week?" into a list.
What about exceptions?
Real operations have them, and pretending otherwise is how people learn to route around a system. Mach 1 handles this in two explicit ways, both optional. An agency can allow an administrator to bypass a block, but only with a recorded reason. And enforcement itself can be switched off for an organization that is not ready for it.
The point is that an exception is a decision someone made and signed, not a gap nobody noticed.
What should you check in your own process?
Run this against how your agency works today.
- When a coordinator assigns a clinician, does anything check credentials automatically, or does it depend on the coordinator?
- Is the check made against the date of the shift, or against today?
- Does the same check run when a clinician picks up an open shift or swaps with a colleague?
- Are requirements defined per job, or is there one generic list for everyone?
- Does an uploaded document count as valid before a person has reviewed it?
- Do clinicians get their own expiration reminders, or only your ops team?
- When someone overrides a block, is the reason recorded?
- Can you produce, today, a list of every clinician with a credential expiring in the next 30 days who is also booked on a shift after that date?
If the answer to the last question is "not without a spreadsheet afternoon," that is the gap. It is the same gap described in every shift tells three stories: the scheduled record says who, where, when, and under which credentials, and the last part is usually the one nobody is checking.