Emerging trend of delays in infrastructure project completion

# Investigate Why U.S. Infrastructure Projects Take So Long to Deliver

## Overview

The United States regularly authorizes large investments in transportation, broadband, water, energy, and public facilities, yet years may pass before communities receive completed infrastructure. The delay can occur at many stages:

These stages are often collapsed into a single claim that money has been “invested.” In reality:

* **Appropriated** money has been legally made available;
* **Obligated** money has been formally committed;
* **Outlayed** money has actually been paid;
* **Started** projects have entered physical delivery;
* **Completed** projects are providing usable infrastructure.

The distinction is consequential. As of December 31, 2024, federal agencies had obligated approximately $275.1 billion of the Infrastructure Investment and Jobs Act funding available for fiscal years 2022–2025, but had outlayed approximately $119.4 billion. This represented about 47% obligated and 21% outlayed of the funding then available to states, localities, Tribes, and territories.

At the Department of Transportation, approximately 59% of available IIJA grant funding had been obligated by April 2025. GAO found that award recipients faced inflation, project-scope changes, administrative requirements, and grant-agreement delays that could increase costs or cause projects to miss statutory deadlines.

The central research question is:

> **Which stages, institutional conditions, and project characteristics most strongly predict whether publicly funded U.S. infrastructure is delivered late, over budget, or not completed?**

The investigation should focus on delivery performance rather than debating whether the United States spends too much or too little. The objective is to identify bottlenecks that add substantial time or cost without producing corresponding improvements in safety, quality, public participation, or environmental outcomes.

The recommended primary unit of analysis is the **project**, supplemented by agency-program-year and recipient-year analyses.

---

## Action Items

### Initial Evidence

Several established findings justify the investigation:

* U.S. transportation infrastructure is often more expensive and time-consuming to build than comparable infrastructure in other developed countries. Potential explanations include limited public-sector capacity, complex approval requirements, poor project planning, fragmented accountability, and weak institutional expertise.
* DOT administers more than 100 IIJA grant programs. Before construction can proceed, agencies and recipients may need to negotiate grant agreements, revise budgets, document local matches, complete environmental review, and satisfy procurement requirements.
* GAO found that DOT had not comprehensively assessed risks across its grant portfolio, even though recipient challenges could produce schedule delays, increased costs, or missed obligation deadlines.
* Federal reviews beginning in January 2025 added another source of delay and uncertainty. By July 2026, selected agencies had approved approximately 9,500 IIJA and Inflation Reduction Act awards, canceled about 800 awards worth nearly $18 billion, and had not resolved approximately 2,500 awards worth about $34 billion.
* Permitting is frequently identified as a major source of delay, but individual environmental reviews are only one component of total delivery time. Procurement, design, property acquisition, utility relocation, litigation, financing, staffing, and contractor availability may be equally important.
* Skilled-worker and engineering shortages can slow project design, review, procurement, and construction.
* Inflation can cause a previously feasible project to require redesign, additional funding, or reduced scope before a grant agreement is signed.
* Delays themselves increase costs through inflation, extended management, financing expense, remobilization, contract amendments, and deterioration of existing infrastructure.

These findings establish a delivery problem but do not prove that any single regulation, agency, or level of government is primarily responsible.

---

### Hypotheses

#### H1 — Pre-construction planning quality is the strongest predictor of delivery

Projects may be announced before design, scope, cost, property, permitting, and financing are sufficiently mature.

**Evidence to seek:**

* Projects awarded at an earlier design stage experience more delays;
* Incomplete scope definition predicts change orders;
* Projects with realistic contingency reserves perform better;
* Independent cost estimates reduce later overruns;
* “Shovel-worthy” planning maturity predicts completion better than political priority.

#### H2 — Competitive grants take longer to deliver than formula funding

Competitive programs may require lengthy applications, evaluation, award negotiation, and recipient-specific agreements.

**Evidence to seek:**

* Competitive awards take longer from appropriation to obligation;
* Formula programs reach construction faster after controlling for project type;
* Application cost is disproportionately high for small jurisdictions;
* Competitive selection produces better projects, but only after substantial delay;
* Differences vary by federal agency and grant size.

