How to Choose Construction Safety Management Software

A construction safety software shortlist is usually assembled by three people who want different things: a safety manager, a procurement lead, and someone from the project side whose brief is to make sure this does not turn into another system nobody opens. I am in the room for that argument often enough to know the questions that decide the outcome are rarely the ones on the shortlist spreadsheet.

So this is how I would choose, including the parts that do not help me sell anything. What we build for construction is on its own page; this is the buyer’s version.

The stakes are not abstract. Construction recorded 37 worker deaths in 2024, 20% of the 188 across all Australian industries, and 17,600 serious workers’ compensation claims in 2023-24, 12% of the national total, at a median of 8.4 weeks of time lost for each one.⁴

What Construction Changes About the Requirement.

A generic WHS platform is built for a workforce you employ, on a site you control, doing work that looks much the same in March as it did in February. Construction breaks all three assumptions.

Your workforce changes weekly and most of it is not yours. A head contractor carries subcontractors several tiers deep and is accountable for people it never engaged directly. Australian WHS law is blunt about what that means: a duty cannot be transferred to another person, and more than one person can concurrently have the same duty.¹ The subcontract does not move the obligation. It only decides who you argue with afterwards.

The paperwork is different too. There are 18 categories of high risk construction work, and each one needs a safe work method statement before the work starts: a risk of falling more than 2 metres, a trench deeper than 1.5 metres, work near energised electrical services, tilt-up or precast concrete, and any area where powered mobile plant is moving.² That last category covers most live sites on most days, which is why SWMS volume here is unlike anything a generic platform is sized for.

Induction is two things, not one. Every worker needs general construction induction training, the white card, before carrying out construction work at all, and needs it again if they trained more than two years ago and have not done construction work since.² On top of that sits workplace specific induction, delivered by whoever has management or control of that particular site.³ Per site, not per company. A system that holds one induction record per contractor business has already missed the point.

And above AU$250,000 of construction work the job becomes a construction project, which must have a principal contractor, and only one at a time.³ That role carries a written WHS management plan prepared before work starts, naming the people with health and safety responsibilities, the consultation arrangements between every business on site, the site-specific rules, and the arrangements for collecting and reviewing SWMS.⁶ Plant that moves between your sites moves between those plans with it.

The Requirements That Actually Decide It.

Every vendor ticks every box on a feature list, so score the seven below instead, and ask the question underneath each one in the demo. The wider version of this list, for contractor management outside construction, is in what to look for in contractor management software.

Subcontractor Prequalification, and What Keeps It Current.

Prequalification is easy to demonstrate and hard to sustain. The real question is not whether a subcontractor can submit an insurance certificate and a safety plan. It is what happens on day 200, when the certificate of currency expires and the crew is already on site. Ask to see the re-verification flow end-to-end: who gets chased, on what schedule, what the subcontractor sees, and what happens at the gate if it lapses. Then ask whether one prequalification record can satisfy several of your projects, or whether it is re-collected per job.

Worker-Level Competency, Not Company-Level Status.

Company-level approval tells you a business passed a review. It does not tell you the rigger working level four tomorrow holds a current high risk work licence for that class, and those licences are per class and per person.² Ask the vendor to open a single worker’s record: white card, trade licence, high risk work licence classes, site inductions, and the expiry date on each. Then ask what happens 30 days before one expires, and whether the alert reaches the subcontractor or only your team. Worker-level records are the difference between a document library and a control.

SWMS Review, and the Bottleneck It Creates.

A SWMS must identify the high risk work, state the hazards and the risks, describe the control measures, and describe how those controls will be implemented, monitored, and reviewed.² The subcontractor has to give you a copy before work starts, and as principal contractor you must take all reasonable steps to obtain it.² In practice that becomes one person reading PDFs against a standard, and it is the most common reason a start slips. Regulator guidance warns against generalised controls such as “use appropriate personal protective equipment”, because they push the decision back onto the worker, so a reviewer has to actually read the thing.⁵ Ask how the system measures review turnaround, whether a reviewer can comment against a clause rather than emailing a marked-up file, and what the audit trail shows about who accepted what.

Site Access and Sign-In at a Gate With No Signal.

Whoever has management or control of a construction workplace must ensure, so far as is reasonably practicable, that it is secured from unauthorised access.² That duty is only as good as what happens at 6:20 in the morning at a gate with no reception. Ask to see sign-in working offline and syncing afterwards, and ask what the evacuation roll call looks like when the site holds three tiers of subcontractors. If the demo runs on office wifi, you have not seen the product.

Inspections and Actions That Actually Close.

