GuardChek / Features / Scheduling
Drag-and-drop schedules, 52-week recurring patterns, and open shifts that fill themselves by text message. Written into the software by people who dispatch real guards every night.
Every guard company owner knows the feeling. It is 9 PM on a Friday, a guard just texted that his car died, and the site he covers has a contract that says coverage starts at 10. What happens next in most companies: the owner starts calling down a list, one guard at a time, while the clock runs. Whatever tool you use for scheduling, that moment is the test.
GuardChek's scheduling exists because the founder's own security company lived that moment too many times. The whole module is designed backwards from the worst night, not the best one.
The schedule is a drag-and-drop calendar. Drop a guard on a site, stretch the shift to the right hours, done. For contract sites that run the same pattern all year, build the pattern once and set it to recur for up to 52 weeks. Build the pattern once, set it to recur for up to 52 weeks, and the calendar fills itself for the year.
Employee groups with hour caps keep you honest on overtime before it happens: if a guard is about to blow past their cap, you see it while scheduling, not on the payroll report two weeks later.
Drafts stay private until you publish. Build next month quietly, move people around, and push it to the guards' phones only when it is final. No more "but the app said I worked Tuesday" confusion from a half-built schedule.
Back to that Friday night. In GuardChek you post the empty shift as an open shift and broadcast it by SMS text blast to eligible guards. For real emergencies there is an urgent-cover mode that makes the message impossible to miss. Guards apply from their phones; you pick one and the schedule updates.
One broadcast instead of nine phone calls, and every eligible guard sees it at the same time.
Guards trade shifts. Fighting it does not work; losing track of it is how the wrong person shows up at the wrong site. GuardChek handles swaps with codes: a guard offers a shift, another accepts with the code, and the swap only becomes real when it passes the rules you set and gets approved. The schedule, the time clock and payroll all follow the swap automatically.
Here is where one platform beats a scheduling app taped to a payroll process. The same shift you scheduled is the shift the guard clocks into, with a geofenced GPS punch proving when and where the shift started. Those verified hours flow straight into payroll and into your client invoices. Schedule once; everything downstream follows. No re-typing hours into a second system, no disputes about who worked what.
If a guard does not clock in on time, you know within minutes, not at the end of the shift. The 2 AM no-show becomes a 10:05 PM alert, while there is still time to blast the open shift.
Bring your ugliest schedule to the demo: rotations, splits, the site nobody wants. We will build it live.
Book a live demoYes. Scheduling, GPS clock-in, incident reports, SOS, payroll and the guard app are on every plan, including Starter. See the published pricing.
Yes. Build a pattern once and set it to recur for up to 52 weeks.
Post the shift, broadcast it by SMS to eligible guards, and pick from the guards who apply. An urgent-cover mode exists for the real emergencies. The schedule updates itself when you choose someone.
Yes. Published schedules appear in the GuardChek app on iPhone and Android, along with site info and post orders for each shift.
Clock-in requires GPS inside the site's geofence. Wrong place, no clock-in. Every punch carries its time and location, and every guard's profile carries a selfie identity photo taken at first sign-in, so the office always knows exactly who is who.