Credential lifecycle
Scheduling around certifications that expire
Every security company deals with the same underlying problem: guards hold credentials that lapse, on different clocks, sometimes mid-contract. The question that actually matters when picking a scheduling tool isn't whether it stores an expiration date — almost all of them do — it's what happens the moment that date passes.
Certifications don't run on one clock
Real variation, because a generic "renewal reminder" undersells how uneven this actually is.
- Who gets licensed varies by state. Some states license the agency and train individual unarmed guards in-house on a short pre-assignment window; others license every individual guard directly, with separate armed and unarmed classes. Know which model your state uses before assuming a "guard card" works the same way everywhere you operate.
- Renewal cycles range from one year to five, or not at all. Some states require an armed license renewal annually while the unarmed license on the same roster runs five years. At least one state has no refresher requirement whatsoever. A single "certs expire every N years" reminder rule doesn't hold across a multi-state roster.
- CPR/first-aid requirements aren't universal. Some states mandate it as part of licensing; others leave it entirely up to the employer or the client contract.
- Some credentials are client-driven, not state-driven. A maritime-facility post may require a federally issued transportation credential on its own five-year cycle; a hot-work post may carry an OSHA-driven fire-watch duty with no formal "certification" at all, just a trained, documented minimum stay. Neither shows up if you're only tracking state licenses.
The question that actually matters: block, or flag?
A tool that stores an expiration date and a tool that refuses to let an expired guard get scheduled are very different products, even if their feature lists both say "certification tracking." Here's what's documented, precisely — some of this is genuinely unclear from public documentation, and it's flagged as such rather than guessed at.
| Product | What happens when a cert lapses |
|---|---|
| Deputy | Documented: the manager sees a training-expiry warning at scheduling time, but can override it and schedule the person anyway. |
| Belfry | Alert-based — the vendor describes expiration alerts sent ahead of the date; no documentation found describing an automatic scheduling block. |
| Connecteam | Alert-based — expiration alerts on stored documents; no block language found. |
| TrackTik / Trackforce | Genuinely unclear from public sources — the platform's own documentation describes configurable requirement tiers and states expired skills don't block scheduling by default, while separate marketing material describes protected posts blocking ineligible guards when credential tracking is active. Worth asking directly what the default behavior is before assuming either way. |
| When I Work, Celayix, Shiftboard, Nowsta, LASSO | Not independently confirmed either way from public documentation — don't take anyone's word for this, including ours, without checking directly. |
How NabShift handles it: a hard gate, not a flag
Checked against the shift, not "today"
A required certification's expiry is checked against the actual date and time of the shift being claimed — not the date you happen to be looking at the schedule. A cert good today but lapsed by a recurring post three weeks out already makes that worker ineligible for that date.
The same gate, every path in
A claim, a direct admin assignment, and a trade all run through the identical check. There's no faster path that skips it — assigning a worker directly can't be used to get around an expired cert.
Re-checked at the last second on a trade
If a guard's cert lapses in the gap between proposing a trade and a dispatcher approving it, the approval itself re-runs the check and refuses it — the re-check is a deliberate feature, not an afterthought.
Not every competitor's cert-gating behavior could be pinned down publicly — where it couldn't, this page says so rather than guessing. NabShift's own behavior is a hard block; ask any vendor you're evaluating the same direct question — "what happens the moment a required cert expires" — and see how specific the answer is.
Show us one difficult shift
Bring us your messiest cert situation — the armed post, the client-specific training requirement, the guard whose renewal is cutting it close. We'll show you exactly what happens when it lapses.
Show us one difficult shift Try the live demoor email hello@nabshift.com directly