The Know Before You Drive Act targets gaps between what partially automated driving systems actually do and what consumers are told. It forbids manufacturer statements that imply a partially automated system is a full automated driving system or has capabilities beyond those it actually performs, requires structured consumer notices at first sale and after material software updates, and adds mandated labeling content to the federal automobile window‑sticker law.
Practically, the bill forces manufacturers to disclose the system’s operational design domain (ODD), the specific subtasks a driver must perform (notably object and event detection and response), and whether any ongoing fees or services are required. It creates parallel enforcement routes—NHTSA, the FTC, and state attorneys general—and directs DOT to write implementing regulations for the new sticker requirements.
For manufacturers, dealers, and compliance teams this means new content, timing, and recordkeeping obligations; for buyers it means more standardized information to compare systems and understand what to expect behind the marketing.
At a Glance
What It Does
The bill bars representations that would lead a reasonable person to think a partially automated driving system is a fully automated driving system or can perform beyond its capabilities. It requires clear, conspicuous notices at first sale describing system features, capabilities, limitations, the operational design domain, and the driver subtasks retained; it also requires notices when software updates materially change dynamic‑driving performance. The Automobile Information Disclosure Act (window‑sticker law) is amended to add plain‑language and icon disclosures for these systems.
Who It Affects
Original equipment manufacturers (OEMs) that market and update partially automated systems, franchised dealers who must deliver the first‑sale notices, vehicle software teams that push OTA updates, the Department of Transportation (for rulemaking), NHTSA and the FTC (for enforcement), and state attorneys general who gain civil‑action authority. Consumers and safety·compliance professionals will use the disclosures to compare systems.
Why It Matters
The bill standardizes ODD and task disclosures that today vary widely across vendors, making marketing claims easier to compare and regulate. It also shifts compliance responsibilities into sales and software‑update workflows, potentially changing how OEMs describe features, how dealers train staff, and how software releases are documented and communicated to owners.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
At its core the Know Before You Drive Act tries to close a persistent mismatch: manufacturers use language and imagery that leads drivers to expect more autonomy than the vehicle actually provides. The bill addresses that with three tools.
First, it creates a bright‑line prohibition against claims that imply a partially automated driving system is a fully automated driving system or that the system does things it cannot. Second, it creates mandatory consumer notices at first sale and for material software updates that affect the dynamic driving task.
Third, it supplements the federal window‑sticker law so buyers see standardized, plain‑language information that makes cross‑model comparisons possible.
The first‑sale notice must be ‘‘clear and conspicuous’’ and enumerate the system’s features, its capabilities and limitations, the operational design domain (ODD), and the specific subtasks a driver must perform while the system is engaged—most importantly the object and event detection and response subtask and the requirement to supervise the system. The bill places the initial notice obligation on manufacturers to furnish the notice to dealers before vehicle delivery, while protecting dealers from liability if the manufacturer fails to supply compliant material and protecting manufacturers if dealers fail to hand the notice to purchasers.For recurring changes, the bill requires manufacturers to notify an owner, lessee, or driver whenever a software update materially affects how the vehicle performs any part of the dynamic driving task, and explicitly includes over‑the‑air updates.
The update notice must describe each material change to capabilities and limitations so a recipient can understand how an OTA patch altered driver responsibilities or system behavior. In parallel, the Automobile Information Disclosure Act is amended to require the Monroney label to list whether a vehicle has a partially automated or automated driving system, describe what subtasks the system performs, state whether driver supervision is required, describe ODD restrictions (geography, time‑of‑day, environment, road characteristics), and disclose any recurring service cost or fee on an annual basis.Enforcement is layered.
The bill adds the new notice and marketing prohibitions to NHTSA’s enforcement authorities, treats violations as unfair or deceptive acts the FTC can pursue under its existing powers, and authorizes state attorneys general to bring civil suits (with notice and coordination provisions so the FTC may intervene and to avoid simultaneous state suits while a federal action is pending). The Department of Transportation must issue regulations within nine months to implement the Monroney label changes, with an implementation window of two years for labels to appear on new vehicles.
The Five Things You Need to Know
The bill bans, within 180 days of enactment, any manufacturer representation that implies a partially automated system is a fully automated driving system or that it can perform beyond its actual capabilities.
Within two years of enactment, manufacturers or dealers must provide a conspicuous first‑sale notice describing the system’s features, capabilities and limitations, the operational design domain, and which dynamic driving subtasks the driver must perform (explicitly including object/event detection and response).
Manufacturers must notify owners, lessees, or drivers when any software update materially affects the performance of the dynamic driving task, and that duty covers over‑the‑air updates.
The Automobile Information Disclosure Act (Monroney label) will require plain‑language or icon disclosures that identify performed subtasks, whether driver supervision is required, ODD restrictions (geographic, time‑of‑day, environmental), and any annual service cost or fee; DOT must issue implementing rules within nine months.
Enforcement is split: NHTSA gains an explicit statutory hook, the FTC can treat violations as unfair or deceptive acts, and state attorneys general may sue for injunctive relief, damages, penalties, and restitution, subject to notice and coordination with federal actions.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title: Know Before You Drive Act
This section simply supplies the Act’s short name; it has no substantive compliance effect but is the reference point used throughout the statute and in regulatory or enforcement citations.
Prohibition on misleading claims
The statute forbids manufacturer statements that would lead a reasonable person to believe a partially automated driving system is a full automated driving system or that the system can do more than it actually can. Practically, this is a marketing standard judged from the perspective of a reasonable consumer rather than a technical correctness safe harbor; promotional materials, owner’s manuals, in‑vehicle messages, and advertising will be evaluated under that objective test.
First‑sale notice requirements and dealer/manufacturer roles
Manufacturers must deliver a clear, conspicuous notice to purchasers by the time of the first sale (deadline: within two years of enactment for the rule to apply). The notice must say the vehicle has a partially automated system, list its features, explain capabilities and limitations including the ODD, and identify the driver subtasks the owner is expected to perform (naming object/event detection and response and supervising the system). The manufacturer must provide the notice to the dealer before delivery; the statute insulates dealers from liability if a manufacturer never supplied the notice and insulates manufacturers from dealer failures to hand the notice to the buyer.
Notification obligations for material software updates
When a software update materially changes how the vehicle performs the dynamic driving task—explicitly including over‑the‑air updates—the manufacturer must give a clear, conspicuous notice to the owner, lessee, or driver describing each material change to capabilities and limitations. The statutory term “materially affects” is not further defined in the text, so implementation will depend on DOT/agency guidance and future enforcement interpretations; this is the rule that governs incremental software changes post‑sale.
Enforcement by NHTSA, the FTC, and state attorneys general
The bill amends NHTSA’s enforcement citation to cover the new prohibitions and notice duties, and simultaneously classifies violations as unfair or deceptive acts under the FTC Act so the FTC can bring actions with its usual remedies. State attorneys general get explicit civil‑action authority (injunctions, damages, penalties, restitution, attorneys’ fees), but must notify the FTC before filing and cannot sue while a federal enforcement action against the same defendant is pending—this sets up coordinated federal‑state enforcement with the FTC able to intervene.
Monroney label amendments and DOT rulemaking
The Automobile Information Disclosure Act is modified to require new sticker content for vehicles equipped with partially automated or automated driving systems: short descriptions sufficient to identify subtasks the system performs, whether driver supervision is required, stated ODD restrictions (geographic, time‑of‑day, road and environmental conditions), and any recurring service cost on an annualized basis. The Secretary of Transportation must issue regulations within nine months to implement the label changes, and labels must be in place within two years of enactment—putting a concrete timeline on standardizing disclosures at point of purchase.
Key statutory definitions
The bill defines critical terms to set the scope: 'automated driving system' means hardware and software that can perform the entire dynamic driving task; 'partially automated driving system' performs lateral and longitudinal control while expecting the driver to complete object/event detection and response; 'dynamic driving task' is defined to include steering, acceleration, environment monitoring, response preparation/execution, maneuver planning, and conspicuity actions. These definitions fix the statute’s scope and will be the reference for both disclosures and enforcement.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Prospective vehicle purchasers — they gain standardized, plain‑language information on what a vehicle’s partially automated system actually does and where it won’t, enabling better comparisons across makes and models.
- Safety and consumer advocates — clearer disclosures and FTC/NHTSA enforcement tools make it easier to challenge misleading marketing and to push for behavior that reduces driver overreliance on partial automation.
- Regulators and compliance teams — standardized requirements reduce ambiguity about what disclosures regulators expect, allowing structured audit trails for marketing and software‑release decisions.
Who Bears the Cost
- Vehicle manufacturers (OEMs) — they must change marketing, labeling, documentation, sales workflows, and software‑release playbooks to produce and distribute required notices, plus absorb costs for producing Monroney label content and potential litigation or penalties.
- Dealers and sales staff — dealers must receive, store, and present the required first‑sale notices and may need additional training and recordkeeping, even though the statute limits their liability in certain manufacturer failures.
- Regulatory agencies (DOT, NHTSA, FTC) — agencies will need to write guidance, process complaints, and enforce new disclosure and update obligations, which can strain budgets and staff resources if enforcement activity rises significantly.
Key Issues
The Core Tension
The central dilemma is protecting consumers from overstating system capabilities while avoiding regulatory requirements that either swamp buyers with technical minutiae or chill manufacturers from communicating useful, incremental improvements; the bill trades off consumer clarity and legal enforceability against the practical difficulty of standardizing highly technical ODD and software‑update disclosures across rapidly evolving vehicle software ecosystems.
The bill’s practical impact hinges on a set of implementation choices and ambiguous legal terms. ‘‘Materially affects’’—the trigger for update notices—has real operational significance for OTA‑heavy firms that ship frequent incremental changes; without agency guidance that term could produce over‑notice (flooding owners with minor release notes) or under‑notice (manufacturers declining transparency to avoid the burden). The statutory prohibition uses the reasonable‑person benchmark for marketing claims, which is purposefully broad; enforcement will require subjective judgments about advertising context, in‑vehicle messaging, and technical disclosures.
Coordination among NHTSA, the FTC, and state attorneys general creates an enforcement web that is robust but also potentially duplicative. The statute prevents state suits while a parallel federal action is pending, but it still allows staggered enforcement and differing interpretations across jurisdictions.
Finally, mandating detailed ODD disclosures and listing subtasks improves transparency but risks overwhelming consumers with technical detail unless DOT and industry converge on concise iconography and plain‑language templates.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.