Vehicle Standard (Australian Design Rule 31/03 – Brake Systems for Passenger Cars) 2013

This ADR is built on a set of key, concrete regulatory concepts drawn from the UN Regulation No. 13-H text which the ADR adopts in Appendix A. Describe them in the order the Rule uses them.

• Type/Category driven applicability. The ADR ties requirements to ADR vehicle categories (MA, MB, MC, NA, LEP, etc.) with staged dates for new model and fleet-wide compliance (clauses 2.1-2.4, applicability table clause 2.8). The notion of "vehicle type" and the scope of differences that define a type are taken from Reg. 13-H definitions (Appendix A, Reg. 13-H 2.1-2.2).
• International harmonisation by incorporation. The ADR treats Reg. 13-H as the technical rules for braking (clause 4.1, Appendix A). That imported text contains definitions, construction requirements, functional requirements (service, secondary, parking brakes), electronic system safety rules (Annex 8), and ESC/BAS technical performance and test regimes (Annex 9).
• Mandatory ESC and BAS for specified categories. ADR 31/03 requires an Electronic Stability Control System and a Brake Assist System in MA/MB/MC/NA vehicles, each meeting Annex 9 (clause 4.2). The UN text defines ESC in detail (Appendix A, Reg. 13-H 2.25) and prescribes dynamic performance tests and tell-tale requirements (Annex 9).
• Test-driven conformity. Reg. 13-H embeds a test regime: Type-0 cold tests and engine-connected tests, Type-I fade and recovery (Annex 3), wheel-lock sequence and torque wheel testing (Annex 5), anti-lock system performance and energy reserve checks (Annex 6 and Annex 4), and ESC dynamic manoeuvres including Sine-with-Dwell or validated simulation (Annex 9 and its Appendices). The ADR makes these the operative standards unless equivalence paths are used (clauses 4.1, 6.1-6.3).
• Equivalence and alternative standards. The ADR allows UNECE Reg. 13-H itself, and certain UN GTR or other UNECE regulations, to be treated as equivalent technical standards subject to specified additional requirements and narrow exemptions (clauses 6.1-6.3 and 6.2.1). For example, GTR No.8 may be deemed equivalent to Annex 9 Part A but with explicit exceptions for specified clauses (clause 6.2, 6.2.1).
• Targeted procedural exemptions. Clause 5.1 expressly lists parts of Appendix A that are not applicable under the ADR (for example Sections 3, 4, 7-12 of the UN text and Annex 1 and 2), and clause 5.2 allows that certain sub-parts of Annex 9 may be deemed met via Conformity of Production assessments rather than full technical testing at approval.
• Documentation and verification of complex electronic controls. Annex 8 (incorporated in Appendix A) requires manufacturers to provide a documentation package, safety concept statements, failure analyses and verification plans for "complex electronic vehicle control systems", which includes ESC and other higher level systems. The ADR therefore imports a procedural disclosure obligation into the Australian approval system (Appendix A, Annex 8).

These concepts translate into concrete obligations: supply of type-approval documentation, submission of a representative vehicle for tests (Appendix A 3.3), affixation of approval marks (Appendix A 4.4), performance of COP (conformity of production) regimes (Appendix A 8), and meeting the specific ESC/BAS signalling and functionality requirements (Appendix A, Annex 9, e.g. ESC malfunction tell-tale, ESC Off controls, and dynamic stability performance criteria).

The rule imposes obligations and creates choices for several identifiable actors, each with distinct costs and decision rights under the instrument.

