Vehicle Standard (Australian Design Rule 35/03 – Commercial Vehicle Brake Systems) 2009

The text organises braking requirements around a set of defined systems and measurable performance outcomes. Key technical concepts are:

• Service Brake System: The primary braking system must act on all road wheels via a single driver control and must incorporate wear compensation devices and failure indicators. For categories MB and MC, an Electronic Stability Control system is mandatory (clause 4.1.1 and Appendix 2 cross‑reference). The Service Brake must meet energy/retardation requirements when towing trailers using compressed air (clause 4.1.9).

• Visible and Audible Indicators: The standard requires visible indicators for service brake failures and in many cases audible indicators where single Brake Power Units are employed (clause 4.2, 4.1.11). The visible indicator must operate under precisely‑defined fault conditions, with labelling rules (e.g., “BRAKE” or ISO symbol), location bounds and light colour specifications (clauses 4.2.1-4.2.12).

• Parking Brake System: A separate parking brake control retained mechanically in the applied position is required; where vehicles tow trailers using positive air pressure the parking brake operation must cause the trailer supply line pressure to fall below 35 kPa and be restored on release (clauses 4.3.1-4.3.6).

• Secondary Brake System: Vehicles must have a secondary brake system. For hydraulic systems, split circuits are required; spring brake systems must have stored energy capacity sufficient to permit repeated applications; protection must be automatic if a trailer becomes disconnected (clauses 4.5 and subclauses).

• Brake Power Units and Stored Energy: For systems using stored energy or brake power units (positive pressure air or vacuum assist), the standard specifies minimum combined volumes, pressure gauge visibility to the driver, test connections and recharge time calculations (clauses 4.7.1-4.7.6 and 4.7.3-4.7.5).

• Antilock (ABS) and Electronic Stability Control (ESC): Appendix 1 sets dynamic and tell‑tale requirements for vehicles with ABS (locking behaviour at specified speeds, warning lamp rules, trailer electrical connections). Appendix 2 sets detailed functional, performance and test procedures for ESC, including the Sine‑with‑Dwell manoeuvres, performance thresholds for yaw rate and lateral displacement, tell‑tale requirements, and documentation requirements for complex electronic control systems and simulation validation (Appendix 2 and its Attachments).

• Performance Tests and Metrics: A suite of dynamic tests (Service Brake effectiveness lightly laden and laden, secondary brake tests, partial failure tests, service brake fade, parking test, actuation time and compatibility tests) is specified in Table 1 and Part 7. The Service Brake Compatibility Test uses an Established Retardation Coefficient (ERC) derived from initial speed, stopping distance, stopping time and response time; constants and formulas are provided (see Service Brake Compatibility Test provisions and Table 3).

• Equivalence and Alternative Standards: The standard allows conformity to certain UNECE Regulation No. 13 versions and UNECE GTR No. 8 to be treated as equivalent to parts of ADR 35/03, subject to specified exemptions (clause 8.1-8.3). Conformity of production assessments may be required for certain annex compliance (clause 8.1.2.2).

Structural cross‑references are frequent: vehicle categories and definitions are cross‑referenced to Vehicle Standard (Australian Design Rule Definitions and Vehicle Categories) 2005 and Appendix 2 definitions (clause 3). The instrument also relies on international technical standards where recognised (clause 4.1.6, referring to SA, SAE, BS, JIS, DIN, ISO, ECE; clause 4.1.8 refers to AS 4945‑2000).

Together, these concepts convert the high‑level objective of safer braking into detailed component, instrumentation, test and documentation obligations for manufacturers and technical services.

Primary duties fall on vehicle manufacturers and those that seek approval to supply new vehicles into the Australian market. The standard repeatedly addresses the ‘Manufacturer’ and requires them to design, document and, where appropriate, supply test data to the ‘Administrator’ (see clause 4.1.10.2 and numerous documentation provisions in Appendix 2). The Administrator appears as the recipient of certification, data, or simulations; the standard does not define the Administrator’s powers in detail but anticipates an administrative role in assessing compliance (see multiple clauses referencing provision to the ‘Administrator’).

