Security robot, guard and remote monitoring: who does what?

Replace the general expression “monitor the site” with observable tasks. For example: check a point at a defined time, flag a presence in an area, obtain a usable image, verify an authorised exception or contact the designated person. Define the information needed to move to the next stage.

This breakdown avoids comparing a machine that follows a route with a human service involving other responsibilities. It also helps identify repetitive tasks for which equipment could be considered, without assuming it replaces all existing activities.

A mobile patrol can be considered when observing several points is useful and the terrain allows movement. The pilot must check the route, interaction with site use, information obtained and transmission. Completing a route does not, by itself, show that every observation was useful.

Describe limitations: inaccessible areas, obstacles, conditions encountered, maintenance, charging, downtime or manual recovery. Establish how the operator learns that a task was not completed. The absence of an alert must not conceal the absence of a check.

Our guide to robotic business patrols explains how to define a pilot. At a dealership or car park, authorised movement and presence must remain compatible with the task. At a warehouse after hours, operational exceptions form part of the context to communicate.

Describe remote monitoring through the services actually provided: events received, handling hours, verification methods, instructions, reports and possible mobilisation of another party. Ask what the operator can see and what they can do when the evidence is insufficient.

An app notification recipient is not necessarily a remote monitoring service. A remote monitoring contract does not automatically mean someone will attend the site. Ask who carries out that visit, under what conditions and with what commitments, without quoting a marketed response time out of context.

The second-home alert handling sheet shows how to provide a deputy and handle no response from the first contact. The same approach can be adapted to a business and its on-call arrangements.

An on-site guard can perform tasks specified in their assignment and suited to their skills: presence, checks, verification or support for a procedure. Describe these concretely. The term “guard” guarantees neither permanent presence nor every possible response capability.

Ask which company actually delivers the service and check the applicable conditions. In Geneva, the official list of private security companies provides an initial provider check. For another canton, use the competent authority. Technology offered on the site does not constitute a private security authorisation.

Organise response without asking occupants, staff or a neighbour to confront a suspicious presence. Instructions must distinguish an announced test, a technical fault and a real situation requiring the appropriate services.

For each task, note the means used, the person responsible for handling it, the evidence expected and the fallback if it fails. A row with no owner is a point to resolve. Two parties who each think the other handles the same stage also create an ambiguity to correct.

In a fictional example, a depot plans mobile observation and remote reception. A presence is detected, but the service does not have the late delivery schedule. The problem here is missing context. Adding a sensor would not automatically resolve that gap; handovers and access to instructions need organising.

The matrix does not replace the contract. It helps identify services to confirm, integrations needed and scenarios to test jointly.

Test at least a normal task, an inadequate observation, a transmission fault and an unavailable contact, using agreed scenarios. Record expected and actual results. Do not send a false real-world call-out request to a service that has not been informed of the exercise.

In the workplace, the FDPIC distinguishes legitimate security from monitoring employees’ behaviour. Integrating a robot does not remove this requirement. Define areas, hours, information for people and data access in line with the chosen purpose.

Finally, compare the total cost of scenarios that fulfil the necessary tasks. Assumed savings in human hours must not be presented as an outcome without measuring which tasks are actually removed, retained or added. The quote comparison checklist helps keep limitations and responsibilities alongside the figures.