What Happens When WHS Systems Look Compliant but Aren’t?

5 min read

Most organisations don’t lack workplace health and safety documentation. Policies exist, procedures are written, and WHS risk assessments are completed often with good intent and in many cases, aligned to recognised WHS standards and guidance. I’ve sat in plenty of meetings and on paper it can look reassuring.

On paper, this creates confidence and suggests alignment with the Work Health and Safety Act 2011 (NSW) and the Work Health and Safety Regulation 2025 (NSW).

When the system is tested in real time

It suggests that risks have been considered and controls have been implemented. However, documentation is only one part of the system. The real test is whether those controls show up operationally, on site where decisions get made quickly and the job doesn’t pause so someone can reference a procedure.

The more relevant question is what happens when systems are tested, not during an audit or a scheduled review, but in the moment when work is being performed under pressure, variability and real world conditions. That’s the moment I tend to get called in when the plan meets the pace of operations.

Risk assessments intended work vs actual work

Risk assessments are typically completed at a point in time and reflect how work is intended to be performed under assumed conditions, with expected controls in place. In the real world, I’ll often read a procedure or similar that describes a calm, uninterrupted task, then watch the same task happen between phone calls, competing priorities, and a queue of work.

Over time, work rarely remains static. Operational demands shift, time pressures increase, workforce capability varies, equipment changes and informal practices develop. The task evolves, but the WHS risk assessment often does not.

In practice, this can leave controls that are no longer relevant, hazards that are no longer identified, and workers developing informal methods to get the job done safely, or at least efficiently.

For example, a control might assume a two person lift, but the roster changes and the work continue with one person and a workaround. These informal methods aren’t inherently unsafe, but they’re often unrecognised by the system. From experience, WHS risk assessments frequently describe intended work rather than actual work as performed.

Procedures technically correct, operationally absent

A similar pattern shows up with procedures. It’s not uncommon for organisations to have well developed documents that align with WHS legislative requirements and codes of practice, and in many cases, they are technically sound. I’ve reviewed procedures that read beautifully, right up until you ask someone in the workplace to walk you through how they actually do the job.

The issue is rarely the quality of the document itself, it’s whether it is embedded into everyday operations. In practice, employees may be unaware of procedures relevant to their role, training may be informal or inconsistently applied and supervisors may rely on experience rather than documented controls. If the procedure lives on a shared drive but not in pre-starts, take fives, toolbox talks or similar, it won’t shape behaviour.

Procedures often become reference documents that are only revisited after an issue arises, rather than tools that actively guide work. Documentation alone does not demonstrate compliance, implementation does. Implementation is often the hardest to undertake and get right.

The compliance gap you can’t see in a folder

Across these scenarios, a consistent gap emerges between the documented system and the reality of how work is performed. Most organisations have the foundational elements in place, WHS risk assessments, procedures and a general awareness of safety requirements. The gap usually shows up when you step out from behind the desk and observe the work for an hour, then compare it to what the documents say should be happening.

However, the system may not reflect actual work practices, may be applied inconsistently across teams or locations, and may not be reviewed as conditions change. This misalignment isn’t always visible in documentation, but it becomes obvious in practice, particularly when systems are tested under real conditions.

In practical terms, many WHS systems aren’t ineffective because they don’t exist. They’re ineffective because they’re not aligned to real work, not embedded in operations and not actively reviewed. When I’m at a workplace, the fastest indicator is simple, can a supervisor and a worker both describe the same controls the paperwork describes?

From a compliance perspective, this distinction is critical. WHS obligations aren’t satisfied by the presence of documentation alone, they require that risks are identified, assessed, controlled, and reviewed in a way that reflects actual conditions in the workplace and that you can demonstrate this through training, supervision, verification, and review.

A quick ‘proof it’s working’ check

• Walk the task - pick a high-risk job and observe it end to end. Compare what you see to the WHS risk assessment.

• Ask two people - ask a worker and a supervisor what the key controls are. If you get two different answers, the system isn’t embedded.

• Check currency- when did the WHS risk assessment last change because the work changed, not because the calendar said annual review?

• Verify training - can people show they’ve been trained and deemed competent, or is it “I got shown once”?

• Test retrieval - can the right document for example in an infrequent high-risk work activity be found in a matter of minutes where the work happens?

When it matters, can you show it worked?

WHS systems are rarely tested under ideal circumstances. They’re tested when something goes wrong, when an incident occurs, or when a WHS regulator asks what was in place at the time. At that point, the question is no longer whether a system exists, but whether you can demonstrate it was working in practice.

In my experience, the organisations that do well aren’t the ones with the most documents, they’re the ones that routinely verify work as done, listen to the people doing it through consultation and update controls before they become outdated.

If you want to know whether your WHS system is genuinely working (not just well documented), let’s pressure test your high-risk tasks. I’ll walk the job with your team, compare work as imagined to work as done, and give you a short, practical list of fixes you can implement immediately. Get in touch to book a meeting.

By Darren Lane - WHS Compliance Specialist & Lead Auditor

Managing Director, Certified ISO 45001 Lead Auditor, Bachelor of Occupational Health and Safety.

Darren Lane is the Lead Auditor at Lane Safety Systems with over 20 + years of experience in NSW WHS compliance and ISO 45001 systems, with a strong focus on managing WHS risk for clients.

With a background as a former WHS Inspector, he delivers clear, practical guidance aligned with WHS legislative requirements and regulatory expectations.