Vehicle Standard (Australian Design Rule 35/07 – Commercial Vehicle Brake Systems) 2022

The main concepts that appear in the supplied text are scope, staged applicability, mutual-recognition/deeming, vehicle-category treatment, and limited exceptions. These concepts are expressed in the preliminary provisions and the Applicability Table.

Scope and function. The standard declares its purpose to be specification of braking requirements for commercial and large passenger vehicles, with the objective phrased as ensuring safe braking under normal and emergency conditions (cl. 2.1). That function frames what follows in the full instrument, namely technical and test requirements for brake systems (see the Contents listing: Definitions; Design Requirements; Performance Requirements; General and Particular Test Conditions; Alternative Standards; and Appendices).

Staged applicability. The standard applies to a set list of ADR and UN categories (LEG, MB, MC, MD, ME, NA, NB, NC), but not all categories are subject to the same commencement dates. The instrument prescribes specific dates for different cohorts: NB2/NC vehicles over a stated width, new model vehicles, and other categories (cl. 3.1.1-3.1.4). The Applicability Table further links ADR category codes to UN codes and contains a “Manufactured on or After” column for many categories.

Definition of “new model”. A “new model” is expressly defined for the purpose of the staged start date as a vehicle model first produced with a Date of Manufacture on or after the relevant commencement date (cl. 3.2). This definition ties compliance obligations to production dates and model first-production events rather than, for example, registration or import dates.

Mutual recognition and deeming. The standard provides for a number of deeming or acceptance pathways:

• Category MB, MC or NA vehicles that comply with ADR 31 (Brake Systems for Passenger Cars) will be accepted as complying with this standard (cl. 3.3).
• Category MB, MC and NA vehicles certified to this standard must also be certified to ADR 88 (Electronic Stability Control Systems) and ADR 89 (Brake Assist Systems) (cl. 3.7).
• Category NA vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments are deemed to comply with this standard (cl. 3.8).
• Category MD, ME, NB and NC vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments are also deemed to comply, subject to meeting specific ADR clauses (cl. 3.9).

Exceptions and special cases. The standard explicitly excludes combinations of drawing vehicle and trailer from its application (cl. 3.5). It treats a vehicle comprised of two or more non-separable articulated units as a single vehicle for the standard’s purposes (cl. 3.6). It also places a specific treatment on category LEG motorcycles fitted with a single foot pedal controlling both front and rear service brakes, which must comply with the NA requirements in this standard; other LEG vehicles must comply with ADR 33 for motorcycles and mopeds (cl. 3.4). The Applicability Table contains further category-specific notes such as acceptable prior rules (e.g. “/06” or “Nil”) which indicate transitional acceptance paths for pre-existing approvals.

Structure and omitted detail. The supplied contents list confirms the standard contains detailed definitions, design and performance requirements, test conditions, alternative standards and multiple appendices (including three appendices with annexes). The substantive technical requirements are not reproduced in the supplied extract, but the structure indicates the instrument will combine prescriptive design requirements, performance criteria, test methods, and alternate compliance options.

The instrument targets vehicle manufacturers, certifiers and approval authorities, and indirectly affects operators and purchasers of vehicles within the named categories because it governs the design and certification criteria that vehicles must meet.

Primary regulated parties. The standard applies to manufacturers and approval holders responsible for vehicles of ADR categories designated in cl. 3.1 and the Applicability Table: LEG (motorcycles and related subcategories), MB (forward-control passenger vehicle), MC (off-road passenger vehicle), MD (light omnibus subcategories MD1-MD4), ME (heavy omnibus), NA (light goods vehicle N1), NB (medium goods vehicle N2, NB1, NB2) and NC (heavy goods vehicle N3), plus various trailer categories noted as Not Applicable in the table (that is, trailer categories TA-TD are listed but mostly “Not Applicable” in the Manufacture date column) (cl. 3.1; Applicability Table). The specified staged commencement dates make the instrument particularly material for manufacturers introducing new models or producing vehicles on or after those dates (cl. 3.1.1-3.1.4; cl. 3.2).

Manufacturers of “new models”. The standard explicitly treats “new model” status as determinant of compliance obligations for the 1 November 2023 staged commencement (cl. 3.1.2 and cl. 3.2). A vehicle model first produced with a Date of Manufacture on or after the stated dates will be subject to the standard’s requirements as a new model.