• Vehicle manufacturers and their accredited representatives. They are the primary actors responsible for type approval applications, submitting the vehicle representative for testing, supplying the technical documentation and test reports, and ensuring the vehicle design meets the ADR and Appendix A technical prescriptions (Appendix A 3.1-3.3; clause 4.1). Annex 8 requires manufacturers produce a two-part documentation package describing system functions, safety concepts, and failure analyses for complex electronic control systems.
• Importers and distributors. For imported models, importers must ensure that the vehicle was approved under a standard acceptable under the ADR (e.g. UNECE Reg. 13-H) or obtain Australian type approval where required (clauses 6.1, Appendix A 4). Approval marks and approval numbers must be affixed to conforming vehicles (Appendix A 4.4-4.7).
• Brake system and supplier industry. Suppliers of ESC modules, BAS implementations, ABS components, brake hardware, sensors and software face demand shifts: the ADR requires ESC and BAS fitment for several categories (clause 4.2), and Annex 9 specifies ESC capabilities and hardware (e.g. wheel-by-wheel braking, sensors to determine yaw rate, steering input monitoring; Appendix A, Reg. 13-H 2.25 and Annex 9 2.1-2.4). Suppliers must meet the documented technical specs, and manufacturers must include identification codes for brake discs/drums in approval communications (Appendix A, Annex 1, items 7.2.1-7.2.2).
• Technical Services and Approval Authorities. The ADR relies on Technical Services for testing and type-approval tasks as per Reg. 13-H (Appendix A 3-4), and on Administrative Departments for communicating approvals (Appendix A 4.3, 11). Where the ADR allows Conformity of Production assessment to substitute for certain annex subparts, Technical Services and approval authorities must exercise discretion in verifying COP evidence (clause 5.2, 6.1.1, Appendix A 8).
• Vehicle repair and inspection industry. Periodic technical inspection requirements are embedded in Reg. 13-H: Annex 3 requires means by which wear condition and the operational status of complex electronic systems can be verified at periodic inspection (Appendix A, Reg. 13-H 5.1.4). Repairers and inspection stations will need training and possibly equipment to read tell-tales and to apply the verification steps described by manufacturers.
• End consumers and fleet purchasers. Consumers and fleet buyers are indirectly affected by design choices and potential cost pass-throughs. The ADR does not set direct consumer-facing obligations, but manufacturers may change prices to reflect compliance costs, and consumers obtain vehicles with ESC/BAS where the ADR requires them (clause 4.2).

Who decides. The central decision nodes are the manufacturer (design choices, documentation, whether to use UN Reg. equivalence), the Technical Service/Approval Authority (testing, type-approval, COP verification), and the Department administering the Motor Vehicle Standards Act 1989 which determines the standard instrument. The ADR specifies what manufacturers must provide and which tests will be applied; Technical Services decide whether the vehicle meets those requirements in approving types (Appendix A 3-4, 7).

Who pays. Upfront compliance costs fall to manufacturers and importers (design changes, test programmes, documentation, adding tell-tales, validation of ESC/BAS algorithms and sensors, possibly hardware changes). Technical Services and test facilities incur testing and administrative costs that manufacturers typically reimburse. Repair and inspection industry participants may face costs for retraining and new diagnostic tools. Consumers ultimately pay through vehicle pricing and choice of models offered for sale domestically.

This ADR and the incorporated Reg. 13-H impose specific duties on manufacturers and grant procedural rights to approval authorities. The principal duties, and the operational rights that accompany approval processes, are as follows.

Duties on manufacturers and applicants

• Demonstrate compliance with Appendix A requirements and Annex 9 for ESC/BAS where applicable. Clause 4.1 requires vehicles to comply with Appendix A, and clause 4.2 explicitly requires ESC and BAS for MA/MB/MC/NA categories meeting Appendix A, Annex 9.
• Supply type-approval application material and submit a vehicle representative for tests as required in Appendix A, Reg. 13-H 3.2-3.3. The list includes description of vehicle type, component lists, assembled braking equipment diagram, and detailed drawings (Appendix A, Reg. 13-H 3.2.1-3.2.4).
• Provide documentation relevant to complex electronic control systems. Annex 8 requires a two-part documentation package: an approval submission package and additional analysis material retained by the manufacturer and made available for inspection at approval time (Appendix A, Annex 8, 3.1-3.1.1).
• Mark the vehicle with an approval mark and, where ESC/BAS are fitted, add the letters "ESC" per Appendix A 4.4.3, and ensure the approval mark is legible and indelible (Appendix A 4.4-4.7).
• Ensure specific onboard functions and tell-tales: ESC malfunction tell-tale, ESC Off tell-tale, brake failure tell-tales, and stored energy warning devices as specified in Annex 3 and 9 (Appendix A, Reg. 13-H 5.2.3, 5.2.14, Annex 9 3.4-3.6).

