One Operator, Two Safety Cases: A Lone-Working Framework for Powered Access

Lone working in powered access is frequently reduced to a rota question: can one operator cover the task, or do we need two? That is the wrong starting point. A single operator in a mobile elevating work platform (MEWP) creates a different safety case from a two-person team, particularly in supervision, communication and rescue. Facilities teams and contractors should treat lone working as a control package to be evidenced, not a headcount to be assumed.

Define the exposure before assessing it

Lone working is not limited to an operator standing alone on a remote roof. It includes any situation where the operator cannot be directly observed by a competent person who can intervene, and where immediate assistance is not available. That can cover overnight works, a contractor working alone in a locked compound, a single operator on a large distribution site, or a short-duration task in a plant room where the only other person is not trained or equipped to help.

The first practical step is to record the actual exposure. Where will the MEWP be set up? Who else will be on site? Can those people reach the operator quickly, and do they know what to do? If the answer depends on a mobile phone signal and a colleague in another building, the assessment should say so plainly. The question is not whether one person is enough, but which safeguards replace the missing second person.

Apply a suitability test, not a default

Lone working should be a deliberate decision for each task. A simple suitability test can be recorded alongside the risk assessment and MEWP selection. It should consider the task, the environment and the operator.

Task factors include complexity, duration, material handling, rigging, and the likelihood of unplanned events. Environment factors include weather exposure, ground conditions, overhead lines, public interface, access and egress, and communications coverage. Operator factors include competence, familiarity with the machine and site, and the ability to summon help and carry out emergency lowering if trained and authorised to do so.

Some activities should trigger a presumption against lone working. Examples include work requiring a second person to manage materials, tasks where the operator cannot maintain effective communication, and work at height where fall arrest may be required. A harness and lanyard do not make lone working acceptable on their own. If the operator could be left suspended and unable to self-rescue, the rescue case must be resolved before the task proceeds.

The output of the test should be a clear record: task, location, hazards, controls, communication method, check-in interval, rescue arrangement and authorisation. If any of those elements cannot be demonstrated, lone working is not suitable for that task.

Design communication and check-in around failure

Communication arrangements are often written as an assumption: mobile phone available, site office contactable. A defensible framework assumes that the first method may fail. Coverage should be verified in the actual work area, not at the site gate. Where signal is unreliable, alternatives such as site radios, a designated telephone line, satellite communication or a physical check by a nominated person should be specified.

Check-in intervals should be proportionate to risk. A short task in a low-risk area may need only a start and finish confirmation. Longer or more complex work may require periodic check-ins at fixed intervals. The important control is the escalation route: who monitors the check-in, what happens if it is missed, and how quickly does that trigger a response? A missed check-in must lead to a defined action, not a note to try again later.

In 2026, telematics and remote monitoring can support lone-working arrangements by providing machine status and location data. They should be treated as supporting evidence, not as a substitute for a named monitor and a clear escalation plan. The same applies to lone-worker alarms and dead-man devices: useful, but only effective if someone is responsible for receiving and acting on the alert.

Confirm rescue availability, not just rescue intent

Rescue is where lone working most often fails. A rescue plan that relies on colleagues who are not on site, or on emergency services arriving within a safe period, needs to be tested rather than assumed. The plan should identify who will perform the rescue, what equipment they will use, how they will access the platform or casualty, and how quickly they can reasonably arrive.

If the rescue depends on the fire and rescue service, the arrangements should be confirmed with the relevant service and recorded. Some services may not have the equipment or training to rescue from a MEWP, and response times vary. If the rescue depends on an on-site team, those team members should be competent and available for the duration of the work. A rescue kit on site without trained people is not a rescue plan.

For facilities teams, this is a reasonable question to put to any contractor proposing lone working: show me the rescue plan, name the rescue team, and confirm their availability for the shift. For contractors, the rescue plan should be written before mobilisation and briefed to the operator. It should also be revisited if the work area, shift pattern or site access changes.

Supervise and review in proportion to risk

Lone working does not mean unsupervised working. Supervision can be remote, periodic or physical, but it must be defined. Site induction, permit arrangements and daily briefings should make clear who is monitoring the work, how contact is maintained and what the operator should do if conditions change. For longer duration work, rotation or periodic physical checks may be more appropriate than continuous remote monitoring.

The assessment should be reviewed when anything material changes: weather, ground conditions, access arrangements, task scope or the availability of the rescue team. A post-task review is also useful. It can confirm whether the communication and check-in arrangements worked in practice and whether the rescue plan remained viable.

Treat lone working as a scope decision

Lone working in powered access can be appropriate, but it should not be the default. It requires a documented suitability decision, a communication and check-in protocol designed around failure, and a rescue plan that is available in practice. Facilities teams should expect to see that evidence in the contractor's paperwork, and contractors should be prepared to explain it. The single operator is not the control; the framework around that operator is.