Product · Web
One screen for the whole operation: which sites are short, who is on post, where every manager is — and the evidence behind each of those answers.
Screen by screen
Every screen below is a real capture from the product, on demo data.
Every active site as a marker coloured by staffing — fully staffed, partially staffed, understaffed — with managers on patrol and their pending and visited checkpoints. It updates over a live connection, not on refresh.
Each shift row opens to its evidence: check-in and check-out times, the GPS fix and its accuracy, the selfie, and whether the device reported a mocked location.
A manager’s patrol is a route, not a claim. See where they started, the path driven, each checkpoint’s arrival and departure, time on site, and the report they filed before leaving.
When a guard presses the alert, the incident appears here with their live position, the closest manager, who has been notified and who is responding. Resolve it from the control room when it is over.
Guards raise leave requests and grievances from the app. They land in a queue with a category and a status, and the response you write is shown back to the guard on their phone.
Create a checkpoint for a gate, a basement or a rooftop, print its code, and stick it on the wall. Scans from the guard app arrive with location and selfie. Managers’ site visits — notes and up to five photos — are filed alongside.
Give each customer a read-only login scoped to their own sites. They see their staffing, attendance and reports — and nothing about anyone else. Fewer calls asking whether the guard was there.
A control room that runs all night gets a dark theme; a daytime back office gets a light one. Each user picks their own, and it sticks.
Next step
A 30-minute walkthrough on a live account: your sites on the map, a guard checking in, a manager on patrol. No slides.