Rights and procedural features afforded to manufacturers

• Use of alternate, accepted international standards. Clause 6 allows manufacturers to treat UNECE Regulation No. 13-H, GTR No.8, and certain other UNECE texts as equivalent technical requirements, subject to additional fitment conditions and specified exemptions (clauses 6.1-6.3). This reduces duplication where vehicles have already been approved under those international instruments.
• Conformity of Production (COP) substitution for certain subparts. Clause 5.2 and clause 6.1.1 permit manufacturers to demonstrate compliance with specified subparts (Annex 8, some parts of Annex 9) during COP assessments rather than initial labelling/testing, provided the COP assessment satisfies the Technical Service.
• Opportunity to rely on simulation for ESC compliance. Annex 9 allows validated dynamic simulation to demonstrate ESC effectiveness for versions or variants of a vehicle type (Annex 9 Appendix 1 and Appendix 2), which can reduce the need for multiple full dynamic driving tests.
• Right to apply for approval and extension, and to be notified of refusal. Appendix A, Reg. 13-H paragraphs 4.1-4.3 set out approval grant and communication procedures, and 7.1-7.3 set out modification and extension notification obligations.

Operational duties to regulators

• Allow Technical Services to verify COP methods and production conformity at manufacturing sites, with a normal verification frequency of once every two years (Appendix A 8.2).
• Notify administrative departments of modifications, discontinuation of production, or other changes required under Reg. 13-H 7 and 10.

The text also specifies operational requirements that function as duties in practice: e.g. manufacturers must ensure brake wear can be readily assessed (Reg.13-H 5.2.11.2), reserve energy capacity for hydraulics or electric transmissions (Annex 4; 5.2.20 for electric control transmission), and that warning signals are visible and persistent while the ignition is on (Reg.13-H 5.2.21). These are prescriptive technical duties with concrete engineering and documentation implications.

The ADR imports a technical approval and conformity system that interfaces with enforcement mechanisms. The instrument itself does not set out monetary fines in the text provided, but it incorporates approval, conformity and withdrawal mechanics from Reg. 13-H and operates under the Motor Vehicle Standards Act 1989 which establishes statutory authority for standards and enforcement.

Primary enforcement mechanisms apparent in the instrument

• Type approval and marking. Vehicles must be type-approved and carry the approval mark as evidence of conformity (Appendix A, Reg. 13-H 4.4-4.7). Failure to obtain approval would prevent lawful market supply in jurisdictions that link registration to type approval under the Motor Vehicle Standards Act and associated regimes.
• Conformity of Production (COP) verification. Appendix A 8.1-8.2 permits the approval authority to verify production methods and control procedures in manufacturing facilities, with the authority to withdraw approvals if products cease to conform to the approved type (Appendix A 8.2; 9.1). The ADR allows certain annex subparts to be deemed satisfied by COP assessments (clause 5.2, 6.1.1), but this increases the importance of COP verification as an enforcement touchpoint.
• Withdrawal of approval for non-conformity. Reg. 13-H includes procedures for withdrawal of approvals and for communicating withdrawal to other Contracting Parties (Appendix A 9.1-9.2; 10). Although clause 5.1 of the ADR removes some procedural sections from applicability, Appendix A retains provisions concerning withdrawal which may be used administratively by approval authorities under the broader Australian statutory framework.
• Registration and first-use controls. The ADR’s staged applicability (clauses 2.1-2.3) and transitional provisions in Appendix A 12 allow approval authorities to refuse national or first registration of vehicles that do not meet the Regulation as amended by certain supplements if they lack ESC/BAS (Appendix A, Reg. 13-H 12.1-12.2). In domestic practice such refusal to register can be an effective enforcement tool.

Penalties and who decides

