Proposal to enable the application to ADS vehicles, including exemptions of vehicles of subcategories X and/or Y from certain provisions concerning manual driving, attention to non-DDT tasks otherwise performed by the driver, introduction of provisions for “ADS features of type 1 and type 2”, and to update provisions concerning the running mass and occupants.

Proposal to enable application of UN R116 to ADS vehicles.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable application of UN R121 to ADS vehicles, including the exemption of vehicles of subcategory Y from the requirements of the Regulation.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable application of UN R125 to ADS vehicles, including the exemption of vehicles of subcategories X and Y.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to exempt ADS vehicles of subcategory Y from the requirements and to adapt the requirements for application to ADS vehicles, including vehicles of subcategory X. The proposal relies on the establishment of requirements for ADS vehicles to define specifications for ADS performance while an ADS feature is active.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable application of UN R151 to ADS vehicles, including the exemption of vehicle subcategories X and Y from the requirements, and to remove the references to Unique Identifier markings.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to exempt vehicles of subcategories X and Y from the requirements and limit the requirements for other vehicles equipped with an ADS and when an ADS feature is active.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to exempt vehicles not operated by a human driver from the requirements of this Regulation, including vehicles of subcategories X and Y, and to delete the provisions concerning Unique Identifier markings.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable the application of UN R161 to ADS vehicles.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable application of UN R162 to ADS vehicles.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable application of UN R163 to ADS vehicles.

Proposal from the GRSG task force on Automated Vehicles Regulation Screening to enable application of UN R166 to ADS vehicles, including the exemption of ADS vehicles of subcategories X and Y from the requirements of the Regulation.

Proposal to exempt vehicles of subcategories X and Y (ADS vehicles) from the requirements on UN R167 and to delete the provisions for Unique Identifier markings.

Proposal from the GRSG task force on Automated Vehicles Regulatory Screening to exempt ADS vehicles of subcategories X and Y from the requirements of UN R176.

Proposal to clarify that ocular reference point adjustment applies only to back angle, and to reference the original version of UN R166 to prevent future ambiguity should Annex and paragraph numbering change in subsequent amendments.

Proposal to delete paras. 15.1.2. and 15.1.3., renumber para. 15.1.4. as 15.1.2., and amend the renumbered para. 15.1.2. to provide that as from 36 months after the official date of entry into force of the 06 series of amendments, Contracting Parties applying this Regulation may prohibit the sale of helmets and visors which do not meet the requirements of the 06 series of amendments. The proposal is based on informal document GRSP-78-44 and permits Contracting Parties to issue approvals according to the 05 series of amendments, which aligns with Revision 3 of the 1958 Agreement.

Proposal to transpose GTR-9 Amendment 3 (ECE/TRANS/WP.29/2024/77) on technical requirements for Deployable Pedestrian Protection Systems, amend Chapter 0 Introduction, amend para. 2. to add provisions for vehicles equipped with DPPS and measurements taken with system undeployed, delete footnotes 2 and 3 from para. 2.1., replace reference to 2.27. by 2.29. in para. 2.31., delete footnotes 5 and 6 from paras. 2.43. and 2.45., insert new paras. 2.50. to 2.61. defining DPPS-related terms including Deployment Time, Detection test area, Head Impact Time, Sensors and Testing of DPPS, amend para. 4.2. to delete approval number supplementation provisions, delete para. 4.4.3., amend paras. 5.2. to 5.2.2. to reference Annex 7 requirements when tested with DPPS activated, replace paras. 11.1. to 11.25. with transitional provisions and insert paras. 11.26. to 11.29. establishing that as from entry into force Contracting Parties shall not refuse type-approvals under 05 series amendments, as from 1 September 2031 shall not accept prior series approvals first issued after that date, shall continue accepting prior approvals first issued before 1 September 2031, and shall continue granting approvals using atypical windscreen fracture procedures until 1 September 2033, amend Annex 1 para. 9.23.1., amend text under Annex 2 heading, amend Annex 3 para. 3.2., and insert new Annexes 7 and 8 establishing test procedures for DPPS including prerequisites, HIT verification methods, headform test procedures, HBM qualification, and documentation requirements.

Proposal to amend para. 3.3.2. to insert structured subsections for REESS trade name, cell types, physical dimensions, description, electrical specifications, gas combination rate, installation description, thermal management and electronic control, insert new paras. 4. to 9.1. requiring information on fuel cell specifications, fuses and circuit breakers, power wiring harness, protection against electric shock, power circuit component details, and hydrogen system components located in the energy absorption zone. These modifications address insufficiently defined topics on REESS type, electrical system and hydrogen system in vehicles by introducing relevant sections from UN R100 and adding hydrogen system documentation requirements.

Proposal to:

