This article sits behind the "See how Worx manages this" link on the Psychosocial Self-Check. If you haven't run the self-check yet, start there — it takes about five minutes and scores you against the 17 recognised psychosocial hazards.

So you've done the self-check. Somewhere across those 17 hazards, you marked "Not in place" or "Unsure" — most operators do. That's not the problem. The problem is what usually happens next: someone writes a policy, files it, and the gap stays exactly where it was.

The regulator doesn't want your policy. The regulator wants to see the loop: you identified the hazard, you put a control in place, you reviewed it when things changed, and you can prove all of it — across every site, every crew, on an ongoing basis.

That loop is the same loop you already run for physical risk. Psychosocial hazards aren't a different discipline. They're the same discipline pointed at different hazards. And the same system runs both.

Here's how that works in Worx, theme by theme — including the parts where Worx deliberately stays out of it, because some of these hazards can't be fixed by software, and we're not going to pretend otherwise.

The loop, in practice

Before the themes, the mechanics. Every hazard below runs through the same four moves in Worx:

Raise it as an issue. Anyone on site can create an issue and categorise it as psychosocial — from their phone, at the moment they see it. It's time-stamped, attached to the site, and visible to the people who need to act. Not an email that dies in an inbox. Not a comment in a toolbox talk that nobody wrote down.

Assign the task. Every issue gets an owner and a due date. Worx chases the owner with automated reminders until it's closed — and nothing closes without a record of what was done. That's the difference between "we discussed it" and "we managed it."

Run the checklist. Pre-start checklists and electronic forms put the question in front of your crews on a schedule — a fatigue check at pre-start, a workload review when scope changes, a confidential reporting form that's always one tap away. If the check isn't built into the routine, it doesn't happen.

Report the incident. When something does happen — an aggressive client, a bullying complaint, a traumatic event — it's captured at the moment, not reconstructed three days later. Notifications go to the right people immediately, and the response is documented end to end.

Underneath all four sits the register and the audit trail: every psychosocial hazard recorded with its control and a review date, and a time-stamped history of every action. When the regulator asks "show me how you're managing this," you open the system. You don't assemble a binder.

Theme 1 — How the work is designed

Job demands · Low job control · Lack of role clarity · Fatigue · Low or monotonous job demands

The strongest fit here is role clarity — and it's where most sites actually bleed. Responsibilities blur fastest across the contractor boundary: two crews, one task, nobody sure who owns the exclusion zone. Worx holds the who-is-who — roles, responsibilities and reporting lines for every worker and contractor on your books — and your SWMS pin accountability to the task. Inductions make sure every person knew what was expected before they set foot on site, and the records prove it.

Fatigue gets a daily control, not an annual policy: build a fit-for-work check into your pre-start checklist, and every shift starts with the question asked and the answer recorded. When a crew flags they're running hot, that's a psychosocial issue raised on the spot — assigned, tracked, closed.

Job demands belong on your risk register with a review date, so high-demand periods get reassessed when scope changes instead of when someone burns out. Worx hosts the review, holds the record, and reminds you when the date comes around.

Where this needs to be managed instead: Worx does not write your rosters, set your workloads, or decide how much say a crew gets in how a task is sequenced. Low job control and monotonous work are work-design decisions made by the people who plan the work. What Worx does is document that you consulted your crews and reviewed the design — which is exactly the evidence the regulator asks for — but the decision itself happens in your planning room, not in software.

Theme 2 — Support and fairness

Poor support · Low recognition and reward · Poor organisational justice · Poor organisational change management · Job and employment insecurity

This theme is about process — fair, consistent, documented process. Which is squarely what a system does well.

Organisational justice lives or dies on consistency. A grievance handled one way in March and another way in September is how trust dies on a site. In Worx, the process is a form: raised the same way every time, routed the same way every time, with a time-stamped trail proving the rules were applied to everyone equally.

Change management is the same story run earlier. Consultation forms go out before the roster changes or the restructure lands — and the record shows workers were heard, not just informed. The transition itself is the recognised risk, and the consultation evidence is the control.

Poor support is partly a channel problem: workers need a used, trusted way to flag that they don't have the tools, information or back-up the job needs. A reporting form gives them one. The audit trail closes the loop — people can see their request was actioned, not absorbed into silence.

Where this needs to be managed instead: Worx has no feature for recognition and reward, and we won't invent one in the marketing. How you recognise effort, how pay and progression are seen to be fair, and how much certainty you give casual and contract workers about future work — those are leadership and commercial decisions. The honest claim is narrow: Worx can record that you've reviewed these, and hold the review date. The substance is yours.

Theme 3 — Relationships and conduct

Poor workplace relationships and conflict · Bullying · Harassment, including sexual harassment · Violence and aggression

This is where the system earns its keep — because the law has moved, and a complaints process is no longer enough.

The positive duty on sexual harassment requires you to prevent it before it happens, proactively. In Worx that's three controls working together. Training through the LMS sets the standard of behaviour for every person on site — employee or contractor — before they start, with a record of who completed it and when. Confidential reporting forms give workers a safe path to raise it, including a path that bypasses the person involved. And when a report lands, the incident workflow makes sure it's acted on, by the right person, with every step documented.

Bullying runs the same playbook: a known standard everyone is trained on, more than one way to report, and an act-and-document response. Violence and aggression adds the SWMS layer — design the work to reduce exposure, set procedures and back-up for high-risk interactions, and capture every incident and near miss so the pattern shows up before the serious one does.

Prevention, reporting, evidence. That's not a poster in the lunchroom. That's a system doing its job.

Theme 4 — Environment and exposure

Remote or isolated work · Traumatic events and exposure · Poor physical working environment

Remote and isolated work is the most concrete fit in the whole assessment. Site check-in gives you a real-time record of who is on site, right now — which means you also know who's out there alone. Pair it with a scheduled check-in routine and an escalation form, and "how does help reach someone who can't call for it" stops being a hope and becomes a procedure.

Traumatic exposure is about being ready before it happens. Identify the exposed roles on your register, train people on the support pathway in advance through the LMS — so support is known, not improvised — and when an incident occurs, the report can trigger that pathway automatically.

Poor physical environment is the hazard most operators already manage without realising it counts twice. The noise, heat, dust and cramped conditions that wear people down psychologically are controlled with the tools you already run in Worx: SWMS for the work design, inspection checklists for the conditions, and the asset register keeping the plant that causes the problem serviced and tracked.

What this looks like on Monday

Run the self-check if you haven't. Take your "Not in place" and "Unsure" answers and put each one on the register with a control and a review date. Build the fatigue check into your pre-starts. Stand up a confidential reporting form. Raise your first psychosocial issue and assign it to someone with a due date.

Book a demo and we'll walk you through the psychosocial loop on your own sites — including the parts Worx won't do for you, and where they belong instead.

This article is general guidance, not legal advice. For obligations specific to your state and circumstances, refer to the relevant WHS regulator and Code of Practice.