Improving Operative Safety With Monitoring Systems

---

The phrase “monitoring system” covers a wide range of technologies that have nothing in common except that they observe something and generate a response. A driver-facing DSM camera that detects fatigue is a monitoring system. A proximity sensor that detects a pedestrian behind a reversing vehicle is a monitoring system. A portal that flags a vehicle stationary in an unexpected location is a monitoring system. What matters for operative safety is not the category of monitoring but whether it detects the right hazard, reliably, in time for the detection to be useful.

This guide works through the monitoring systems relevant to council and public sector fleet operations, what each is designed to detect, and how the combination addresses the HSE’s duty of care requirements for vehicle-related operative safety.

Driver Safety Monitoring (DSM)

Driver Safety Monitoring systems use an in-cab forward-facing camera with AI processing to detect specific driver behaviours that indicate fatigue or inattention: eye closure frequency, gaze direction, head position, phone use, and absence of seatbelt. When the system detects a trigger behaviour, it issues an in-cab alert — audible, visual, or both — before the behaviour develops into a collision.

For council fleet operations, DSM systems address several duty of care obligations:

• Fatigue management: Refuse crews starting pre-dawn, winter service drivers operating through the night, and parks crews doing long summer shifts are all in fatigue risk categories. A DSM system that detects micro-sleep events provides a last-resort alert that complements scheduling controls and rest break policies — but cannot replace them.
• Phone use detection: Mobile phone use while driving is a known collision cause. DSM systems with phone detection alert the driver and create an event record that the fleet manager can review. This both prevents incidents and provides the coaching data for driver behaviour management.
• Coaching and performance: DSM event data — scored across the fleet — identifies which drivers have elevated risk profiles and require additional training or intervention. The data is objective and specific: driver X had 12 phone-use events in the last 30 days is a coaching conversation supported by evidence.

Proximity Monitoring for Reversing Operations

Proximity sensors for reversing operations detect objects behind or alongside the vehicle that the driver cannot see in mirrors or cameras. For council fleet operations, reversing hazards are concentrated at specific points in the working day: refuse vehicles reversing in cul-de-sacs, street maintenance vehicles reversing to a works site, grounds maintenance vehicles reversing on narrow tracks.

Two-zone radar proximity systems provide:

• Zone 1 (0–2 metres): high alert — stop required. In-cab audible and visual alert, external audible warning
• Zone 2 (2–5 metres): warning — hazard present, caution. In-cab visual alert at minimum

For refuse vehicles where WISH WASTE-04 guidance identifies reversing as a high-risk operation, a proximity sensor combined with a rear camera — providing both automated detection and visual confirmation — is the engineering control that addresses the reversing hazard. Administrative controls (banksmen, reversing procedures) supplement but do not replace the engineering controls where the consequence of failure is fatal.

Bin Lift Zone Monitoring

The bin lift mechanism on refuse vehicles creates a zone where operatives are at risk of being struck by the moving arm, trapped between the arm and the vehicle body, or struck by material falling during the lift cycle. LOLER requires that this lifting operation is supervised and conducted safely.

Monitoring systems for the bin lift zone:

• Proximity sensors mounted on the lift arm assembly detecting objects in the immediate lift zone before and during the lift cycle
• Pressure sensing on hydraulic lifting circuits detecting abnormal resistance (obstruction) and holding the lift rather than continuing under load
• Hopper camera providing the driver with visual confirmation of the lift zone before initiating the lift cycle
• Emergency stop switches accessible from both sides of the vehicle at the working position

GPS and Geofence Monitoring for Lone Workers

Street maintenance and grounds maintenance operatives often work alone on public land — council parks, road verges, highway maintenance sites. Lone worker safety monitoring via the MDVR platform provides:

• Real-time GPS position — the operative’s vehicle location is known at all times during the working day
• Geofence alerts — the fleet manager is notified if a vehicle enters an unexpected area or if a vehicle that should be working on a specific site moves off that site during working hours
• Non-movement alerts — a vehicle stationary for more than a defined period in an unexpected location triggers a welfare check notification
• G-sensor events — a sudden deceleration or impact triggers an immediate alert to the fleet controller, who can view the camera feeds and contact the driver

This monitoring capability does not replace a formal lone worker policy — operatives should still have scheduled welfare check-in times and an emergency contact protocol. But it provides a real-time safety net that passive procedures cannot.

MOIS for Pedestrian Safety at Moving-Off