Other directly affected parties are:

• Type‑approval technical services and test laboratories, which must perform the full suite of performance tests under the specified ambient and test surface conditions, instrument vehicles and produce reports as set out in Parts 6-7 and Appendix 2 attachments.

• Specialist suppliers and component manufacturers, including suppliers of brake power units, reservoirs, valves, polarized couplings, ABS and ESC modules, who must meet recognized international or national standards where required and produce components compatible with the vehicle design (clause 4.1.6, 4.1.8).

• Trailer manufacturers and operators of heavy towing combinations: the ADR specifies compatibility requirements when a vehicle is equipped to tow trailers using air at positive pressure, sets tests for supply and control lines, and imposes electrical connector requirements for ABS/ESC signalling to trailers where ATM exceeds 4.5 tonnes (clauses 4.1.9-4.1.10, Appendix 1 clause 1.3).

• Vehicle importers and remanufacturers that present vehicles for entry as new models or individual vehicles after the relevant dates (clauses 2.1-2.2). The staged applicability dates mean some actors who import or certify new models before 1 November 2011 may have had different obligations to those placing models on the market after the date.

• Fleet managers and purchasers indirectly: the standard effectively requires vehicles to incorporate specified systems (ABS/ESC where applicable, visible indicators, reservoir sizes) so purchasers will receive vehicles built to meet these specifications. The cost of design, testing and certification is borne by manufacturers and typically priced into vehicles.

• Regulators and inspection authorities: while the ADR itself does not set out enforcement penalties, it creates a technical benchmark that regulators enforce under the enabling Motor Vehicle Standards Act 1989 (header) and that Conformity of Production procedures will monitor (clause 8.1.2.2).

Who pays: the instrument’s obligations (design, testing, documentation, component changes, software validation) are directed at manufacturers. Where the manufacturer elects to rely on alternative approvals (UNECE or GTR), there is an option to transfer testing and certification costs to the pathway chosen, but the manufacturer carries the administrative burden to show equivalence (clause 8).

Who decides: technical conformity is decided through testing and documentation submitted to the Administrator and assessed under the ADR process. The manufacturer can elect to demonstrate conformity by ADR testing, UNECE approvals or validated simulation models for ESC (Appendix 2 Attachments 1-3), but the Administrator retains the assessment role in all instances.

Duties imposed by the standard are technical, documentary and procedural.

Design and equipment duties (Part 4)

• Equip every vehicle with a Service Brake System operable on all road wheels through a single Control within reach of the driver (clause 4.1.1). For MB and MC categories, include ESC meeting Appendix 2 requirements (clause 4.1.1.1).
• Provide visible indicator(s) for service brake failure that meet the exact activation conditions, labelling, placement and check‑of‑function requirements (clauses 4.2.1-4.2.12).
• Ensure parking brake controls are separate from service brake controls, retained mechanically in the applied position, compensating for wear, and accessible (clauses 4.3.1-4.3.4). For vehicles towing trailers using air at positive pressure the parking brake must vent the trailer supply line below 35 kPa upon application and restore it upon release (clauses 4.3.5-4.3.6).
• Fit reservoirs, condensate drain valves and labelling specifying fluid type, with minimum reservoir capacity rules tied to piston displacement and “fully‑worn, fully‑applied” criteria (clauses 4.1.12, 4.6.1-4.6.2).
• Where Stored Energy or Brake Power Units are used, meet minimum combined volumes and recharge performance timings, and provide driver‑visible pressure gauges accurate to within 7 per cent of the cut‑out pressure (clauses 4.7.2, 4.7.3, 4.7.5).

Performance and testing duties (Parts 5-7)

• Demonstrate compliance in the test suite set out in Table 1 and associated particulars, including lightly laden and laden effectiveness, partial failure tests, secondary brake tests, fade tests, parking brake tests, actuation time and service brake compatibility tests (Parts 5-7 and Table 1).
• Ensure test instrumention checks, ambient conditions, tyre and brake element specifications, gear selector positions and deceleration conditions adhere to the General Test Conditions (Part 6).

