The Psychosocial Compliance Checklist for Blue-Collar Employers — What You Need in Place Before an Inspector Knocks

SafeWork NSW just launched its largest ever psychosocial compliance operation. If an inspector walked onto your site tomorrow, could you produce what they’re looking for?

On 9 October 2026, SafeWork NSW announced its biggest psychosocial compliance operation to date. This was not a media statement. It was an operational deployment — inspectors visiting workplaces across NSW, asking specific questions, and looking for specific evidence.

It followed a smaller operation in May and June 2026, where inspectors visited more than 200 workplaces and issued more than 80 improvement notices on psychosocial risk management. One in five of all SafeWork NSW service requests now raises psychosocial harm as the issue.

It followed a smaller operation in May and June, where inspectors visited more than 200 workplaces and issued more than 80 improvement notices on psychosocial risk management. One in five of all SafeWork NSW service requests now raises psychosocial harm as the issue.

Over the past few months, this blog series has covered the regulatory framework, the Code of Practice, what claims cost, what documentation looks like, what supervisors need, and what “reasonably practicable” actually requires. This article pulls all of it together into a practical checklist any blue-collar employer can use to work out where they stand right now.

What inspectors actually ask

SafeWork NSW’s approach is not a paper audit. Inspectors visit the worksite. They speak to workers and health and safety representatives separately from management. And they ask questions that test whether the system is real or whether it exists only in a policy folder.

Based on published guidance and reports from recent inspections, these are the kinds of questions inspectors ask:

To management: How do you identify psychosocial hazards on this worksite? What controls do you have in place? How do you know those controls are working? Can you show me the records?

To workers and HSRs, separately: Do you know what a psychosocial hazard is? Do you know how to report one? Has your employer consulted you about psychosocial risks? What happened the last time someone raised a concern?

That second set of questions is the one most employers are not prepared for. It does not matter what the policy says if the workers on site cannot describe how the system works in practice — or if their account does not match what management has described.

The checklist

Here is what an inspector is looking for — and what every blue-collar employer should be able to produce or demonstrate right now.

1. A psychosocial hazard register that links identified hazards to specific controls.

Not a generic risk register with “psychosocial” added as a line item. A register that names the specific psychosocial hazards present on your worksite — workload pressure, low job control, poor supervisor support, conflict, fatigue, isolation — and maps each one to the specific control measures you have implemented.

If your risk register only covers physical hazards, you have a gap. If it lists “psychosocial hazards” as a single line with “EAP” as the control, you have a gap. The register needs to be specific to your workplace, built in consultation with your workers, and reviewed regularly.

2. Evidence that you applied the hierarchy of controls.

The NSW WHS Regulation 2025 made this explicit for psychosocial hazards: employers must consider the hierarchy of controls, starting with elimination or redesign of the work, before falling back to administrative controls like training and awareness programs.

If training is your primary response to psychosocial hazards, an inspector will ask what structural changes you considered first. Did you look at workload? Rostering? Supervision ratios? Job design? The hierarchy requires you to work through higher-order controls before relying on policies, EAPs, and awareness campaigns — which sit at the bottom.

3. Worker consultation records.

The Code of Practice requires genuine, ongoing consultation with workers about psychosocial risks. An annual engagement survey does not meet this requirement. A toolbox talk sign-off sheet with no evidence of what was discussed does not meet it either.

What does meet it is documented evidence of regular, meaningful consultation — records showing that workers were asked about psychosocial hazards, that their input was captured, and that the employer responded to what they raised. Daily check-in data, completed by workers themselves as part of the shift, is exactly this kind of evidence. Each completed check-in is a timestamped record of genuine worker consultation.

4. A documented flag or escalation process.

When a worker raises a psychosocial concern — bullying, harassment, excessive workload, fatigue, conflict — what happens? Is there a documented process for how concerns are received, recorded, escalated, and resolved? Can you show the trail from the moment a concern was raised to the outcome?

Most small blue-collar employers have no formal process for psychosocial concerns. Physical safety has incident reports, hazard forms, and investigation protocols. Psychosocial safety has nothing — and that nothing is exactly what an inspector will find.

5. Training records for supervisors and managers.

Supervisors need to understand what psychosocial hazards are, how to recognise them in their crew, and what to do when a concern arises. Managers need to understand their obligations under the Code of Practice and the WHS Act. An inspector will ask what training has been delivered, when, and to whom — and whether that training covered psychosocial hazards specifically, not just physical safety.

6. Evidence of ongoing review.

The Code of Practice does not just require employers to set up controls. It requires them to review whether those controls are working. A control implemented in January and never reviewed is not a compliant control. An inspector will ask when your psychosocial risk management controls were last reviewed, what the review found, and what changes were made as a result.

This is where most employers fall down. Setting up a system is one thing. Demonstrating that the system is monitored, reviewed, and improved over time is another — and it is the one the Code specifically requires.

7. Evidence that the system runs every day — not just when someone remembers.

This is the difference between a compliant system and a policy folder. A compliant system generates evidence continuously. It does not depend on a supervisor remembering to run a wellbeing check or a manager scheduling a quarterly review. It runs as part of the daily rhythm of work, producing timestamped, documented records that prove the system was operating on any given day an inspector asks about.

A policy document proves someone wrote a policy. Daily check-in records prove the system was running. When an inspector asks “what were you doing to manage psychosocial risk on your site last Tuesday?” — the answer needs to be in the data, not in someone’s memory.

Where most blue-collar employers stand right now

Be honest with yourself as you read through that checklist. Most small-to-medium blue-collar employers — civil contractors, earthmoving crews, trade businesses — can produce one or two of those items. They might have a risk register that includes physical hazards. They might have training records for supervisor inductions. They might have a policy document.

But a psychosocial hazard register linked to specific controls? Documented worker consultation records from the past month? A flag escalation process with a documented trail? Evidence that the system runs every shift? Evidence of ongoing review?

For most blue-collar employers, the honest answer to those questions is no. And that honest answer is exactly what SafeWork NSW’s compliance operation is designed to find.

The good news — this is solvable

The gap between where most employers are and where they need to be is not a gap that requires enterprise-level resources to close. It requires a system. One that runs daily, generates documentation automatically, and is proportionate to the size of the business.

For a 12-person crew, closing this gap does not mean hiring a compliance officer or purchasing an enterprise platform. It means implementing a system that checks in with workers every shift, captures concerns through a structured flag process, documents the consultation and the response, and produces the timestamped evidence trail that answers every question on the checklist above.

That is what SOV·32 is built to do. Every item on that checklist — hazard identification through daily data, worker consultation through shift check-ins, a flag escalation process with a documented trail, evidence that the system runs every day, and review capability through ongoing data — is built into the daily rhythm of the platform. Not as a separate compliance layer. As a byproduct of the same daily engagement that gives workers a private, low-friction way to check in and gives supervisors the data to act early.

The checklist above is not aspirational. It is what the Code of Practice requires right now, what SafeWork NSW is actively testing, and what SOV·32 is designed to produce from day one.

SOV·32 enters its first live beta in mid-November 2026, with general availability early 2027. Businesses can register their interest now to secure early access and priority onboarding. Book a demo at sovsystems.com.au.