The Capitol LedgerEvery move in Congress, on the record
HomeBillsRecordsLedger AI

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

AboutFAQFeedbackTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

The Capitol Ledger

Built from the Congressional Record and Congress.gov. Every summary links to its source.

The projectAboutFAQFeedback
LegalTerms of ServicePrivacy Policy
Follow us onlineInstagram

Summaries are AI-generated from primary sources. Verify anything important against the original record.

All bills
S. 3629·119th Congress·Introduced Jan 13, 2026

Transportation Project Accountability Act of 2026

IntroducedTransportation and Public WorksSubstantive
View bill text
Sponsor
Sen. Alsobrooks, Angela D. [D-MD]
Committees
Environment and Public Works Committee (primary)
Last action
Jan 13, 2026

Bottom line

The bill aims to enhance transparency and accountability in state transportation project selection by requiring public reporting on performance metrics and justifications, thereby promoting data-driven decision-making and public oversight.

What it actually does

This bill amends title 23, United States Code, to mandate that states annually publish online reports detailing the selection of certain transportation projects costing over $10 million. These reports must include project performance scores against state and national goals, anticipated benefits, and justifications for selection. Additionally, states are required to integrate a review of these projects' progress and contribution to goals into their long-range transportation plans.

Proponents argue

Supporters argue that this legislation will ensure greater transparency in how federal and state transportation funds are utilized, leading to more efficient allocation of resources towards projects that genuinely align with state and national performance objectives. They contend it empowers the public with information to hold state agencies accountable and fosters data-driven decision-making.

Opponents contend

Opponents might argue that this bill imposes an unfunded mandate on states, significantly increasing administrative burdens and costs associated with data collection, scoring, and online reporting. They may contend that these new requirements could divert resources from actual infrastructure development and that the prescriptive nature of the reporting might limit state flexibility in addressing unique local transportation needs.

The bill is very concise and can be read quickly, allowing ample time for detailed consideration of its implications.

Section 2(a), adding subsection (n)(1) to 23 U.S.C. 135

Definition of 'Covered Project'

prominently featuredstraightforward

This provision establishes the criteria for what constitutes a 'covered project' subject to the new reporting requirements. A project must be included in the statewide transportation improvement program, enhance or expand the transportation system, and have an estimated cost exceeding $10,000,000. This threshold ensures that only larger, more significant transportation investments are included in the accountability framework.

GroupImpactMechanismScale
GroupState Departments of Transportation (DOTs)ImpactMust identify and categorize projects based on these specific criteria for subsequent reporting.MechanismLegal mandate to adhere to the defined scope of projects.ScaleApplies to all states receiving federal highway funds.

Supporters argue

Supporters argue that a clear and consistent definition ensures uniform application of accountability standards across states, focusing oversight on substantial public investments in transportation infrastructure.

Critics contend

Critics might contend that the $10,000,000 threshold could be arbitrary or too low for some states, potentially encompassing a large volume of projects and leading to an excessive administrative burden.

Tradeoffs

This provision balances the desire for comprehensive oversight of significant projects with the need to avoid overwhelming states with reporting requirements for minor undertakings. The specific monetary threshold is a key point of this balance.

Section 2(a), adding subsection (n)(2) to 23 U.S.C. 135

Mandates Annual Public Report on Covered Projects

prominently featuredmoderately complex

This section requires each state to publish an annual report online, identifying all covered projects selected in the previous year. For each project, the report must include a score based on its contribution to state performance measures and national goals, anticipated benefits, the year it was first programmed, and a brief description explaining its selection, including projected benefits and geographic coordinates. The report must also summarize the metrics used for scoring.

Section 2(a), adding subsection (n)(3) to 23 U.S.C. 135

Integrates Performance Review into State Transportation Plans

mentioned in summarymoderately complex

Following the publication of the first annual report, states are required to incorporate a review of the progress, cost-effectiveness, and contribution of selected covered projects into their statewide transportation improvement program and long-range statewide transportation plan. This review must assess how projects contribute to state targets and national goals described in paragraphs (1) through (3) of section 150(b), ensuring ongoing evaluation and integration of performance data into future planning.

FOUND

This conforming amendment states that the new transportation accountability report required under subsection (n) 'may be considered to satisfy' the requirements of an existing provision, 23 U.S.C. 135(g)(5)(B), which pertains to the content and consistency of the statewide transportation improvement program (STIP).

Section 2(b), amending 23 U.S.C. 135(g)(5)(B)

Why it matters:This is standard legislative practice for ensuring that new statutory requirements integrate smoothly with existing law, avoiding redundancy. It is not intended to be evasive, but its implications for administrative efficiency might be missed.

Case for: Proponents would argue that this amendment is a sensible measure to prevent redundant reporting, allowing states to use a single comprehensive report to fulfill multiple federal compliance requirements, thereby streamlining administrative processes and reducing unnecessary burden.

Case against: Critics might argue that the phrase 'may be considered' introduces ambiguity, potentially leading to inconsistent application across states. They might also contend that it could allow states to fulfill existing requirements with less detail than originally intended if the new report's scope does not perfectly align with the nuances of the prior mandate.

Estimated impact: Potentially reduces administrative burden for states by allowing a single report to serve multiple compliance purposes, but the actual impact depends on how states interpret and implement the flexibility offered by 'may be considered.'

About this analysis. AI-Generated from the official bill text and available committee reports. Gaps in available data are noted explicitly. Verify important details with the official Congress.gov record.

On this page

  • Executive summary
  • Key provisions
  • Buried treasure
  • Follow the money
  • Critical analysis
  • Questions to ask
Ask Ledger AI about this