Documentation duties (Appendix 2)

• For vehicles with ESC or complex electronic systems, supply system diagrams, operational explanations, logic diagrams, understeer information and simulation validation documentation where simulation is used (Appendix 2 paragraph 3.7 and Attachments 1-3). The manufacturer must keep simulation reports and validation materials (Attachments 2-3).

Trailer and towing duties

• For vehicles with Rated Towing Capacity > 4.5 tonnes, either certify the vehicle for trailer brakes using positive air pressure or supply sufficient data to allow the Administrator to model the vehicle’s Service Brake System under laden braking conditions (clause 4.1.10.1-4.1.10.2).

Rights, options and equivalences

• Manufacturers may rely on recognized international or national standards for components where such standards exist (clause 4.1.6).
• Equivalence routes exist: compliance with UNECE Regulation No. 13 (series of amendments) or UNECE GTR No. 8 is deemed equivalent for many technical requirements, subject to enumerated exceptions and conform‑production provisions (clause 8.1-8.3).
• ESC compliance may be demonstrated by validated computer simulation in lieu of full physical testing, provided the simulation tool is validated and the simulation report is available (Appendix 2 Attachments 1-3).
• For variants of previously tested vehicles, ‘approved’ calculations based on component or subassembly tests can substitute for full vehicle tests where the effect of changes is known (clauses 4.1.9.4, 4.1.10.3).

Procedural duties

• Sensors and tell‑tales must operate as specified during ignition checks and under fault conditions, and failure indicators must remain operative whenever the ignition is in the “engine on” position and the fault remains uncorrected (clause 4.2.1 and 4.2.6).
• Where multiple sensors are required they may be interconnected to actuate one visible indicator (clause 4.2.3).

What the standard does not do

• It does not set criminal or civil penalties; those enforcement mechanisms are in the enabling legislation (header). It also does not itself supply a step‑by‑step administrative process for approvals; it presumes an Administrator and conformity procedures external to the instrument.

The ADR text supplied does not create or list pecuniary penalties, sanctions, or a detailed enforcement regime. The instrument is made under section 7 of the Motor Vehicle Standards Act 1989 (header) and repeatedly references the ‘Administrator’ as the entity to receive certification, data or demonstrations of compliance (see clauses 4.1.10.2 and Appendix 2 paragraphs 3.7, Attachments 2-3). Enforcement powers, sanctions, and administrative procedures are therefore matters reserved to, or specified in, the enabling Act and any procedural instruments under that Act, not in this ADR itself.

The standard, accordingly, provides the technical bench‑marks and the documentary evidentiary requirements that the Administrator will use when making compliance decisions. It anticipates enforcement in the following practical ways:

• Type approval and conformity of production: the ADR includes references to conformity of production assessments for certain UNECE Annexes where equivalence is claimed (clause 8.1.2.2). That means regulators will expect ongoing production checks and manufactured vehicles to remain consistent with approved designs.

• Required documentation and test evidence: Appendix 2 and its Attachments require manufacturers to retain and, if requested, provide detailed system diagrams, simulation validation reports and test reports. These documents will be the primary material the Administrator uses to accept or reject compliance claims (Appendix 2 paragraphs 3.7, Attachments 1-3).

• Failures identified at test: the Table 1 tests and specific actuation, pressure and performance thresholds provide objective pass/fail criteria that test laboratories, type approval bodies and the Administrator will use. For example, service brake actuation times (clause 7.12), supply line pressure response (clause 7.12.6), or ESC yaw rate thresholds (Appendix 2 paragraph 3.1) are numeric criteria.

Risks in enforcement and implementation

• Because the standard relies on external instruments (ISO, AS, UNECE, GTR) and detailed lab measurements, enforcement requires suitably equipped and skilled technical services. The requirement that simulation tools be validated (Appendix 2 Attachment 2) increases administrative burden on regulators to assess validation reports and to accept simulation results.

