Sponsors (2)
The bill increases safety, transparency, and regulatory enforceability by requiring manufacturers to define and publish exact ODDs and enabling NHTSA oversight, but does so at the cost of added industry compliance expenses, potential higher vehicle prices and narrowed system functionality, plus some proprietary/security exposure for manufacturers.
Drivers and other road users: experience fewer unexpected automated driving maneuvers because manufacturers must restrict driving automation to clearly defined, safe operational design domains (ODDs).
Consumers and the public: gain clearer information about where and how driving automation will operate because manufacturers must publish exact ODD declarations on a public website.
Federal and state safety regulators: obtain clearer authority and an enforceable basis because NHTSA can treat ODD requirements as motor vehicle safety standards, enabling more consistent oversight and enforcement.
Vehicle manufacturers (and ultimately buyers): face additional compliance costs to define, report, and prevent operation outside ODDs, which could raise vehicle prices.
Drivers and transportation workers: may get reduced real-world automated driving functionality if systems are limited to narrower ODDs to avoid noncompliance.
Manufacturers and technology workers: face proprietary and security risks because publishing exact ODDs could reveal sensitive software/hardware details or attack vectors.
Based on analysis of 2 sections of legislative text.
Introduced December 17, 2025 by Edward John Markey · Last progress December 17, 2025
Requires vehicle manufacturers to define the exact operational design domain (ODD) for any driving automation system, file that exact ODD declaration with the federal Administrator, and publish the identical declaration on a public website. Prohibits driving automation systems from operating outside their defined ODD and adds those requirements to the motor vehicle safety standard framework, with the law taking effect 180 days after enactment.