Lone Working at Night: What UK Law Requires

At 2 a.m. on a Tuesday in February, a maintenance fitter walks into a plant room alone. His supervisor clocked off at ten. The next shift does not start until six. If something goes wrong in that four-hour window, the gap between incident and response could cost him his life. It is a situation that plays out every night across UK manufacturing, and it deserves more rigour than a laminated poster on the noticeboard.

What UK Law Actually Says

There is no single “Lone Working Act.” The requirement falls under the Health and Safety at Work Act 1974 and the Management of Health and Safety at Work Regulations 1999. Together they require employers to:

• Assess the risks of lone working specifically, not just fold it into a general risk assessment
• Put controls in place that are proportionate to those risks
• Ensure lone workers can do the work safely without direct supervision
• Provide adequate supervision, which does not mean a warm body standing next to someone, but it does mean knowing where people are and being able to reach them

The HSE’s position is that lone workers should not face greater risk than employees working alongside others. That is the bar. If the risk of a maintenance task rises when there is nobody else around, the risk assessment needs to reflect that.

Night shifts and early starts raise the stakes because response times stretch. A two-minute walk to a colleague becomes a fifteen-minute wait for the nearest on-call person. That gap has to be in the risk assessment, and it has to be addressed.

Where Most Sites Fall Short

Many sites have a lone worker policy on paper and almost nothing in practice. The policy says workers should check in every hour. In reality, the supervisor on call is asleep, nobody monitors the check-ins, and if a worker stops responding at 3 a.m. it might not be noticed until the day shift walks in.

That is not a technology problem. It is a process problem. Before reaching for an app or a wearable, it is worth asking three questions:

1. Who is responsible for monitoring check-ins right now, at this hour?
2. What happens if a check-in is missed? Is there a written escalation sequence?
3. When was the last time that escalation sequence was tested?

If any of those three questions produces a vague answer, the system is not working, regardless of what the paperwork says.

Building a Check-In System That Holds

A reliable check-in system has four components: a defined interval, a named monitor, a written escalation sequence, and a test record.

Defined interval. The interval should come out of the risk assessment, not out of habit. A fitter doing planned maintenance in a well-lit machine room with a charged phone is a different case from an engineer doing confined space work. The interval for the latter might be ten minutes; the former might be forty-five. Write it down and tie it to the task, not to the person.

Named monitor. Someone specific must be responsible for receiving check-ins at any given time. “The supervisor” is not enough if the supervisor changes mid-shift or is covering three sites. A named person, with a backup named person, and a phone number that is answered.

Written escalation sequence. If a check-in is missed, what happens? Call the worker. If no answer within two minutes, call the backup contact. If no answer within five minutes, call site security or the emergency contact. If still no contact after ten minutes, call the emergency services with the worker’s last known location. Write that sequence down, put it in the hands of the monitor, and test it.

Test record. Run a live test every quarter. Pick a shift, run through the scenario as if a check-in had genuinely been missed, and time each step. Keep a record of what worked and what did not. A system that has never been tested is a system you do not fully understand.

The Records That Back It Up

The risk assessment for each task needs to specify the lone working controls. The check-in log, even if it is just a timestamped message thread, should be kept for at least three years. If an incident does occur, these records are what an HSE inspector will ask for first.

If your site is already working through a structured operational review, lone working usually surfaces as a gap in the accountability section. Night-shift hours routinely carry a disproportionate share of unplanned downtime and near-misses, and running a six-loss review through the losses worksheet gives you something concrete to put in front of management rather than a general complaint about nights.

For sites doing a broader operational audit, the diagnostics tool covers lone worker controls as part of the people and compliance section. It will not write your policy for you, but it will tell you quickly whether the current arrangements would hold up to scrutiny.