• The standard’s specification of precise activation thresholds for tell‑tales and trailer pressure (e.g., 35 kPa, 450 kPa, 0.15E/sec) means that enforcement may hinge on transient measurements; disputation over test set‑up, instrument calibration and vehicle configuration is possible in practice.

What the ADR does not specify

• Penalty amounts, suspension or seizure powers, administrative appeal routes, or the procedural steps for withdrawl/refusal of type approval are not in this text. Those are governed by the Motor Vehicle Standards Act 1989 and related instruments, which must be consulted for enforcement outcomes.

The standard is explicitly cross‑referential. It does not operate in isolation.

References to other ADRs and definitions

• Vehicle category definitions and terms are defined in Vehicle Standard (Australian Design Rule Definitions and Vehicle Categories) 2005 and Appendix 2 of this instrument (clause 3). Several clauses accept compliance with other ADRs: vehicles of category MB, MC or NA complying with ADR 31/… are accepted as complying with parts of this standard (clause 2.4). Vehicles of certain LEG categories may comply with ADR 33/… (clause 2.5). Vehicles certified to ADR 35/04 (or later) need not comply with this rule (clause 2.8). This creates a network of ADRs where compliance with one instrument can discharge obligations under another.

UNECE and GTR equivalence

• The ADR allows conformity to UNECE Regulation No. 13 (braking) as equivalent to this ADR for most categories except MB, MC and LEG, subject to completing certain UNECE annex compliance during conformity of production where needed (clause 8.1). It also accepts UNECE Regulation No. 13 amendment series 11 Annex 21 for stability functions as equivalent to Appendix 2 for ESC in vehicles >1,735 kg (clause 8.2). The ADR deems UNECE Global Technical Regulation No. 8 on ESC equivalent to Appendix 2, but it lists specific exemptions to GTR No. 8 provisions for Australian application (clause 8.3 and subclauses 8.3.1-8.3.1.6). These equivalence clauses reduce duplication for manufacturers but create a compliance matrix where particular UNECE or GTR clauses are exempted and therefore cannot be relied on , careful mapping is required.

Standards and technical artifacts

• Where industry standards exist the ADR directs compliance to recognized international or national standards such as SA, SAE, BS, JIS, DIN, ISO and ECE (clause 4.1.6). It specifies AS 4945‑2000 for polarized brake line couplings (clause 4.1.8). For tell‑tales and symbols it references ISO 2575‑2000 for control and indicator symbols (clauses 4.2.10 and 4.3.4).

Interaction with enabling Act and administrative law

• This ADR is made under the Motor Vehicle Standards Act 1989 (header). Administrative decisions, approvals, issuance of certificates, and enforcement follow that Act and subordinate instruments. The ADR anticipates the Administrator receiving documentation and data (e.g., clause 4.1.10.2) but does not itself set out procedural steps, timeframes or appeal processes. Those rights and processes will exist under the enabling legislation.

Compatibility with vehicle configurations and other rules

• The ADR anticipates complex vehicle configurations (retractable axles, multi‑unit articulated vehicles) and provides rules on configurations, required tests and exemptions (clauses 2.7, 6.14 and associated test provisions). It interacts with mass and axle load regulatory rules via Table 2 Group ‘Axle Load’ limits which prescribes maximum axle group loads used for testing and for compatibility tests.

Practical consequence of cross‑referencing

• The ADR’s cross‑referencing creates practical compliance choices for manufacturers: meet ADR tests directly; rely on UNECE approval; or use GTR/ISO standards where permitted. But equivalence is conditional, and the ADR specifically lists some non‑applicable UNECE or GTR clauses. This means manufacturers must track both ADR text and the exact version/annexes of the external rules they rely upon. Conformity of production and documentation requirements in Appendix 2 create ongoing interactions with regulatory oversight.

The standard text includes a Table of Instruments and a Table of Amendments setting out its formal compilation history.

Key instrument dates (Table of Instruments)

