NezTrack Console, guard scheduling & workforce management
Runs in a browser on the office desktop, all shift long. Everything about the business lives here, and it is the only screen a dispatcher needs open.
- Live operations
- Every on-duty guard on one map, with site radii, named zones, incident pins, panic alerts, out-of-zone alerts and position replay.
- Scheduling
- Month, week, day and list views. Drag assignment with clash and certification checking, templates, recurring shifts, open shifts and coverage requests.
- Incidents
- Category-specific questionnaires, severity, evidence, triage workflow, follow-ups and a permanent searchable archive.
- Payroll
- Pay runs generated from verified attendance, overtime on your real period boundaries, adjustments and late additions.
- Workforce and compliance
- Directory, invitation onboarding, credential expiry tracking, and scheduling that refuses a guard whose licence has lapsed.
- Clients and sites
- Client records and contracts, sites with a map boundary, named zones, a clock-in radius and the posts that need covering.
- Notifications
- Push, email and an in-app inbox carry panic alerts, out-of-zone alerts, incident dispatch and shift reminders as they happen.
- Access control
- Permission profiles, per-site time zones, guards who work for more than one company, and a full audit history of every change.
Who works in the console
The office runs the whole business from here. Different people open it for different reasons, and a permission profile decides what each of them can see and do.
- Owner / general manager
- Reviews performance across the operation and approves payroll.
- Dispatcher
- Builds the schedule, watches the live map, and fills coverage gaps as they open up.
- HR and payroll staff
- Onboards guards, tracks licences and certifications, and runs pay periods.
- Field supervisor
- Oversees a group of sites from the console or their phone, and responds when an alert comes in.
Access follows the same idea. Permission profiles are built from a catalogue of individual permissions: who can view the live map, approve payroll, close incidents, edit sites, invite staff. So a dispatcher, a supervisor, an HR administrator and an owner each see a different version of the same console. Every record keeps a history of who created it, who changed it, and when, so that version is also an audit trail.
A shift, start to finish
Building next week's schedule starts with placing shifts against sites and posts. Dragging a guard onto a shift checks for a clash with another booking, a post that is already full, and a certification the post requires but the guard does not hold, before the assignment is made rather than after. Once a shift is assigned, the guard gets an invitation on their phone with a response deadline, and the console shows who has not yet replied. Unfilled shifts can be published as open, and the first qualified guard to claim one gets it.
On the day, the dispatcher watches the guard arrive on the live map. The app will not let them clock in until they are inside the site's radius, so the position that appears is a position that was verified, not typed in. Through the shift the console shows checkpoint scans as they happen, and any incident the guard files arrives for triage immediately, with photos, a category, a severity, and the exact location attached. At the end of the pay period, the pay run is generated straight from the verified attendance record, so there is no separate timesheet to reconcile it against.
When something goes wrong
- A no-show
- If nobody has clocked in shortly after a shift was due to start, the office is alerted automatically.
- A lapsed credential
- A guard whose required licence or certification has expired cannot be assigned to a post that requires it. The schedule enforces it.
- An incident
- It arrives for triage immediately, moves through review, and collects follow-up notes; every status change records who made it.
- A guard leaving the site
- An out-of-zone alert reaches the office the moment a guard leaves the boundary they are assigned to.
The rest of the system
NezTrack is three applications sharing one record. Here are the other two.
Start with one site and five guards.
Add your sites, draw a radius on each, invite your guards, and build your first week. You can do that today.