The Moving Off Information System addresses a specific pattern of operative and pedestrian injury: a vehicle moves off from a stopped position while a person is in the vehicle’s immediate forward path. MOIS uses AI-based pedestrian detection to alert the driver before the vehicle moves, providing 2–5 seconds of additional reaction time.

For council fleet operations, the MOIS hazard is most acute in specific situations: refuse vehicles moving off after a collection in a busy residential street where residents approach from the front; street maintenance vehicles moving off from a works site where operatives are still working near the vehicle’s path; grounds maintenance vehicles moving between positions on a site where members of the public are walking. MOIS provides the detection that mirrors and cameras alone do not — the area directly ahead at ground level, below the driver’s sightline in a large vehicle cab.

Integrating Monitoring into Fleet Safety Culture

Monitoring systems that are installed but not integrated into the fleet’s safety management process are hardware costs without safety benefits. Integration requires:

• Driver coaching: DSM event data reviewed in driver coaching sessions — not as a disciplinary exercise, but as a performance conversation with specific, evidence-based content
• Incident review: After any near-miss or incident, camera footage and sensor event logs are reviewed as part of the investigation — establishing what the monitoring systems detected and how the outcome related to those detections
• Maintenance records: Camera and sensor systems that are listed in daily walkaround checks and repaired promptly when faults are identified — not deferred because the vehicle needs to stay on route
• Management reporting: Regular reporting of fleet-wide monitoring data (event rates, incident trends, coaching outcomes) to senior management — demonstrating that the monitoring investment is being used and is producing results

Frequently Asked Questions

Do council operative safety monitoring systems need to comply with employment law?

Yes. Driver-facing monitoring systems on council vehicles record employees in the course of their employment. This requires: disclosure to employees of what is monitored, for what purpose, and how footage may be used — documented in the employment contract or a separate CCTV/monitoring policy. Union consultation may be required where a recognised trade union represents the drivers — monitoring systems that affect terms and conditions of employment are a consultation matter. Using monitoring data for disciplinary purposes requires prior disclosure of this use. Council HR and legal teams should be involved in the deployment of any driver-facing monitoring system.

Can monitoring system data be used to defend a claim that an operative was at fault in a collision?

Yes, subject to data protection obligations. Driver behaviour monitoring data (DSM event records, speed profiles, G-sensor logs) is evidence of how the operative was driving at the time of the collision. Footage showing the operative was not using their phone, was paying attention, and was travelling at an appropriate speed is positive evidence in a claim where the claimant alleges negligent driving. The data should be preserved as soon as an incident occurs and treated as potential evidence. Legal advice should be sought before any disclosure of monitoring data to a third party.

How frequently should operative safety monitoring data be reviewed?

At a minimum: event logs should be reviewed weekly for high-priority events (G-sensor triggers, DSM fatigue alerts). Driver behaviour scores should be reviewed monthly for trend identification and coaching prioritisation. The full footage archive should be reviewed within 48 hours of any incident or near-miss reported by an operative or a member of the public. Annual reviews of the monitoring system’s performance — are the alert thresholds correctly calibrated? Are false alerts being managed? — should be part of the council’s fleet safety management programme.

What is the difference between monitoring for safety and monitoring for performance management?

Safety monitoring detects hazards and prevents incidents. Performance monitoring measures driver behaviour over time to identify coaching needs and fleet risk profiles. The distinction matters for data protection: safety monitoring footage (a specific incident capture) has a clear legitimate purpose and defined retention period. Performance monitoring data (a driver’s rolling event score) is processed more broadly and requires clear disclosure of purpose and use. Both are permissible under UK GDPR with appropriate lawful basis documentation; both require employee transparency. The council’s data protection policy should address both uses separately.

Do proximity sensors need to be tested daily on refuse vehicles?

Yes. Under FORS Silver requirements, daily walkaround checks must include camera and sensor systems. A proximity sensor that has failed silently — not alerting when objects are detected — is a safety failure that daily testing would identify. The daily check should include a physical function test: walking behind the vehicle in the sensor’s detection zone and confirming an alert is triggered. A sensor that fails the function test should be reported and the vehicle should not operate in proximity to pedestrians until the fault is repaired. FORS audits check walkaround check records for camera and sensor entries, not just the hardware specification.

---

Free download: Improving Operative Safety With Monitoring Systems — Checklist

Download this free checklist to apply the guidance in this article to your fleet.

---

Related guides: Camera and Sensor Systems for Road Gritters · Camera Systems for Council Fleets