• Administrative enforcement will be exercised by the Approval Authority and the Department administering the Motor Vehicle Standards Act 1989, which determine approvals and may suspend, withdraw or refuse approvals or registrations, guided by the Reg. 13-H procedures that the ADR adopts or varies (Appendix A 4, 7, 8, 9, 12; ADR clause 5.1 exemptions must be noted).
• The ADR does not set civil or criminal penalties in its text; statutory penalties for supplying non-compliant vehicles to the market, or for false approvals/documentation, would sit in the Motor Vehicle Standards Act 1989 and subordinate instruments, not repeated in the ADR text provided. Appendix A does however provide for withdrawal of approval for failure to conform (Reg. 13-H 9.1-9.2).

Practical enforcement risks and implementation friction

• Technical complexity increases enforcement resource needs. Annex 9 ESC tests, Annex 6 ABS tests and Annex 5 brake distribution verification are complex, data-intensive and may require specialised test facilities and validated simulation tools; the availability and resourcing of Technical Services to verify claims is therefore central to enforcement (Appendix A, Annexes 5, 6, 9, and Annex 9 Appendices 1-3).
• Procedural carve-outs narrow direct statutory procedures. Clause 5.1 removes certain approval administration sections of the UN text from applicability, which changes the administrative pathway and may concentrate reliance on domestic processes under the Motor Vehicle Standards Act to effect similar enforcement outcomes.
• COP reliance shifts enforcement from upfront testing to production surveillance. Where subparts can be met by COP, enforcement becomes inspection and audit oriented, requiring regular manufacturing inspections and record audits rather than a single comprehensive type test.

The ADR invokes and sits within an administrative and international regulatory architecture; the text explicitly references other ADRs, UNECE instruments and the Motor Vehicle Standards Act 1989. Key interaction points follow.

• Motor Vehicle Standards Act 1989. The ADR is made under s 7 of the Motor Vehicle Standards Act 1989 (see instrument heading). That Act governs type approvals, import restrictions and related enforcement and is the primary statutory source that gives the ADR legal effect. The ADR must be read as a subordinate instrument within that framework.
• Other Australian Design Rules. Clause 2.5 and 2.6 of the ADR cross-reference ADR 35 and ADR 33: vehicles in categories MB, MC or NA complying with ADR 35 will be accepted as complying with ADR 31/03 (clause 2.5); certain LEP vehicles fit into ADR 33 compliance instead (clause 2.6). Clause 2.7 says vehicles certified to ADR 31/04 or later need not comply with ADR 31/03, creating an explicit sequencing with successor ADRs. The ADR’s applicability table (clause 2.8) lists ADR compatibility.
• UNECE instruments and GTRs. The ADR formally deems UNECE Regulation No. 13-H and UNECE Global Technical Regulation No.8 (ESC systems) as equivalent technical requirements subject to stated conditions (clauses 6.1-6.3). Manufacturers may therefore rely on UN approvals or GTR compliance to secure Australian acceptance, reducing duplication. The ADR also specifies narrow exemptions to the GTR No.8 provisions when used as equivalent (clause 6.2.1 lists specific clauses).
• Technical Standards and International Test Protocols. Annex 9 references ASTM test methods and Annexes 6 and other appendices refer to ISO standards and specific test methods (e.g. ISO 9128 for brake fluid identification, Annex 3 Appendix references). Where the ADR adopts these materials, it brings those technical standards into regulatory effect.
• Administrative law and information disclosure. Annex 8 requires manufacturers to provide system documentation and safety analyses to Technical Services for approval. That creates an interplay between trade-secret protection and administrative disclosure obligations; the UN text contemplates confidentiality for some material, but Annex 8 requires certain analyses to be open for inspection by technical services at approval time (Appendix A, Annex 8, 3.1.1 and 3.4.4).
• Vehicle registration rules. The ADR’s staged applicability and Appendix A transitional provisions allow Contracting Parties to refuse first national registration or national approval if vehicles lack required ESC/BAS (Appendix A, Reg. 13-H 12.1-12.2). In Australia these registration-level controls will be effected via the national motor vehicle regulatory and registration systems which enforce ADR compliance as a prerequisite to first registration or import approval.

Practical interaction consequences

