10 March 2021
Registered Industry Codes of Practice (RICPs) are codes developed by any Chain of Responsibility (CoR) party that are registered by the National Heavy Vehicle Regulator (NVHR) and set out detailed and practical standards and procedures to help these parties comply with the Heavy Vehicle National Law (HVNL).
Why develop or adopt a RICP?
RICPs operate on a voluntary ‘opt-in’ basis. We set out the advantages that arise from developing and adopting RICPs below.
RICPs translate HVNL requirements into workable, business solutions
RICPs are a useful tool for any party in the CoR or industry group to set out practical ways to achieve compliance with HVNL requirements. As they are developed by industry participants, they offer industry-focused solutions to compliance issues.
For example, the Master Code is a RICP administered by Safe Trucking and Supply Chains Ltd. It focuses on compliance with speed, fatigue, mass, dimension and loading requirements, as well as compliance with vehicle standards.
Rather than simply stating the HVNL requirements for various CoR parties, the Master Code offers options and procedures for CoR parties to implement to avoid these breaches. Rather than stating, “don’t allow a driver to drive in breach of work and rest options”, it tells operators, “If you become aware the driver is impaired by fatigue, stop the driver immediately, and arrange for the drier to have a rest break” (page 50). It further prompts the operator to establish escalation processes to deal with drivers impaired by fatigue.
RICPs are a buffer to charges
RICPs are admissible as evidence in proceedings as to whether or not a duty or obligation under the HVNL has been complied with according to section 632A of the HVNL. If a HVNL contravention arises that is covered by an RICP, the Court can have regard to the RICP to ascertain the nature of a hazard or risk, risk assessment or risk control and to also determine what would have been reasonably practicable for the accused to do in response to such risks and HVNL obligations.
Therefore, if a party voluntarily adopted a RICP to set out its standards and procedures for compliance with a particular HVNL obligation and that party were charged for contravening that same obligation, it could produce the RICP as evidence in the proceedings to support a finding that it complied with that particular HVNL obligation.
RICPs have the capacity to clarify regulatory grey-zones
An industry code of practice that is tabled for development is the Australian Livestock and Rural Transporters Association’s Managing Effluent in the Livestock Supply Chain code of practice (Effluent Management Code). The issue of restraining livestock effluent has long been an industry concern, particularly where effluent discharge is an inherent risk of transporting livestock and drivers may nonetheless be charged in respect of a failure to contain their loads.
Arguably a code addressing this ongoing concern has the capacity to assist industry to comply with effluent load restraint requirements under the HVNL and to obtain the NHVR’s tick of approval to their proposed steps for compliance with that obligation, while also giving industry (in particular drivers and operators) a buffer to defend against charges for failures to restrain effluent.
As the Effluent Management Code may assist CoR parties in the livestock transport supply chain to clarify their HVNL obligations, the same may be said of the capacity for RICPs to assist industries facing regulatory grey-zones to clarify their HVNL obligations.
How do you develop and register an RICP?
A RICP must comply with the NHVR’s Industry Codes of Practice Guidelines for Preparing and Registering Industry Codes of Practice (Guidelines).
Before formally approaching the NHVR, it is useful for code developers to consider the target areas the code will cover, its purpose and do an industry call out to ascertain whether a code would be adopted if introduced. This is because there are costs associated with developing, registering and maintaining a code.
Formal steps to register a code involve:
Author: Nathan Cecil
The information in this publication is of a general nature and is not intended to address the circumstances of any particular individual or entity. Although we endeavour to provide accurate and timely information, we do not guarantee that the information in this article is accurate at the date it is received or that it will continue to be accurate in the future.