• Insert new paragraphs 2.64. to 2.xx. on electronic components,
• Amend para. 3.2.1. to require technical descriptions including overview of Supplemental Restraint Systems,
• Insert new paragraphs 4.7.5. and 4.7.6. on international insert and small infant support marks,
• Renumber paragraphs 4.12. (second one), 4.12.1. to 4.12.4., and 4.13. as 4.13., 4.13.1. to 4.13.4., and 4.14.,
• Amend para. 4.12. to clarify insert information on labels,
• Insert new paragraphs 4.12.5. and 4.12.6. on international insert and small infant support marks,
• Insert new paragraphs 5.4.4. and 5.4.5. defining international insert and small infant support marks,
• Amend para. 6.2.1.1. to clarify insert and small infant support requirements,
• Amend para. 6.2.6. to reference user inflatable elements,
• Insert new paragraph 6.6.4.1.9. on dynamic testing with Supplemental Restraint Systems,
• Insert new paragraph 6.9. on provisions for electronics including battery removability, low battery voltage reminders, and vehicle battery connection warnings,
• Amend paragraphs 14.3.1. and 14.4.1. to include insert information in size range declarations,
• Insert new paragraph 16.18. on transitional provisions applicable from entry into force through 1 September 2029,
• Insert new paragraphs 3. and 4. in Annex 2 on insert and small infant support mark arrangements.

Guidance request on restraint system with airbag submitted by Kingdom of the Netherlands. Question whether a restraint system approved according to UN R16 shall bear the word AIRBAG in the approval mark when an airbag is part of the restraint system. The Regulation seems not to require it. Discussion whether it is desirable and whether the Regulation must be updated. Proposal to amend the Regulation to include AIRBAG in the approval mark in case an airbag is part of a restraint system. Alternatively, it could be decided to leave the situation as is and see the addition of AIRBAG as optional.

Proposal to amend UN R155 and UN R156 regarding approval authority requirements:

• Add a refusal ground to para. 5.1.3. of UN R155 where the Certificate of Compliance for the Cyber Security Management System has not been issued by the same approval authority granting type approval
• Insert new para. 5.4. into UN R156 to provide that approval authorities shall not grant any type approval if the Certificate of Compliance for the Software Update Management System has not been issued by the same approval authority granting type approval.

Status report on the ADS Workshop since the 25th GRVA, covering two meetings held in June and July 2026. Task 3 addressed interpretation and guidelines, with nearly 60 change requests discussed and concluded during the Brussels meeting. Four types of changes were needed to GRVA/2026/24: consolidation of approved changes, addition of GTR version references, revised number formatting, and editorial improvements. Two informal documents are provided for clarity: a clean revision (GRVA-26-09e) and a listing of substantive changes (GRVA-26-09a1e). The workshop seeks GRVA approval for submission to WP.29 in November 2026 for adoption in March 2027. The revision applies alphabetical headings aligned with ADS regulations structure, alphanumeric subheadings for explanations, and deletes consecutive numbering to avoid confusion with GTR and UN R185 paragraph numbers.

Proposal to amend para. 5.1.3., insert new paras. 5.1.5. and 5.1.5.1. requiring the Approval Authority to refuse type approval unless the Certificate of Compliance for the Cyber Security Management System is issued by the same Approval Authority granting vehicle type approval, while permitting referencing of certificates from other Approval Authorities under specific conditions with documented agreements and clarified responsibilities, and insert new paras. 5.4. and 5.4.1. with equivalent requirements for the Software Update Management System Certificate of Compliance.

Proposal to amend UN R155 by inserting new para. 5.1.3.(e) establishing that the Certificate of Compliance for the Cyber Security Management System shall not be issued by a different Approval Authority than the one granting type approval, and amend UN R156 by inserting new para. 5.4. establishing that Approval Authorities shall not grant type approval if the Certificate of Compliance for the Software Update Management System has not been issued by the same Approval Authority granting type approval. Justification includes ensuring holistic cybersecurity assessment, clarifying reporting obligations under para. 7.2.2.2.(g), addressing unharmonized mutual recognition of management system certificates, maintaining consistency between regulations, and upholding the fundamental principle that approval authorities retain responsibility for all aspects of type approval.

Proposal to amend para. 1.4. to clarify obligations for recording data elements where sensors or systems cannot meet specified format requirements. Recording is not required if no system or sensor is designed to provide the trigger or data element, or if not operational at the time of the trigger condition or recording. However, if the vehicle is fitted with an original equipment manufacturer sensor or system designed to provide the trigger or data element in the specified format, reporting in that format is mandatory when operational. Where sensor or system design capabilities do not allow format requirements to be met, the data element shall nevertheless be recorded and the corresponding limitation reported. Failure states shall be recorded by the EDR.