The bench, not the core crew

Scheduling per-diem and occasional security guards

Most security rosters have a core group who work every week and a much larger bench who work occasionally — a few shifts a month, or a few a year. Most scheduling advice is written for the core crew. The bench behaves differently, and it's worth treating as its own problem instead of a smaller version of the same one.

Why an occasional guard is a different scheduling problem

"Per diem" is the term the industry actually uses. Real job postings for this work — overnight, event, or fill-in security — are titled "per diem," not "occasional" or "on-call." If you're the one writing the job posting, that's the word candidates search for.
Turnover in this industry is front-loaded and steep. Industry data on newly activated security staff shows meaningful drop-off inside the first two months — a real chunk of anyone you onboard this quarter won't still be reachable next quarter, which is a different planning problem than retaining a stable core crew.
Re-onboarding tax compounds with infrequency. A guard who works twice a year is the guard most likely to forget an app login, need a password reset, or need a walkthrough of a tool they used once eight months ago. The friction isn't the tool being bad — it's that infrequent use is friction, for any tool.
Reachability, not willingness, is usually the actual bottleneck. A per-diem guard who'd take a same-day shift only helps if the message reaches them somewhere they'll actually see it before the shift starts.

The billing wrinkle, briefly — and where it belongs

Per-seat scheduling tools bill for every name on the roster whether that person worked this month or not, which puts real pressure on companies to either prune their bench (losing the reachability advantage of keeping people on file) or eat the cost of paying for names that aren't working. That's a real dynamic — but it's a pricing-model question more than a scheduling one, and it has its own page: scheduling without per-seat bench charges →

What actually helps with a bench-heavy roster

No app to relearn

A per-diem guard who claims a shift by texting CLAIM and a code doesn't need to remember a login, reinstall an app, or get walked through an interface they haven't touched since spring. The channel that reaches them is one they already use every day.

Reachable the same way, working or not

A guard stays on file with their certs and eligibility intact whether they've worked this week or not this year — nobody has to manually re-add them to get a text out when a shift opens up.

Only billed when active

Pricing is flat by active crew size — a name on the roster who isn't working this month costs nothing. See pricing for the tier ladder.

Show us one difficult shift

Bring us your hardest-to-reach per-diem name — the one who works twice a year and never opens the app you're paying for. We'll show you how they'd get the text.

Show us one difficult shift Try the live demo

or email hello@nabshift.com directly