Nexus Track Direct.
Implementation

Fleet Telematics in Australia: Work Diaries, Chain of Responsibility, Privacy and Costs

Choosing fleet management software in Australia is mostly a compliance decision: EWD approval, Chain of Responsibility evidence, state surveillance notice rules and a retention plan. Here's what each one costs and how long rollout takes.

Nexus Track Direct editorial team · November 2026 · 12 min read

Which rules decide your shortlist before features do

If you run heavy vehicles, buying fleet management software in Australia is mostly a compliance decision with a dashboard attached. Four sets of rules decide what you can buy, what you must tell drivers and how long you keep the data. Get them wrong and you own a platform you can't legally use as planned. Get them right and the same data becomes your best defense in a Chain of Responsibility investigation.

Start with the Heavy Vehicle National Law (HVNL). The National Heavy Vehicle Regulator (NHVR) administers it in Queensland, New South Wales, Victoria, South Australia, Tasmania and the ACT. Western Australia and the Northern Territory haven't adopted it. WA manages driver fatigue through its own framework, and the NT doesn't apply the national work diary regime. A fleet running Perth to Adelaide therefore crosses two fatigue systems on one trip, and your software has to handle both.

Advertisement

HVNL fatigue rules cover fatigue-regulated heavy vehicles: broadly, trucks and combinations over 12 tonnes gross vehicle mass, plus buses over 4.5 tonnes built to carry 12 or more adults. Drivers of these vehicles must carry a work diary when working beyond a 100 km radius of their base, or when working under Basic Fatigue Management (BFM) or Advanced Fatigue Management (AFM). The diary can be the written National Driver Work Diary or an NHVR-approved electronic work diary (EWD).

The other three layers are the HVNL's Chain of Responsibility (CoR) duties, the federal Privacy Act 1988, and state and territory workplace surveillance laws, which differ more than most buyers expect. HVNL reform has been underway for years, so check current NHVR guidance before you sign. Ask each vendor whether a rule change means a configuration update or a fresh approval.

For multinational buyers: an Australian EWD isn't a US ELD or an EU digital tachograph. A device approved in another market doesn't comply here by default. Global platforms such as Geotab, Samsara and Webfleet operate in Australia, but EWD approval attaches to specific products, not brands.

Evaluating electronic work diary vendors against NHVR approval

NHVR approval covers a specific EWD system: the device or app, the back end and the provider's processes, assessed against the NHVR's standards. It doesn't approve the rest of a telematics platform. A vendor can have excellent GPS tracking and no approved EWD, or an approved EWD that runs as a separate app from its main fleet product. The NHVR publishes a list of approved EWDs and it changes as products are added or withdrawn. Check it yourself instead of trusting sales material.

