Command & Control. Live tracking, dispatch, and monitoring.
Bring recorded guard positions, operational tickets, guard dispatch, and response context into one clear view—so your team can decide what happens next.
Location freshness depends on connected field devices and company configuration.
Authored operations example. The map is a schematic, not a live GPS trace or customer feed.
One operation. A clear next move.
1
See what is recorded
Review recorded positions, site activity, incidents, shifts, and pending work without losing their timestamps or context.
2
Assign the response
Create the operational ticket, choose the guard, and provide the priority, site, instructions, and optional vehicle.
3
Carry the context forward
Follow response status, retain resolution notes, acknowledge safety alerts, and carry the right context into the next shift.
The operation, in one workspace. From recorded context to coordinated response.
Move from recorded field context to operator-led assignment and the wider operational queue. Each view supports a different decision without pretending every update is a live telemetry event.
Live tracking
View the latest recorded guard position and timestamp when field location updates are available, alongside site context, assigned shifts, and recent clock-in, checkpoint, or incident activity. Continuous background tracking is not promised.
Attlock Live trackingLive trackingOperations workspace
Harbour Centre
Assigned team and geofence context
Sam R.
Jordan L.
Site schematic · not a live GPS trace
Recent activity
North checkpoint scanned
17:42
Jordan L.
Incident report submitted
17:35
Sam R.
Evening shift clock-in
17:00
Jordan L.
Current positions are viewable when recorded field updates are available; no fixed GPS refresh interval is promised.
Authored operational example. Changing views does not track a guard, create a ticket, assign a responder, or send a notification.
Panic acknowledgement. Make receipt and ownership clear.
A guard can hold the mobile panic control for three seconds to create an alert and a critical operations ticket. Supervisors and administrators can review and acknowledge it, then coordinate the next operational step.
Guard, site, alert time, and available context recorded
A panic alert does not call emergency services. Follow site procedures and contact local emergency services for immediate danger.
Escalation depends on site configuration, timing, and notification preferences. Acknowledgement is not proof of dispatch or arrival, and a panic alert does not call emergency services.
Shift handover without the loose ends. Keep the next shift and the client record distinct.
Create structured pass-down records with site and shift context, category, priority, notes, and attachments. Previous handover notes can inform the next guard, while comments and read or acknowledged receipt keep the follow-up understandable.
Site, shift, priority, and follow-up notes together
Read or acknowledged receipt with viewer history
Client records shared through the configured workflow
Authorized operations users can review recorded guard positions and timestamps when field location updates are available, alongside site context and recent activity. The page does not promise continuous background tracking, a fixed GPS interval, or a position for every alert.
Operations creates the ticket, selects a guard, and records priority, site, instructions, and an optional vehicle. Dispatch status can progress through pending, acknowledged, en route, on scene, completed, or cancelled. Assignment is operator-led, not automatic nearest-guard selection.
No. The workflow does not promise route- or traffic-aware ETAs, guaranteed response times, or automatic emergency-service contact. Operational notes and human updates carry the current context.
A guard can hold the mobile panic control for three seconds to create an alert and a critical operations ticket. Supervisors and administrators can review and acknowledge it. Unacknowledged alerts can escalate according to the site's configured settings and notification preferences.
No. Acknowledgement records that a supervisor or administrator acknowledged the alert; it does not prove that a responder was dispatched or arrived. Follow your site's emergency procedures and contact local emergency services for immediate danger.
Pass-down records can include site/shift context, category, priority, notes, attachments, comments, and read or acknowledged receipt. Previous shift-handover notes can inform the next guard. Detailed observations and follow-up remain the team's responsibility.
Clients see only the records and activity their provider makes available through the applicable workflow. Some report types can be visible immediately when approval is not required; others follow review. Client visibility is not automatic proof of attendance, response, or resolution.
No. All map positions, incidents, alerts, assignments, and notes on this page are authored examples. The preview does not access live operations, track a guard, create a ticket, send a notification, or contact emergency services.
Run your security team in one place.
Schedule shifts, track patrols, and share reports.