The Stay in Your Lane Act adds a new section to title 49 that requires manufacturers of driving automation systems to ensure those systems do not operate outside the manufacturer-defined operational design domain (ODD). The bill also requires manufacturers to submit the ODD definition to the National Highway Traffic Safety Administration (NHTSA) and to publish the exact declaration on their websites.
The Act gives NHTSA an enforcement hook by treating violations of the ODD-operational rule and the declaration requirement as subject to civil penalties under existing law, and it incorporates these requirements into the statutory definition of a motor vehicle safety standard. The statute takes effect 180 days after enactment, creating a short compliance window for manufacturers and suppliers.
At a Glance
What It Does
The bill compels manufacturers of driving automation systems to both define their system’s operational design domain and to prevent the system from operating outside that domain. It requires submission of the exact ODD declaration to NHTSA and public posting on the manufacturer’s website.
Who It Affects
Original equipment manufacturers and suppliers that build or sell driving automation systems (systems capable of sustained lateral and longitudinal control); companies offering over-the-air software updates for those systems; and NHTSA, which gains explicit enforcement authority tied to civil penalties.
Why It Matters
The measure turns manufacturer ODD statements into enforceable obligations and expands what counts as a motor vehicle safety standard — shifting legal risk and compliance duties onto makers of higher-level automation and their software supply chains, while giving regulators clearer grounds to penalize noncompliance.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill introduces a single new statutory section that starts with compact but consequential definitions. It defines a “driving automation system” as the hardware and software that together can take over both lateral and longitudinal control of a vehicle on a sustained basis — in practice targeting higher-level automated driving systems rather than simpler driver-assistance features.
It also defines an operational design domain (ODD) to mean the set of conditions—environmental, geographic, time-of-day, traffic or roadway characteristics—under which a system is designed to function safely.
Under the core operative text, the manufacturer must make the ODD the boundary of where the system may lawfully operate: the statute requires the manufacturer to ensure the system does not operate outside its ODD. The bill then requires each manufacturer to (1) produce a precise, written definition of that ODD, (2) submit that exact declaration to the NHTSA Administrator, and (3) post the identical declaration on a publicly accessible page of the manufacturer’s website.
The publication requirement is explicit: what NHTSA receives must match what the public can read.On enforcement, the Act adds the ODD operational prohibition and the declaration rule into the existing civil-penalty framework by amending the statute that authorizes monetary penalties. It also expands the statutory definition of a “motor vehicle safety standard” to include the new ODD-operational duty and the declaration requirement, which elevates the legal consequences of noncompliance and makes these provisions a formal safety standard rather than merely guidance.Practically, compliance will require manufacturers to translate their engineering constraints into legally framed ODD declarations and to build technical or operational controls so that systems cannot exceed those boundaries — whether by software lockouts, geofencing, capability detection, or automated fallbacks.
The Act sets the legal standard for safety as “no more than an inconsequential risk,” which is a deliberately high and somewhat ambiguous benchmark manufacturers and regulators will need to interpret in rulemaking and enforcement actions. The new obligations take effect 180 days after the Act becomes law, starting the clock for both documentation and any necessary product or software changes.
The Five Things You Need to Know
The bill mandates that a driving automation system must not operate outside the manufacturer-defined operational design domain (ODD); manufacturers must ‘ensure’ compliance.
Manufacturers must create a precise ODD definition, submit that exact declaration to the NHTSA Administrator, and publish the identical text on a publicly accessible company website.
The statute defines a driving automation system as the hardware and software that can perform both lateral and longitudinal vehicle control on a sustained basis, and it specifies ODD content (environmental, geographic, time-of-day, and presence/absence of traffic or roadway characteristics).
The bill makes violations of the ODD-operational rule and the declaration requirement subject to civil penalties by amending the existing enforcement provision (49 U.S.C. 30165).
It defines ‘safely’ as presenting no more than an inconsequential risk and takes effect 180 days after enactment, requiring relatively rapid compliance and interpretation of that safety threshold.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions: driving automation system, operational design domain, and safety standard
This subsection sets the technical vocabulary the rest of the section uses. Importantly, it narrows the covered systems to those capable of sustained lateral and longitudinal control — a practical delineation that separates true driving automation from lower-level driver-assist features. It also lists what an ODD must address (environmental, geographic, time-of-day limits, and required/forbidden traffic or roadway characteristics) and provides a statutory meaning of ‘safely’ as producing no more than an inconsequential risk. Those definitional choices will shape how manufacturers write their declarations and how NHTSA evaluates compliance.
Operational restriction: systems must not operate outside their declared ODD
This is the operative mandate: manufacturers ‘shall ensure’ that their driving automation systems do not operate outside the declared ODD. The language imposes an affirmative obligation on manufacturers to build controls, monitoring, and fallback behaviors so that operation beyond the domain does not occur. From an implementation standpoint this raises questions about required technical solutions (e.g., geofencing, sensor-based detection, forced handoff or safe-stop behaviors) and about how NHTSA will prove in enforcement actions that a system ‘operated’ outside its ODD.
ODD declarations: submission to NHTSA and public posting
Paragraph (1) requires each manufacturer to define its ODD and submit that definition to the NHTSA Administrator; paragraph (2) requires posting the exact declaration on a public website. The statute makes the submitted text and the public text the same document, preventing manufacturers from using different wordings for regulators and consumers. Practically, manufacturers will need internal processes to draft, approve, and update ODD declarations and to align software release processes so that any change to a system’s capabilities is matched to an updated public and submitted declaration.
Enforcement: making ODD violations subject to civil penalties
The bill inserts a cross-reference so that violations of the new ODD operational restriction are explicitly within the scope of civil penalties authorized under section 30165(a)(1). That links the new duties to an existing statutory enforcement tool, enabling NHTSA to impose monetary penalties without first creating a separate enforcement regime. How NHTSA chooses to investigate, prove, and quantify violations will determine the statute’s real-world bite.
Classifying the ODD rule and declaration as motor vehicle safety standards
The bill amends the statutory definition of ‘motor vehicle safety standard’ to include the requirements in subsections (b) and (c)(1) of the new section 30130 — i.e., the operational restriction and the NHTSA-submitted declaration. By making these statutorily recognized safety standards rather than guidance, the law elevates their legal status and exposes manufacturers to the full regime of regulatory consequences and liability that attach to safety standards.
180-day compliance clock
The Act and its amendments take effect 180 days after enactment. That timetable creates a short window for manufacturers to draft ODD declarations, adjust product designs or software update practices, and establish publication and recordkeeping practices before the new requirements become enforceable.
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
- Road users and the general public — benefit from clearer statutory limits on where automated systems may operate, which can reduce incidents caused by system misuse outside tested conditions.
- NHTSA and federal regulators — gain explicit authority and a clearer enforcement pathway (civil penalties and safety-standard status) to hold manufacturers accountable for systems operating beyond declared capabilities.
- Manufacturers that take a conservative approach — receive regulatory clarity: firms that document realistic, well-validated ODDs can use those declarations defensibly in compliance programs and in communications with customers and insurers.
Who Bears the Cost
- Vehicle manufacturers and software suppliers — must invest in ODD documentation, technical controls (e.g., geofencing, capability checks, safe-stop systems), revised design and testing procedures, and processes for synchronizing software updates with ODD declarations.
- Smaller startups and suppliers — face disproportionate compliance burdens and potential market exclusion if they lack resources to validate ODDs and implement the required operational safeguards within the 180-day window.
- NHTSA and enforcement apparatus — will need staff, investigative resources, and technical expertise to review declarations, assess whether systems actually operated outside ODDs, and oversee timely updates to public declarations.
Key Issues
The Core Tension
The central dilemma is between enforceable, transparent limits that protect public safety and the risk that turning manufacturer ODDs into binding legal commitments will either push companies to choose overly narrow, commercially uncompetitive domains or to draft ambiguous declarations that undermine consumer clarity; the law seeks both stronger safety guarantees and straightforward implementation, but those goals pull in opposite directions when translated into engineering and business choices.
The bill converts manufacturer ODD statements into enforceable commitments without spelling out the technical or procedural standards for compliance. That leaves several hard implementation questions: what evidence will suffice to show a system ‘operated’ outside its ODD (onboard logs, telematics, witness statements), how granular an ODD must be, and how frequently manufacturers must update the public declaration as software changes.
The statutory definition of ‘safely’ as ‘no more than an inconsequential risk’ raises the bar in broad terms but offers little operational guidance on acceptable risk thresholds, test methods, or validation protocols.
The enforcement design also creates strategic incentives that could cut both ways. Manufacturers may respond by narrowing ODDs to minimize exposure, producing conservative but limited deployments; or they may write vague ODDs that are difficult for regulators to challenge.
Making the declaration a public document aids consumer transparency but also creates potential litigation leveraging those statements as precise promises. Finally, the statute does not address how ODD boundaries interact with over-the-air updates, interstate operation near jurisdictional lines, or the handoff dynamics between automated systems and human drivers — practical gaps that will require regulatory guidance, industry standards, or follow-on legislation.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.