A telematics or Smart On-Board Mass (Smart OBM) fault is not just a problem for the equipment supplier. If monitoring forms part of a heavy vehicle’s access conditions, a malfunction may also affect where or how that vehicle can legally operate.
In a written response to Which Way To Go on 29 October 2026, the National Heavy Vehicle Regulator (NHVR) said the effect of a malfunction depends on the permit, notice or telematics scheme attached to the vehicle. It also explained how operators’ efforts to report and repair faults are considered during compliance decisions.
That matters for operators using the Intelligent Access Program (IAP), the Telematics Monitoring Application (TMA) or TMA combined with Smart OBM. Not every GPS or fleet-management device is a regulated intelligent transport system, and not every scheme imposes the same access conditions.
What counts as a malfunction?
Under the NHVR’s published guidance, an approved intelligent transport system may be malfunctioning when it stops working, works intermittently, fails to perform a required function or produces unreliable results. Examples include missing location or mass data, a non-responsive device, and an error or failure in a connected approved OBM system or self-declaration application.
A unit does not need to be completely dead before a driver or operator treats its behaviour as a potential fault.
What should the driver do?
The NHVR says the driver should report the problem to the operator promptly, follow directions about diagnosing or repairing it, and keep a record. An operator should have a clear reporting procedure so the driver knows who to contact and what information to provide.
Useful details include when and where the fault was noticed, the vehicle’s identity, the warning or missing data, who was contacted and any immediate action taken.
For drivers of intelligent access program vehicles, section 408 of the Heavy Vehicle National Law (HVNL) includes reporting and written-record duties. The NHVR’s guidance specifies retention of malfunction reports for at least four years.
What should the operator do?
The regulator’s telematics malfunction guidance directs operators to contact their certified Application Service Provider (ASP) in the first instance. The operator should log the issue, cooperate with the provider or equipment supplier, make the vehicle available for necessary work and confirm the system is functioning again before resuming normal operations under the relevant conditions.
Operators should keep their own written record of the fault and its resolution. Sections 406 and 408 of the HVNL set out four-year record requirements for operators and drivers of intelligent access program vehicles. The NHVR also encourages keeping evidence of tickets, correspondence, diagnostics and repair action.
Reporting route requires care: the NHVR’s operational guidance directs operators to the ASP first, while section 406 of the HVNL refers to an operator reporting a malfunction to the Regulator. WWTG has not established that notifying the ASP alone discharges every statutory reporting obligation in every circumstance. An operator should check the applicable scheme and promptly confirm any additional reporting requirement with the NHVR rather than assume the provider ticket is sufficient.
The NHVR also says operators cannot report malfunctions directly to Transport Certification Australia (TCA); certified ASPs manage and log faults within that system. TCA is not the same body as the NHVR.
Does the vehicle have to stop?
There is no single answer that applies to every vehicle and every fault. The NHVR told WWTG that access to particular routes, mass concessions or operating conditions may be affected when monitoring is a condition of access and those conditions cannot be met.
A malfunction should therefore not be treated as automatic permission to continue operating under the same access arrangement. Operators need to check the relevant notice or permit and obtain appropriate direction about the trip. The response may differ between IAP, TMA and Smart OBM arrangements, and Western Australia and the Northern Territory have separate regulatory arrangements.
Does a provider fault mean the operator will be penalised?
Not automatically. The NHVR told WWTG it recognises that equipment and system failures occur. Where an operator can show it took reasonable steps to report, investigate and rectify a malfunction, those circumstances will be considered in any compliance or enforcement response.
In particular, the NHVR identified evidence of timely reporting, engagement with the ASP and reasonable repair efforts as relevant considerations.
That is not an exemption from access conditions or a promise that no action will follow. It is an explanation of how the regulator says it considers an operator’s response to a fault.
The practical record to keep
A useful fleet-level fault file should show the first alert or driver report, the time and location, the fault description, the provider case or ticket number, follow-up calls and emails, instructions given to the driver, the vehicle’s availability for repairs, any decision about access and the confirmation that the system was restored. Statutory records should include the particulars required by the relevant section of the HVNL.
This is separate from the provider’s technical obligations. In an earlier WWTG report, Austroads explained the certified TMA provider’s device and system-fault responsibilities. Those provider time frames do not automatically authorise a truck to operate while monitoring requirements are unmet.
The immediate lesson for operators is straightforward: report suspected faults early, document the response, check the vehicle’s access conditions and do not assume that a malfunction caused by the supplier removes the operator’s responsibilities.
Sources: NHVR written response to WWTG, 29 October 2026; NHVR telematics malfunction management guidance; Heavy Vehicle National Law, Chapter 7. Scheme and permit conditions should be checked for individual operations.