LO
Security guard — tasks, one by one
The unit of analysis is the task, not the job title. Each one below carries its direction, whether the judgement rests on evidence or on platform inference, the reasoning, and what it does not establish.
Every task on this page#
Watching the screens
Automating✓ Evidence-backedSitting in front of a wall of camera feeds looking for the thing that is out of place.
This is the clearest automation in the occupation and it is not new: humans are famously bad at sustained visual vigilance, attention collapses within about twenty minutes, and detection software does not get bored. Video analytics is deployed widely precisely because the human baseline on this specific task is poor.
Detection is not response, and every deployment we know of converts a watching post into an alert queue rather than removing the post. The important second-order effect is the false-alarm rate: a system that flags too much moves the guard from watching to dismissing, which is a worse job and, after a few hundred dismissals, a less attentive one.
Walking toward the situation
Still human-led✓ Evidence-backedBeing the person who physically approaches the argument, the intruder, the person who is unwell — and de-escalates it or calls it in.
The value of a guard at an incident is that a person with a uniform is standing there, which changes the behaviour of everyone present. That is a social fact rather than a technical one, and no sensor substitutes for it — the robot patrol units deployed in retail and transit are explicitly specified as observe-and-report and route their alerts to a human.
The task holding does not mean the headcount holds, because the usual design is fewer guards covering more ground with faster alerts. A site can halve its guards and keep response times by adding cameras — the task survives intact and the roster does not, which is the most common shape of change in this occupation.
Controlling the door
Automating≈ Platform inferenceDeciding who comes in: badges, visitors, deliveries, the contractor who is not on the list but is expected.
Access control is a solved engineering problem and has been for years: badges, turnstiles, visitor kiosks and remote verification handle the rule-following portion completely. What remains at the door is the exception, and the exception is exactly what the system escalates to a person.
Automating the rule does not settle who takes responsibility for the exception, and in practice the exception is where every real incident starts. Sites that removed the staffed door and kept only the turnstile have generally re-added a person for reception rather than security reasons — worth knowing, because it means the post can come back under a different name and a lower grade.
The log and the report
Automating≈ Platform inferenceRecording patrols, incidents and handovers in a form that will stand up if it is ever read in an investigation.
Patrol logging has been automated by scan points for a decade and incident reports are the same structured-text problem being solved everywhere else on this site: a person describes what happened, a system formats it, the person signs.
Automating the log changes what the log is for. Scan points prove presence, not attention, and a route that is verified by scans rewards walking it fast — which is the opposite of what the job needs. That trade-off shows up nowhere in the business case for the system.