This bill restricts how litigation can affect environmental approvals for data centers and projects built to support them. It defines covered applications (siting, construction, expansion, operation) for data centers and related infrastructure, then prevents courts from invalidating permits tied to those applications; instead a court must remand alleged legal defects to the agency and allow processing to continue.
The measure also centralizes and accelerates judicial review: it gives exclusive original jurisdiction to the federal court of appeals for the circuit where the project is located, requires expedited docketing, allows transfer of pending petitions on an applicant's motion, and imposes a 90‑day filing bar for challenges after the agency publishes final notice in the Federal Register. Taken together, the bill aims to preserve permit continuity for data‑center projects while narrowing the timing and remedies available to challengers.
At a Glance
What It Does
The bill limits remedies courts can impose in environmental challenges to permits for data centers and associated infrastructure, requiring remand instead of vacatur and keeping agency actions in effect while problems are fixed. It also funnels review to the relevant federal court of appeals and mandates expedited handling and a 90‑day challenge deadline after Federal Register notice.
Who It Affects
Operators and developers of data centers and any infrastructure primarily built to support them; federal agencies that issue environmental permits (e.g., EPA, Corps, FERC, Fish & Wildlife); environmental plaintiffs and local parties who bring challenges; and the federal courts that will handle consolidated, expedited petitions.
Why It Matters
By changing remedies and procedure, the bill reduces the likelihood that permits for large data‑center projects will be vacated by courts, increasing project schedule certainty and lowering litigation leverage for challengers. It shifts dispute resolution toward agencies and front‑loads the timing of challenges, with consequences for environmental review, agency workloads, and local stakeholders.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill begins by defining its scope: a "covered application" is any federal authorization to site, build, expand or operate a data center or infrastructure whose primary purpose is to support a data center. That catch‑all definition is deliberately broad: it covers not only server halls but also supporting facilities if their primary role is to serve a data center.
On substance, the bill bars courts from using their usual remedy of setting aside or vacating a permit, license, or approval even if the court finds the agency violated a federal environmental statute (listed explicitly in the bill). Instead, a successful challenger gets a remand back to the issuing agency.
The agency must then address the identified defects while the underlying authorization remains in effect; the bill also expressly requires agencies to continue processing covered applications during and after remand.Procedurally, the bill channels judicial review to a single, predictable forum. It gives the court of appeals for the circuit where the project sits original and exclusive jurisdiction (except for Supreme Court review).
That court must treat petitions as expedited and place them on the docket as soon as practicable. For petitions already filed when the law takes effect, an applicant may move to transfer the case into the local circuit for adjudication under the new rules.Finally, the bill shortens the window to bring claims: any federal-law challenge to a permit for a covered application is barred unless filed within 90 days after the agency publishes final notice in the Federal Register (unless a shorter statutorily mandated period applies).
The text also preserves citizens’ ability to raise claims that someone violated permit terms, but it does not create a broader right to judicial review beyond the narrow procedural path the bill establishes.
The Five Things You Need to Know
The bill defines "covered application" to include any federal authorization to site, construct, expand, or operate a data center or infrastructure primarily built to support one.
If a court finds an environmental‑law violation tied to a covered application, the court must remand to the agency and may not set aside or vacate the underlying permit, license, or approval.
The court of appeals for the circuit where the facility is (or will be) located gets original and exclusive jurisdiction over federal challenges to covered applications, and the court must expedite those cases.
Existing petitions for review may be transferred on the applicant’s motion to the local circuit and then adjudicated under the bill’s rules; the bill requires courts to place such cases on an expedited docket.
A claim seeking federal judicial review of a permit for a covered application is barred unless filed within 90 days after publication in the Federal Register that the agency action is final (absent a shorter statutory deadline).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions that set a broad operational sweep
Section 2 establishes the statute’s scope with three definitions: "covered application," "data center," and "covered infrastructure." The practical effect is expansive because "data center" is defined functionally (facilities primarily for processing, storing, or transmitting digital information), and "covered infrastructure" covers any supporting project whose main purpose is to serve a data center. Compliance officers should treat a wide range of supporting facilities — electrical substations, fiber trunks, cooling plants, on‑site generation, and transmission interconnections — as potentially captured if their primary purpose is to support a data center.
Courts cannot vacate permits for covered projects
Section 3(a) bars courts from affecting the validity of permits, licenses, or approvals for data centers or covered infrastructure when the litigation concerns enumerated environmental statutes. Practically, that eliminates vacatur as a remedy in those challenges; a court may rule a violation occurred but cannot nullify the agency action. That changes litigants’ strategic calculus and reduces the immediate project‑stopping power of successful challenges.
Remand remedy and continuity of agency processing
Section 3(b) requires courts that find legal violations to remand matters to agencies rather than vacate permits, and it directs agencies to keep processing all covered applications. The provision effectively preserves permit continuity and signals congressional preference for administrative correction over judicial interruption. It also creates a workload issue: agencies must resolve substantive legal defects while the project authorization remains operative, potentially requiring supplemental analyses, corrected findings, or revised mitigation without the normal delay caused by vacatur.
Exclusive, centralized, expedited appellate review and transfer rule
Section 4(a) grants original and exclusive jurisdiction to the court of appeals for the circuit where the project is located (except Supreme Court review), so district courts are removed from the mix. Subsection (b) mandates expedited scheduling. Subsection (c) lets applicants move to transfer pending petitions to the local appeals court for adjudication under the statute. Together these rules create predictable, centralized review but also raise stakes for forum control and may lengthen travel and coordination needs for parties and witnesses.
90‑day filing bar and savings clause for enforcement claims
Section 4(d) imposes a firm 90‑day limit for filing federal statutory claims challenging permits after publication of final agency notice in the Federal Register, narrowing opportunities for late challenges. Section 4(e) clarifies that the statute does not itself create a new right to judicial review and does not limit actions alleging violation of permit terms — preserving enforcement avenues while constraining pre‑enforcement review.
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
- Data‑center developers and operators — They gain reduction in the risk that a successful environmental challenge will shut down or freeze a project, improving predictability and financing prospects because courts cannot vacate permits and review is centralized and expedited.
- Utilities and project contractors — Faster, more certain permitting reduces scheduling and interconnection risk for power, cooling, and fiber providers that service data centers, lowering mobilization and hold costs.
- Investors and lenders — The combination of non‑vacatur, shorter challenge windows, and exclusive appellate jurisdiction reduces legal tail risk, making debt and equity arrangements easier to underwrite and enforce.
Who Bears the Cost
- Environmental and community organizations — They lose a powerful remedy (vacatur), face shortened filing windows, and must litigate in a single appeals court under expedited timelines, reducing leverage and time to build administrative records.
- Federal agencies (EPA, Corps, FWS, FERC and others) — Agencies inherit a heavier operational burden: they must correct remanded deficiencies while permits remain in force and continue processing new covered applications, potentially without additional resources.
- Local communities and permitting authorities — Residents and local governments may see reduced practical ability to pause projects pending environmental fixes; local decision‑makers may face permits that remain active even after courts find procedural or substantive problems.
Key Issues
The Core Tension
The central tension is between project certainty and environmental accountability: the bill advances economic and scheduling certainty for data‑center projects by eliminating vacatur and compressing judicial review, but it does so by narrowing judicial remedies and shifting corrective responsibility to agencies — a trade‑off that speeds deployment while potentially weakening independent judicial oversight and the ability of affected communities to obtain timely relief.
The bill swaps judicial nullification for administrative correction; that trade‑off has implementation and accountability implications. When courts remand without vacatur, the agency retains a live authorization while it revisits its analyses.
That can expedite projects but also risks that agencies will feel pressure to produce post‑hoc fixes to preserve an authorization rather than conduct a full, transparent re‑evaluation. Remand without vacatur may also make it harder for plaintiffs to obtain injunctive relief that protects ecological or community interests pending agency correction.
Operationally, exclusive appellate jurisdiction and expedited dockets centralize litigation but create pressure points: certain circuits may see a surge in complex environmental appeals involving technical NEPA, ESA, CWA, or CAA questions on compressed timetables. The 90‑day filing bar tightens standing and monitoring demands for local stakeholders; failure to spot and challenge a final agency notice within that window could forfeit federal review entirely.
The definitions of "data center" and "covered infrastructure" are functional and broad, raising the possibility that the statute will sweep in facilities not traditionally thought of as core data‑center real estate and thus extend these procedural constraints beyond large hyperscalers to smaller, regional operations.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.