• Original instrument: Vehicle Standard (Australian Design Rule 35/03 - Commercial Vehicle Brake Systems) 2009, registered 29 June 2009 and commenced 30 June 2009.
• Amendment 1: Vehicle Standard (Australian Design Rule 35/03 - Commercial Vehicle Brake Systems) 2009 Amendment 1, registered 16 September 2014 and commenced 17 September 2014.
• Most recent compilation amendment in the file: Vehicle Standard (Australian Design Rule) Amendment Instrument 2021 (No.1), registered 13 May 2021 and commenced 14 May 2021. The compilation indicates the document is up to date to that instrument (Prepared Date: 14 May 2021).

Table of Amendments (summary of clause changes)

• Clause 0.2 was deleted as a result of the Legislation Act 2003 , section 48D (Table of Amendments).
• Clause 2.8 was added (abbreviated as ad) by the 2014 Amendment , that clause exempts vehicles certified to ADR 35/04 or later from this rule.
• Clause 4.7.5.2 was removed and replaced (rr) by the 2021 Amendment Instrument (No.1).

Notes on compilation and effect

• The compilation notes that this copy includes the instruments in the Table of Instruments and indicates which clauses have been added, amended or deleted (endnotes). The ADR therefore must be read in conjunction with the instruments listed and the enabling Act for full effect and interpretation.

Implications for compliance and historical tracing

• Stakeholders must review the specific amending instruments when tracking the rule’s history or when assessing compliance obligations for a vehicle manufactured during the transition windows (new model date 1 November 2011 and all vehicles 1 November 2013 as in clause 2.1-2.2). The amendment that added clause 2.8 (2014) changed the scope by explicitly exempting vehicles certified to a later ADR (35/04), which can materially affect whether a particular vehicle must meet ADR 35/03 obligations.

Record keeping

• Manufacturers and technical services should retain the amending instruments and the ADR compilation history to demonstrate which version of the rule applied at the time of a model’s first production date, because the ADR distinguishes ‘new model’ and ‘all vehicles’ dates and provides equivalence routes that have specific version and annex dependencies.

The standard text supplied contains no judicial decisions, declared cases or litigation history. It does not cite any court or tribunal authority, nor does it record any disputes or judgments arising from its provisions.

What this means in practice

• Any enforcement disputes, administrative reviews, or judicial challenges arising from the application of this ADR would be handled under the Motor Vehicle Standards Act 1989 and the relevant administrative law frameworks, but no such cases are referenced within this ADR text itself. Users seeking precedent or litigation-driven interpretation will need to search external judicial decisions under the enabling Act or related administrative decisions; this ADR does not provide such material.

Implication for advisors

• Legal and compliance advisers must rely on the ADR’s text, the enabling Act, administrative instruments and any external case law or tribunal decisions in the Australian system for interpretation or disputes. Because the ADR is highly technical, disputes are likely to turn on expert evidence (test set‑up, simulation validation, instrument calibration) rather than on novel legal doctrines. The ADR itself prescribes objective test criteria (e.g., pressures, times, deceleration metrics) that will be central in any factual contest.

This ADR contains numerous technical specifics that can be sources of compliance error or operational surprise if not carefully followed.

1. Two‑stage applicability and the meaning of “new model”

• The ADR applies to new models from 1 November 2011 and to all vehicles from 1 November 2013 (clauses 2.1-2.2). The definition of “new model” is a vehicle model first produced with a Date of manufacture on or after the agreed date (clause 2.3). Manufacturers must be precise in recording dates to establish which version of the ADR applies to a particular vehicle.

2. Vehicles certified to later ADRs are excluded

• Vehicles certified to ADR 35/04 or a later version need not comply with this rule (clause 2.8). That creates potential subtleties where a model has multiple certifications or is marketed under different approvals in different jurisdictions.

3. Indicator activation thresholds and trailer‑connected logic

• The Visible Indicator criteria depend on multiple triggering conditions with exact thresholds: differential line pressure of not more than 1.55 MPa; pedal effort thresholds of 225 N (unassisted) or 115 N (assisted) (clauses 4.2.2 A.2.1-A.2.3); brake fluid reservoir level drops (B.1-B.2); and air supply line thresholds of 450 kPa and 35 kPa for towing vehicles (clauses 4.2.2, 4.2.4). A visible indicator must not operate when a trailer is not connected and no other defect is present; absence of a trailer can be determined by supply line pressure dropping to or below 35 kPa (clause 4.2.2.2 and 4.2.2.2.1). Getting the logic wrong when integrating trailer interfaces can cause false alarms.

