Af Syed Muhammad Daud Rizvi — Medstifter af TapOkie Work. Bygger besøgstjek ind og revisionsklar overvågning for enearbejdere i små teams — uden enterprise-lock-in.
Field engineers and mobile technicians often work alone at customer sites, after hours, or in remote locations. Compliance means assessing those risks, using timed visits or job check-outs, alerting supervisors on misses, and keeping records. App-based monitoring is usually easier to adopt than devices built only for high-risk ARC deployment.
Who this covers
Field service work is one of the largest categories of lone working in the UK. It includes utilities engineers visiting customer premises, HVAC and facilities maintenance technicians, IT field engineers attending client sites, inspectors and surveyors working alone at various locations, mobile mechanics and engineers, and sales representatives or account managers spending significant time on the road visiting sites.
What these roles share is that the worker is at a series of locations during the day, at premises they do not control, without immediate access to a colleague if something goes wrong.
The field service risk profile
Field service workers face a combination of hazards that most office-based risk assessments do not capture.
Physical hazards at unfamiliar sites: a technician visiting a new customer premises may encounter slipping hazards, confined spaces, electrical risks, or poorly maintained equipment that has not been flagged in advance. They are arriving without full knowledge of what conditions they will find.
Isolation and delayed detection: if a worker is injured at a remote site, in a basement plant room, or at a customer location with limited mobile coverage, the time between the incident and anyone knowing something is wrong can be significant. The severity of some injuries is directly related to how quickly emergency assistance arrives.
Third-party risk: field service workers interact with customers, site staff, and sometimes members of the public. While most interactions are routine, the risk of aggressive or threatening behaviour exists, particularly in debt-related or enforcement-adjacent roles.
Vehicle and travel risk: field workers spend more time travelling than office workers. While road risk is a separate category from lone working, organisations with significant field operations should treat it as part of the same risk landscape.
Lone worker policy for employer obligations in field service
A lone worker policy for field service operations needs to cover more ground than a policy for a static workplace. It should address:
Employer obligations: site risk information. Workers going to a new customer site for the first time should have access to any known hazard information. This might be as simple as "roof access required" or "confined space entry" in the job record. Field service management systems can carry this information if populated correctly.
Mobile coverage gaps. Your risk assessment should identify jobs or locations where mobile coverage is likely to be poor. For these jobs, alternative check-in arrangements may be needed: a call to the office before going into a building, a specific re-check time, or a requirement to have a colleague aware of the specific location.
Session monitoring during jobs. Workers should start a monitoring session when they arrive at a site and end it when they leave. For multi-stage jobs, the expected session duration should reflect the realistic job length, not a fixed minimum.
SOS capability. Field workers encountering an unexpected hazard at a site, an aggressive customer, or a medical emergency need to be able to raise an immediate alert. A single SOS action from their phone is the standard.
Out-of-hours jobs. Many field service operations include emergency call-outs, planned maintenance at night, or weekend work. The escalation chain for out-of-hours monitoring needs to be different from the office-hours chain. Identify who receives alerts at 11 pm and what they are expected to do.
Lone working in vehicles. If a worker breaks down or is in an accident in a remote location, they may be in a lone working situation without having triggered any session. Consider whether your policy addresses vehicle incidents specifically.
Practical monitoring for field service
Field service workers typically use their phones for job management already: job lists, directions, customer contact details, completion notes. A lone worker monitoring app that runs alongside their existing tools is practical. One that requires a separate device or a desktop login is not.
The monitoring action should be quick. A field engineer arriving at their fifth site of the day needs to start a session in two taps without it feeling like an additional administrative burden. Session extensions, where the worker can add time to an existing session from their phone, are important in field service because job duration varies.
Manager alerts should be specific enough to be actionable. "Worker X has not checked out of job at Customer Y after Z minutes" is useful. A generic "lone worker alert" without location or job context is not.
Records for compliance
For field service organisations, visit records serve a dual purpose: they document the lone working monitoring (duty of care evidence) and they corroborate the job completion record. Exportable records showing when a worker arrived at a site and when they left are useful for both purposes.
For regulated industries, such as utilities or facilities management with large corporate or public sector clients, the ability to export lone working records on request may be explicitly specified in the contract.
Related reading
- What is a lone worker? UK definition explained
- Lone worker risk assessment for small teams
- How to write a lone worker policy
- RIDDOR and lone workers
- Features: how TapOkie Work monitors field workers
Almindelige spørgsmål
What make field roles high risk?
Isolation, plant and equipment, customer sites, night work, travel between jobs, and delayed discovery if an incident occurs.
Should every job use dual attendance?
Only where the risk assessment says so. Most jobs rely on check-outs and escalation; some high-risk permits still need two people.
How fast should missed check-outs escalate?
Define timers by job type and site risk. Document who is on-call and how acknowledgements are recorded.
Does vehicle GPS replace lone worker apps?
Fleet tracking shows a vehicle, not always that a technician is safe on site. Pair location tooling with explicit visit end/SOS signals if risk warrants it.