Mining workforce management software for FIFO scheduling & compliance

If you supply labour to mine sites, run a contracting business servicing resources projects, or manage a mining operation’s own contractor workforce, scheduling looks nothing like a retail or hospitality roster. This guide covers what makes mining workforce scheduling different, which obligations are actually law and in which state, and what to check for in software that claims to handle it.

Why mining scheduling is a different problem

FIFO and DIDO cycles run on their own clock

A fly-in fly-out or drive-in drive-out roster runs on a fixed swing pattern — 8:6, 2:1 and 4:1 are commonly used, among many others — that continues regardless of which individual is filling the seat. The scheduling challenge is not just who is working today. It is making sure the right number of competent, cleared workers is inbound for every swing changeover, weeks in advance, with enough lead time to book travel and camp accommodation.

Site competencies do not transfer

A worker fully inducted at one mine is not automatically cleared for another, even within the same company and certainly not across operators. Site-specific inductions, equipment competencies — heavy vehicle, confined space, working at heights, particular plant tickets — and fitness-for-work medical clearances generally have to be tracked per site, not just per worker.

Currency can lapse mid-swing

A worker can start a two-week swing fully cleared and have a medical, ticket or induction expire while they are on site, hundreds of kilometres from anywhere they could renew it. A system that only checks at the point of rostering will miss that entirely.

Where the legal obligations actually sit

This is the part most software marketing gets wrong, so it is worth being precise. There is no single national mining safety law. Mine safety is regulated state by state, and the rules that apply to you depend on where you work and what you are mining.

These frameworks were developed from the national model WHS regulations for mining, with additional mining provisions agreed between New South Wales, Queensland and Western Australia — so they rhyme, but they are not identical and they are not interchangeable. Other states and the Northern Territory have their own arrangements again. Do not assume a requirement you meet in one state satisfies another.

Standard 11 is a Queensland standard

Standard 11 is frequently described online as “the Australian mining induction”. It is not. It is a Recognised Standard issued under Queensland’s Coal Mining Safety and Health Act 1999, setting out training and assessment requirements for Queensland coal mine sites. It is widely recognised by sites in other states, particularly for contractors and FIFO workers crossing borders, and holding it can help with site access elsewhere — but that is recognition by operators, not a legal requirement outside Queensland. Treat it as a site access requirement to be confirmed per operator, not a national ticket.

Fatigue: a duty, not a prescribed roster limit

There is no FIFO-specific national fatigue law setting maximum swing lengths for mining workers. Fatigue sits under the general WHS primary duty of care: risks, including fatigue, must be eliminated or minimised so far as is reasonably practicable, with consultation and work designed accordingly. Safe Work Australia’s model Code of Practice on managing the risk of fatigue at work (September 2025) is the practical guidance most jurisdictions point to, alongside state codes such as SafeWork NSW’s.

Note carefully what this is not. The prescriptive heavy-vehicle fatigue rules administered by the National Heavy Vehicle Regulator — the counted work and rest hours that apply to fatigue-regulated heavy vehicle drivers — do not generalise to FIFO or mining workers as a class. Some of your people may be covered by those rules because of the vehicle they drive; most site-based mining workers are not. Any software or supplier that tells you it enforces “mining fatigue law” is describing something that does not exist as a single rule set.

What to look for in mining workforce software

1. Site-specific competency and induction tracking. The system needs to track clearance per site, not just per worker, and show at a glance which sites a given person is currently cleared for.
2. Enforcement, not just a red dashboard. A dashboard showing an expired ticket still relies on someone noticing before they roster that worker. A gate that prevents the placement removes that dependency, which matters most where the consequences of a miss are highest.
3. Swing pattern management. Recurring cycles that project forward, showing who is inbound for the next changeover, who is due for R&R, and where gaps are opening weeks ahead rather than this week.
4. Fitness-for-work and medical currency. Medical clearances often carry defined validity periods and can be site- or role-specific. They need the same expiry tracking and reminders as licences and tickets.
5. Real-time visibility across remote sites. Mine sites are remote and thin on admin support. A live view of coverage, upcoming swing changes and clearance status, reachable from a phone, matters more here than in a metro operation.
6. Clean payroll export with site-based hours. Mining rosters carry different rates for different shift types and site allowances. Hours need to reach payroll without manual re-entry.
7. An audit trail that survives scrutiny. When an operator or a regulator asks what was tracked and when, you want a record, not a reconstruction.

How OnCrew approaches mining workforce management

OnCrew’s core model — a fluctuating workforce assembled and kept compliant across multiple sites, rather than a single fixed team — maps onto how resources labour supply actually runs. Here is precisely what it does and does not do.