4. Reservoir capacity and “fully‑worn, fully‑applied” calculation

• Reservoir sizing is linked to the volume displaced from new to fully‑worn pad/shoe positions with a detailed table of worn thickness thresholds (clause 4.6.2). Errors in lining‑wear assumptions or failing to account for the displacement during full master cylinder stroke can cause non‑compliance.

5. Stored energy volume and recharge calculations

• The ADR specifies that the combined volume of Brake Power Units at positive pressure must be not less than 12 times the combined volume of all service brake chambers at maximum piston travel, and sets a formula for recharge time based on actual and test capacities (clause 4.7.2-4.7.3). The test capacity includes an additional allowance per tonne of Rated Towing Capacity (clause 4.7.3.1). Misunderstanding these multiplier rules or failing to include trailer allowances when relevant is a common pitfall.

6. Precise timing and pipe geometry in actuation tests

• The service brake actuation and trailer control line response have exact test set‑ups: a 2.5 m pipe with 13 mm internal diameter must be joined to the coupling head, and pressures must reach specified kPa levels within millisecond limits (clause 7.12.6). Small differences in test set‑up will change measured response times.

7. ESC simulation validation and documentation

• When ESC compliance is demonstrated by simulation, the simulator must be validated against physical tests (Appendix 2 Attachments 1-2). Validation requires exact data, repeatable manoeuvres and test reports in a prescribed format (Attachment 3). Regulators may scrutinise validation methodology; producing inadequate validation may result in rejection.

8. Equivalence exemptions

• The ADR accepts UNECE Regulation No. 13 and GTR No. 8 equivalence, but with enumerated exemptions (clause 8.3 subclauses). A manufacturer who assumes wholesale equivalence without mapping the exemptions risks non‑conformity.

9. Trailer and ABS electrical connector requirements

• For vehicles designed to tow trailers of ATM > 4.5 tonnes, specific electrical connector pin functions and minimum current ratings are mandated for trailer ABS connection (Appendix 1 clause 1.3.2). Connector wiring mistakes can break trailer ABS functionality and trigger non‑compliance.

10. Test surface and ambient conditions

• Specified ambient temperature ranges (0°C-40°C for general tests, Appendix 2 allows up to 45°C for ESC tests), wind limits, and test surface peak braking coefficient (PBC ~ 0.9 unless otherwise specified) are mandatory (Part 6 and Appendix 2 paragraphs 4.1-4.2). Inconsistent test surfaces or out‑of‑range ambient conditions will invalidate results.

11. “Manufacturer” versus “Administrator” responsibilities

• The ADR repeatedly assigns duties to the Manufacturer (design, documentation, data supply) but also expects the Administrator to accept simulations or approve calculations in variant cases (clauses 4.1.9.4, 4.1.10.3). The Administrator’s discretion in accepting “approved” calculations may create uncertainty during compliance negotiations.

Below is a practical checklist anchored to the ADR text for manufacturers, technical services and compliance teams. The list is ordered to reflect design, test, documentation and administrative steps.

Design and build

1. Ensure the Service Brake System operates on all road wheels via a single Control placed for driver operation, includes wear compensation, and incorporates the necessary visible indicators and audible indicators where a single Brake Power Unit is used (clauses 4.1.1, 4.1.4, 4.1.11, 4.2).

2. For MB and MC categories, integrate an ESC that meets Appendix 2 performance and documentation requirements (clause 4.1.1.1 and Appendix 2 paragraphs 2-3).

3. Fit polarized brake line couplings complying with AS 4945‑2000 (clause 4.1.8) and ensure air reservoir drain valves are fitted in compressed air Brake Systems (clause 4.1.12).