• Where manufacturers have ECE approvals, the ADR’s equivalence clauses reduce the need for duplicate type approval testing, but the ADR retains the Australian requirement that the vehicle meet Annex 9 ESC/BAS fitment for categories MA/MB/MC/NA (clause 4.2, clause 6.1). Consequently, manufacturers that already comply with Reg. 13-H can often rely on their UN approval documents, subject to satisfying any ADR-specific exemptions or additional requirements.
• The ADR’s exemption of specific administrative sections of the UN text (clause 5.1) means the domestic administrative mechanics will differ from the UN approval pathway, so parties must reconcile documentation for Australian authorities in the format required by local processes.
• Conformity-of-production monitoring, which is in both the UN text and the ADR, interacts with manufacturing quality systems and supplier contracts, transferring ongoing compliance risk to manufacturers and their COP processes (Appendix A 8, clause 5.2).

The compilation notes appended to the ADR record the instrument’s legislative history and recent changes. The table in the compilation notes and the Table of Amendments set out the amending instruments and the clauses altered.

Chronology and instruments listed

• Original instrument: Vehicle Standard (ADR 31/03 - Brake Systems for Passenger Cars) 2013, registered 01/10/2013, commenced 02/10/2013 (Compilation Table of Instruments).
• Amendment 1: Vehicle Standard (ADR 31/03 - Brake Systems for Passenger Cars) 2013 Amendment 1, registered 18/09/2017, commenced 19/09/2017.
• 2021 instrument: Vehicle Standard (Australian Design Rule) Amendment Instrument 2021 (No.1), registered 13/05/2021, commenced 14/05/2021.

Recorded clause-level changes

• Clause 0.2 was deleted in a miscellaneous amendment (Legislation Act 2003 section 48D), reflecting a non-substantive housekeeping change (Table of Amendments).
• Clause 2.7 was added by Amendment 1 (2017), creating the statement that vehicles certified to ADR 31/04 or later need not comply with this rule (clause 2.7). This is a substantive interaction provision which recognises successor ADRs.
• Clause 2.8 (Applicability Table) was added by the 2021 Amendment Instrument, updating the vehicle category applicability table and making explicit the vehicle categories, ADR codes, UNECE codes and manufactured-on-or-after dates (clause 2.8).

What the amendments do practically

• The 2017 insertion (clause 2.7) creates an upstream escape route for manufacturers whose vehicles are certified to a later ADR. This is a standard drafting technique to avoid duplication of technical regimes when a later ADR supersedes an earlier one.
• The 2021 update to the applicability table formalises the cross-reference to UNECE category codes and clarifies which vehicle types are in/out of scope for the specified dates. That improves regulatory clarity for manufacturers and importers when assessing admission timelines.
• The deletion of clause 0.2 via an administrative Act indicates non-substantive housekeeping consistent with broader instrument maintenance.

Limitations to the amendment register in the compilation notes

• The Table of Amendments records only clause-level changes and the instruments that effected them. It does not summarise technical changes within Appendix A, because Appendix A is the UN text and the ADR’s role is to incorporate or vary parts of that text. Any technical evolution in the underlying UN Regulation would be captured by clause 6’s references to particular supplements and series, but domestic amendment instruments are used where Australia changes applicability, equivalence or exemptions (clauses 5, 6).
• The ADR’s Compilation Notes do not list later supplements to the UN Regulation that Australia has incorporated by notice in Appendix A; however Appendix A itself lists the series and supplements incorporated up to a specified cut-off date.

If you need a migration table summarising exactly how the 2017 and 2021 amendments changed compliance obligations for particular vehicle categories or for manufacturers of LEP vehicles, those changes can be extracted from clause 2.7 and the updated applicability table at clause 2.8.

The ADR text and the attached compilation materials do not record any litigation, judicial interpretations, or administrative appeals with respect to ADR 31/03, and the incorporated UN text does not itself name cases. The compilation notes and Table of Instruments list only legislative instruments and clause amendments; there are no court decisions, tribunal findings, or recorded judicial reviews included in the material supplied.

What that means for legal practitioners and compliance officers