Approval is the entry ticket. These criteria separate workable products:

  • Fatigue scheme support. Confirm the EWD handles standard hours, BFM and AFM (if you're accredited), plus any exemptions you operate under. AFM support varies most, because each accreditation has its own hours.
  • Offline operation. Large stretches of regional and remote Australia have no mobile coverage. The EWD must keep recording and warning drivers offline, then sync later. Ask how long it can buffer and what a driver sees near a limit with no signal.
  • Network generation. Australia's 3G networks have closed. Every device should be 4G or newer. If a vendor quotes hardware you already own, confirm it isn't 3G-only.
  • Hardware model. Some EWDs run on a fixed in-cab terminal, others on a phone or tablet the driver carries. Phone-based options cost less and follow the driver across vehicles, but you take on device management, battery life and personal-phone issues.
  • Record keeper access. You need easy exports for the three years of records the HVNL requires record keepers to hold, and drivers must be able to show recent diary records to an authorized officer at the roadside.
  • Contractor and multi-employer drivers. If subcontractors or agency drivers use your vehicles, confirm how their records are separated, and who counts as record keeper when a driver works for two operators in one week.

Red flags: a vendor that can't name its approved EWD product and version, "approval pending" offered as a reason to sign now, or a contract with no exit clause if approval is suspended. Be wary too of any claim that the EWD works in WA exactly as it does on the east coast.

Our position: for most fleets of 20 to 150 trucks, an EWD built into the same platform as tracking and maintenance beats a standalone app. You get one driver login and one data set for CoR reviews, and payroll needs a single integration. Standalone EWDs make sense when you lease prime movers with factory telematics you can't replace, or when drivers rotate across fleets you don't control.

Using telematics data as Chain of Responsibility evidence

Since the 2018 reforms, every party in the chain has a primary duty to ensure the safety of its transport activities so far as is reasonably practicable. That covers consignors, consignees, loading managers, loaders, schedulers, operators and employers. Executives carry a personal due-diligence duty. Top-tier penalties run into the millions of dollars for corporations, and individuals can face jail for the most serious offenses.

Telematics does two things for chain of responsibility compliance. It produces evidence that you took reasonable steps, and it produces evidence of what you knew. The second catches people out. If your platform flagged a driver exceeding the speed limit dozens of times last quarter and nobody acted, that log works against you. Buying the data creates an obligation to review it.

A defensible CoR setup usually includes:

  • Defined alerts with owners. Speeding, fatigue-limit warnings, harsh braking and speed limiter tampering each go to a named role with a response time. A shared inbox nobody reads doesn't count.
  • Schedule-versus-actual reporting. Schedulers and customers can breach CoR by setting delivery windows that can't be met legally. Compare planned trip times against EWD-recorded work and rest, and keep the reports.
  • Mass and loading records. Onboard weighing integrations or load-restraint checklists in the driver app give loaders and consignors proof of their own duties.
  • Regular board-level reporting. Due diligence means directors see safety metrics, not just assurances. A quarterly fatigue and speed summary from telematics is the simplest evidence of oversight.

If you run Performance Based Standards combinations or need higher-mass or restricted-access routes, look at the National Telematics Framework run by Transport Certification Australia (TCA). Road managers may require certified devices for Intelligent Access Program (IAP) or similar applications, and not every telematics unit is certified. Put this in the RFP early. Swapping hardware later wipes out the savings from a cheaper first choice.

Privacy Act duties and state workplace surveillance laws

The Privacy Act and its Australian Privacy Principles (APPs) generally apply to organizations with annual turnover above AUD 3 million, plus some smaller businesses in specific categories. Private-sector employers get an employee records exemption for records directly related to the employment relationship. Don't lean on it. It doesn't cover contractors, owner-drivers, agency drivers or job applicants, nor data you share with customers, such as live tracking links. APP 8 also makes you accountable for overseas disclosure, which matters when a vendor hosts data or runs support outside Australia. Ask where data is stored, where support staff sit, and which sub-processors can access location and video.

Two recent changes matter. The 2024 privacy amendments created a statutory tort for serious invasions of privacy, now in force. They also add transparency duties for automated decision-making, scheduled to start in December 2026. If your platform automatically scores drivers and those scores feed rostering or discipline, expect to explain that in your privacy policy. The Notifiable Data Breaches scheme already applies to covered entities holding location and video data.

The bigger operational differences sit in state and territory workplace surveillance laws. NSW and the ACT have dedicated workplace surveillance statutes with specific notice rules. Most other jurisdictions regulate tracking and listening through general surveillance-device laws. The table is a starting point, not legal advice. Have an employment lawyer in each state where you operate confirm your notices.

JurisdictionMain legislationWhat it means for vehicle telematics
NSWWorkplace Surveillance Act 2005Generally 14 days' written notice before surveillance starts, unless the employee agrees to less; visible notice on tracked vehicles; signs and visible cameras for camera surveillance
ACTWorkplace Privacy Act 2011Written notice, generally 14 days, plus consultation and a surveillance policy; notice on tracked vehicles
VictoriaSurveillance Devices Act 1999Restricts tracking devices without consent; no dedicated workplace act, though a parliamentary inquiry has recommended one
South AustraliaSurveillance Devices Act 2016Tracking and listening devices generally need consent
Western AustraliaSurveillance Devices Act 1998Tracking devices generally need consent; in-cab audio restricted
Northern TerritorySurveillance Devices Act 2007Consent-based rules for tracking and listening devices
QueenslandInvasion of Privacy Act 1971Mainly covers listening devices; in-cab audio is the main risk
TasmaniaListening Devices Act 1991Mainly covers listening devices; in-cab audio is the main risk

For a national fleet, build to the strictest common standard: 14 days' written notice to every driver, signed acknowledgment, visible vehicle stickers, and a written policy on what's collected, why, who sees it and how long it's kept. Turn off in-cab audio on driver-facing cameras unless you have a documented reason and consent. Audio is where listening-device laws bite in every state. If an enterprise agreement or modern award requires consultation before new technology, that consultation must happen before the notice period starts.

A retention schedule that holds up

Retention differs by record type, so set it per data class rather than with one blanket setting:

  • Work diary records: at least three years, as the HVNL requires of record keepers.
  • Hours used as time and wage records: Fair Work rules generally require seven years for employee time and wage records. If telematics hours feed payroll, keep them that long.
  • Raw GPS trails: 12 to 24 months is typical. Holding detailed location data longer raises breach exposure and is harder to justify under the APPs.
  • Video events: 30 to 90 days, unless an event is flagged for an incident, claim or investigation. Then hold it until the matter and any limitation period close.

Telematics cost per vehicle in Australia

Vendors quote in AUD, usually excluding GST, and most bundle hardware into 36- to 60-month contracts. The figures below are indicative USD conversions of typical 2026 market ranges. They vary widely by fleet size, contract length and negotiation, and local pricing differs, so confirm with vendors before you budget.

Cost itemTypical 2026 range (USD)What drives the price
Basic GPS tracking unit$60 to $200 per vehicle, or $0 upfront when bundledBundling, CAN-bus or engine data access, satellite fallback
EWD-capable in-cab terminal or rugged tablet$300 to $900 per vehicleFixed terminal or tablet, screen size, mounting
AI dashcam (road- and driver-facing)$250 to $700 per vehicleChannel count, onboard AI, storage
Professional installation$80 to $250 per vehicleMetro or regional location, number of devices, after-hours work
Tracking subscription$15 to $30 per vehicle per monthData plan, reporting depth, API access
Tracking plus EWD and compliance$30 to $60 per vehicle per monthFatigue schemes supported, per-driver EWD fees
Full suite with video telematics$45 to $90 per vehicle per monthVideo storage, event review services, coaching tools
Satellite fallback for remote routesAdds $10 to $40 per vehicle per monthMessage volume and reporting frequency

Watch how EWDs are billed. Some vendors charge per driver, not per vehicle. That's cheaper for single-shift fleets and noticeably dearer for double-shifted prime movers or a large casual driver pool. Costs that surface after signing include deinstall and reinstall fees when you rotate vehicles, early-termination clauses that bill remaining months in full, API or payroll integration fees, and hardware refresh charges when a network change obsoletes your devices.

Hypothetical worked example: say a 60-truck regional distributor wants tracking, an integrated EWD and dual-facing cameras on a 48-month contract. Hardware and installation net of any vendor contribution come to $450 per truck, or $27,000. A subscription at $65 per truck per month adds $46,800 a year. Satellite fallback on 15 remote-route trucks adds about $4,500 a year. Year one lands near $78,000, and later years near $51,000. Averaged over the contract, that's roughly $970 per truck per year. Weigh it against the admin time saved on written diary audits and the cost of one CoR prosecution or a serious fatigue incident.

A realistic rollout timeline for a mid-size fleet

Most delays come from people and legal steps, not installs. Fitting a device takes a few hours per truck at most. Notice periods, consultation and driver training take weeks. For 30 to 150 heavy vehicles across more than one state, plan on roughly 14 to 20 weeks from shortlist to full go-live.

WeeksPhaseKey outputs
1 to 3Requirements and shortlistFatigue schemes, states, TCA or IAP needs, data-residency questions; check the NHVR approved EWD list
4 to 6Trial and contractFive- to ten-truck pilot on your worst-coverage route; negotiated exit, data-return and price-lock clauses
5 to 8Privacy and workforcePrivacy impact assessment, surveillance policy, consultation under any enterprise agreement, written notices issued
8 to 10Notice period and setup14-day notice runs; user roles, alert owners, retention settings and payroll integration configured
10 to 16Staged install and trainingDepot-by-depot installs; driver EWD training, with written diaries kept on hand during transition
16 to 20Stabilize and reviewFirst CoR alert review, data-quality checks, retire written diaries where the EWD is confirmed working

Two sequencing rules matter most. Don't install cameras or switch on tracking before the notice period ends. In NSW and the ACT, starting early can make the surveillance unlawful. And don't retire written diaries the day the EWD goes live. Keep them in trucks for the first few weeks so drivers can fall back if a device fails and stay compliant.

The decision rule: shortlist only vendors whose EWD is on the NHVR's approved list for the fatigue schemes you actually use, pilot on your worst-coverage route, then pick the platform whose retention controls, alert ownership and contract terms you'd be comfortable explaining to an NHVR investigator.

Frequently asked questions

Is an electronic work diary mandatory in Australia?

No. Under the HVNL, drivers of fatigue-regulated heavy vehicles can still use the written National Driver Work Diary or an NHVR-approved EWD. Some operators require EWDs internally, and some customers make them a contract condition. The choice usually comes down to admin savings and record accuracy.

Do work diary rules apply in Western Australia and the Northern Territory?

Not the HVNL work diary regime. WA manages heavy vehicle fatigue through its own framework, and the NT hasn't adopted the national fatigue rules. Fleets crossing those borders need software and procedures that can handle each regime.

How much notice do drivers need before we turn on tracking or cameras?

In NSW and the ACT, workplace surveillance laws generally require 14 days' written notice, plus visible notices on tracked vehicles. Other states rely mainly on consent-based surveillance-device laws. Most national fleets give 14 days' written notice and collect signed acknowledgment everywhere, then have an employment lawyer confirm the approach.

Does the Privacy Act employee records exemption cover our telematics data?

Only in part. It can cover records directly related to employing your own staff. It doesn't cover contractors, owner-drivers, agency drivers or data shared with customers. Treat telematics data as personal information and handle it under the Australian Privacy Principles.

How long should we keep telematics and work diary data?

Record keepers must keep work diary records for three years under the HVNL. Hours used for payroll are generally held for seven years under Fair Work record-keeping rules. Raw GPS trails and video can usually be held for shorter periods unless they relate to an incident or claim.

What does fleet management software cost per vehicle in Australia?

Typical 2026 ranges are about USD 15 to 30 per vehicle per month for basic tracking, USD 30 to 60 with an integrated EWD, and USD 45 to 90 with video telematics. Hardware and installation often add USD 150 to 1,000 per vehicle unless bundled into the contract. Pricing varies by contract length and fleet size, so get written quotes.

Written by the Nexus Track Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.