#### H3 — Local administrative capacity determines whether funding becomes infrastructure

Smaller and lower-income jurisdictions may lack grant writers, engineers, procurement specialists, legal staff, and project managers.

**Evidence to seek:**

* Staffing levels predict time to grant agreement and construction;
* Small recipients return or fail to obligate funds more often;
* Technical-assistance programs improve delivery;
* Repeat federal-grant recipients perform better than first-time recipients;
* Consultant dependence increases either capacity or coordination problems.

#### H4 — Permitting delay is concentrated in a minority of complex projects

Average permitting duration may conceal a heavy-tailed distribution in which a relatively small number of projects account for much of the delay.

**Evidence to seek:**

* Median review times are moderate but upper-tail times are extreme;
* Delay is concentrated by project type, geography, or agency;
* Projects requiring multiple federal and state reviews experience nonlinear delays;
* Concurrent review outperforms sequential review;
* Review duration is not consistently associated with better environmental outcomes.

#### H5 — Procurement design rewards low initial bids rather than reliable final delivery

A low bid can become expensive through change orders, claims, delays, and incomplete performance.

**Evidence to seek:**

* Lowest-bid contracts have larger final-cost deviations;
* Bid spread predicts later contractor claims or failure;
* Best-value, design-build, or progressive design-build methods reduce total duration;
* Effects differ by project complexity;
* Fewer bidders predict higher costs and weaker performance.

#### H6 — Fragmented authority produces coordination delay

Infrastructure projects commonly involve federal agencies, state departments, local governments, utilities, railroads, property owners, contractors, and community stakeholders.

**Evidence to seek:**

* More participating entities predict longer delivery;
* Sequential approvals add more time than concurrent approvals;
* Unclear ownership of decisions predicts repeated review;
* Integrated project teams reduce rework;
* A designated lead agency improves schedule performance.

#### H7 — Utility relocation and property acquisition are hidden major bottlenecks

Road, transit, broadband, and water projects often cannot proceed until utilities are moved and rights-of-way are acquired.

**Evidence to seek:**

* Utility conflicts explain a large share of construction-start delays;
* Early subsurface mapping reduces change orders;
* Property acquisition duration predicts total project duration;
* Standardized utility agreements improve performance;
* These delays are underrepresented in public project dashboards.

#### H8 — Workforce and contractor shortages constrain delivery

A large increase in simultaneous public investment may exceed available engineering, project-management, and skilled-trade capacity.

**Evidence to seek:**

* Regions with high infrastructure spending experience wage and bid inflation;
* Projects receive fewer bids when local construction demand is high;
* Engineering vacancies predict longer design and review;
* Contractor backlog predicts schedule slippage;
* Workforce-development investments improve delivery only after a lag.

#### H9 — Funding uncertainty causes costly stop-start delivery

Policy reviews, delayed appropriations, short obligation windows, and uncertain grant continuation may cause agencies and contractors to postpone hiring, purchasing, and construction.

**Evidence to seek:**

* Funding pauses predict project delays;
* Projects with multi-year certainty perform better;
* Cancellation risk increases bid prices;
* Short obligation periods produce rushed or lower-quality procurement;
* Repeated program redesign causes recipients to redo applications and plans.

As of mid-2026, federal reviews had left billions of dollars of previously selected infrastructure awards unresolved, providing a potential natural experiment for studying the effects of funding uncertainty.

#### H10 — Public reporting rewards announcements rather than usable outcomes

Agencies may prominently report authorized dollars, awards, or obligations while lacking consistent completion and benefit data.

**Evidence to seek:**

* Award dates are readily available but start and completion dates are missing;
* Project dashboards do not distinguish obligation from construction;
* Agencies use incompatible status definitions;
* Projects remain labeled “active” despite prolonged inactivity;
* Reported program success is weakly connected to completed outputs.

---

### Research Plan

#### 1. Create a common project-delivery lifecycle

For every project, record dates for:

* Legislative authorization;
* Funding availability;
* Funding notice;
* Application submission;
* Award announcement;
* Grant agreement;
* Obligation;
* First outlay;
* Environmental-review start and completion;
* Design completion;
* Procurement advertisement;
* Contract award;
* Construction start;
* Substantial completion;
* Final completion;
* Entry into service.

Calculate stage durations:

Total delivery time:

Where no completion occurs, treat the observation as censored rather than assigning an artificial duration.

#### 2. Select an initial project sample

Begin with three sectors:

1. Federal transportation grants;
2. Drinking-water and wastewater infrastructure;
3. Broadband deployment.

These sectors provide variation in:

* Project size;
* Agency;
* recipient capacity;
* approval process;
* construction type;
* urban and rural geography.

A later extension may cover electric-grid, school, housing, and federal-building projects.

#### 3. Build a project-level dataset

Core variables:

* Project identifier;
* program;
* agency;
* recipient;
* geography;
* initial award;
* obligations and outlays;
* original and current cost;
* original and current schedule;
* project type;
* project size;
* planning maturity;
* delivery method;
* contractor;
* number of bids;
* change orders;
* environmental-review type;
* property acquisition;
* utility relocation;
* litigation;
* funding match;
* recipient staffing;
* status.

Preserve the difference between:

* Award amount;
* federal obligation;
* federal outlay;
* total project cost;
* final cost.

#### 4. Measure delay and cost escalation

Primary outcomes:

Also measure:

* Time to obligation;
* time to first outlay;
* time to construction;
* probability of cancellation;
* probability of scope reduction;
* annual expenditure rate;
* completed output per dollar.

Initial cost estimates must be adjusted for whether they refer to the same project scope.

#### 5. Use survival analysis

Model time to:

* Grant agreement;
* obligation;
* construction start;
* completion;
* cancellation.

A Cox model or accelerated failure-time model could estimate:

This handles active projects that have not yet completed.

#### 6. Decompose where delay occurs

For each program and project type, calculate the percentage of total time spent in:

* Application;
* federal review;
* grant negotiation;
* environmental review;
* design;
* procurement;
* construction;
* closeout.

Use process mining to identify common paths and loops, such as:

The result should show which stages dominate delay rather than discussing “bureaucracy” as one undifferentiated cause.

#### 7. Measure recipient capacity

Construct a capacity index using:

* Government employment;
* Engineering staff;
* procurement staff;
* finance staff;
* prior grant experience;
* audit findings;
* consultant use;
* population;
* tax base;
* administrative expenditure.

Test whether capacity predicts delivery after controlling for project complexity and funding.

#### 8. Compare competitive and formula programs

Use matched projects or hierarchical models to compare:

* Time to award;
* time to obligation;
* administrative cost;
* construction start;
* completion;
* cost overrun;
* project outcomes.

Do not assume faster formula funding is necessarily better; competitive programs may select higher-value or more complex projects.

#### 9. Evaluate procurement methods

Compare:

* Design-bid-build;
* design-build;
* construction manager at risk;
* progressive design-build;
* public-private partnership;
* low-bid versus best-value selection.

Control for project type, scale, recipient, and complexity.

#### 10. Study policy changes as natural experiments

Possible interventions include:

* Permitting deadlines;
* One-stop permitting offices;
* Electronic permitting;
* concurrent agency review;
* standardized grant agreements;
* simplified procurement;
* project-development grants;
* technical-assistance teams;
* expanded design-build authority.

Apply:

* Difference-in-differences;
* event studies;
* regression discontinuity where funding thresholds exist;
* synthetic controls.

#### 11. Estimate the economic cost of delay

Delay cost should include:

Examples:

* Additional vehicle delay while a bridge remains unimproved;
* Continued water loss before pipe replacement;
* Lost broadband access;
* Higher flood losses before resilience work;
* Increased project cost from construction inflation.

#### 12. Identify positive-deviant agencies and jurisdictions

Find recipients that consistently:

* Reach grant agreement quickly;
* Start construction promptly;
* Limit change orders;
* Complete near budget;
* Maintain safety and environmental compliance;
* Deliver measurable benefits.

Match them with similar recipients to identify practices rather than merely rewarding simple projects.

#### 13. Build an Infrastructure Delivery Dashboard