Anyone can capture an inspection. The value sits in the action it raises: assigned to a named person, with a due date, visible to the subcontractor who has to fix it, and closed with evidence. Ask to see an overdue action, who it escalates to, and how a site manager sees today’s open items without running a report. Inspections that produce a PDF nobody opens are worse than a paper pad, because they create a durable record of a problem you did not close.

Incident Capture and Regulator Notification.

A notifiable incident must be reported to the regulator immediately after you become aware of it, by the fastest possible means.¹ Ask what the system does in the first hour: who is alerted, what a phone can capture at the scene, and whether the record locks once it is submitted. Then ask the less comfortable question. In two years, what does this show a regulator or a court about who signed off what, and when.

Reporting a Principal Contractor Can Hand to a Client.

Head contractors get asked for compliance reporting by their own clients and by an insurer at renewal. Ask to see the report a project director would send out, not the internal dashboard. If the only way to produce it is to export to a spreadsheet and rebuild it by hand, that work lands on your safety team every month for the life of the contract.

Integration, and Who Owns the Contractor Record.

Two questions, and both are commercial rather than technical.

First, what has to flow to your enterprise resource planning system. Usually it is one thing: the approval state of a subcontractor before a purchase order is raised or a progress claim is paid, because that is the only control that actually stops work. Everything else is reporting convenience.

Second, who owns the contractor master record. If finance creates vendors and safety creates contractors, you will end up with two lists that disagree, and the argument about which one is right will outlive everyone in the room. Settle it before you buy, and put your procurement team in that decision rather than telling them about it afterwards.

Rollout Is Where These Purchases Fail.

Internal adoption is the risk everyone plans for, and it is not the one that kills the project. Your safety team will use the system because their job depends on it. The subcontractor businesses you are asking to load documents into a portal have no such incentive, and several of them already do the same thing in four other portals for four other head contractors.

What works, in order. Start with one project and the subcontractors already on it, never with the whole panel. Make the contract the lever, so no approved record means no site access, and say that at tender rather than after award. Give subcontractors a named person to call in the first month, because the ones who give up are the ones who got stuck at seven in the evening with nobody to ask. And carry over the documents you already hold instead of asking hundreds of businesses to re-upload what is sitting in your shared drive. That single decision does more for adoption than any feature on the list.

Assume the panel takes longer than the software. The platform goes live in weeks. Bringing the panel across is a phone-call exercise, and somebody on your side has to own it by name.

The Total Cost, Including the Part Nobody Prices.

Four costs, and only the first appears on the quote.

Licences. Ask what the unit is, whether site, contractor business, worker, or module, and model it on the numbers you will have in two years rather than today. Per-worker pricing behaves very differently on a job that doubles its crew for a six-week pour.

Implementation. Configuration, data migration, and integration work. It is quotable, so get it in writing.

Your own time. Somebody internal has to decide what a plumbing subcontractor must hold that a traffic controller does not. That work is the product, and it is usually what slips, because it needs your best safety person for a fortnight and they are already busy.

The subcontractors’ time. Every hour a subcontractor spends in your portal is an hour they price into their next tender, and nobody puts it on the business case. You cannot avoid it. You can count it, and it is the number that tells you whether to ask for 30 documents or 12. No Australian regulator or peak body publishes a cost benchmark for this category, and the comparisons circulating online are mostly United States pricing against a different product set, so build the model on your own quotes.

When Not to Buy a Platform at All.

If you run one site at a time with six regular subcontractors you have used for years, a platform is probably the wrong answer. A well-kept spreadsheet with an expiry column, a calendar reminder a month ahead, and a folder for each subcontractor will do the job, and it will do it on day one rather than in month three.

The honest test is not headcount. It is churn and depth. When you can no longer say from memory who is on site tomorrow, when you are carrying subcontractors you did not engage directly, or when you are running projects under more than one state’s requirements, manual control has already failed and you simply have not had the incident that proves it. Until then, spend the money on a better site manager.

I would rather lose that deal than sell a system that sits unopened. The ones abandoned in year two are almost always the ones bought a year too early.

How I Would Run the Decision.

Write the requirement from the duties rather than from a feature list: the WHS management plan, SWMS coordination, induction, licence currency, site access, and incident notification.³ Score vendors against the seven demo questions above with your most difficult subcontractor in mind, not your easiest. Then, before you sign, ring two of that vendor’s customers and ask one question.

What proportion of your subcontractors completed the portal without needing a phone call. That number predicts your rollout better than any feature comparison, because subcontractor completion is the thing these systems actually fail at. Get it right and the rest is configuration. Get it wrong and you have bought a very expensive place to store documents nobody updates.