Certifiers and approvals. Approval authorities and certification agents will be affected where the standard creates deeming arrangements with other ADRs or UN Regulations. For example, MB, MC or NA vehicles complying with ADR 31 will be accepted as complying with this standard (cl. 3.3), and NA vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments will be deemed to comply (cl. 3.8). Conversely, MB, MC and NA vehicles certified to this standard must also be certified to ADR 88 and 89 (cl. 3.7), which creates coordination requirements across ADR certificates.

Operators, buyers and fleet managers. Although the standard regulates design and certification rather than direct operating behaviour, it affects fleets and purchasers because vehicles placed on the market after the relevant dates will need to meet the ADR’s braking requirements. For example, NB2 and NC vehicles with an Overall Width exceeding 2,500 mm are subject to the 1 October 2023 start date (cl. 3.1.1). Buyers of new model vehicles produced on or after the relevant dates should expect compliance to be certified by manufacturers.

Special cases and technical advisers. The instrument assigns particular treatments that impact engineering and certification choices. Category LEG motorcycles with a single foot pedal controlling both front and rear service brakes are required to comply with NA requirements in this standard (cl. 3.4). Manufacturers of articulated multi-unit vehicles must treat a non-separable articulated vehicle as a single vehicle for compliance purposes (cl. 3.6). Entities using UN Regulation No. 13 approvals will need to confirm whether their approval incorporates the 11 series of amendments and, where applicable, whether the listed ADR clauses are met (cl. 3.8-3.9).

Excluded parties. The standard expressly does not apply to combinations of drawing vehicle and trailer (cl. 3.5). That exclusion should be noted by manufacturers or modifiers that operate equipment in combination with trailers, and by approval authorities assessing combinations.

The supplied extract sets out primarily scope and cross-reference duties rather than detailed technical obligations. The following duties and limited rights are stated or implied by the clauses included.

Duties imposed by the standard (scope and certification duties)

• Comply if your vehicle falls within the listed ADR categories on or after the stated dates. The standard applies to listed categories from the dates set out in cl. 3.1.1-3.1.4 and the Applicability Table (cl. 3.1).
• Treat “new model” vehicles as those first produced with a Date of Manufacture on or after the specified commencement date for the relevant cohort; such vehicles must satisfy the standard (cl. 3.2).
• Category MB, MC or NA vehicles that comply with ADR 31 (Brake Systems for Passenger Cars) will be accepted as complying with this standard, so certification to ADR 31 is a route to compliance (cl. 3.3).
• Category MB, MC and NA vehicles certified to this standard must also be certified to ADR 88 (Electronic Stability Control Systems) and ADR 89 (Brake Assist Systems), so manufacturers seeking certification under ADR 35/07 need to ensure compliance with ADR 88 and ADR 89 as well (cl. 3.7).
• Category NA vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments are deemed to comply with ADR 35/07, which gives a certification pathway by reliance on UN Regulation No. 13 approvals where the UN approval incorporates that specific series of amendments (cl. 3.8).
• Category MD, ME, NB and NC vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments are also deemed to comply, provided particular ADR clauses are met (cl. 3.9 lists clauses 5.3.5, 5.3.6, 5.3.7, 5.8.1.1, 5.8.2 and 8.12.6(b) where applicable).

Specified exceptions and constraints

• The standard does not apply to combinations of drawing vehicle and trailer (cl. 3.5). That is a negative duty for parties operating with trailers: they are not required to meet ADR 35/07 for the combination but must check whether other standards apply to individual units.
• A vehicle comprising two or more non-separable articulated units must be considered a single vehicle for the standard’s purposes (cl. 3.6), shifting the compliance analysis from unit-by-unit to whole-vehicle.
• Category LEG vehicles fitted with a single foot pedal controlling both front and rear service brakes must comply with all requirements of this standard applicable to category NA vehicles (cl. 3.4). Other LEG vehicles must comply with ADR 33.

Rights or acceptance pathways

• The instrument provides “acceptance” routes where compliance with other ADRs or UN Regulations will be treated as compliance with ADR 35/07. This includes acceptances for vehicles complying with ADR 31 (cl. 3.3) and deeming where UN Regulation No. 13 incorporates the 11 series of amendments (cl. 3.8-3.9). These are procedural rights that allow manufacturers to rely on prior approvals.
• The Applicability Table records “Acceptable Prior Rules” entries such as “/06” or “Nil” for certain categories. While the extract does not explain the procedural mechanics of that column, it implies limited transitional recognition for pre-existing approvals in some categories.

Limitations within the supplied extract