Display:

* Projects by lifecycle stage;
* Median stage duration;
* obligations versus outlays;
* planned versus actual cost;
* planned versus actual completion;
* stalled projects;
* recipient capacity;
* sector and geographic comparisons.

Each status must have a formal definition.

#### 14. Produce the Final PowerPoint

Recommended structure:

1. Funding is not the same as infrastructure;
2. The project-delivery lifecycle;
3. Where federal infrastructure money currently sits;
4. Time from authorization to usable asset;
5. Which stages create the greatest delay;
6. Recipient capacity;
7. Permitting and environmental review;
8. Procurement and contractor competition;
9. Inflation, change orders, and scope changes;
10. Positive-deviant projects;
11. Hypotheses supported and rejected;
12. Highest-value process reforms.

The presentation must distinguish:

* Appropriation from obligation;
* Obligation from outlay;
* Outlay from construction;
* Construction from completion;
* Delay from necessary planning;
* Original estimate from comparable final scope;
* Administrative speed from project quality.

---

## Resources

### Data, APIs, and Where to Get Data

#### USAspending API

USAspending provides federal award, transaction, obligation, outlay, recipient, agency, place-of-performance, and program data.

Use for:

* Grant and contract awards;
* obligations;
* outlays;
* award modifications;
* recipients;
* agency and program comparisons;
* geographic distribution.

The API can establish financial milestones, but it generally does not provide a complete construction lifecycle or reliable physical completion date.

#### Federal Audit Clearinghouse API and Data

Use for:

* Recipient audit findings;
* internal-control weaknesses;
* questioned costs;
* federal expenditure;
* recipient grant-management capacity.

These measures may help test whether administrative capacity predicts delivery.

#### Grants.gov API

Use for:

* Notice of funding opportunity dates;
* application deadlines;
* program descriptions;
* amendments;
* eligibility;
* expected award timing.

Compare the date a program is authorized with the date recipients can first apply.

#### Department of Transportation Grant Dashboards

Potential sources include:

* Federal Highway Administration;
* Federal Transit Administration;
* Federal Railroad Administration;
* Build America Bureau;
* Maritime Administration;
* Office of the Secretary grant programs.

Use for:

* Project descriptions;
* award dates;
* amount;
* recipient;
* project type;
* status where available.

GAO’s 2025 review found that DOT’s public reporting did not provide a complete portfolio-level account of obligations and outlays across formula and discretionary programs.

#### Federal Highway Administration FMIS and Project Data

Use for:

* Highway obligations;
* project categories;
* state programs;
* construction and funding status.

State departments of transportation may provide richer project-level schedule and contract data.

#### Federal Transit Administration National Transit Database

Use for:

* Transit capital expenditures;
* agency capacity;
* asset condition;
* service outcomes.

FTA’s Capital Investment Grants program and project profiles may provide milestone and cost histories for major transit projects.

#### Federal Railroad Administration Data

Use for:

* Rail grants;
* project selections;
* corridor programs;
* safety and infrastructure projects;
* environmental review.

#### EPA ECHO and Infrastructure Programs

Potential sources:

* Drinking Water State Revolving Fund;
* Clean Water State Revolving Fund;
* Water Infrastructure Finance and Innovation Act;
* EPA grant and project dashboards.

Use for:

* Water-project funding;
* recipient;
* compliance need;
* project type;
* completion where reported.

#### NTIA Broadband Data

Use:

* Broadband Equity, Access, and Deployment records;
* Tribal Broadband Connectivity Program;
* Middle Mile Grant Program;
* BroadbandUSA datasets;
* state broadband-office records.

Track:

* Planning allocation;
* state plan;
* award;
* subgrant;
* construction;
* locations served.

#### OpenFEMA API

Use for:

* Hazard-mitigation projects;
* public-assistance projects;
* obligations;
* project status;
* disaster;
* recipient;
* project type.

OpenFEMA is particularly useful for studying whether post-disaster projects are delayed by damage assessment, matching funds, environmental review, or recipient capacity.

#### USACE Civil Works Data

Use for:

