Fatigue risk management software for transport and heavy vehicle operations

Most industries manage fatigue as a general WHS duty. Transport is different: it’s the industry where the regulator writes prescriptive hours — maximum work, minimum rest, counted in ways that don’t forgive sloppy rostering. For heavy vehicle operations, fatigue management isn’t a policy document; it’s a set of hard numbers your schedule either respects or breaches.

Fatigue risk management software (FRMS software) exists to make those numbers operational: encoded as rules the roster checks before a shift is booked, monitored as hours accumulate, and evidenced when the regulator, a client or an incident investigation asks how fatigue was being managed.

The rules transport operators are actually working under

• Heavy vehicle drivers (NHVR jurisdictions). The Heavy Vehicle National Law sets standard, BFM and AFM hours — the NHVR’s fatigue management requirements prescribe maximum work and minimum rest across multiple counting periods, from 5½ hours to 14 days. Operators accredited under BFM or AFM take on explicit obligations to schedule within those limits and keep records proving it.
• Chain of responsibility. Under the HVNL’s chain of responsibility provisions, schedulers, consignors and managers — not just drivers — hold duties to ensure work demands don’t induce fatigue breaches. A roster that pressures drivers into non-compliant hours implicates the business that built it.
• Everyone else in the operation. Depot crews, loaders, mechanics and non-HVNL drivers still sit under the model WHS duty to manage fatigue as a foreseeable risk — Safe Work Australia’s fatigue guidance covers shift structure, night work and cumulative hours. Rail operations carry their own fatigue obligations under ONRSR’s fatigue risk management requirements.

The common thread: these are scheduling rules. Which is why FRMS software that lives outside the roster — spreadsheets, standalone fatigue calculators, after-the-fact reports — always ends up telling you about the breach after it was worked.

What FRMS software needs to do

1. Encode your fatigue rules as rostering policies

Standard hours, BFM limits, internal policies stricter than the law, client-specific site rules — each becomes a policy in the system: maximum daily and weekly hours, minimum breaks between shifts, night-shift caps, cumulative counting windows. Humanz supports layered fatigue policies — a business-wide default, overridden per client or site where contracts demand tighter limits.

2. Gate the roster, don’t just report on it

The defining FRMS feature is the gate: when a scheduler tries to book a driver whose accumulated hours would breach the policy, the platform flags or blocks the booking at that moment. The difference between a fatigue report and a fatigue gate is the difference between discovering a breach on Monday and preventing it on Friday. That gate logic is built into Humanz’s fatigue management at the point of scheduling.

3. Count hours the way the rules count them

Transport fatigue rules use rolling windows and cumulative counting — 24-hour periods, 7-day and 14-day windows, long/night hour distinctions. Software has to count the same way, across all work the person does: the depot shift on Saturday counts against the driving shift on Monday, and travel time on remote jobs compresses rest windows. Whole-of-roster counting is what spreadsheets get wrong first.

4. Show fatigue status live, not at month-end

Coordinators need to see, per worker, how much headroom remains — who’s approaching a threshold this week, who can legally take the extra shift, who can’t. Live status turns fatigue from a compliance afterthought into an input the daily rostering decision actually uses. It also answers the 5am backfill question safely: of the available drivers, who has hours left?

5. Keep the evidence trail

Accreditation audits, chain-of-responsibility investigations and client reviews all ask the same question: show us how the schedule managed fatigue. An FRMS platform holds the answer as data — policies in force, checks run at booking, warnings raised, actions taken, actual hours worked. That record is your defence, and it assembles itself as a by-product of rostering. Pair it with digital time capture and planned-versus-actual hours reconcile automatically.

Beyond line-haul: who this applies to

FRMS software isn’t only for linehaul fleets. The same machinery serves logistics depots and last-mile operations, mining services crews on FIFO swings, civil fleets running night works, and any operation mixing driving with site work. Our broader guides cover fatigue management software in Australia generally and workforce management for logistics and transport specifically.

How Humanz handles fatigue risk management

Humanz builds FRMS into the scheduling core rather than bolting it alongside:

• Layered fatigue policies — business defaults, tightened per client or site
• Booking-time gates — non-compliant shifts flagged or blocked before confirmation
• Cumulative counting across all shift types, sites and clients in the roster
• Live fatigue status per worker, visible to schedulers as they fill shifts
• Mobile alerts — workers see warnings in the app before they accept extra work
• Audit-ready records — policies, checks, warnings and worked hours, exportable

See how Humanz manages fatigue in a transport roster →

Frequently asked questions

What is fatigue risk management software? Software that turns fatigue rules — regulatory hours, internal policies, client requirements — into live rostering controls: checking bookings against accumulated hours, alerting on approaching thresholds, and keeping the records that prove fatigue was managed.

Does Humanz enforce NHVR work and rest hours? Humanz enforces the fatigue policies you configure — daily, weekly and rolling-window limits, minimum rest between shifts, night-hour caps. Operators encode their standard, BFM or internal limits as policies and the roster gates against them. Accreditation obligations themselves remain with the operator.

What’s the difference between a fatigue report and a fatigue gate? A report tells you about a breach after the shift was worked. A gate checks the rule when the shift is being booked and stops the breach happening. Regulators and courts are considerably more interested in the second.

Can it handle drivers who also do depot or site work? Yes — hours count cumulatively across every shift type in the roster, which is exactly where manual systems fail: the Saturday depot shift that quietly breaks Monday’s driving limits.

How do drivers see their fatigue status? Through the app: warnings when they’re approaching limits, and visibility of rest requirements alongside their roster — so the conversation happens before shift acceptance, not roadside.

We run a mixed fleet across two states — can policies differ? Yes. Policies layer by business, client and site, so a WA mining contract’s tighter limits can sit alongside standard rules for east-coast work, each enforced automatically for the relevant shifts.

Scheduling drivers against prescriptive hours with a spreadsheet? Book a demo and bring your fatigue matrix — we’ll configure it as live roster gates while you watch.