The Need for Speed Act directs the Secretary of Transportation to engage a university-based transportation research institute to develop and maintain a national infrastructure intelligence tool that aligns disparate datasets to an official roadway inventory (for example, the Highway Performance Monitoring System). The tool must integrate publicly available federal, state, local, and private data (when publicly available) to identify congestion locations, diagnose causes, quantify impacts, and support quicker investment and operational decisions.
The bill prescribes specific data elements (speed and posted limits, origin–destination, crashes, asset condition, commodity flows, truck parking) and names existing federal and academic resources to be leveraged. It requires at least annual updates, consultation with State DOTs and other stakeholders, and authorizes $50 million from the Highway Trust Fund (excluding the Mass Transit Account) available for five fiscal years to carry out the program.
At a Glance
What It Does
The bill requires DOT to contract with a university-based transportation research institute to build and operate a national congestion-analysis platform that maps multiple datasets to a common roadway inventory and delivers tools for locating congestion, diagnosing causes, measuring impacts, and informing mitigation choices.
Who It Affects
Federal and State DOTs, metropolitan planning organizations, regional planning bodies, freight stakeholders (including truck operators and shippers), university transportation centers, and providers or aggregators of speed, O–D, and commercial freight data are directly affected.
Why It Matters
It creates a federally coordinated, standardized data backbone for congestion analysis that could change how projects and operations are prioritized, enable more comparable performance measurement across jurisdictions, and concentrate analytical capacity at a national level rather than leaving it fragmented among states and MPOs.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill inserts a new section into title 23 requiring the Secretary of Transportation to engage a university-based transportation research institute with demonstrated experience across traffic, freight, safety, asset condition, congestion mitigation, and data integration to develop and maintain a national infrastructure intelligence tool. The statute names the tool’s audience broadly—DOT, state and local transportation agencies, MPOs, coalitions of public agencies, and regional planners—and frames the tool as a persistent national resource for congestion identification, cause attribution, impact quantification, and faster deployment of mitigation resources.
Congress prescribes the types of data the tool must leverage and align to an official roadway inventory. That list includes a national speed dataset (operating speeds and posted limits) with at least three years of history for functional classes 1–6, a national origin-and-destination dataset with at least three years of history, crash and safety records, asset-condition records (for example, HPMS data), commodity flow measures (type, tonnage, value), and truck parking demand/supply where available.
The bill also directs use of existing federal products (Urban Congestion Report, Freight Mobility Trends, FHWA safety and condition measures) and named academic and state tools as sources to be aligned—explicitly citing Texas A&M, University of Maryland resources, and several State DOT tools as models or inputs.Operationally, DOT must update the tool at least annually and consult with State DOTs, transportation advocacy groups, and other “appropriate organizations.” The statute authorizes $50 million from the Highway Trust Fund (excluding the Mass Transit Account) for implementation, available for five fiscal years; the text also clarifies these funds are additive to other funding. The combination of statutory data requirements, specified examples, and a defined funding pot creates a bounded scope: a national, standardized analytic platform that builds on existing federal and academic products but is intended to provide a single, comparable congestion intelligence capability for public agencies.
The Five Things You Need to Know
The statute requires DOT to engage a university-based transportation research institute (not an unspecified contractor) to develop and maintain the tool.
The tool must include a national speed dataset and an origin–destination dataset with not less than three years of historical data for public roads functionally classified 1–6.
Congress explicitly lists datasets and resources to be leveraged (HPMS, FHWA Urban Congestion Report, Freight Mobility Trends) and names state and academic tools—Texas A&M and University of Maryland among them—as sources to align.
DOT must update the tool at least annually and consult State DOTs, advocacy groups, and other stakeholders in its development.
The bill authorizes $50 million from the Highway Trust Fund (other than the Mass Transit Account), available for five fiscal years, and specifies those amounts are additive to other funding.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Declares the Act’s short title as the "Need for Speed Act." This is a formal label with no programmatic effect but signals Congressional intent focused on congestion and travel speeds.
Required engagement with a university-based institute
Directs the Secretary to engage a university-based transportation research institute with a history across traffic, freight, safety, asset condition, congestion mitigation, performance measurement, and data integration to develop and maintain the national tool. The statutory requirement to pick a university-based institute (rather than an arbitrary contractor) steers the program toward institutions with established research credentials and public-sector collaboration experience, which may affect procurement approaches and IP/data-sharing expectations.
Purpose and core functions of the tool
Sets four explicit objectives—locate congestion, provide context to determine causes, quantify impacts, and enable faster deployment of mitigation through investment and operations. Those objectives shape design priorities: diagnostics and performance metrics over, say, purely visualization or commercial product features. They also create an expectation that the tool will support decision-making at project, program, and operational time horizons.
Required data components and named sources
Lists core datasets the tool must leverage and align to an official roadway inventory: HPMS/roadway inventory, a national speed dataset, a national O–D dataset (each with ≥3 years historical), crash and safety data, asset-condition data, commodity flow details, and truck parking supply/demand where available. The provision also directs alignment with specific federal products and explicitly names several state and academic tools as inputs. That combination both constrains the technical design (data alignment to HPMS) and pressures interoperability with a mix of legacy state systems and proprietary commercial feeds.
Update cadence, consultation, and funding
Requires at least annual updates to the tool, consultation with State DOTs and other groups, and authorizes $50 million from the Highway Trust Fund (not the Mass Transit Account), available for five fiscal years and additive to other funds. The authorization sets a finite funding window and scale that will influence the initial scope, hosting model, and whether the tool is sustained within DOT or moved to an external host after the authorization period.
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
- Federal Highway Administration and DOT policy offices — gain a standardized, national data backbone for congestion diagnostics and performance measurement that can improve comparability across states and inform federal grant and program decisions.
- State DOTs and metropolitan planning organizations — receive a ready-made analytical tool and curated datasets that can reduce in-house data aggregation efforts, especially for agencies without strong analytics capacity.
- Freight operators, shippers, and logistics planners — benefit from integrated commodity flow, truck parking, and speed/O–D data that can improve route planning and highlight bottlenecks affecting reliability.
- University transportation research centers — stand to gain contracts, visibility, and a role in long-term tool maintenance if selected, reinforcing university–government partnerships.
- Regional coalitions and multi-agency planning bodies — can use a common dataset and methodology to coordinate cross-jurisdictional congestion responses and investment prioritization.
Who Bears the Cost
- Highway Trust Fund (general highway account) — the $50 million appropriation is authorized from the Highway Trust Fund (excluding the Mass Transit Account), which represents an opportunity cost for other highway priorities.
- State and local agencies — will need to align local inventories and feed data into the national tool, incurring integration, QA/QC, and possibly licensing costs for proprietary inputs.
- DOT operational units and FHWA staff — must manage contracts, maintain the tool, and conduct stakeholder outreach, creating staffing and administrative burdens without a separate fully funded operations line beyond the 5-year window.
- Private data providers and data aggregators — may face pressure to make more data ‘‘publicly available’’ or deliver compatible feeds; they may also bear costs in standardizing and sharing data at the required granularity.
- Smaller MPOs and rural agencies — may need technical assistance to map local data to the official roadway inventory and to use the outputs effectively, which could require additional training or local investments.
Key Issues
The Core Tension
The central tension is between standardization and subsidiarity: Congress seeks a single, standardized national congestion intelligence capability to make performance comparable and speed deployment of mitigations, but doing so requires imposing technical standards, data-sharing expectations, and governance choices that may override local methods, impose costs on smaller agencies, and raise proprietary and privacy concerns—trade-offs between national comparability and local flexibility that have no simple technical fix.
The bill centralizes a large set of heterogeneous data under a federally coordinated platform, but leaves several implementation questions open. It requires alignment to an "official" roadway inventory (eg, HPMS) without defining the technical mapping rules, change-management processes, or acceptable error tolerances; those details will determine whether state inventories can be harmonized at scale or whether extensive rework will be necessary.
The statute also requires certain historical data horizons (≥3 years for speed and O–D) but does not specify sampling resolution, spatial granularity, privacy-preserving aggregation techniques, or standards for commercially sourced feeds. Those omissions create downstream choices that will affect data costs, representativeness, and privacy risk.
Another trade-off is sustainability. Congress authorizes $50 million over five fiscal years and labels those funds additive, but the law does not create a permanent funding stream or a post-authorization governance model.
If the tool proves valuable, agencies will face decisions about hosting, maintenance, licensing, and staffing once those appropriations lapse. Finally, the statute explicitly names several state and academic tools as inputs; that accelerates initial development but risks embedding the assumptions and biases of those models (for example, Texas-centric congestion measures or specific freight fluidity methodologies) into a national standard, making future recalibration politically and technically harder.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.