4. Size hydraulic reservoirs to contain the fluid displacement from new to fully‑worn linings per clause 4.6.2, and ensure every Brake Power Unit has a reservoir sized to cover those volumes plus piston/accumulator displacement (clause 4.6.3).

5. For vehicles with stored energy or Brake Power Units at positive pressure, design combined supply volumes to meet the 12× rule for service brake chambers and include gauges visible to the driver accurate to ±7% (clauses 4.7.2, 4.7.5.1).

6. For vehicles designed to tow trailers, ensure the Service Brake System meets established retardation coefficient boundaries using the general test conditions and particular trailer test conditions (clause 4.1.9; Service Brake Compatibility Test provisions).

Testing (Parts 6-7 and Table 1)

1. Prepare test plan covering the full Table 1 test suite, grouping tests per clause 5.1.2 if optimal. Ensure test site ambient temperature and surface PBC meet requirements (Part 6 and Appendix 2).

2. Use manufacturer specified tyres and friction elements, adjust brakes per manufacturer’s recommendations, and instrument the vehicle as specified. Maintain brake temperatures below 100°C before most tests (clauses 6.3-6.5).

3. Run Service Brake Burnishing if desired, following clause 7.3; do not readjust brakes during mandatory tests unless allowed.

4. For Service Brake Actuation Time and Control Line response tests, set up the precise 2.5 m, 13 mm pipe connection for trailer control line measurements (clause 7.12.6).

5. For ESC compliance tests, follow the Sine with Dwell test procedures in Appendix 2 paragraph 5, including tyre and brake conditioning, steering robot requirements and data post‑processing (Appendix 2 paragraphs 5-5.11).

Documentation and validation

1. Prepare a documentation package for complex electronic systems per Appendix 2 paragraphs 3.7.1-3.7.4: system diagram, brief operational explanation, logic diagram and understeer inputs.

2. If using simulation for ESC compliance, validate the simulation tool per Appendix 2 Attachments 1-2, produce the simulator test report in Attachment 3 format, and retain the validation documents for the Administrator (Attachments 1-3).

3. Maintain test reports and conformity of production evidence where relying on UNECE Annexes or GTR equivalence, and be prepared for Conformity of Production assessments (clause 8.1.2.2).

Administrative steps

1. Decide whether to rely on ADR testing, UNECE approvals, or GTR equivalence. Map exemptions and annex requirements carefully; document the equivalence route and submit required evidence to the Administrator (clause 8).

2. For vehicles with Rated Towing Capacity > 4.5 tonnes, choose the certification route for trailer brakes or prepare and submit sufficient modelling data to the Administrator as described (clause 4.1.10).

3. Ensure visible and parking brake tell‑tales meet wording, labelling, colour and placement rules (clauses 4.2.8-4.2.12 and 4.3.2-4.3.6).

Calibration and quality control

1. Use calibrated pressure gauges and test instrumentation, ensuring gauges are visible to the driver where required and accurate within the specified tolerance (clause 4.7.5.1).

2. Establish production controls to maintain conformity to approved designs; retain records to demonstrate conformity of production as required by the Administrator where equivalence is claimed (clause 8.1.2.2).

Risk management and negotiation points

1. Engage early with the Administrator on alternative compliance routes (UNECE/GTR or simulation) to confirm acceptance criteria and documentation expectations (clause 8 and Appendix 2 Attachments).

2. For variants, consider whether ‘approved’ calculations based on component tests will be accepted in place of full vehicle retests and obtain written agreement where possible (clauses 4.1.9.4, 4.1.10.3).

3. Anticipate retest requirements around ESC and ABS failures and prepare for potential changes in test surface, wind conditions and ambient temperature that influence outcomes.

Follow‑up and continuous compliance

• Keep the ADR, its amending instruments and referenced standards (ISO, AS, UNECE documents) under active review for version changes and amendments, particularly where the ADR accepts specific series of amendments or annexes as equivalent (clause 8).

This checklist should be adapted into a compliance project plan tied to particular vehicle models, the chosen compliance route, and the Administrator’s procedural requirements.