The emergency case

A guard calls off two hours before the shift. Now what?

This isn't the general "we need better scheduling" problem — it's the specific, worse version of it: a post that has to be covered in a window measured in minutes, not days. What actually happens at most small and mid-size operators today, and what changes when the fill mechanism isn't a phone list.

What actually happens tonight

Not a hypothetical — this is the documented, common pattern at operators without dedicated dispatch software.

One person works down a list, one call at a time. An on-call supervisor or dispatcher starts dialing — often from memory, a personal contacts list, or a group text — and waits for a response before trying the next name. Each unanswered call or unread text is time spent finding out someone's not available, before moving to the next name.
The bottleneck is the dispatcher's bandwidth, not the guards' willingness. A sequential process can only work one vacancy at a time even if five guards would say yes if asked simultaneously — nobody gets asked until the person ahead of them says no.
The standard operational advice is still "build a better phone list." Industry guidance for handling this recommends keeping a standing regional standby list of a handful of guards near each site and flagging gaps around a day and a half out — a real improvement over no list at all, but it's still a list a human works by hand.

There's no reliable, security-specific published call-off rate distinct from the industry's well-documented 100–300% annual turnover figure — if you see a specific call-off percentage cited anywhere, including here, treat it as a rough proxy, not a hard industry number.

Two moments where speed of discovery matters as much as speed of fill

The advance call-off

A guard texts "can't make it tonight" at 4:45pm for a 6pm shift. There's a window, but not much of one — every minute spent on the first two calls that don't answer is a minute not spent reaching guard three, four, or five.

The no-show, discovered late

Nobody calls off. The 11pm-7am relief just doesn't show, and the outgoing guard is still standing there at 10:55. There's no advance warning at all here — whoever notices first (roll call, or a text from the guard waiting to leave) is the actual start of the clock, and a phone tree that starts at 11:05 is already behind.

The cluster

Two guards on different posts call off inside the same hour — common around a competing local event pulling people away. One dispatcher working one phone can only chase one vacancy at a time; the second one waits.

What a few vendors specifically claim about this

Worth knowing before you evaluate anyone on this basis — including us.

Deputy can convert a call-off into an open shift and push it to recommended team members who can claim it — routine open-shift handling, not a distinct "emergency" mode.
Celayix and Shiftboard both surface a list of qualified, available workers to the scheduler when a callout happens, who then reassigns or sends a request — a faster search, still a human-in-the-loop push.
A newer AI-focused entrant markets automatic detection of a call-off and automatic outreach to qualified guards, with specific speed and fill-rate numbers attached. Those figures are the vendor's own self-reported marketing claims, not independently verified — worth asking any vendor making a specific number like this how it was measured, not just taking the number at face value.

How NabShift changes the mechanism, specifically

The honest version, including what this isn't:

Simultaneous, not sequential

When a slot opens back up, every certified, opted-in, available guard sees it on the map and gets a claim text in the same pass — not one call at a time waiting for a no before trying the next name. No double-booking, ever — the slot resolves to exactly one guard, automatically.

Reaches guards who won't open an app

The claim code works over plain SMS. A guard whose phone is in a pocket at a bar can glance at a text and reply — full service without unlocking into an app.

Still bounded by who's reachable

Consent gating applies at 4:45pm the same as any other hour — only opted-in guards get texted, urgency doesn't override that. This isn't magic; it's a faster version of asking, not a guarantee someone says yes.

What this deliberately isn't: there's no automatic call-off detection and no auto-assignment. A human — the guard or dispatch — still has to release or re-open the slot; what changes is what happens in the instant after that, not before it. And we're not going to hand you a specific minutes-saved number, because we don't have pilot data to back one up yet — the honest pitch is the mechanism, not a stat.

Show us one difficult shift

Bring us the call-off that ate your whole evening last month. We'll show you exactly how the same situation plays out on NabShift.

Show us one difficult shift Try the live demo

or email hello@nabshift.com directly