Lone Worker Safety Australia: PCBU Guide 2026

If you're signing off SWMS, approving after-hours maintenance, or sending one technician to a remote corner of a site, lone worker safety is already your problem. In construction, manufacturing, and industrial services, the failure point usually isn't that nobody knew there was risk. It's that the risk assessment stayed broad, while the job on the ground needed a hard rule about what cannot be done alone.

Generic lone work controls break down under production pressure. Supervisors improvise. Workers back themselves. The permit says "controls in place", but nobody has written the short prohibited solo tasks list that removes the argument at the point of work.

Table of Contents

• Defining Your Duty of Care for Lone Workers
  • What duty of care looks like in practice
  • Where businesses usually get it wrong
• The Full Spectrum of Lone Worker Risks
  • Physical hazards that escalate when nobody is nearby
  • Psychosocial hazards are not secondary
  • The control implication
• Your Legal Obligations Under Australian WHS Law
  • What Regulation 48 means on site
  • Reasonably practicable means context matters
  • State application still matters
  • Minimum legal standard for PCBUs
• Conducting a Defensible Lone Worker Risk Assessment
  • Start with the real work, not the policy
  • Build the prohibited solo tasks list
  • Document the decision trail
• Practical Control Measures and Emergency Procedures
  • Communication controls that actually work
  • Check-ins should be risk-based
  • Emergency procedures need named actions
  • Construction and manufacturing examples
  • Training is part of the control, not an add-on
• Evaluating Lone Worker Safety Technology
  • Devices, apps, and platforms are not the same thing
  • What to test before rollout
  • What doesn't work
• Frequently Asked Questions on Lone Worker Safety

Defining Your Duty of Care for Lone Workers

A PCBU doesn't get to treat lone work as an informal staffing decision. Under Australian WHS law, it's a duty of care issue that sits squarely with the business, the officers who govern it, and the line leaders who authorise how work gets done.

The starting point is simple. If a worker is by themselves with limited support arrangements, the business must assume delayed assistance, reduced supervision, and higher consequence if something goes wrong. That's the practical meaning of lone worker safety in Australia.

The injury pattern matters. In Australia, more than 80% of serious compensation claims for lone workers are directly linked to body stressing, slips, trips and falls, being struck by objects, or mental stress, based on Safe Work Australia data discussed here. That tells you where to look first. Not at exotic scenarios. At common tasks done without backup.

What duty of care looks like in practice

For most PCBUs, duty of care for lone workers means three things.

• You identify where lone work takes place. Not just field service. Also early starts, shutdown work, weekend callouts, cleaning, inspection rounds, testing, security patrols, and one-person warehouse tasks.
• You decide what level of lone work is acceptable. Some tasks can proceed with controls. Others need a second person, a permit condition, or supervisor approval.
• You make the system auditable. If an inspector asks how you manage isolated work, "we tell people to call in" won't hold up.

Practical rule: If the job depends on a worker rescuing themselves after a fall, exposure, medical event, or violent incident, your control set is already weak.

There's also an administrative reality here. Lone work failures often sit beside other compliance gaps such as contractor control, induction records, fatigue oversight, and supervision. If you're trying to tighten those systems at the same time, it helps to automate employment compliance with Dynamics 365 so worker status, training, and accountability don't live in disconnected files.

Where businesses usually get it wrong

The weak point isn't usually policy. It's permission.

A manager approves "routine maintenance". A supervisor assumes the worker has reception. The worker assumes the task is quick. No one stops to ask whether the task should be prohibited for solo work in the first place. That's where serious harm starts.

The Full Spectrum of Lone Worker Risks

Most lone work controls focus on physical injury first. That's necessary, but it isn't enough. Safe Work Australia confirms that remote or isolated work involves both physical and psychosocial hazards, with risks made worse by poor access to emergency help in its remote and isolated work overview.

That matters because a legally sound system has to address both. If your process only deals with falls, entanglement, vehicles, and plant, but ignores stress, fatigue, isolation, and aggression, it's incomplete.

Physical hazards that escalate when nobody is nearby

In construction and industrial settings, lone work changes the consequence profile of ordinary hazards.