• The extract does not set out the technical design, performance or testing duties themselves; those are referenced in the Contents (clause headings 4-9 and appendices) but their substance is not included in the supplied text. The clauses cited in cl. 3.9 (e.g., 5.3.5, 5.8.1.1) identify specific substantive obligations elsewhere in the instrument; compliance pathways tied to UN Regulation No. 13 depend on satisfying those clauses, but the supplied extract does not state their text.

Practical implication of duties

• Manufacturers and certifiers must map vehicle category, Date of Manufacture and overall dimensions (for the NB2/NC width threshold) against the commencement dates and acceptance pathways in cl. 3 to determine whether ADR 35/07 applies and whether alternative compliance routes (ADR 31 or UN R13 approvals) are available (cl. 3.1-3.9; Applicability Table). The supplied text places the burden of checking these criteria on parties responsible for certification and approval.

The supplied extract does not contain any express provisions on penalties, infringement notices, sanctions or enforcement mechanisms. The content provided covers the standard’s name, function, applicability, and an applicability table, but it does not include provisions that describe enforcement powers, administrative penalties, criminal sanctions, compliance monitoring regimes, or the role of particular enforcement agencies. The Contents list identifies the normative technical parts of the standard (clauses on definitions, design and performance requirements, test conditions and appendices), but it does not include any enforcement chapter in the portion supplied.

Consequently:

• No monetary penalties, civil sanctions, or criminal offences are specified in the supplied text.
• No enforcement agency is named in the supplied text for monitoring compliance or issuing directions or prohibitions.
• No compliance or audit procedures, recall mechanisms, or rectification orders are set out in the extracted material.

What the reader must do. Given the absence of enforcement material in the supplied extract, users who need to assess legal exposure or enforcement risk should consult:

• The full text of ADR 35/07 beyond the extract supplied, as the omitted clauses or appendices could contain certification procedures, conformity of production requirements, or administrative provisions.
• The enabling Commonwealth legislation and subsidiary instruments under which ADRs operate, because enforcement of ADR compliance in Australia is typically effected through registration and import control mechanisms and other statutory instruments outside an ADR’s technical text. The supplied extract does not reference those enabling provisions or administrative mechanisms.

In summary, the supplied extract sets technical scope and certification routes but does not include enforcement or penalty provisions. Any assessment of sanctions, sanctions-procedures or regulatory enforcement must be made on the basis of the complete ADR 35/07 and the relevant implementing legislation and administrative rules, which are not part of the text provided.

The supplied text expressly cross-references and interacts with other Australian Design Rules and with a United Nations regulation. Those cross-references define acceptance and coordination paths between ADRs and between UNECE approvals and ADR conformity.

Interaction with other ADRs

• ADR 31 - Brake Systems for Passenger Cars: Category MB, MC or NA vehicles complying with ADR 31 will be accepted as complying with ADR 35/07 (cl. 3.3). This creates a substitutional compliance route whereby conformance to ADR 31 suffices for ADR 35/07 for those vehicle categories.
• ADR 33 - Brake Systems for Motorcycles and Mopeds: Other category LEG vehicles (that is, LEG vehicles that are not the single-foot-pedal variant described in cl. 3.4) must comply with ADR 33 (cl. 3.4). The standard therefore defers to ADR 33 for the bulk of motorcycles and mopeds.
• ADR 88 - Electronic Stability Control (ESC) Systems and ADR 89 - Brake Assist Systems (BAS): Category MB, MC and NA vehicles certified to ADR 35/07 must also be certified to ADR 88 and ADR 89 (cl. 3.7). That linkage makes ADR 35/07 part of an interdependent certification regime for vehicles in those classes, requiring compliance across multiple ADRs.

Interaction with UN Regulation No. 13

• The standard provides deeming: category NA vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments will be deemed to comply with ADR 35/07 (cl. 3.8). Similarly, category MD, ME, NB and NC vehicle types approved to UN Regulation No. 13 incorporating the 11 series of amendments will be deemed to comply, provided specified ADR clauses are met (cl. 3.9). This creates a harmonisation pathway between UNECE type approvals and Australian ADR compliance, conditional upon the UN approval incorporating a particular set of amendments and upon meeting specified ADR subsections.

Interplay of deeming and clause-specific requirements

