Common Safety-System Pain Points Aren’t Just Paperwork

“It works, it’s just… a lot of admin.”

Most businesses don’t describe their safety system as broken. They describe it as heavy: too much paperwork, too many places records could be, too much depending on one person remembering things. That description usually undersells what’s going on. Admin weight is often the visible symptom of gaps in how a business demonstrates its WHS compliance, meeting its WHS (OHS) obligations in a way it can show, and those are the same gaps regulators and courts look for when something goes wrong.

The pain points that show up again and again

• Outdated documents. Procedures that describe how the business used to operate, not how it operates now, often because nobody was assigned to update them after a change.
• Duplicated forms. The same information captured twice in two different registers that don’t talk to each other, doubling data entry without doubling the value of the data.
• Unclear ownership. Nobody quite sure whose job it is to update a document or close out an action, so it drifts until someone external asks about it.
• Spreadsheets everywhere. Registers that live in personal files, not a shared, controlled system, with no single version anyone can trust is current.
• Missing evidence. Training that happened but was never recorded, or a record that exists but can’t be found when it’s actually needed.
• Overdue actions. Corrective actions raised, then quietly forgotten, until an audit or an incident brings them back into view.
• Inconsistent inductions. Every new starter getting a slightly different version depending on who ran it, so nobody can be certain what any given worker actually knows.
• Dependence on one employee. The person who “knows how it all works” being the only one who actually does, with nothing written down that would let anyone else pick it up.

Why these pain points cluster together

These problems rarely show up in isolation. A business with duplicated forms usually also has unclear ownership, because nobody’s been made responsible for reconciling the overlap. A business dependent on one employee usually also has missing evidence, because that person’s knowledge substitutes for documentation that was never written down. The pattern underneath is almost always the same: no one has been made clearly, individually responsible for keeping the system honest.

The obligation behind the paperwork

Under the WHS (OHS) Act 2012 (SA), every business carries an obligation to ensure health and safety, so far as reasonably practicable. That obligation is the law. A documented safety management system (procedures, registers, training records, corrective action logs) is how a business demonstrates it’s meeting that obligation. It isn’t the obligation itself, and a system that exists only on paper doesn’t meet it, no matter how complete it looks in a folder.

That distinction has real teeth in South Australia. Since 1 July 2024, section 30A of the WHS (OHS) Act creates an industrial manslaughter offence: gross negligence or recklessness in breaching a health and safety obligation that causes a death, carrying a maximum penalty of $18 million for a body corporate. The threshold is high. But the offence exists because “we had a system” has never been an acceptable answer to “why didn’t the system catch this.”

It isn’t hypothetical

South Australia’s courts are testing this right now. In July 2026, SafeWork SA laid the state’s first industrial manslaughter charges, against Nylastex Tooling Pty Ltd, Nylastex Holdings Pty Ltd and two directors, over the death of 28-year-old worker Lachlan Carslake at their Edwardstown plant in July 2024. He was allegedly struck by a metal object ejected from a milling machine, on a machine where SafeWork SA alleges the guarding interlock switch had been disabled. Court documents allege an external technician had raised safety concerns about that same switch just two days before the fatality. These are allegations, not yet tested in court. But the pattern is the one this article opened with: a control that existed on paper, a warning that came in from outside the business, and, allegedly, no one who acted on it in time.

It isn’t a one-off nationally either. In May 2026, Mastermyne Crinum Operations was fined $7 million plus $299,000 in costs over the 2021 death of underground miner Graham Dawson in a roof collapse, in what was reported as the first test of the strengthened industrial manslaughter provisions added to Queensland’s mining safety laws in 2020. The court heard the company had changed its roof support method amid what the judge described as an alarming lack of consultation, and that repeated warnings about the risk had been raised before the fatality.

Different states, different industries, the same failure underneath: a change or a warning that didn’t make it into how the business actually ran on the day it mattered.

Where the real line sits

A safety system meets the obligation when:

• Documents describe how the business operates today, not how it used to, reviewed on a set cycle by a named owner.
• Records are captured when the work happens, not reconstructed afterwards to fill a gap.
• Every action raised has a visible due date and an escalation point if it’s missed.
• A change in practice triggers a documented review before it becomes “how we do things now.”
• More than one person could explain how a given control works.

It fails the obligation, even with a folder full of paperwork, when:

• The documents describe a process the business stopped following months or years ago.
• A defect, near-miss or warning is logged once and nobody is responsible for closing it out.
• Practice on the ground has quietly drifted from what’s written down, with no record of why.
• The system depends on one person’s memory to keep functioning at all.
• Registers exist in multiple versions and nobody could say which one is current.

Questions worth asking yourself, honestly

• Would I notice if a control in my workplace had quietly changed in practice, without the paperwork ever catching up?
• If a genuine warning came in tomorrow, could I say, without checking with anyone else, exactly who’s responsible for acting on it and by when?
• Could I personally walk a regulator through how our documented system matches what actually happens here day to day?
• If the one person who “knows how it all works” left tomorrow, would the business keep running the way it’s supposed to?
• Do I know the difference between a system that looks complete and one that’s been tested against how this workplace really operates?

If any of those land uncomfortably, that discomfort is worth sitting with. It’s usually a better read than the folder.

Why WLSS

The WLSS team’s job isn’t to hand a business a checklist and wish them luck. It’s to sit inside a system, work out which pain points are real risk and which are just noise, and show the business what that looks like in writing, without softening it to make the quote easier to swallow. Where software like Areesa closes a real gap (ownership, evidence, tracking overdue actions), the WLSS team builds it around how the business actually runs, then works through it with them rather than dropping it and leaving. A WHS system audit is the usual starting point, and the broader WHS compliance services carry it through.

• Triple ISO certified: ISO 9001, ISO 45001, ISO 14001
• 80+ years combined team experience
• 500+ SA businesses supported

Common Questions