Czechia now permits Tesla FSD Supervised under a provisional approval. For a company fleet, the important fact is not the product name: the driver must supervise continuously and remains responsible for driving.
On 21 September 2026, the Czech Ministry of Transport recognised a provisional approval for Tesla FSD Supervised that had been issued by the Dutch type-approval authority RDW. The decision makes the system usable in Czechia under the conditions of that provisional approval.
This is relevant to companies with Tesla vehicles in their fleet, but its wider lesson matters more. Advanced driver-assistance systems are becoming part of vehicle policy, insurance communication, driver training and incident reporting. A company should decide how it will manage them before an employee uses one on a business trip.
The starting point is clear. The Ministry of Transport classifies FSD Supervised as SAE Level 2, meaning partial driving automation. It is an assistance system, not an autonomous vehicle. The driver must stay focused on the road, supervise the system and be ready to take control immediately. Legal responsibility for driving remains with the driver.
What the Czech decision does and does not mean
The Ministry recognised a Dutch provisional EU type approval issued by RDW on 10 April 2026 under Regulation (EU) 2018/858. Czechia joined the Netherlands and five other European countries in allowing use under the stated conditions.
That is a market-access decision for a specific system. It is not a general approval of autonomous driving, a transfer of liability to a vehicle manufacturer or a promise that every function will be available on every compatible vehicle.
| What has changed | What has not changed |
|---|---|
| Tesla FSD Supervised may be used in Czechia under the conditions of the provisional approval | The driver remains responsible for driving and must supervise at all times |
| A Czech fleet can assess whether the system fits its internal vehicle policy | The company should not assume a feature is available on every vehicle, road or software version |
| The decision gives a practical example of how a Member State can recognise a provisional approval | It does not create a general European autonomous-driving framework |
| The system can assist with driving tasks | It does not permit a driver to read, work, use a phone or stop watching traffic |
The Ministry’s announcement does not publish a complete operational feature list, vehicle list or activation timetable for Czechia. Fleet managers should therefore verify current manufacturer information for each vehicle and software version rather than relying on a news headline.
SAE Level 2 in plain English
The SAE levels describe the division of driving tasks between the system and the human driver. At Level 2, a system can support steering and speed control in defined circumstances, but the human driver remains the person responsible for the driving task.
This distinction is easy to lose when a product name uses words such as “self-driving”. It is especially important in a company environment, where a driver may assume that an approved feature is also approved by an employer or insurer.
For fleet policy, the useful question is not whether a car can perform an impressive manoeuvre. It is whether the driver can still supervise safely in real traffic, identify when the system is not suitable and take over without delay.
Make the fleet rule explicit
An advanced assistance system should not sit outside the usual vehicle-policy framework. A company does not need a long document, but it should give drivers a clear answer to five questions.
1. Which systems are allowed?
List the approved systems by vehicle model and, where necessary, software version. Distinguish the manufacturer’s description from the company’s own permission to use the feature for business travel.
A simple rule may be enough: only manufacturer-provided functions that are lawfully available in Czechia may be used, and only as assistance under continuous driver supervision. Do not create a policy that implies hands-free or unattended operation where the system and the law do not allow it.
2. What must a driver understand first?
Before a system is used on company travel, drivers should receive a short practical induction. It should cover the need to watch the road, keep control of the vehicle, recognise warnings, intervene promptly and follow normal rules on mobile-phone use, fatigue and speed.
The induction should also say that a system may perform differently after a software update or in rain, poor visibility, roadworks, unclear lane markings or an unfamiliar route. The point is not to test every edge case. It is to avoid the false belief that activation removes the driver’s attention duty.
3. What happens after an incident or near miss?
Use the same immediate safety and reporting route as for any other vehicle incident. The driver should first secure the situation and follow emergency procedures. The company’s internal report should then record whether an assistance feature was active, which vehicle and software version were involved, what warnings appeared and what action the driver took.
This is useful operational evidence. It is not a conclusion about fault. A fleet manager, insurer, manufacturer or authority may need separate information and should make its own assessment.
4. Who owns software updates and vehicle settings?
Some systems change materially through software updates. Assign a fleet owner for checking update notices, vehicle eligibility, driver communication and any change to the company’s permitted-use rule.
Drivers should not be expected to interpret a release note, guess whether a function is approved locally or decide alone whether a changed system remains appropriate for a company vehicle.
5. How will the company handle data and insurance communication?
Connected vehicles can generate location, video, diagnostics and event data. A company should decide what it collects, who can access it, how long it keeps it and how it informs drivers, consistent with its privacy and employment obligations.
It should also review fleet-insurance terms and the incident-notification process before a major policy change. The aim is not to assume that an insurer has accepted a new risk. It is to make sure that a driver and manager know whom to contact after an event.
Do not build a policy around one manufacturer
Tesla is the immediate reason for this article, but the policy should be technology-neutral. More vehicles will arrive with increasingly capable lane, speed, parking and driving-assistance functions. A separate rule for each brand quickly becomes difficult to maintain.
Instead, classify systems by what the driver must do. A fleet policy can distinguish between standard safety assistance, supervised partial driving automation and any future system that would require a different legal or insurance assessment.
The company can then update one policy as vehicles change, rather than issuing a new instruction every time a manufacturer introduces a feature name.
A sensible introduction sequence
- Identify the vehicles and assistance functions already present in the fleet.
- Confirm which functions are lawfully available in Czechia and relevant for the vehicle’s current software.
- Set a written supervised-use rule and give drivers a short induction before use on business travel.
- Update the incident form, fleet contact route and internal data-handling guidance.
- Review the policy after the first incidents, driver feedback or material software updates.
The main conclusion
The Czech decision makes FSD Supervised a real fleet-policy question, not merely a consumer-technology story. It does not make a company car autonomous, and it does not remove responsibility from the person behind the wheel.
For a fleet manager, the practical response is straightforward: allow advanced assistance only when the driver knows its limits, the company has a clear reporting route and the vehicle’s actual availability has been checked. A written rule is more valuable than a broad promise that the system will make driving safer.
How Kodo can help
Kodo helps international mobility, technology and industrial companies prepare the commercial and operational side of entering Czechia. We support early market validation, partner mapping, local positioning, English and Czech communication, web content and coordination of the first implementation steps.
For legal, tax, regulatory, certification and investment-incentive matters, companies should work with qualified specialists and the responsible authorities.
Related reading
- Why Czechia Works as a Central European Aftersales and Service Hub
- Your First Business Days in Prague: Transport, Money, Alcohol and Staying Safe
- Entering the Czech Market: What International Businesses Should Prepare Before They Launch
Sources
- Czech Ministry of Transport — recognition of the provisional approval of Tesla FSD Supervised
- RDW — explanation of the provisional type approval for Tesla FSD Supervised
- Regulation (EU) 2018/858
This article provides general fleet and market-entry information, not legal, insurance, road-safety, employment or privacy advice. Companies should verify requirements for their specific vehicles, drivers, policies and operating model.