• The deeming in cl. 3.9 is conditional: the MD, ME, NB and NC approvals to UN R13 will be deemed to comply only if certain detailed ADR clauses are met (the provision lists cl. 5.3.5, 5.3.6, 5.3.7, 5.8.1.1, 5.8.2 and 8.12.6(b) where applicable). Those clause cross-references indicate that not all technical elements of ADR 35/07 are covered solely by UN R13 approvals; certain ADR-specific items need to be satisfied in addition to the UN approval. The supplied extract does not contain the text of those clauses, so the exact items to be satisfied must be checked in the full standard.

Transitional and prior-rule recognition

• The Applicability Table includes a column labelled “Acceptable Prior Rules” with entries such as “/06” or “Nil” for some ADR categories. The supplied extract does not explain the mechanics of this column, but it indicates the standard recognises some predecessor approval rules for particular categories. Users should consult the complete standard to understand which prior approvals remain acceptable and the conditions for their recognition.

Exclusions and boundaries

• The standard expressly excludes combinations of drawing vehicle and trailer (cl. 3.5). That exclusion influences which standards apply to combinations, leaving open the need to consult other ADRs or regulations for trailer-related braking requirements.
• A vehicle composed of non-separable articulated units is to be considered a single vehicle for the purposes of ADR 35/07 (cl. 3.6). That treatment affects whether other ADRs or regulations, which may treat units separately, apply.

Practical interaction consequences

• Where manufacturers or certifiers rely on prior ADR approvals or UN R13 approvals, they must ensure the specific amendments and clause conditions listed in ADR 35/07 are met. For example, reliance on UN R13 approvals requires that the approval incorporate the 11 series of amendments (cl. 3.8-3.9).
• Where ADR 35/07 requires concurrent certification to ADR 88 and ADR 89 for MB, MC and NA vehicles, applicants must plan certification strategies that address the technical and test requirements of multiple ADRs simultaneously (cl. 3.7).

Limitations in the supplied extract

• The extract does not set out the detailed text of the referenced ADRs, the UN Regulation, or the enabling legislation that gives ADRs legal effect. To fully map interaction effects and compliance obligations, the full ADR 35/07 text and the related ADRs and UN Regulation must be consulted.

The supplied extract contains limited material about amendment history. What is explicit:

• The instrument’s name is Vehicle Standard (Australian Design Rule 35/07 - Commercial Vehicle Brake Systems) 2022 (cl. 1.1). The inclusion of “2022” in the name indicates the version and year of the standard as presented in the extract.
• The standard may be cited by a number of forms of the title, including Australian Design Rule 35/07 - Commercial Vehicle Brake Systems; Australian Design Rule 35/07; or ADR 35/07 (cl. 1.1.1 and cl. 1.1.2).

What the extract does not provide

• The supplied text does not include any express history of amendments, prior versions, or dates of previous revisions beyond the 2022 title. There is no table of amendments, no explanatory memorandum, and no list of removed or replaced provisions in the extract.
• The Applicability Table’s “Acceptable Prior Rules” column contains entries such as “/06” or “Nil” for some categories. The extract does not explain the meaning of those entries beyond signalling that some prior ADR rule references are relevant to transitional acceptance. The extract does not specify the dates or instruments that correspond to “/06” nor does it provide a history of how ADR 35/07 replaced a prior ADR version.

Implication for users

• Users seeking a complete amendment history, including the changes introduced in 2022 compared with prior ADR 35/x versions or predecessor ADRs, must consult the complete text of ADR 35/07 (full document), any published amendment instruments, the Federal Register/legislative database entries for the ADR, and associated explanatory material or regulatory impact statements which typically accompany ADR amendments.
• The extract alone does not permit reconstruction of the standard’s amendment chronology or the substantive changes made in 2022.

The supplied extract contains no references to cases, litigation, tribunal decisions, or dispute-resolution outcomes. It does not cite judicial interpretations of ADR 35/07 or of predecessor instruments. The Contents page and the clauses supplied are purely technical and administrative in nature and do not record any litigation history.

What this means practically

• There is no litigation history within the excerpt to analyse or to use as precedent or interpretive guidance for ADR 35/07’s terms.
• Parties seeking case law or interpretive decisions that concern ADR 35/07 or its predecessors must search external legal databases, administrative decisions or tribunal records. The extract provides no leads such as case names or decision citations.

Caveat on litigation and ADRs in general

• ADRs are technical standards administered within an administrative framework; disputes involving ADR compliance commonly arise in administrative, regulatory or civil contexts rather than constitutional or criminal litigation. The extract does not address how compliance disputes are resolved or the forum in which contestation might occur.

