Field notes › Compliance

Site inductions: why every site does them differently

Ask ten site managers what their induction covers and you will get ten different answers, all of them correct. Site inductions are meant to differ, because sites differ. The frustration for labour hire firms is not that inductions exist. It is keeping track of which of your workers has done which induction for which client, and when each one runs out.

Why there is no standard site induction

General induction training, the White Card in construction, covers the hazards common to an entire industry. Everything after that is local. A site induction exists to cover the things no generic course can know: this site's traffic plan, this site's exclusion zones, where the muster points are, who the first aiders are, what the permit system looks like, which radio channel to use.

On top of that, every operator runs its own safety management system, and the induction is how workers get formally brought inside it. Mine operators in particular tend to have layered, formal induction regimes, and two mines owned by the same company can still run different inductions because the ground, the plant and the risks are different. Expecting them to standardise is wishing for something that will not happen. The better move is to build your own systems assuming every client will be different.

The layers a worker actually goes through

In practice a worker heading to a remote site often stacks up several layers:

DashboardON SITE NOW12UNFILLED SHIFTS3EXPIRING SOON5Expiring in the next 60 daysWorking at Heights · 2 workersRemindSite induction · 3 workersRemind12
The office dashboard: who's on site, what's unfilled, what's expiring.
  • A general industry induction, such as the White Card for construction work.
  • Your own company induction, covering your policies and how employment with you works.
  • The client or operator induction, covering their overarching safety system.
  • The site-specific induction for the particular site or project.
  • Area or task inductions for specific parts of the site, such as processing plants or workshops.

Each layer can have its own validity period and its own refresher requirements, set by whoever owns that layer. None of them substitutes for the others. A worker fully inducted for one client starts from zero with the next one, and that is by design.

The tracking problem this creates

For a single employer with a single site, induction tracking is manageable. For a labour hire firm it multiplies fast. Every client relationship adds a new set of inductions with new expiry rules, and your workers move between clients, which means the question at rostering time is always specific: is this worker currently inducted for this site, not inducted somewhere, once.

The failure mode is familiar. A worker gets rostered onto a site they have not been inducted for, or their induction quietly lapsed since their last swing. Nobody notices until the site does. Then you are paying for flights and accommodation for someone who cannot start, the client is re-planning their shift coverage, and your name is attached to the mess.

Inductions also expire on their own schedule, separate from licences and tickets, so a compliance record that only tracks certificates misses half the picture.

Making the roster respect inductions

The fix is to treat inductions as first-class compliance records and connect them to the roster itself. In Mustr, inductions sit against each worker alongside their competencies, and every booking is checked server-side against both before it is made. Book a worker onto a site they are not inducted for and the booking is blocked outright, at rostering time, weeks before anyone books a flight. Expiring inductions surface up to 60 days ahead with one-click reminder emails, which is enough time to get a refresher organised around a swing rather than in a panic.

Because the roster runs on one timeline across every client site, the induction question is answered in the same place the shift is created, not in a separate spreadsheet someone has to remember to cross-check.

One caution: induction requirements, like most site access requirements, are set by the operator and can change. When a client tells you their rules have changed, believe them, update your records, and if a legal question sits underneath it, confirm the position with your state regulator.

If working out who is inducted where takes you more than a few seconds today, book a demo and see it on your own roster.

Bring one roster to the demo. We'll show you Mustr running it.

Book a 20-minute demo