FOI: UN R171 Notice Covering Tesla FSD Sat in a Rarely Checked UK Inbox
A Freedom of Information response from the Foreign, Commonwealth and Development Office was released on 3 November 2026 (FOI2026/22677). It shows how a United Nations notice about UN Regulation 171 Series 02 reached the United Kingdom 🇬🇧.
The UK Mission in Geneva received that notice at 18:25 on 28 July 2026. UNECE said the notice "triggers the start of the six months period" under Article 12(2) of the 1958 Agreement, and asked the Mission to "transmit this Notification to the Ministry in charge". It went to what the Mission itself described as "a generic UKMis email account that only gets checked occasionally".
The Department for Transport received a copy on 15 September 2026, seven weeks later.
UN Regulation 171 Series 02 is the next set of Driver Control Assistance Systems rules. That's the framework that covers Tesla FSD (Supervised) TAD. The FOI itself does not mention Tesla. For the wider rule changes, see What UN R171 Series 02 changes for Tesla FSD and the UNECE, DCAS and UN R171 explainer.
It looks like the six-month clock was already running while the official notice remained in a sparsely checked inbox.
| Date | What the FOI records |
|---|---|
| 28 July 2026, 18:25 | UK Mission in Geneva receives UNECE's preliminary notification for UN R171 Series 02 |
| 15 September 2026 | Department for Transport receives a copy (seven weeks later) |
| 24 December 2026 | Into-force date calculated by the Department for Transport from the notification document |
Timeline from FCDO FOI2026/22677. The 24 December figure is the Department for Transport's calculation, as recorded in the digest.
What did the UNECE notice say?
At 18:25 on 28 July 2026, the UK Mission in Geneva received an email from UNECE's Vehicle Regulations, Road Traffic Safety and Transport Innovations Section. Attached to that email was a Preliminary Notification of Proposals for Amendments to UN Regulations. The FOI digest describes that attachment as UNECE/TRANS/2026/10, dated 27 June 2026.
How did the notice reach the Department for Transport?
On 15 September 2026, at 14:55, the Mission told the Department for Transport that it receives these notices periodically. It wrote: "Next time I receive one, I will forward immediately to this group".
At 15:41 the same day, the Mission forwarded the July notice and explained where it had landed. The notices, it wrote, "only get sent to a generic UKMis email account that only gets checked occasionally".
At 15:53, the Department for Transport asked whether the Mission received emails confirming dates of entry into force for WP.29 regulations. Then it said: "These dates are very important for manufacturers wanting to obtain approvals as soon as legally possible, and for VCA colleagues to be sure they know when they can start issuing approvals."
At 15:59, the Department asked the Mission to forward the last notice it had received, and said: "We can then work out whether there are any others." It also wrote: "I wondered if you could set up a 'rule' in your email inbox that automatically forwards future ones to save you having to remember?"
On 16 September 2026, at 08:20, the Mission asked: "Do you think there's something we've missed since July?"
At 14:54 that afternoon, the Department for Transport replied that it would only expect these emails after a session of WP.29 itself, rather than after the working groups, and therefore only after the March, June and November sessions. It said it did not think anything had been missed since July.
What date did the Department for Transport calculate?
At 22:55 on 15 September 2026, the Department for Transport told the Mission that the July attachment was what it needed. Officials wrote that the preliminary notification document "gives us the date of 24 June", and that they believed "the into force date should be exactly six months after that, so 24 December".
That 24 December 2026 figure is the Department for Transport's calculation from the notification document, as recorded in the FOI digest. The papers do not include a later depositary notice confirming the date. They do not show that type approvals, or Tesla FSD (Supervised) TAD, were delayed because of the seven weeks.
The Vehicle Certification Agency is the UK body that issues type approvals.
The FOI does not mention Tesla, and it does not show illegality or a deliberate delay. It shows how this notice was received and passed on, in the words of the people who handled it. Without this FOI, that exchange would not be on the public record.
Sources
- FCDO FOI2026/22677, information digest, 3 November 2026. Names are redacted in the release as [Name]. The images above are watermarked excerpts from that digest. The full PDFs are not published with this article.
- What UN R171 Series 02 changes for Tesla FSD
- UNECE, DCAS and UN R171 explainer
- Tesla FSD (TAD) in the UK: current status
