A WHS Management System: Doing the Job Is Not the Same as Proving It

“We did do it properly, we just didn’t write it up.”

It’s one of the most common things said after the fact, and it’s usually true. The task was done. Nobody’s lying about it. But “we did it” and “we can show it” are two different claims, and only one of them survives being tested. When a regulator, an insurer, a new manager, or simply time itself asks the question, the work that actually happened and the work that can be demonstrated to have happened need to be the same thing. Often, they aren’t, and that gap is exactly where WHS due diligence gets tested.

What people actually mean when they say “the work got done”

Pull the statement apart and it usually breaks down into one of a few things:

• The task was completed, but nothing was recorded at the time. The record, if it exists at all, gets created later, once someone remembers or someone asks.
• Something was recorded, but not what actually happened. A generic form gets ticked because it’s quicker than describing what was actually checked and found.
• The person who did it can vouch for it, but nothing else can. The proof lives in one person’s memory, not anywhere the business can reach if that person is unavailable, has moved on, or simply doesn’t recall the detail six months later.

None of this means the work wasn’t done properly. It means the only evidence that it was done properly is a person’s word, and a person’s word isn’t something a business can produce on request.

Paperwork isn’t the job, but it’s the only evidence you have of it

A record was never meant to replace the work. Nobody’s system gets safer because a form was filled in; the form doesn’t do the task. But once the task is finished, the record is the only thing left standing. The work itself is over the moment it’s done. From that point on, whether anyone can trust that it happened correctly depends entirely on what was captured, not on what actually occurred. Treating the record as a formality misses that it isn’t documenting the job for its own sake. It’s the only thing that will still be there to answer for the job once the moment has passed.

The duty behind it, and where the record comes in

Under the WHS (OHS) Act, a business has a duty to manage risks to health and safety, so far as reasonably practicable. That duty exists regardless of whether anyone ever asks to see evidence of it. It isn’t created by paperwork and it isn’t satisfied by paperwork either. But in jurisdictions operating under the model WHS laws, officers also carry a due diligence duty, and that duty is specific: it includes verifying that the business actually has, and actually uses, appropriate processes for managing risk, not simply that a process exists on paper somewhere. In practice, that verification almost always comes down to records: if a process can’t be evidenced, there’s no way to verify it was used, only a claim that it was.

When a record is proof, and when it just looks like one

What this looks like when it’s tested

The gap between “we did it” and “we can prove it” isn’t hypothetical. In July 2025, the District Court of NSW convicted AWB Contractors Pty Ltd and its director following a fatal crane lift during a 2021 salvage operation. SafeWork NSW’s investigation found no risk assessment had been conducted for the lift, no safe work method statement existed, and there was no system in place to monitor or audit whether safety processes were actually being followed. The court found this reflected a fundamental failure to ensure the business had, and used, appropriate resources and processes, under the officer due diligence duty in the WHS (OHS) Act. The company was fined $765,000. The director was fined $300,000 personally. The case didn’t turn on whether the work could have been done safely. It turned on whether the business could show it had a process, and had actually used it.

A pattern worth recognising

A pattern the WLSS team sees regularly: a business is confident a task happened, and it did. Everyone involved agrees the work took place. But when asked to produce the evidence, what exists is a form completed well after the fact, reconstructed from memory once someone realised it would be needed. The work itself may have been done correctly. The problem is that nothing was recorded as it happened, so there’s no way to demonstrate what was actually checked, by whom, or against what. The gap only becomes a problem when it’s tested: an audit, an incident, an insurance claim. By then there’s no way to go back and create a genuine record. The fix was never more paperwork. It was making the record part of doing the task, not something chased afterward.

Questions worth asking yourself

• If the person who did this task left the business tomorrow, could you produce something that proves it happened the way it was supposed to, or only their word, which would leave with them?
• Handed two records for the same kind of task, one made at the time, one reconstructed from memory a fortnight later, would you actually be able to tell them apart?
• Are you confident your team creates records as the work happens, or are you assuming that and simply trusting that the forms show up eventually?
• If someone asked you to prove a specific task happened six months ago, would you know exactly where to look, or would you be hoping something turns up?
• Would you personally notice if a record had been quietly backfilled rather than made at the time, or would it look identical to the real thing to you?

Why WLSS

The WLSS team builds the record into the process, not after it. Every recommendation and every sign-off is put in writing at the time, so what exists afterward is proof, not a reconstruction. That’s the same discipline behind WLSS’s own WHS management systems work and WHS system audits: checking not just whether the paperwork exists, but whether it was made when and where the work happened.

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

Common Questions