• Falls and slips: A fall from a platform, stair, ladder, or uneven ground becomes more serious when there's no immediate first aid or rescue.
• Plant and equipment incidents: Jam clearing, isolations, tool kickback, and moving plant interactions can leave a worker unable to call for help.
• Violence and aggression: Service technicians, delivery staff, security workers, and anyone entering uncontrolled environments carry added exposure when no one else is present.
• Medical events: Heat illness, cardiac events, diabetic episodes, seizures, and respiratory distress can become unwitnessed emergencies.

A lot of these aren't unusual jobs. They're ordinary jobs with no immediate support.

Psychosocial hazards are not secondary

Isolation affects judgement. It also affects reporting behaviour. Workers on their own are more likely to push through discomfort, delay escalation, or make a bad call because they don't want to stop the job.

Typical psychosocial exposures in lone work include:

• Isolation and anxiety about whether help will arrive
• Fatigue during long shifts, travel-heavy work, or out-of-hours callouts
• Stress and burnout where workers carry responsibility without local support
• Harassment or bullying risks in remote teams or one-to-one work situations

A lone worker can be physically safe on paper and still be operating in a psychosocially unsafe system.

The control implication

If you're reviewing lone worker safety in Australia, test your system against both hazard classes.

If your controls don't cover both the body and the mind, the system won't hold when conditions deteriorate.

Your Legal Obligations Under Australian WHS Law

The legal test is not whether you meant well. It's whether the PCBU identified the risk, assessed it properly, and put in controls in place that were reasonably practicable for the work.

Under Regulation 48 of the Model Work Health and Safety Act 2011, Australian employers have a strict duty to manage risks associated with remote or isolated work, including reliable communication systems and emergency procedures for lone workers, as outlined in this summary of working alone legislation in Australia.

What Regulation 48 means on site

Strip away the legal wording and the obligation is fairly direct. If someone is working remotely or in isolation, you must control the risk created by that isolation. In practice, that means lone work can't be approved without a workable method for contact and a clear emergency response.

That usually requires:

• A defined risk assessment for the task, location, timing, and worker capability
• A reliable communication method that suits the environment
• An emergency response procedure that doesn't depend on guesswork
• A contact regime so missed check-ins trigger action
• Training and supervision so workers know what to do and supervisors know when to intervene

The duty isn't satisfied by handing someone a phone if the phone won't work in the area. It isn't satisfied by writing "call supervisor if needed" if the supervisor doesn't know the worker's route, hazards, or expected finish time.

Reasonably practicable means context matters

Reasonably practicable isn't a loophole. It means the control level must match the risk profile.

For a low-complexity task in a controlled warehouse, scheduled contact and local supervision may be enough. For after-hours plant maintenance, remote inspection work, or isolated construction tasks, you'll usually need stronger controls such as exclusion of solo work, duress capability, location visibility, and specific emergency escalation.

A useful reference point for duty holders is this guide on WHS duties of a person conducting a business or undertaking, especially when you're mapping officer due diligence to day-to-day supervision.

Legal view: Lone work is not a separate side issue. It sits inside the primary duty to provide and maintain a work environment without risks to health and safety so far as is reasonably practicable.

State application still matters

Most Australian jurisdictions align broadly with the model WHS framework, but enforcement language, regulator guidance, and approved codes can vary. That affects how you document controls, train workers, and justify the decision to allow solo work.

For example, one regulator may focus heavily on psychosocial risk integration, while another will look closely at emergency communication and field supervision arrangements. Good practice is to build a company standard that meets the highest internal requirement, then check any state-specific guidance for the sites you operate.

Minimum legal standard for PCBUs

If your lone worker system cannot answer these questions clearly, it's exposed:

1. Who is working alone and when
2. Which tasks are allowed solo and which are not
3. How the worker gets help
4. Who acts if contact is lost
5. How the business proves workers were trained and monitored

That's the baseline. Anything less leaves too much to individual judgement.

Conducting a Defensible Lone Worker Risk Assessment

Most lone worker risk assessments fail because they stay generic. They identify hazards, assign a rating, and list broad controls, but they don't resolve the decision that matters most. Can this task be done alone, yes or no?

That's where a prohibited solo tasks list is stronger than a standard matrix. It removes interpretation at the point of work.