* Flood-control;
* navigation;
* water-resource projects;
* schedules;
* budgets;
* expenditures;
* benefit-cost estimates.

#### Federal Permitting Dashboard

The Permitting Dashboard tracks selected major infrastructure projects and milestones across federal reviews.

Use for:

* Environmental-review milestones;
* agency schedules;
* project status;
* permitting duration;
* participating agencies.

Caution: covered projects are not representative of all infrastructure.

#### Council on Environmental Quality NEPA Data

Use for:

* Environmental impact statements;
* records of decision;
* review duration;
* lead and cooperating agencies.

Historical completeness and consistent project identifiers may be challenging.

#### State Procurement Portals

Use for:

* Solicitations;
* bids;
* contract awards;
* contractors;
* contract value;
* amendments;
* completion.

A pilot should include states with relatively accessible procurement and project data.

#### Local Capital-Improvement Dashboards

Cities and counties may publish:

* Planned budget;
* current budget;
* schedule;
* completion percentage;
* contractor;
* project manager;
* change orders.

These provide detailed delivery evidence but require harmonization.

#### Bureau of Labor Statistics APIs

Use for:

* Construction employment;
* engineering employment;
* wages;
* producer prices;
* occupational shortages;
* local labor-market conditions.

#### Census Annual Survey of Public Employment and Payroll

Use for:

* State and local government staffing;
* engineering and public-works capacity;
* payroll;
* government-function employment.

#### Census Annual Survey of State and Local Government Finances

Use for:

* Capital spending;
* debt;
* revenue;
* administrative expenditure;
* recipient fiscal capacity.

#### Census Building Permits and Construction Data

Useful for comparing public delivery performance with wider local construction-market conditions.

#### FHWA National Highway Construction Cost Index

Use to distinguish inflation from changes in project scope or delivery efficiency.

#### Government Accountability Office Reports

Key current sources include:

* *Infrastructure Grants: Status of Funding to Tribes, States, Localities, and Territories as of December 31, 2024*.
* *Infrastructure Investment and Jobs Act: DOT Should Better Communicate Funding Status and Assess Risks*.
* *Funding Status: Infrastructure Investment and Jobs Act and Inflation Reduction Act*, published July 22, 2026.

### Foundational Resources

* Brookings and AEI, *The Priority List*, on U.S. transportation construction cost, delay, planning, expertise, and accountability.
* GAO’s IIJA funding and delivery reports.
* Federal permitting and agency project dashboards;
* State auditor and inspector-general reports;
* National Academies research on infrastructure procurement and project delivery;
* Transit Costs Project for detailed comparative transit-construction research.

### Central Scientific Caution

A long project is not necessarily an inefficient project. Major infrastructure may require extensive engineering, public participation, environmental mitigation, property acquisition, and safety review. Removing a step may accelerate delivery while imposing costs that are not visible in the construction budget.

The correct question is therefore not:

> “Which requirements take time?”

It is:

> **Which requirements add time, what measurable benefit do they produce, and could the same benefit be achieved more quickly or predictably?**

The strongest investigation will measure both sides:

1. Delivery time;
2. Final cost;
3. Infrastructure quality;
4. Safety;
5. Environmental outcomes;
6. Public participation;
7. Equity of benefits and burdens;
8. Long-term maintenance;
9. Actual public use.

The most valuable result may be identifying a small number of repeatable bottlenecks—such as incomplete design, utility relocation, grant negotiation, or recipient staffing—that explain more delay than the politically prominent stages.

- If this issue requires access to 311 data, please answer the following questions:
- Do you need a one-time or ongoing dump of the data?
- Do you need subset of data (i.e. certain years) or the entire data set (approx. 4 million rows or 11 GB)?
- If a subset is needed, please define subset characteristics (i.e. date range, etc.)
- Do you need online access via an API or a download of data?

Start with the Research Plan in this issue, defining the common project-delivery lifecycle and the initial sample across transportation, drinking-water and wastewater, and broadband projects. Identify the required project-level variables and data sources, then document a reproducible dataset and analysis plan; done means the sample, lifecycle dates, and outcome measures are consistently defined.

Written by the indexing model from the issue text.