Compliance metrics that prove the patrol happened

"How do we know the guards are doing their job?" Every client asks it in the renewal meeting. The compliance metrics that answer it have to be numbers you can trace back to a record, not reassurance.

Which numbers actually answer the question?

Five, for the period you pick.

• Route completion rate. Scheduled patrol routes finished versus started, with the trend against the previous period.
• Task completion rate. Work items closed versus opened.
• Shift completion rate. Shifts worked versus scheduled.
• Reports filed. How many your team submitted, and which way it is moving.
• Team participation. How many members were active, and how many are reporting right now.

Those five carry the compliance conversation because each one has a record behind it. Route completion is not an opinion about coverage; it is a count of checkpoints scanned against checkpoints scheduled.

How do you find the site that is dragging the average?

A headline number tells you something is wrong, not where. Every figure opens into the detail behind it:

• Compare sites against each other by activity
• Open a group to see what its members completed
• Open one person to see their own completion figures
• See which sites drew the most geofence visits

This is where the work is. An 82 percent route completion rate across nine sites usually means eight sites at 95 and one at 30, and the one is a route that was scheduled badly rather than a guard who is not walking it. Where you put the checkpoints and how the route is timed explain far more misses than effort does.

How do you read the period?

Switch the window and every figure re-reads with a trend against the period before it:

• Today, as it stands right now
• This week against last week
• Monthly trend
• Activity by hour of day, which shows when the team is actually busy

The hour-of-day view is the one that changes staffing decisions. If the activity clusters between 11pm and 2am and your second patrol runs at 4am, the schedule is fighting the site.

How do incidents move across a year?

The chart below is an illustrative example of how incident types shift over twelve months. The pattern you plan staffing around is the one in your own incident records, not this one. Toggle types to isolate a trend.

What you are looking for is seasonality and clustering. Package theft rising every November, alarm calls concentrated on one entrance, a run of medical calls at a site with an aging tenant base. Each of those is a staffing or route change, not a report line.

What do you actually hand a client?

The record, not the chart.

1. Open the finished patrol route and export its completion report
2. The PDF carries your company name, a map of the route, every checkpoint with the method that proved it, and the completion percentage
3. Shifts and incidents export the same way from their own screens

The checkpoint proof the dispatcher watched land in real time is the same proof that lands in the PDF. There is no separate spreadsheet to reconcile, which is the whole point of scanning checkpoints instead of signing a sheet. How to package it for the client is covered in client reports that win renewals.

Which problems should reach you before the report does?

A monthly metric tells you what went wrong four weeks ago. Some things cannot wait that long, so they fire on their own:

• Route overdue and due soon. A patrol not finished in time escalates without anyone watching for it.
• Missed checkpoint. A checkpoint left unverified when the route is due raises an alert naming it.
• Overtime. A shift crossing an overtime threshold raises an alert, which is the cheapest lever in getting overtime costs down.
• No-show. A guard who has not clocked in for a scheduled shift is flagged.

Treat these as the real dashboard. The analytics screen is for the review meeting; the alerts are for the shift.

How do you get the data out?

• CSV from the tasks, routes, incidents, events, members, groups, channels and timesheets lists
• PDF from an incident, shift, task, event or member record, plus a route completion report for a finished patrol
• CSV or JSON from the audit log, for who changed what and when

The figures on the analytics screen are for reading. The file you hand over comes off the record it describes.

Where to start

Analytics appears in the main menu once it is switched on for your team, and it populates from activity rather than from anything you enter.

Pick the period you already report on. Read the five rates. Then open the record behind whichever number a client would question, and export that one. The chart shows you where to look. The record is what you hand over. There is more on the proof side in proving your patrols happened.