Induction Is Not a WHS System
- WHS Systems
- Published 8 September 2026
- 9 minute read
- By Tristan Winen
An induction tells a worker once. A WHS system keeps checking: that the training still matches the job, the equipment, and the procedures as they change. A signed induction form from week one proves an event happened, not that anyone is still competent for the work they’re doing today.

“We’ve got an induction. New starters do it in the first week, sign the form, and they’re right to go.”
That sentence is usually true and still misses the point. A site induction is one event. A WHS (OHS) system is what happens every day after it: when a procedure changes, when new equipment turns up, when someone comes back from three months off, when a role’s risk profile shifts and nobody sends out a memo about it. Most businesses have the event. Very few have connected it to an actual WHS (OHS) system, and that’s the gap that actually matters inside a WHS (OHS) management plan. The induction is not the system. It’s one input into one.
What an induction is actually for
Before the fix, it’s worth being honest about the job an induction is meant to do, because “welcome the new person” undersells it badly.
An induction exists to do four things at once: discharge the WHS (OHS) obligation to inform, train, instruct and supervise a worker before they’re exposed to risk; transfer the knowledge that’s specific to this site, this role and this equipment, not generic industry knowledge; set the behavioural standard the business actually expects, not the one written in the handbook; and create a genuine record that the business can stand behind if something goes wrong. New workers are at their most exposed in the first weeks of a role, precisely the window an induction is supposed to cover. If the induction is thin, that’s the window with the least protection in it.
None of that is achieved by a single session, however well the session is run. It’s achieved by whatever happens for the weeks and months after it, which is where “system” stops being a buzzword and starts being the actual mechanism.
An event tells them once. A WHS (OHS) system keeps checking
An induction event is a session: orientation, a policy briefing, maybe a demonstration, a signature. It happens, it’s recorded, and then it’s over.
An induction system is the mechanism inside the WHS (OHS) management plan that keeps that record alive: tied to the specific tasks a worker actually performs, updated when those tasks change, and set up to flag reassessment automatically rather than relying on someone remembering who needs it. Two things have to be true for that mechanism to work. It has to be tailored to how the business actually operates: the tasks, the equipment, the site-specific hazards of this workplace, not a generic template that reads the same for a warehouse and an office. And it has to be easy enough that a supervisor runs it without a specialist standing over them. A system that only works when one person personally manages it isn’t a system, it’s a dependency.
The obligation, and why more businesses are building this into a WHS (OHS) system
The WHS (OHS) obligation here isn’t optional or new. The Work Health and Safety Act 2012 (SA) sets it out in what the Act itself calls the “primary duty of care”: a PCBU must provide the information, training, instruction and supervision necessary to protect workers from risks arising from the work (s19(3)(f)). That obligation doesn’t end at day one. It’s ongoing, for as long as the worker is exposed to the risk.
A formal WHS (OHS) system is simply the recognised way of demonstrating that an ongoing obligation is being met on an ongoing basis, rather than asserted once and assumed to still hold a year later. Businesses running ISO 45001-aligned systems will recognise this as the separation between Clause 7.2 (Competence: can this person actually do the job safely) and Clause 7.3 (Awareness: do they understand the risks, the policy, and their own right to stop unsafe work). Those are two different questions, and a business doesn’t need formal ISO certification to benefit from asking both of them deliberately, inside its own WHS (OHS) management plan, rather than folding them into one induction form and calling it done.
Training and competency are not the same thing
This is the line most induction processes blur, and it’s the one that matters most.
Training is complete when:
- The content has been delivered: a session run, a video watched, a briefing given.
- Attendance is recorded and a signature is captured.
- The worker has been told the procedure and where to find it.
Competency is established only when:
- The worker has demonstrated the task correctly, under direct observation, on the actual equipment they’ll use.
- That demonstration is assessed against a defined standard, not a supervisor’s general impression that “they seemed fine.”
- The sign-off is tied to that specific task and environment, not a single generic line that says “induction complete.”
- It’s captured somewhere the business can actually retrieve later, linked to that worker and that task, not buried in a folder of signed attendance sheets.
A worker can tick every box on the left and still not be able to do the job safely. The business that only tracks the left column has a training record. The business that tracks both has a competency system, and only one of those actually reduces risk. (The full version of this distinction, including what legally triggers a reassessment, is in competency assessment vs training.)
Why this has to live inside the WHS (OHS) system, not sit beside it
An induction that isn’t connected to anything else decays the moment the workplace changes, and workplaces change constantly. New equipment arrives. A procedure gets amended after a near miss. Someone’s back from extended leave. A worker moves into a role with a different risk profile. If the induction record is a standalone form filed away after week one, none of those events touch it. Nobody is prompted to look again, and the record quietly stops reflecting reality while still looking complete on paper.
Inside a proper WHS (OHS) management plan, the induction is instead the entry point into a live competency register: one that already knows which tasks a role requires, what “competent” looks like for each of them, and what should trigger a fresh look: a changed procedure, a new piece of equipment, an incident, a long absence. That’s what makes it tailored rather than generic. And because it’s built around how the business actually runs rather than a copy-paste template, a supervisor can run it without needing to be a WHS (OHS) specialist themselves, which is what makes it something the business will actually keep using instead of something that gets skipped the first time things get busy.
A pattern worth recognising
A pattern the WLSS team sees regularly: a business with a genuinely well-run induction. Proper orientation, a clear briefing, a supervised first shift, everyone signed off. On paper it looks like exactly what it should be. Eighteen months later, half the equipment on site has changed, two procedures have been rewritten after incidents elsewhere in the group, and three staff have had extended periods off. None of that touched a single induction record, because the induction was never connected to anything that would have flagged it. Every new starter since had a great first week. Nobody could say, for the people already on the floor, whether the training they got at induction still matched the job they were now doing.
Questions worth asking yourself
- Could you point to the exact moment a recent new starter’s training turned into confirmed competence, or did the induction just end and independent work quietly begin?
- If a piece of equipment on your site changed tomorrow, would anything actually flag which workers need reassessing, or would you find out the hard way?
- On your site, do you genuinely know the difference between someone who’s been trained and someone who’s been checked, or are you trusting the signature to mean more than it does?
- Could a supervisor run your induction consistently without you personally involved, or does it only hold together because you’re the one who remembers what’s needed?
Why WLSS
The WLSS team builds induction into the WHS (OHS) management system itself, tailored to the actual roles and tasks on site, and simple enough that supervisors run it without needing to be specialists. Not a generic form. Not a slideshow with a signature at the end. A live link between what a worker was trained on and whether that training still holds, updated as the business changes rather than left to quietly go stale, backed by the same discipline behind WLSS’s training services and WHS management systems work.
- Triple ISO certified: ISO 9001, ISO 45001, ISO 14001
- 80+ years combined team experience
- 500+ SA businesses supported
Common Questions
Isn't this just a better induction checklist?
No. A checklist tracks whether steps happened once. A system tracks whether the worker is still competent for the job they're currently doing, and prompts a fresh look when the job, the equipment or the worker changes. The checklist can be complete and the system can still be failing.
Does a small business really need an induction system, or is that overkill for a handful of staff?
The obligation doesn't scale down with headcount, and neither does the first-weeks risk window. What scales down is the complexity of the system needed to meet it. Five staff need something proportionate and easy to run, not a smaller version of a large enterprise's paperwork. Proportionate and absent are different things.
How does this connect to a broader WHS (OHS) management plan?
An induction system should sit as one live component of the plan, feeding the same competency register that tracks training, licences, refresher dates and reassessment triggers across the whole workforce, not as a separate process that only gets referenced when someone asks for the paperwork.
What should a site induction actually cover?
The things that are specific to this site, this role and this equipment: the actual tasks and hazards the worker will face, the behavioural standard the business genuinely expects, and a record of what was covered and demonstrated. Generic industry content a worker could have received anywhere is the part templates get right; the site-specific part is the reason the induction exists.