• Absent any reported litigation in the instrument itself, rely on administrative procedures for dispute resolution. Disputes about approval, withdrawal or COP findings will follow the Motor Vehicle Standards Act 1989 administrative processes and any applicable administrative review regimes rather than discrete ADR text procedures. The ADR imports approval and withdrawal procedures from Reg. 13-H (Appendix A 4, 7, 9), but clause 5.1 removes certain administrative sections from applicability; therefore the domestic statutory framework under the Motor Vehicle Standards Act will be the primary locus for appeals and legal challenge.
• Technical challenges will likely be resolved in administrative or expert fora, since many compliance matters require specialist testing and interpretation of engineering data (ESC dynamic tests, ABS cycling thresholds, brake energy reserve calculations). Annex 9 explicitly contemplates the use of validated simulation tools and Technical Services’ role in tool validation (Annex 9 Appendices 1-3), which centralises expertise in Technical Services and may affect forum choice for disputes.
• Practitioners should review the Motor Vehicle Standards Act 1989 and associated procedural instruments for details of review rights, judicial review thresholds, and avenues to challenge administrative findings about compliance, approval or withdrawal. Those authorities are outside the ADR text reproduced here.

If you would like, I can prepare an annotated note listing likely administrative appeal pathways under the Motor Vehicle Standards Act 1989 and the practical evidence thresholds a Technical Service will expect in contestable COP or approval disputes, drawing directly from the approval and COP provisions the ADR imports (Appendix A 3, 4, 8, 9).

This instrument contains multiple practical traps that commonly cause non-compliance or surprise costs. Each entry below is grounded in the ADR text and the UN Reg. 13-H text incorporated by reference.

1. Applicability is model- and category-driven, with "new model" defined in a specific way. Clause 2.1 applies to "new model" vehicles from 1 November 2015, and clause 2.4 defines a "new model" as a vehicle model first produced with a 'Date of manufacture' on or after the agreed date. Many suppliers assume a calendar-year compliance rather than tying to a vehicle production date, and that can change which models must comply when imported. Manufacturers must check the 'Date of manufacture' stamp against clause 2.4 before assuming a vehicle is out of scope.

2. ADR 31/03 accepts some vehicles approved under other ADRs, but the mapping is narrow. Clause 2.5 accepts MB, MC or NA vehicles complying with ADR 35 as meeting ADR 31/03, clause 2.6 directs certain LEP vehicles to ADR 31/03 only if they have a single foot pedal controlling front and rear service brakes, and clause 2.7 exempts vehicles certified to ADR 31/04 or later. Do not assume cross-ADR acceptance is universal; confirm category and configuration specifics.

3. ESC and BAS fitment requirement is categorical and absolute for MA/MB/MC/NA. Clause 4.2 requires ESC and BAS for those categories in accordance with Annex 9. Manufacturers who rely on marketing messages that omit ESC/BAS or who configure optional packages that disable these systems risk non-compliance; Annex 9 also sets requirements for "ESC Off" controls and tell-tales (Annex 9 3.5-3.6), so simply installing an ESC hardware unit without the correct software behaviour and driver indication will not meet the ADR.

4. Some detailed Annex 9 sub-parts may be accepted at COP rather than initial type-approval, but only where clause 5.2 or clause 6.1.1 allow it. Clause 5.2 states that for Annex 8, paragraph 3.7 of Annex 9, and Appendices 1-3 of Annex 9, vehicles will be deemed to meet those requirements if compliance can be demonstrated during a Conformity of Production assessment. Reliance on COP shifts the burden to production controls and auditability; manufacturers must therefore be able to prove the ongoing production system ensures the design meets those subparts.

5. The ADR removes some UN administrative provisions, which changes procedure. Clause 5.1 lists specific sections of Appendix A that are not applicable under the ADR, including Section 3 (Application for approval) and Section 4 (Approval). Because the ADR excludes those sections as written, the domestic approval pathway is governed by Australian practice under the Motor Vehicle Standards Act and the ADR’s own provisions. Do not attempt to follow the UN text's administrative forms verbatim without checking Australian processes.

6. Testing and data requirements are intensive and technical. Annex 3 Type-0 and Type-I tests, Annex 5 wheel-lock sequence and torque wheel tests, Annex 6 anti-lock performance and Annex 9 ESC Sine-with-Dwell tests require specialised instrumentation, sampling rates, filtering and data processing standards (see Annex 9 5.11, Annex 6 Appendices and Annex 3). For ESC, simulation is permitted, but the simulation tool must be validated against practical tests and a simulator test report provided (Annex 9 Appendices 1-3). Small-volume manufacturers may find these costs concentrated and significant.

