Every part of a shift
that somebody has to prove
A contract guarding company sells hours, then spends the month demonstrating those hours happened. These pages cover each piece that produces the demonstration.
Guarding is an evidence business disguised as a labour business. You are paid for bodies on posts, but you keep the account by answering questions after the fact: was anyone at the loading dock at 2:40, did the officer walk the fourth floor, why does this invoice show nine hours. Each answer is a record that exists or does not.
Each piece below produces a different record, and each record feeds the next. The schedule says who was supposed to be there; the clock-in says who was, and that figure runs payroll and the invoice. The tour says the property was walked, the report says what the officer saw, the portal decides whether the client has to ask at all. Spread those records across a group chat, a binder and two spreadsheets and every question costs an afternoon.
Filling the schedule and proving the hours
Every dispute with a client, an officer or an insurer comes back to a number of hours and who says so.
Guard scheduling software
Building rotations across sites, filling a call-off at 4 a.m., and catching overtime before it reaches the invoice.
Read the page →Time and attendance
Geofenced clock-in with a selfie, so a covered post and a billed post match.
Read the page →Payroll and billing hours
Turning verified shift records into what you pay and what you invoice.
Read the page →What the officer carries into the shift
Nobody logs into a laptop at a gatehouse. Everything the field does happens on a phone, in the dark, one-handed.
Security guard app
The whole shift on one phone: clock-in, tour, report and radio, in real screenshots.
Read the page →Patrol software
Mobile patrol and multi-stop routes, including what one car covering eleven sites looks like.
Read the page →Guard tour system with QR
QR and NFC checkpoints instead of wand hardware, and what a tour shows a client who doubts it.
Read the page →GPS guard tracking
Live positions for the supervisor deciding which site to drive to next, with the privacy limits stated.
Read the page →Talking to the field
Dispatch and radio are separate problems solved on one phone: a conversation, and a record of it.
Writing down what happened
Most shifts produce nothing worth reading. The value shows up months later, when someone asks about one specific night.
Incident reporting
Structured forms with photos, time and a named author, and why a narrative field alone loses a dispute.
Read the page →Daily activity reports
The DAR as something a client reads rather than files: what belongs in it, and how it is delivered.
Read the page →VigIA, the AI assistant
Questions about your operation in plain language, plus what it refuses to do and why.
Read the page →The rules of the post and the people at the door
What a relief officer needs on a site they have never worked: what the post does, and who gets through the door.
When the shift goes wrong
Two different emergencies: an officer who presses something, and an officer who stops responding while nobody notices.
What the client sees
Retention turns on whether the account feels informed: a portal moves the monthly call from justifying the service to reviewing it.
One licence, not a feature matrix. Everything above is included at 5 USD per user per month, plus a one-time 299,99 USD implementation fee and a 14-day trial. One limit, stated here rather than in a demo: with no data connection the app queues incidents, visitor entries and the start and end of a tour, but clock-in needs a live connection.
Common questions
Are features priced separately or by tier?+
Neither. One licence at 5 USD per user per month includes everything on this page — no premium tier holding back reporting or dispatch, no per-module add-on. Separately there is a one-time 299,99 USD implementation fee covering setup, and a 14-day trial first.
Which of these should a company adopt first?+
Time and attendance, almost always. It settles payroll and invoicing in the first billing cycle and is the least contentious change with officers, because accurate hours help them too. Reporting comes second: it needs a decision about what is worth writing down. Tours come third, since someone has to mount checkpoints.
What still works when an officer has no signal?+
The app queues incidents, visitor entries and the start and end of a tour, then sends them when data returns; an incident keeps the time it was written. Two limits: clock-in needs a live connection, and a checkpoint scanned out of coverage is stamped when the server receives it. Plan basement routes around that.
Can we edit report forms for a specific account?+
Yes. Incident types and their fields are configured to match each contract, as part of implementation. One thing to know first: the platform keeps no version history of those forms or of post orders — you edit the current one. If you have to prove which instruction was in force on a past date, keep that record elsewhere.
How many apps does the team need?+
Two. Officers use the guard app to clock in, run tours, file reports and talk on the radio; supervisors have their own with the map, alerts and post status. Office staff and clients work in a browser.
Try it on one account first
Fourteen days is enough to run one real site and see whether the records read the way your client would want.