Fleet and equipment management for forestry

Yes, that's the whole point of Chain of Responsibility: every party in the supply chain carries a duty, not just the driver or the operator who owns the truck. If you bring a contractor's vehicles onto the same platform, their speed, location and service records sit alongside your own, so you have the same evidence of oversight for both. The duty itself still rests with each party, EROAD just gives you the records to show you've met yours. 

A fatigue camera watches for the signs a driver often won't notice in themselves, like yawning or eyes closing, and gives them a voice alert on the spot. On a log truck, pairing it with the Seat Shaker adds a physical alert that's harder to sleep through, and a third-party monitoring service can pick up a severe fatigue event and start your escalation process even if nobody's in the office at the time, which matters on an overnight or early-morning run.

On a quiet haul road, your evidence is the data: GPS location and trip history, driving events from telematics, and video from the road and cab if a camera's fitted. On compatible heavy vehicles, CAN Bus data adds engine speed and pedal position at a hard braking event, so you're not relying on the driver's account, or anyone else's, to work out what happened. 

Yes. Off-road distance is captured by GPS automatically as each truck works, and auxiliary equipment running rates can be set once rather than estimated trip by trip. That record is what backs an FTC claim, and the ATO has confirmed via Class Ruling 2026/69 that an EROAD-generated report using the Ehubo2 can be used as an official record for FTC purposes. 

No, and it isn't meant to. Logmaster is still how NHVR and Western Australian fatigue rules get met, recording hours and breaks as a proper Electronic Work Diary. EROAD runs alongside it, giving you telematics, location, driver safety and in-cab fatigue detection, so the compliance side and the operational side are covered by the tools built for each job.