Australian Truck Fatigue Planner
Lay out a driver's work and rest intervals on a timeline, check the records for the things that quietly go wrong, and plan ahead from what has actually been recorded. It encodes no fatigue rule and no maximum work hours - it analyses the intervals you enter and refuses to turn a gap in your records into a favourable answer.
Australia has no single rule set, so this is required.
The moment every window is counted back from.
Optional.
Add a recorded interval
Optional.
Runs entirely in your browser. Your input is not uploaded or stored.
Before you rely on this: First-pass guide only. Verify safety-critical or regulated work against the relevant standards, your project requirements and a qualified professional.
How to use this calculator
- On the Timeline tab, enter each interval with its kind - driving, other work, a break from driving, stationary rest, moving sleeper rest, or unknown.
- The Checks tab reports what the intervals themselves say, including where two rests have been treated as one and where the record is incomplete.
- Plan ahead works forward from the recorded history against a limit you enter.
- Rules holds the scheme information you provide; History keeps past entries in this browser only.
How it works
The tool models what a recorded interval means, which is the part that is the same under every scheme and the part most implementations get wrong.
A gap between two periods of driving is not automatically rest. Unless something records what happened in it, it is unknown, and unknown is not counted in your favour.
Two separate rest periods are not one continuous rest. Adding them together produces a continuous-rest figure that never happened, so the tool keeps them separate.
An incomplete history cannot produce a complete long-period answer, however short today's shift was. If the records do not cover the period being assessed, the tool says the answer is not available rather than computing one from the part it can see.
Worked example
Worked example. A driver records driving from 06:00 to 10:00 and again from 12:00 to 16:00, with nothing recorded between. A naive tool counts two hours of rest. This one counts two hours of unknown, because nothing in the record says the driver rested - and the difference between those two readings is exactly the kind of assumption that makes a fatigue calculation worthless.
Common mistakes
- Expecting it to say whether a driver is compliant. It holds no fatigue rule, so it cannot and does not.
- Treating an unrecorded gap as rest.
- Adding two rest periods together to reach a continuous rest requirement.
- Assuming a short shift today means a long-period figure is fine, when the records for that period are incomplete.
Tips
- Record the intervals you actually have, including the unknown ones. Leaving a gap out is what produces a falsely favourable result.
- Check continuous rest separately from total rest. Two short rests are not one long one.
- If the tool says an answer is unavailable because the history is incomplete, that is the answer - filling the gap with an assumption would change it to a number nobody can stand behind.
Frequently asked questions
Does this tell me whether a driver is compliant?
No. It encodes no fatigue rule, no maximum work hours and no required rest, under any scheme or jurisdiction. It analyses the intervals you enter. Compliance is determined against the operative instrument and your accreditation, not against this page.
Why are there no Standard Hours, BFM or AFM limits built in?
Because encoding them requires transcription from the operative instruments and validation by an independent competent reviewer, and that review has not been done. A fatigue limit that is subtly wrong is a safety problem rather than a bug, so the tool holds none rather than holding an unreviewed one.
Why does it not count a gap as rest?
Because nothing in the record says it was. A gap is an absence of information, and treating an absence as rest turns missing data into a favourable assumption. That is the single failure this tool exists to avoid.
Why will it not add two rests together?
Because a continuous rest requirement means continuous. Two separate periods summed to a total produce a figure for something that did not happen. The tool reports them as what they are.
Does it grant or support accreditation?
No. It does not grant accreditation and nothing in it is checked against an accreditation scheme.
Does my data leave the browser?
No. Everything runs in this page on your device, and history is kept in local storage on this device only.
Related tools
- Australian Truck Weight & Load Planner
- Haul Road Grade Resistance Calculator
- Haulage Cost Estimate Calculator
- Decibel Exposure Time Calculator
- Fatigue Break Calculator
- Night Shift Recovery Calculator
Explore more in Time, Date, Roster & FIFO.
Cite this tool
Zerdly. (2026). Australian Truck Fatigue Planner. Retrieved from https://www.zerdly.com/tools/australian-truck-fatigue-planner/
Tip: Enter any known values to calculate the remaining results.
Designed to run locally in your browser. Tool inputs are not intentionally stored by Zerdly unless stated otherwise.