The supplied extract contains several specific provisions and structural features that can produce practical traps for manufacturers, certifiers or fleet operators. The following points are grounded in the text provided.

1. Staged commencement dates and the “new model” definition (cl. 3.1.1-3.1.4; cl. 3.2)

• The instrument phases in application by vehicle cohort. A “new model” is defined as a vehicle model first produced with a Date of Manufacture on or after the commencement date (cl. 3.2). The practical consequence is that whether a vehicle is treated as subject to ADR 35/07 can hinge on the precise Date of Manufacture recorded for the model. Misclassification of a model’s first Date of Manufacture can therefore affect whether the vehicle must comply.

2. Width threshold for NB2 and NC vehicles (cl. 3.1.1 and Applicability Table)

• For NB2 and NC categories there is an early commencement (1 October 2023) for vehicles with an ‘Overall Width’ exceeding 2,500 mm (cl. 3.1.1 and table heading). Manufacturers and certifiers must measure and document overall width carefully to determine whether the early date applies.

3. Cross-ADR certification obligations (cl. 3.3 and cl. 3.7)

• Compliance substitution and linkage rules can create overlooked obligations. For example, while compliance with ADR 31 will be accepted for MB, MC or NA vehicles (cl. 3.3), vehicles certified to ADR 35/07 in the MB, MC and NA categories must also be certified to ADR 88 and ADR 89 (cl. 3.7). Failure to secure concurrent certification to those ADRs could prevent an otherwise technically compliant vehicle from being fully certified.

4. Deeming via UN Regulation No. 13 is conditional (cl. 3.8-3.9)

• NA vehicle types approved to UN R13 incorporating the 11 series of amendments are deemed to comply (cl. 3.8). For MD, ME, NB and NC types the deeming is conditional on meeting specified ADR clauses (cl. 3.9). Users cannot assume an automatic acceptance from a UN R13 approval unless the approval explicitly incorporates the 11 series of amendments and the ADR clause conditions are satisfied. The extract identifies the specific ADR clauses that must be met for the conditional deeming (5.3.5, 5.3.6, 5.3.7, 5.8.1.1, 5.8.2 and 8.12.6(b)), but does not give the text of those clauses.

5. LEG motorcycle special-case treatment (cl. 3.4)

• A LEG motorcycle fitted with a single foot pedal controlling both front and rear service brakes is required to comply with the NA class requirements in this standard (cl. 3.4). This is a non-intuitive cross-category obligation: a motorcycle variant must meet light goods vehicle brake requirements. Failure to spot that configuration will produce non-compliance.

6. Exclusion of combinations but not of individual units (cl. 3.5-3.6)

• The standard does not apply to combinations of drawing vehicle and trailer (cl. 3.5). However, a vehicle made of two or more non-separable articulated units is treated as a single vehicle for this ADR (cl. 3.6). The practical distinction between an articulated multi-unit considered a single vehicle and a separable drawing-vehicle-plus-trailer combination determines whether ADR 35/07 applies, and errors in classification could lead to incorrect compliance assessments.

7. “Acceptable Prior Rules” entries in the Applicability Table

• Several entries in the table list “/06” or “Nil” under “Acceptable Prior Rules”. The extract does not explain which prior instrument “/06” refers to, nor whether a “Nil” entry indicates no transitional acceptance. Users must not assume that presence of an entry equates to automatic transitional acceptance; the full text and administrative guidance must be consulted.

8. Missing technical text in the supplied extract

• The extract’s table of contents lists extensive technical material in clauses 4-9 and multiple appendices. Relying solely on the introductory clauses in this extract without examining those detailed sections risks missing precise design, performance and test conditions that determine compliance.

9. Interdependent ADR compliance

• The obligation in cl. 3.7 to be certified to ADR 88 and ADR 89 as well as ADR 35/07 for MB, MC and NA vehicles requires manufacturers to align engineering and testing programmes across multiple standards. Scheduling and testing sequences must account for that interdependence.

10. Terminology precision

• Terms such as “vehicle type”, “vehicle model”, “Date of Manufacture”, “new model”, and “non-separable articulated units” determine applicability. The extract provides a definition only for “new model” (cl. 3.2). Users must confirm the precise definitions of other terms in the missing definitions clause (cl. 4) so that compliance determinations are accurate.

Based on the supplied text, compliance is a process that begins with categorising the vehicle correctly and mapping dates and certification pathways. The following stepwise guidance is grounded in the clauses provided.

