Fill every post. Catch overtime while it's still cheap.
Recurring templates, an open-shift marketplace, and scheduled-vs-worked hours in one calendar — so coverage gaps and overtime surface while you can still do something about them.
Templates that survive reality
Build recurring shift templates once for every stationary and patrol post, then let the exceptions be exceptions. Ad-hoc shifts, recurring shifts, tasks, and patrols live in the same calendar, so a Tuesday add-on doesn't get tracked in a side spreadsheet. Multi-site views let a scheduler work an entire book at once — every site, every post — without a per-site fee for the privilege of seeing your own operation.
- Recurring templates for stationary and patrol posts
- Ad-hoc and recurring shifts, tasks, and patrols in one calendar
- Multi-site views with no per-site fees
The shift-offer marketplace
When coverage opens up, it goes out as an offer instead of a phone tree. Qualified guards see it in the app and claim it; the confirmation is recorded with who accepted and when. Your scheduler stops spending the evening calling down a list, and you stop discovering at 6 a.m. that nobody actually confirmed. Every claim is an auditable record, not a text message someone remembers sending.
- Open coverage published as an offer, not a call list
- Qualified guards claim it from the mobile app
- Confirmations recorded — no more 11 p.m. phone trees
Scheduled vs. worked, live
The gap between what you scheduled and what actually got worked is where margin disappears. SNTNL shows it as it happens: early clock-ins, late starts, and overtime that is still forming surface before payroll closes, by guard, site, and contract. Time-off approvals run in the same flow, so the coverage gap a request creates is visible the moment the request lands — not the week it becomes a no-show.
- Early clock-ins and late starts flagged the same shift
- Forming overtime visible before the pay period closes
- Time-off approvals show the coverage gap they create
Skills, restrictions, and eligibility
Not every guard can work every post, and the schedule should know that. Guard skills — licenses, certifications, weapons endorsements, vehicle qualifications — and site-level restrictions filter who can be scheduled and who even sees an open offer. The wrong guard never gets put on the wrong post by accident, and eligibility is documented if a client ever asks who you sent and why.
- Guard skills and certifications drive eligibility
- Site restrictions limit who can be scheduled
- Offers only reach guards who actually qualify
How it feeds the proof loop
Everything on this page ends up in the same place: an evidence record you can hand to a client, an auditor, or a lawyer.
- 01
A scheduled shift creates the expectation: this post, these hours, this guard.
- 02
Geofenced clock-in turns the expectation into a verified start time.
- 03
Tasks and patrol stops attach the work performed to that same shift record.
- 04
The client report and the invoice are built from that record — not from memory.