← Back to nabshift.com

About NabShift

Built in the Twin Cities, for security crews anywhere

The story

NabShift is veteran-owned, built in Minneapolis–St. Paul, alongside a working Twin Cities security crew. We didn't start from a whiteboard — we started by watching a dispatcher run a roster the hard way: the 1 AM callout when a post goes empty and someone has to start dialing numbers by hand, the group text that says more than it should to people who shouldn't see it, the schedule that only really exists in one person's head. Every feature in NabShift answers one of those problems, not a hypothetical one.

What we believe

• Guards claim shifts. They aren't assigned into silence: every open post goes out to the crew, and guards choose their own work — a post fills first-come, or with dispatch's confirmation when it calls for vetting.
• Pay stays private between guards. What one worker is offered for a shift is never visible to another.
• No penalty, scoring, or "you declined too many" mechanics for anyone, ever.
• Location is a one-time stamp at the edges of a shift (check-in, check-out), never a track. NabShift does not watch where a guard is between those two moments.
• Texting is a first-class channel, not an afterthought. The app and SMS run off the same rules, so they can never tell a guard two different things.

How we handle your data

A crew's data belongs to the crew. If a company leaves, its roster and history export with it. A worker's location is captured only as a one-time check-in/check-out stamp at a shift's venue, never continuous tracking, and a text reply of STOP is always honored, immediately. This page is the plain-language summary; the full versions are in our Privacy Policy and SMS Terms.

Support

Email hello@nabshift.com and a person reads it — not a ticket queue. Guards can text HELP any time. Onboarding is done-for-you: we set up your roster, your sites, and your number. You don't configure anything.