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.

Attlock Command & ControlOperations workspace

Operations overview

Harbour Centre

Authored overview
Sam R.
Site schematic · not a live GPS trace

2

Guards on duty

1

Open incident

1

Dispatch active

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. 1

    See what is recorded

    Review recorded positions, site activity, incidents, shifts, and pending work without losing their timestamps or context.

  2. 2

    Assign the response

    Create the operational ticket, choose the guard, and provide the priority, site, instructions, and optional vehicle.

  3. 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 trackingOperations workspace

Harbour Centre

Assigned team and geofence context

Sam R.
Jordan L.
Site schematic · not a live GPS trace

Recent activity

  1. North checkpoint scanned

    17:42

    Jordan L.

  2. Incident report submitted

    17:35

    Sam R.

  3. 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
  • Supervisor acknowledgement and response history
  • Conditional escalation for unacknowledged alerts
Attlock Panic responseOperations workspace

Harbour Centre

Supervisor acknowledged

  1. Panic alert received

    Guard, site, and alert time recorded

  2. Supervisor acknowledged

    Response ownership visible

  3. Follow-up pending

    Outcome remains with the operations team

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
Attlock Shift handoverOperations workspace

Evening to night shift

Harbour Centre · Operational notes

North service door

Secured at 17:46 · Maintenance informed

Open incident

Responder assigned · Follow-up still pending

Next-shift note

Check the north entrance after handover

Client sharing stays provider-controlled and follows the applicable review workflow.

Connected records. Clear responsibilities.

Operations coordinates

Triage operational tickets, coordinate guard or vehicle assignment, and update the response from the web command center.

Supervisors follow through

Review field activity and safety alerts, acknowledge receipt, and retain the context needed for the next decision.

Clients see the right record

Receive only the provider-shared activity or reviewed records available to the client relationship—not the internal operations console.

Questions about Command & Control.

What to know about getting started, supporting your team, and running your sites.

Talk to our team

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.

Run your security team in one place.

Schedule shifts, track patrols, and share reports.