Track every guard and patrol live, manage visitors at the gate and get SOS alerts within seconds. Yaqiz is an integrated guard management system: one console for the office, one app for the guard.
Watch the tour
From mapping a site to answering an SOS: see how the office and the field work as one.
1:36
Most guard-management software asks you to trust a spreadsheet. Yaqiz asks the site to prove itself — every punch carries a position, every patrol carries a scan, and every alert carries the guard's position when the phone has one.
Draw the exact boundary of each site and place checkpoints on every floor.
Polygon geofences · per-floor checkpoints
Guards clock in with a photo and GPS position inside the zone, then scan checkpoints on patrol.
Photo + position on every punch
See who is on duty and where, review patrol proof and receive any SOS pinned on the map.
Live roster · patrol proof · SOS
The manager in the office and the guard on the gate need completely different things. So they get two apps built for their own job — looking at the same sites, the same people and the same moment.
For the office
Where supervisors track guards and patrols on the live map, and manage visitors, attendance and reports.
For the guard
Clock-in, patrols, SOS and push-to-talk in one app, with nothing lost when the signal drops.
The alert reaches supervisors and the console within seconds, location attached, and each responder acknowledges on the map. No expired plan or suspended account can block it.
A quiet shift reads as quiet. The console says “All clear · watching” and shows the roster on the map. No red, no badges, no invented urgency — so when something does turn red, it means something.
Quiet states are a design decision. An interface that cries wolf gets ignored in the moment it matters.
One tap does nothing on purpose — a phone in a pocket cannot raise an alarm. The second tap arms it and starts a five-second ring with a cancel the size of a thumb. The system back button cancels too, so the countdown can never run where the guard cannot see it.
Five seconds, not three: long enough to undo a mistake, short enough that a real emergency is not waiting on a UI.
The alert leaves with the guard's position, the nearest site, the shift they were on and the time on their own device. No dispatcher has to ask where they are. If the network is gone the alert queues and says so honestly, then goes the moment it can.
The SOS is never blocked by an expired plan, a suspended account or a missing GPS fix. That path stays open by design.
Supervisors and the console get the alert within seconds. Each responder's acknowledgement lands on the map, so nobody double-dispatches and nobody assumes someone else went. The guard sees the count of who is coming.
The guard's screen shows “two responders on the way.” Knowing help is moving is part of the response.
Closing it asks who closed it and what happened. The alert, the positions, who responded and the outcome become one record — the thing you put in front of your board, your insurer or a court six months later.
Every action on an alert is recorded with who did it and when.
Your logo and colours run through the console, the guard app and printed checkpoint cards, so your team sees your organisation, not a vendor.
Yaqiz is built for the guard who uses it every shift and the manager accountable for every site. These principles come before any feature.
No commercial state can block an SOS. Not an expired plan, not a suspended account, not a missing GPS fix. If a guard is in danger the phone still works.
If an alert has not sent, the screen says queued. If a fix is weak, it says weak. Software that pretends everything is fine teaches people to distrust it.
Attendance, patrol proof and emergency events are written once. What you show six months later has to be what actually happened.
Share a few details about your company and guard force, and our team will contact you to arrange a time.