How to Manage Worker Compliance Across Multiple Mine Sites

Managing compliance for one site is hard enough. Managing it across three, five, or ten - with different clients, different portals, and different rules for every role - is a different problem entirely.

Most Australian mining contractors start out with a spreadsheet. It works, sort of, until it doesn't. And when it stops working, it usually stops working at the worst possible moment - an audit, a gate knockback, a client rule change the week before a shutdown.

This is the reality for contractors supplying crews to multiple mine sites. And it's a problem that's getting harder to ignore in 2026.

Why Multiple Sites Changes Everything

When you're operating across a single site with one client, compliance is relatively contained. You know the rules. You've got a handle on who holds what ticket. One person can probably keep it in their head.

Add a second client. Now you've got two portals, two sets of induction requirements, two different rules about which medicals are acceptable and which VoCs are current. A worker who is fully compliant for Site A may not meet the requirements for Site B - even if their qualifications are identical on paper.

Add a third site, a fourth client, a shutdown that pulls workers from three different project teams at once. Now you're not managing compliance. You're managing chaos.

The spreadsheet that was fine for one site becomes a liability. Not because the information isn't there,  but because it can't answer the right question fast enough.

That question is: is this specific person compliant for this specific role at this specific site, today?

If your answer takes more than a few minutes, you have a problem.

Where It Breaks Down

In our experience working with Australian mining contractors, multi-site compliance tends to fail in three predictable places.

1. Expiry tracking falls through the cracks

Licences, tickets, medicals, and VoCs don't expire conveniently. They expire on different dates, for different workers, against different site requirements. A spreadsheet might tell you a ticket expires in June - but it won't tell you that the client at Site C requires 30 days notice before renewal, or that the worker is rostered there in three weeks.

By the time someone notices, it's too late.

2. No single source of truth

One contractor we work with, Frontline Equipment Maintenance, described their pre-GSR process as managing compliance across multiple spreadsheets, portals, and email chains simultaneously. Information lived in different places depending on who had updated what last. When a client asked for a compliance report, it meant someone spending hours pulling data together from four different sources and hoping nothing was missed.

That's not a process problem. That's a structural problem. Spreadsheets aren't built to map requirements by site and by role. They store data. They don't answer operational questions.

3. Over-reliance on one person

Almost every contractor we talk to has a version of this: one mobilisation coordinator, one HSEQ admin, one ops manager who knows where everything is, who checks what, and how the whole thing holds together. That person is invaluable... and they're also a single point of failure.

When they're on leave, sick, or simply overwhelmed during a mobilisation spike, the system breaks down with them.

What Regulators Now Expect

This isn't just an operational inconvenience. It's a compliance risk with real consequences.

Australia's WHS regulators have sharpened their approach in 2026. Inspections are now specifically assessing how information flows between mine operators and contractors - not just whether paperwork exists, but whether it's accessible, current, and defensible. We've written specifically about what the NSW Resources Regulator is focusing on for the first half of 2026 — it's worth a read if your crews work in NSW.

Contractors running crews across multiple sites are squarely in the spotlight. When something goes wrong, investigators look at what you can prove, not what you intended. We've written about what that looks like in practice.

What Actually Fixes It

The good news is that most contractors already have the information they need. The problem is usually structure, not data. Here's where to start - whether you're looking at software or not.

1. Map your requirements by site and role, not just by person
Write down, for each site your crews work on, exactly what's required for each role. Medicals, inductions, VoCs, tickets - listed out specifically. It sounds basic, but most contractors have never done this in one place. Even a well-structured spreadsheet with this information is significantly better than nothing.

2. Identify your single points of failure right now
Which sites carry the most risk if someone isn't compliant? Which roles have the tightest requirements? Which workers are closest to expiry on something important? And honestly - which person in your business is the one holding all of this in their head? That last one is your biggest vulnerability.

3. Set a minimum expiry buffer and make someone accountable for it
Decide that anything expiring within 30 days triggers a review - not a scramble, a review. Put one named person in charge of that list. Review it weekly. It's not a perfect system but it catches most of what kills you at the gate.

If you want a more structured starting point for going digital with this, we've put together a free Workforce Management Playbook that walks through the practical steps toward ditching the spreadsheet for good. Worth a read regardless of what system you're using.

Or, if you want to stop rebuilding this process every time a site adds a new requirement, a new portal, or a new client rule - that's exactly what GO! Site Ready is built for. Requirements mapped by site and role, alerts before expiries hit, and compliance reporting you own and control. No more relying on one person's memory or a client portal you don't control.