The SMART Infrastructure Act of 2025 directs the Secretary of Transportation to build a centralized, web-based e‑NEPA portal and to create guidelines and a pilot program for integrating digital twin technology into permitting for DOT‑led projects. The bill defines key terms, sets deadlines for guidance and portal delivery, and requires Federal agencies to use the portal for covered projects by January 1, 2028.
This is a process and technology-first bill: it moves NEPA paperwork and interagency coordination onto a single digital platform, pushes for interoperable 3‑D models and open application programming interfaces, and sets an explicit target—a minimum 25 percent reduction in environmental review timelines—for projects that use the portal and digital twins. The measure creates compliance obligations, data‑security requirements, and reporting duties that will matter to project sponsors, agencies, and infrastructure technology vendors.
At a Glance
What It Does
The bill requires DOT to develop an e‑NEPA portal within two years and to publish digital‑twin integration guidelines within 18 months. It establishes a pilot (at least 10 DOT‑led projects) to test digital twins, mandates agency use of the portal for covered projects by Jan 1, 2028, and directs the Secretary to pursue a 25% reduction in NEPA review timelines for eligible projects.
Who It Affects
Directly affected are DOT‑led (Title 49) infrastructure projects, Federal agencies participating in NEPA reviews, state and local agencies coordinating on covered projects, project sponsors who will need digital twins and portal submissions, and software vendors who supply modeling and interoperability tools. Communities and public commenters will interact with the process via the portal’s public interface.
Why It Matters
Centralizing NEPA documents and linking them to high‑fidelity, interoperable models represents a structural change in how environmental reviews are prepared and coordinated. The bill could shorten permitting schedules, shift costs toward digital modeling, and set practical standards for interoperability and cybersecurity that will shape vendor offerings and agency workflows.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Act first sets out definitions that carry operational weight: a covered infrastructure project is a DOT‑led Title 49 project, an eligible project requires both an e‑NEPA portal submission and the use of one or more digital twins, and an e‑NEPA portal is a centralized web platform for managing NEPA documents and stakeholder communications. That combination—portal plus digital twin—creates the qualification for the bill’s accelerated permitted treatment.
On the technical side, DOT must publish guidelines within 18 months that spell out standards for creating and maintaining digital twins, requirements for interoperability with federal permitting systems, and protocols for feeding real‑time sensor, GIS, and stakeholder data into models. Those guidelines expressly recommend open application programming interfaces to allow multiple vendors and tools to interoperate without access to proprietary source code.
The bill stops short of mandating a single technical standard, but it pushes agencies and sponsors toward open, machine‑readable integration.Operational testing comes next: within 120 days DOT must establish a pilot program that runs on at least 10 diverse covered projects. The pilot must measure reductions in permitting timelines, improvements in environmental impact assessments, cost savings, and stakeholder collaboration and must emphasize early public engagement.
DOT must report pilot findings to the appropriate congressional committees within two years.Concurrently, DOT—coordinating with CEQ, EPA, and Commerce—must deliver an e‑NEPA portal within two years that integrates digital twins, provides public access to nonsensitive records and comment periods, and stores data under Federal cybersecurity standards. Starting January 1, 2028, agencies participating in NEPA reviews for covered projects must use the portal; the Secretary will oversee portal‑based coordination and ensure compliance with statutory deadlines.
For eligible projects, the Secretary must use all existing authorities to reduce NEPA review timelines by at least 25 percent and issue guidance or regulations within a year to implement that target. Finally, the bill requires an annual report tracking integration progress, timeline and cost reductions, and stakeholder outcomes.
The Five Things You Need to Know
The bill defines an "eligible project" as a DOT‑led project that uses both one or more digital twins and the e‑NEPA portal, making the 25% timeline target conditional on technology adoption.
DOT must publish digital‑twin guidelines within 18 months and recommends (but does not strictly require) open APIs to enable vendor interoperability across engineering tools.
Within 120 days DOT must stand up a pilot program using at least 10 covered projects and submit a findings report to the relevant congressional committees within two years of enactment.
DOT must deliver the e‑NEPA portal within two years, and all Federal agencies involved in NEPA reviews for covered projects must use the portal starting January 1, 2028; the portal must provide public access to nonsensitive documents and comment periods.
The Secretary must seek to cut environmental review timelines for eligible projects by at least 25%, and has one year to issue guidance or regulations to implement that reduction; the statute also mandates a single environmental document be used across agencies for each covered project.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Findings framing policy goals
This section lists the Congress’s rationale: current paper/PDF workflows cause delays, 3‑D digital twins and an electronic portal can improve coordination, and interoperability will accelerate infrastructure delivery while preserving environmental protections. While nonbinding, these findings frame DOT’s mandate and justify the emphasis on high‑fidelity, real‑time modeling and public access in later operative sections.
Key statutory definitions that shape scope
Section 3 establishes operational definitions—particularly for "covered infrastructure project," "digital twin," "e‑NEPA document," and "eligible project." Practically, the eligible‑project definition is consequential: projects only qualify for the statute’s timeline and procedural benefits if they both employ digital twins and use the e‑NEPA portal, creating a compliance nexus between modeling and submission platforms.
Digital twin guidelines and pilot testing
This provision requires the Secretary, working with CEQ and other agencies, to issue guidelines for integrating digital twins into permitting within 18 months and to run a pilot on at least 10 projects. The guidelines must cover modeling standards, interoperability with permitting systems, and real‑time sensor and GIS integration; they recommend open APIs but do not mandate a single technical specification. The pilot is explicitly evaluative—measuring timeline reductions, assessment quality, cost savings, collaboration outcomes, and the role of early public engagement—so its design will shape what practices qualify as successful integration.
Creation and mandatory use of an e‑NEPA portal
DOT must develop a centralized portal within two years, coordinating with CEQ, EPA, and Commerce. The portal is a platform for submitting, reviewing, and tracking e‑NEPA documents, visualizing integrated digital‑twin models in real time, and maintaining secure data storage to federal cybersecurity standards. Agencies are required to use the portal for covered projects beginning January 1, 2028, which forces legacy systems to interoperate or be retired; the Secretary is explicitly assigned oversight responsibility for portal coordination and deadline compliance.
Mandated timeline reductions and cross‑agency document use
The statute directs the Secretary to use all existing authorities to compress NEPA review timelines for eligible projects by at least 25% and requires guidance or regulations within one year to implement that target. The bill also requires that agencies rely on a single environmental document for each covered project, eliminating duplicative interagency drafts but raising questions about legal sufficiency and agency sign‑offs.
Reporting and congressional oversight
The annual report requirement compels DOT to track progress on digital‑twin integration, portal deployment, timeline and cost impacts, and stakeholder outcomes. The pilot program carries a separate two‑year report to the appropriate committees. Together, these reporting duties create regular transparency that Congress and stakeholders can use to evaluate whether the portal and modeling practices actually produce the intended efficiencies.
This bill is one of many.
Codify tracks hundreds of bills on Infrastructure across all five countries.
Explore Infrastructure 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
- DOT‑led project sponsors and prime contractors — They stand to shorten permitting schedules and lower schedule risk if they invest early in digital twins and portal workflows; integrated models can reduce rework and coordination costs across agencies.
- Agencies involved in NEPA reviews (CEQ, EPA, DOI partners) — Centralized document management and a single environmental document reduce duplicated paperwork and help standardize interagency exchange, saving staff time on coordination.
- Engineering firms and software vendors that provide digital twins and integration tools — Demand for high‑fidelity modeling, open APIs, and interoperable toolchains will grow; firms that adopt recommended standards can capture new contracts for model creation and portal integration.
- Local communities and public stakeholders — The portal’s public interface and visualization tools can improve access to project timelines, non‑sensitive documents, and online comment periods, making technical impacts easier to understand for nontechnical audiences.
Who Bears the Cost
- Department of Transportation — DOT must design, build, secure, and maintain the e‑NEPA portal and fund the pilot; DOT will also shoulder oversight duties and the administrative burden of enforcing portal use across agencies.
- Project sponsors without in‑house modeling capacity (often smaller sponsors) — Creating or procuring digital twins adds upfront costs; these sponsors may face a new technical compliance hurdle to qualify as an eligible project.
- Software vendors with proprietary, closed systems — The bill’s recommendation for open APIs pressures vendors to open integration points or risk being sidelined, which can require reengineering and reduce control over downstream revenue.
- State and local agencies that participate in NEPA reviews — They must adapt to portal workflows, integrate legacy systems, and meet cybersecurity and data‑sharing requirements, which could require staff training and IT upgrades.
Key Issues
The Core Tension
The central dilemma is whether embracing interoperable, model‑driven permitting will reliably speed project delivery without undermining environmental review quality and data security: the bill favors efficiency and standardization, but achieving both interoperability and robust environmental oversight requires technical standards, funding, and safeguards the statute directs but does not fully prescribe.
The bill pushes a technology‑driven pathway to faster permitting, but it leaves important technical and operational choices unresolved. It recommends open APIs but stops short of imposing binding technical standards, which means actual interoperability will depend on implementation details in DOT guidance and the pilot’s outcomes.
That ambiguity could produce uneven systems where some vendors and large sponsors achieve seamless integration while smaller players struggle with proprietary formats and higher integration costs.
The statute requires public access to "nonsensitive" documents and real‑time visualization, yet it relies on agencies to reconcile data‑sensitivity, FOIA, and security obligations when exposing model outputs. The tension between transparency and protecting sensitive infrastructure details (or persons’ private data collected through sensors) will force agencies to build granular redaction rules and robust cybersecurity controls—tasks that are costly and complex.
Finally, the 25% timeline reduction target frames success quantitatively but raises questions about review quality: compressing review periods through better tools may be achievable, but deadlines risk pressuring agency legal and scientific reviews unless the guidance carefully aligns procedural steps with substantive review requirements.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.