7. Documentation confidentiality expectations are limited. Annex 8 requires manufacturers to supply a documentation package and to make certain analyses available to technical services. Although the Annex contemplates confidential retention of some analysis material, manufacturers should not assume full secrecy; technical services will expect access to sufficient safety analyses to verify the safety concept and failure strategies (Annex 8 3.1-3.4).

8. Tell-tale and driver interface obligations can be overlooked. Annex 9 details specific symbols, colours, visibility and behaviour for ESC malfunction tell-tales and ESC Off tell-tales (Annex 9 3.4-3.6). These are functional obligations not mere labelling. For example, the ESC malfunction tell-tale must illuminate when a malfunction exists and remain lit as long as the malfunction exists while the ignition is on (Annex 9 3.4.1.6). Manufacturers must ensure instrument cluster software and common-space displays meet these constraints, especially where tell-tales are multiplexed.

9. Regenerative braking and electric architectures bring special requirements. Annex 3 and Reg. 13-H include multiple provisions for electric regenerative braking systems (Reg.13-H 2.17, 5.2.7, 5.2.18), for state-of-charge procedures, and for electric control transmission energy reserve tests (5.2.20). Vehicles with electric traction must manage state-of-charge during tests, and manufacturers must be able to follow the battery monitoring procedure in Annex 3 Appendix for battery charge state monitoring.

10. Marking and approval numbers are prescriptive. Appendix A 4.4 requires approval marks with specific formats, and if ESC/BAS requirements are satisfied, the mark must include the additional letters "ESC" (Appendix A 4.4.3). Missing or incorrect approval marks will complicate registration and market entry.

In short, do not treat ADR 31/03 as merely a list of safety features. It is a full technical approval regime combining engineering tests, documentation obligations, production conformity surveillance and specific human-machine interface requirements. For manufacturers and regulators the practical risks are concentrated costs of dynamic testing, documentation and COP verification; for small-volume producers the administrative overhead and test costs are the common failure points.

This section gives a practical, source-grounded compliance route for manufacturers, importers, compliance teams and technical services. The steps below cite the ADR clauses and incorporated Annexes that specify each requirement.

1. Confirm category and applicability dates

• Identify the vehicle ADR category (MA, MB, MC, NA, LEP, etc.) and the 'Date of manufacture' of the model variant. Clause 2.4 defines "new model" for the 1 November 2015 threshold (clause 2.1). Check the Applicability Table at clause 2.8 to confirm the Manufactured on or After date for the specific category.
• If the vehicle is certified to ADR 31/04 or a later ADR, clause 2.7 exempts it from ADR 31/03, so confirm whether that applies.

2. Decide on the compliance pathway (ADR Appendix A Reg. 13-H baseline or accepted alternative)

• If you have a UNECE Reg.13-H approval or GTR No.8 compliance, clause 6 allows you to treat those as equivalent technical requirements provided you also meet any ADR additional fitment requirements (notably ESC/BAS fitment for MA/MB/MC/NA) and respect the stated exemptions in clauses 6.1-6.3 and 6.2.1.
• If you use an alternative pathway, check clause 6.1.1 and clause 6.2.1 carefully for the specific paragraphs that are exempted or modified when GTR No.8 or Reg. 13-H versions are used.

3. Fulfil ESC/BAS hardware and software requirements where applicable

• For MA/MB/MC/NA vehicles, fit an ESC and a BAS that meet Annex 9 Part A and Part B requirements. Annex 9 sets out ESC functional requirements (ability to apply individual wheel braking torques, read yaw rate, monitor steering inputs, and modify propulsion torque) (Annex 9 2.1-2.5).
• Implement required tell-tales and controls: ESC malfunction tell-tale, ESC Off control and its tell-tale, and ensure they meet colour, visibility and behaviour requirements (Annex 9 3.4-3.6). If the ESC Off control exists, the ESC must return to default mode at each new ignition cycle except in specified drive configurations (Annex 9 3.5).
• Where electric regenerative braking is used, follow the Reg.13-H provisions for phasing, state-of-charge monitoring and test conditions (Reg. 13-H 2.17, 5.2.7, 5.2.18; Annex 3 Appendix).