• Per-site compliance enforcement. Each site carries its own mandatory requirements, and each requirement is set to enforce or to warn. Where a requirement enforces, a worker who is missing it or whose document has expired cannot be allocated to that site and is excluded from the fill list, with every block written to the audit trail. Where it warns, the allocation proceeds and the coordinator is told exactly what is missing. Because the requirements attach to the site, a worker cleared for one operation and not another is handled automatically. More on the compliance engine.
• Expiry tracking with reminders. Every ticket, licence, medical and induction is catalogued with its expiry date and watched continuously, with reminders ahead of a lapse rather than a check only at the moment of rostering.
• Smart Fill for changeovers. Smart Fill applies the hard gates first — site compliance, onboarding readiness and availability conflicts — then ranks the remaining workers by role match, their history at that site and with that client, distance from the site and how recently they last worked, with a bonus for full compliance. Offers go out in one tap and escalate by SMS and voice. It does not rank people by a reliability score, and the ranking is not a model that learns; it is the explicit scoring just described.
• Fatigue and same-day indicators. Where a worker’s recent bookings suggest a fatigue risk, or they are already on another shift that day, OnCrew surfaces that to the coordinator before they allocate. These are operational warnings to inform a human decision — they are not an enforcement of any fatigue law, and they do not discharge your WHS duty.
• Onboarding ahead of mobilisation. Workers self-onboard from their phone — details, tickets and licences photographed, your induction, medical information held with application-level encryption, and tax, super and bank details — so a new starter can be prepared ahead of a mobilisation date without a paper chase.
• Live operational view. A dispatch map shows every site, crew and shift on one screen, from a desktop or a phone.
• Verified hours. Clock-ins are GPS-stamped and checked against the site’s geofence, recorded in the site’s local time, with off-site clock-ins flagged for the supervisor rather than silently blocked. Approved hours export payroll-ready to Employment Hero, Xero (via a bridge file) and MYOB AccountRight.
• Audit trail. Approvals, compliance blocks and changes are logged.

What OnCrew does not do: it does not run payroll, calculate award or site-allowance rates, pay superannuation or file STP; it does not model FIFO travel and camp bookings; it does not replace a mine’s safety management system; and it does not make any operator legally compliant. It manages who is cleared, who is rostered and what hours were worked, and it gives you the record.

Requirements that come up repeatedly on Australian mine sites

Exact requirements vary by operator, site, commodity and state. These recur often enough to plan around, but each must be confirmed with the operator rather than assumed:

• Site-specific induction — almost universally required before site access, and generally not transferable between operators.
• A generic industry induction — Standard 11 in Queensland coal, with different arrangements in other states and commodities.
• Fitness-for-work medical — commonly required before mobilisation and periodically after, often alongside site drug and alcohol policies.
• Plant and equipment competencies — heavy vehicle licences, confined space entry, working at heights and specific machinery tickets, depending on role.
• Right to work verification.
• Police check — frequently requested, particularly for camp-based positions.

Because these differ site to site and change periodically, manual tracking across a mobile, multi-site workforce is one of the higher-risk administrative environments a labour supplier can run without dedicated software.

FIFO roster planning: what good practice looks like

• Plan changeovers weeks ahead, not days. Travel, camp beds and site access all need lead time, so gaps in an upcoming swing must surface early enough to actually fill them.
• Track individual swing history, not just the pattern. Cumulative days on and off tell you something a roster template cannot, and repeatedly compressed R&R is a risk worth seeing.
• Build in buffer for renewals falling due mid-swing, so nobody is caught on site with a lapsed requirement and no way to renew before the next roster.
• Keep a cleared bench per site, rather than one generic pool. Site-specific clearance, not headcount, is usually the real constraint on who can mobilise quickly.

What a clearance miss actually costs

It is worth being direct about the commercial exposure, separately from the legal one.

• Immediate stand-down. Most operators remove a worker the moment a clearance gap is identified, regardless of how far into the swing they are — leaving the position uncovered until someone can be mobilised, which on a remote site can take days.
• Loss of site access for the supplier. Operators track supplier compliance performance. Repeated misses are a common reason a contractor comes off an approved supplier list, which can mean the contract rather than the placement.
• Regulatory exposure. State mine safety regulators can investigate failures that contribute to, or could have contributed to, an incident — and the record of what was tracked and when becomes central to that inquiry.
• Reputation. Resources labour supply is a tight sector, and a supplier known for gaps finds the next tender harder regardless of price.

Winning and keeping mining labour supply contracts

Compliance and scheduling capability increasingly show up directly in tender evaluations. Operators assessing a labour supplier typically want to see a documented, auditable process rather than an assurance that tickets get checked; evidence of consistent fill rates at swing changeovers; the ability to produce clearance and attendance records on request rather than in three days; and a demonstrable time-to-mobilise for a new starter.

Businesses running this on spreadsheets and shared drives can still win a first contract. Retaining and expanding mining work over time tends to favour suppliers who can show the process is systemised rather than dependent on one person’s diligence — which is the same argument we make about spreadsheets and group chats generally, with higher stakes attached.

Build in-house or use purpose-built software?

Some larger contractors consider building their own tracking rather than adopting workforce software. Weighed honestly: a single site with a stable crew can be tracked manually without much risk. Multiple sites, rotating swings and a workforce moving between operators is a different order of complexity, and the failure mode is not slowness — it is that someone misses an expiry and nobody notices until it matters. Purpose-built software encodes the gate as a system rule rather than a process someone has to remember under time pressure, and the audit trail comes built in rather than assembled after the fact.

If you also run construction or civil crews alongside resources work, our construction, mining and engineering page covers the shared ticketing and dispatch ground in more detail.