1. Establish whether ADR 35/07 applies to your vehicle

• Identify the vehicle ADR category (LEG, MB, MC, MD, ME, NA, NB, NC) and subcategory where applicable using the Applicability Table (cl. 3.1; Applicability Table).
• Confirm the Date of Manufacture for the vehicle model and determine whether the model is a “new model” as defined in cl. 3.2. If the model was first produced with a Date of Manufacture on or after the relevant commencement date, ADR 35/07 will apply.

2. Check date and dimension thresholds

• For NB2 and NC vehicles, measure Overall Width. If Overall Width exceeds 2,500 mm, ADR 35/07 applies from 1 October 2023 (cl. 3.1.1).
• Note other staged dates: 1 November 2023 for all new model vehicles, 1 November 2024 for categories LEG, MB, MC, MD, ME and NA, and 1 February 2025 for categories NB and NC, unless other subclauses or table entries specify otherwise (cl. 3.1.1-3.1.4).

3. Use available acceptance pathways where applicable

• If the vehicle is a category MB, MC or NA type that complies with ADR 31 (Brake Systems for Passenger Cars), you may rely on that compliance as acceptance for ADR 35/07 (cl. 3.3).
• If your vehicle type is an NA vehicle approved to UN Regulation No. 13 incorporating the 11 series of amendments, it will be deemed to comply with ADR 35/07 (cl. 3.8). For MD, ME, NB and NC types with UN R13 approval, check the ADR clauses listed in cl. 3.9 (5.3.5, 5.3.6, 5.3.7, 5.8.1.1, 5.8.2 and 8.12.6(b)) and ensure these are satisfied in addition to the UN approval.

4. Coordinate concurrent ADR certifications

• If certifying MB, MC or NA vehicles under ADR 35/07, plan to secure certification to ADR 88 and ADR 89 as required by cl. 3.7. This will typically require aligning electronic stability control and brake assist testing with the braking system tests and design declarations under ADR 35/07.

5. Pay attention to special-case classifications

• If the vehicle is a LEG motorcycle fitted with a single foot pedal controlling both front and rear service brakes, treat it as subject to the NA requirements in ADR 35/07 rather than ADR 33 (cl. 3.4). For other LEG vehicles, follow ADR 33 (cl. 3.4).
• For multi-unit vehicles composed of two or more non-separable articulated units, prepare to treat the whole assembly as a single vehicle for compliance testing and declarations (cl. 3.6).
• For combinations of drawing vehicle and trailer, ADR 35/07 does not apply to the combination; confirm which ADRs or standards apply to the individual units (cl. 3.5).

6. Review “Acceptable Prior Rules” entries

• Consult the full text of ADR 35/07 for explanatory material on the “Acceptable Prior Rules” cell entries in the Applicability Table. Do not assume automatic grandfathering; if the table lists a prior rule reference such as “/06” or “Nil”, confirm whether and how prior approvals remain acceptable.

7. Consult the detailed clauses and appendices

• The supplied extract identifies detailed subject matter in clauses 4-9 and appendices 1-5 plus annexes. Obtain and study those parts of the standard to determine the precise design requirements, performance requirements, general and particular test conditions, and any alternative standards. Compliance to the ADR will require meeting those technical requirements.

8. Document and certify precisely

• Ensure that Date of Manufacture, vehicle category/subcategory, overall dimensions and relevant approvals are documented and available for the approval authority. Where relying on ADR 31 or UN R13 approvals, maintain documentation proving the prior approval and showing that amendment series requirements (for UN R13) are satisfied.

9. Coordinate with approval authorities early

• Because ADR 35/07 ties into other ADRs and conditional deeming on UN Regulation No. 13, engage with the approval authority early to confirm which certification route is appropriate and to align testing schedules for interdependent ADRs (cl. 3.3, cl. 3.7, cl. 3.8-3.9).

10. Where uncertainty exists, obtain full text and formal guidance

• The supplied extract omits definitions and the specific technical clauses referenced in cl. 3.9 and elsewhere. To avoid compliance risk, obtain the full ADR 35/07 text and any administrative guidance or technical notes issued by the regulator.

Concluding practical note

• The mechanics of compliance under the supplied extract are primarily procedural and categorisation-based: determine category, Date of Manufacture, dimensional thresholds and whether accepted alternative approvals apply, then ensure concurrent certifications where required. The full technical validation requires consulting the missing clauses and appendices for design, performance and test specifications before any final certification or acceptance can be issued.