4. Prepare the documentation required for type approval

• Follow the application material list in Reg.13-H 3.2: vehicle type description, list of braking components, diagrams, and detailed drawings (Appendix A Reg. 13-H 3.2.1-3.2.4).
• For complex electronic control systems, prepare the Annex 8 documentation package: system description, safety concept, unit schematics, failure analyses (FMEA/FTA or equivalent), documentation split into the approval package and additional material retained by manufacturer but available on inspection (Appendix A Annex 8 3.1-3.4.4).
• Ensure brake lining, disc and drum identification codes are specified as required in Annex 1 fields 7.1-7.2.

5. Plan and conduct required tests or validated simulations

• For mechanical braking performance, implement Type-0 tests (cold service and secondary braking), Type-I fade and recovery tests, and parking brake tests as per Annex 3. Follow the precise test speeds, temperatures and force limits (Annex 3 1.4-1.5; 2).
• For brake distribution and wheel-lock behaviour, perform wheel-lock sequence tests and, if required, torque wheel tests per Annex 5 Appendices 1-2. For anti-lock systems, test energy consumption and utilization of adhesion per Annex 6 (Annex 6 5.1-5.2).
• For ESC compliance, run the Sine-with-Dwell dynamic tests or use a validated dynamic stability simulation according to Annex 9 Appendices 1-3. If simulation is used, validate the tool against practical tests, and attach the simulator test report to the approval documentation (Annex 9 Appendices 1-3).
• Maintain instrumentation and data acquisition practices as specified (e.g. Annex 9 5.11 post-processing, Annex 6 Appendix 2 sampling requirements, Annex 9 and BAS Appendix 5 digital filtering and sampling rates).

6. Use Conformity of Production (COP) where permitted

• Determine whether certain Annex 9 subparts and Annex 8 items can be demonstrated during COP instead of initial type tests (clause 5.2, clause 6.1.1). If you plan to use COP, prepare documented production control plans and verification routines because Technical Services will audit these (Appendix A 8.1-8.2).

7. Apply for approval and affix approval marks

• Submit the type approval application and required test reports to the Technical Service. Appendix A Reg. 13-H 3 and 4 describe the approval number assignment, approval form communications and affixation of approval marks. If ESC/BAS requirements are met by the vehicle, append the letters "ESC" to the approval mark as required (Appendix A 4.4.3).
• Keep copies of the approval communication form and ensure the vehicle data plate placement follows Appendix A 4.7.

8. Prepare for COP verification and production surveillance

• Ensure the manufacturing facility maintains the production controls, calibration and test records necessary to demonstrate that vehicles in production conform to the approved type. Appendices require Technical Services to verify COP methods at a normal frequency of once every two years (Appendix A 8.2).
• Provide means for periodic technical inspection authorities to verify brake wear and operational status of electronic systems as prescribed (Reg. 13-H 5.1.4 and 5.2.11.2).

9. Post-approval obligations

• If you modify the vehicle type or braking system, notify the approval authority and be prepared to submit additional tests or reports (Appendix A Reg. 13-H 7.1-7.3). If production is discontinued, follow Appendix A Reg. 13‑H 10.

10. Practical compliance checklist items

• Verify the ESC malfunction and ESC Off tell‑tales operate per Annex 9 3.4-3.6.
• Provide brake wear assessment method and replacement limit information for discs/drums as required at type approval and for periodic inspection (Reg. 13‑H 5.2.11.2.2).
• If using regenerative braking, document the method of state-of-charge assessment and ensure test batteries meet the Annex 3 Appendix procedure.
• Keep records enabling technical services to reproduce COP assessments for the parts of the standard that they accept by COP.

If you want, I can produce a ready-to-use compliance pack template (document list, test schedule, data-report templates) keyed to the particular vehicle category you are working with, cross-referenced to the exact Annex paragraphs to use in audits or approval submissions.