The Three Things WHS Software Has to Get Right

Every vendor in this category will show you somewhere between 20 and 40 features, and most of them are real. That is what makes the demo hard. Nothing on the list is obviously wrong, so the decision ends up being made on the screen that looked best.

Three of those features decide whether the system is still in use in eighteen months. The rest are preferences. I sell this software, so treat that as a declared interest, but these are the three I would hold a vendor to if I were buying, us included, and each one has a test you can run inside an hour rather than discover in month four.

Most of a Feature List Is a Preference.

A preference changes how pleasant the system is to use. A requirement decides whether the system gets used at all, or whether it can answer the one question that matters after something has gone wrong.

That distinction is worth making out loud in the room, because it reorders the scoring sheet. Permit workflows, custom fields, and a nicer dashboard are all genuinely useful and none of them will save a rollout that fails on any of the three below.

One: It Has to Be Used by People Who Do Not Work for You.

This is the requirement buyers underweight and the one that ends rollouts. The users who decide whether your WHS system works are largely not your employees. They are the subcontractors, the labour hire crews, and the two-person outfits who turn up for three weeks, and none of them has a reason to log into something you bought.

They are also carrying several of these already. An electrical outfit on eight head contractors’ books is often maintaining eight separate profiles, and lodging the same white card into each of them. None of that time lands on your invoice. It lands on their margin, and it returns to you later as a slower start on site and a price that has absorbed the difference. The good ones have the luxury of choosing whose paperwork they are willing to do.

So the requirement is not that the product has a contractor portal. It is narrower. What does the smallest supplier on your list have to do, on a phone, with nobody helping, and what happens when they will not do it. Ask what share of onboarding the vendor performs rather than your team. Ask the support hours for somebody who is not the vendor’s paying customer. Ask what your administrator can upload for a worker who is never going to do it themselves.

In ComplyFlow a contractor receives an email, creates an account, and accepts or declines the invitation in one pass,¹ and a contractor can share one worker profile and its documents with an external client by link rather than emailing the same records to every client who asks.² That second one matters more than it sounds. It is the difference between a supplier keeping one record and keeping eight, and the supplier is the person whose behaviour you are actually trying to change.

If a vendor’s answer to this is that they will send your suppliers a link, the rollout will stall one tier below your direct contracts, which is where most of the people standing on your sites sit. Workforce compliance that nobody outside the business completes is an empty database with good reporting.

Two: It Has to Produce Evidence, Not a Percentage.

Almost every system in this category can tell you that your workforce is 94% current. No inspector, insurer, or lawyer has ever asked that question.

What they ask is specific and unhelpfully narrow. Was this named person cleared to do this named task, on this named site, on this date. What document was the clearance based on. Who approved it, and when. In 2024, 188 workers in Australia were killed by a traumatic injury, and 2023-24 brought 146,700 serious workers compensation claims involving a week or more of lost time, which Safe Work Australia described as more than 400 a day when it released Key Work Health and Safety Statistics Australia 2025 on 16 October 2025.³ The evidence request is not a paper exercise. It arrives after one of those.

A percentage cannot answer it, because a percentage describes today and the question is about a Tuesday eighteen months ago. What answers it is a record that still holds the documents that were rejected, the ones that expired, and the ones that never arrived, each with the approver’s name against it.

There is a second half to this that buyers skip. An uploaded certificate is a picture of a claim, not proof of one. SafeWork NSW keeps a public register covering high risk work, asbestos, and demolition licences alongside general construction induction cards, and its instruction to employers is plain: check regularly that a licence has not expired, covers the classes the work needs, and carries the right photo and name.⁴ If nobody in your process ever opens a register like that, the system is storing claims and presenting them as evidence.

ComplyFlow’s document report reaches back across the whole life of an account and keeps the rejected, the expired, and the never-supplied alongside the approved, filtered by entity, approver, project, company, and category, and exported to CSV.⁵ The filters are convenience. A rejected document still being there in two years is the part that answers the question. Make the vendor run that request in front of the person who would actually receive it.

Three: It Has to Work at the Gate.

Everything above is worth nothing if the answer cannot reach the boom gate in the time it takes a ute to roll up to it.

The gate is a phone held in one hand before the sun is up, often wet, usually with a queue forming. Anything that asks a supervisor to open a laptop, sign in, and search a list will not survive the second week. In ComplyFlow the check sits on the worker’s own access card as a QR code: any phone camera opens their record, with a green tick when everything assigned to them is current and a red cross when something is outstanding, and the categories, training, and documents behind that answer sitting underneath it.⁶

Then press on the two things a gate demo never covers. What the check does when the network has gone, and who is permitted to wave somebody through anyway, with that override written down against their name. Be precise here, because a mobile app and an app that works offline are different claims and the words get used interchangeably. ComplyFlow’s Inspection app runs a checklist with no signal, holding the checks, photos, and findings on the device until it syncs.⁷ Sign-in at the gate is a separate flow, and if offline sign-in matters at your sites, make every vendor on the list answer that one in writing rather than in a meeting room with good wifi.

The Hour That Settles a Shortlist.

Three requests, and you can make all three in the same meeting.

1. Onboard a two-person subcontractor, live, on a phone, with nobody from the vendor touching it.
2. Produce the evidence that a named person was cleared for a named task on a named site on a named date, including the document it rested on and who approved it.
3. Turn the wifi off, or walk outside, and try to sign somebody in.

The Order These Three Fail In.

They fail in that order and they fail quietly. Adoption goes first, so the record thins out without anybody deciding it should. The evidence gap surfaces second, usually the first time somebody asks for something specific and you find out what is not in there. The gate is the only one you notice on the day, because a person is standing in front of it with a queue behind them.

If you want the same argument at vendor-meeting length, contractor management software: 10 questions and 10 bad answers takes it one question at a time, with the answer to listen out for on each. If you are buying for Australian sites across more than one state, how to choose WHS compliance software in Australia covers the regulator, labour hire, and data questions this post leaves out on purpose. And if you have not yet decided you need to buy anything, when a manual safety management system stops working is the honest version of that question. When you are ready to run the three tests above against something real, book a demo and start with the second one.