Recent data shows 40% of fatal injuries in Australia's construction sector occurred during tasks prohibited for lone work but performed alone due to production pressure, while 60% of employers admit they lack a clear prohibited tasks list, according to EcoOnline's analysis of high-risk lone work. For construction and manufacturing leaders, that's the warning sign. The risk assessment document isn't enough if the frontline rule is still negotiable.

Start with the real work, not the policy

A defensible assessment looks at actual operating conditions:

• Task conditions: energy sources, height, moving plant, chemicals, atmosphere, manual handling, violence exposure
• Work environment: noise, lighting, weather, remoteness, access, egress, mobile coverage
• Worker factors: competence, fatigue, medical issues, experience, language, familiarity with the site
• Support lag: time to contact, time to locate, time to physically reach the worker

If you only assess the task and ignore support lag, you understate the consequence of lone work.

Build the prohibited solo tasks list

This is the practical control many businesses skip. Don't bury it in a long procedure. Put it in a short list that supervisors can use under pressure.

Examples commonly considered for prohibition in construction and industrial work include:

• Confined space entry
• Live electrical fault-finding or work near exposed energised parts
• Work at height where rescue can't be immediate
• Breaking containment on hazardous systems
• Hot work in isolated or poorly supervised areas
• Tasks with credible violence exposure

Your list must reflect your operation. A manufacturing site after hours has different red lines from a civil crew in a remote corridor.

If a task would be stopped immediately after an incident because "no one should have been doing that alone", it belongs on the prohibited list now.

Document the decision trail

A regulator, client, or insurer won't be impressed by a neat template if the logic is weak. Record why the task is allowed solo, what controls make that acceptable, and what conditions cancel that approval.

Use a short decision table.

For teams that need a stronger template, this guide on how to do a risk assessment is useful because it helps turn a broad hazard review into a documented decision process.

Practical Control Measures and Emergency Procedures

Once you've decided what can and can't be done alone, controls need to be operational. Not theoretical. The best lone worker systems use a mix of engineering, administrative rules, and emergency arrangements that are easy for supervisors to apply on a bad day.

SafeWork NSW treats remote or isolated work as a psychosocial hazard and points PCBUs toward controls such as buddy systems, automated inspection tools, satellite tracking, and personal duress alarms that activate on emergency or lack of activity in its guidance on remote and isolated work.

Communication controls that actually work

The communication method has to match the environment. That's the first test.

A mobile phone may be acceptable in metro service work with reliable coverage. It isn't enough for a worker moving through dead zones, plant rooms, basements, tunnels, or remote corridors. In those conditions, you need a communication setup the worker can use under stress.

Good practice usually includes:

• Primary communication: phone, radio, satellite device, or other approved channel
• Backup communication: second method if the first fails
• Location clarity: the business knows exactly where the worker is meant to be
• Duress method: a fast way to trigger help without a long explanation

Check-ins should be risk-based

Check-in frequency should reflect task risk, not managerial preference.

For a low-risk, short-duration task in a controlled area, start and finish confirmation may be enough. For a lone maintenance fitter working after hours in a live plant environment, you need tighter intervals and clear escalation if contact is missed.

A workable check-in process answers four points:

1. When the worker must check in
2. Who receives the check-in
3. How long before it is treated as missed
4. What actions follow each failed contact attempt

Site test: Ask the after-hours supervisor what happens after a missed check-in at 9:40 pm. If the answer starts with "it depends", tighten the procedure.

Emergency procedures need named actions

Emergency response plans often fail because they state intent rather than action. "Emergency services will be contacted if required" isn't a procedure.

A usable lone worker emergency plan should set out:

• Immediate triggers such as panic alert, no-motion alert, missed check-in, violent threat, injury report
• First actions by supervisor or monitoring contact
• Escalation contacts in order
• Worker location method including route, GPS, work area, and site access details
• Site-specific response issues such as locked gates, permit areas, plant shutdown needs, first aid equipment, or confined access
• Handover process when emergency services or site response arrives

Construction and manufacturing examples

In construction, lone work needs to be visible in the SWMS and permit interfaces. If a task is approved for solo work, the SWMS should state the communication method, supervision level, exclusion conditions, and emergency response. If the task isn't acceptable alone, write that directly rather than relying on general wording.

