Field notes › Compliance
Inductions vs competencies: they're not the same thing
Plenty of compliance records treat inductions and competencies as one bucket of tickets. They are not, and the difference is not pedantry. The two answer different questions, are owned by different people, and expire on different clocks. Firms that blur them end up with workers who look compliant on the spreadsheet and get turned away at the gate.
A competency answers: can this person do the work?
Competencies are about the person and the task. A high risk work licence, a trade qualification, a first aid certificate, a verification of competency on a particular machine. They attach to the worker and, for the most part, travel with them. A rigger's licence means the same thing on any site in the country, because it is issued under a national framework through the state regulators.
Competencies are typically owned by a regulator or a training system. They have formal expiry or renewal rules, and when one lapses the worker is not partially qualified, they are unqualified for that class of work until it is renewed.
An induction answers: can this person work here?
Inductions are about the person and the place. A site induction covers this site's hazards, rules, emergency arrangements and systems. It is owned by the site or the client, not a regulator, which is why every operator's induction is different and why none of them care how many other inductions your worker has done. The most qualified rigger in the state still cannot walk onto a site they have not been inducted for.
Inductions mostly do not travel. They are usually specific to a client, a site, sometimes an area within a site, and they lapse according to whatever validity period the owner sets. The general construction induction behind the White Card is the one that behaves more like a competency, in that it is recognised across sites, but everything above it is local.
Why mixing them up costs you
The two failure modes are mirror images:
- Treating a competency like an induction. Assuming a licence needs re-doing per client wastes money on training nobody required.
- Treating an induction like a competency. Assuming an induction travels between sites is the expensive one. The worker flies out fully licensed and gets stood down at the gate because their induction was for a different site, or lapsed under a validity rule that only exists in that client's system.
A single ticket column in a spreadsheet cannot represent this. The real compliance question at rostering time is a compound one: does this worker hold the competencies for the role, and the inductions for this specific site, and is every one of them current on the dates of the shift. Miss any leg of that and the whole answer is no. When you are unsure what a given qualification legally requires, the answer comes from your state work health and safety regulator, not from how the last client handled it.
Track them separately, check them together
The practical conclusion is to model them as the different things they are. Competencies recorded against the worker with their expiry dates. Inductions recorded against the worker per client site, with their own validity. Then, and this is the part spreadsheets never do, check both automatically every time a shift is booked.
That is how Mustr is built. Competencies and inductions are separate records against each worker, and every booking is checked server-side against both, plus availability and double-bookings, before it is confirmed. A worker with the right licence but the wrong site induction is blocked at booking time, not discovered at the gate. Expiring records of either kind surface up to 60 days out with one-click reminder emails, and workers upload renewals through the worker portal from any phone.
Two different questions, one combined check, done before every booking rather than after the flights are paid for. If your records currently answer can they do the work but go quiet on can they work here, book a demo and see it on your own roster.