In manufacturing, pay attention to after-hours patterns. Lone operators, maintenance staff, cleaners, and contractors often work around energised systems, forklifts, and isolated plant areas when supervision is thinnest. That's where simple controls make a difference:

• Restricted areas: some plant rooms or roof spaces require a second person
• Isolation verification: certain troubleshooting tasks cannot proceed solo
• Access logging: every after-hours entrant is logged with expected finish time
• Welfare checks: supervisor or control room follows a timed contact schedule

Training is part of the control, not an add-on

Workers need more than policy awareness. They need to know how to use devices, when to stop work, when to escalate, and what conditions cancel solo work approval.

Supervisors need separate training. Many systems fail because workers know the rule, but supervisors still wave jobs through under schedule pressure. If you want consistency, train the people who grant permission, not just the people doing the task.

Evaluating Lone Worker Safety Technology

Technology helps when it closes a real operational gap. It doesn't help when it's bought as a badge of compliance and then forced onto work that has poor coverage, weak procedures, or no response discipline behind it.

In Australian workplaces, rugged devices or BYO smartphones can trigger emergency alerts instantly, and smartphone users can view colleague locations and stream live video, according to CSE Crosscom's overview of lone worker monitoring. Those capabilities are useful, but only if they fit the risk profile and the response model you've already defined.

Devices, apps, and platforms are not the same thing

A lot of procurement decisions go wrong because these categories get mixed together.

Dedicated duress devices

These suit harsh environments where ruggedness, simple operation, and battery reliability matter more than broad functionality.

Best fit: construction, field utilities, plant maintenance, remote work
Trade-off: another device to issue, charge, inspect, and replace

Smartphone-based apps

These work well where staff already carry a phone and the environment supports it. They can support alerts, check-ins, location sharing, and in some cases live video.

Best fit: service work, inspections, mobile supervisors, lower-complexity field tasks
Trade-off: battery life, durability, worker acceptance, and inconsistent coverage

Integrated safety platforms

These pull together alerts, locations, incident records, task controls, and response workflows into one view. That's often where larger or multi-site businesses get more value, because isolated events no longer sit in separate systems.

If you're comparing options, look at the operational side before the feature list.

What to test before rollout

Don't start with a vendor demo. Start with failure points.

• Coverage reality: test the actual work areas, not the office.
• Battery behaviour: check full shift performance, especially on long callouts.
• Alert path: confirm who gets the alert, how it's acknowledged, and what happens next.
• Worker usability: if activation is awkward with gloves, noise, or stress, adoption will drop.
• Data handling: keep location and monitoring rules proportionate and clearly communicated.

For businesses reviewing response pathways as part of this setup, Hosted Telecommunications routing expertise is useful background when you're thinking about how emergency or escalation calls should reach the right person without delay.

If you're assessing software options specifically, a lone worker safety app should be judged on control effectiveness, not just the interface. The key question is whether it helps your supervisors know who is alone, where they are, what they're doing, and what action is required when contact is lost.

What doesn't work

Technology won't fix:

• a missing prohibited solo tasks list
• weak supervisor decision-making
• poor emergency access planning
• untrained workers
• a culture where missed check-ins are treated casually

Those are management problems first. Software only helps once the rule set is clear.

Frequently Asked Questions on Lone Worker Safety

Managers usually don't struggle with the concept of lone work. They struggle with edge cases. Contractor attendance, worker pushback, and the difference between a buddy system and a digital check-in are where decisions get messy.

A useful external reference for product-level details is SafePing's frequently asked questions, especially if you're comparing how monitoring tools handle alerts and user workflows. For policy and compliance, keep your own internal standard tighter than the device documentation.

The strongest approach is usually the least ambiguous one. Workers know which tasks are prohibited alone. Supervisors know when they can't approve an exception. The emergency path is written, tested, and understood.

If your lone work controls still rely on broad risk assessments, verbal check-ins, and supervisor discretion, it's worth tightening the system before the next after-hours job or remote callout. Safety Space gives H&S and operations teams one place to manage lone worker processes, records, alerts, and site compliance without chasing paper, spreadsheets, and disconnected tools.