Permitting, Regulatory, Environmental & the Critical Path

Developers instinctively picture permitting as a sequence: file the applications, answer the comments, collect the stamps, build. On an AI campus that picture can wreck the schedule even when equipment arrives and construction runs on time. The approvals run mostly in parallel, granted by four layers of authority that do not coordinate with each other, and several take longer than the building. The usual culprits are the utility's service path and any major-source permit for a bridge plant. Screen for both early, and file each application the day its prerequisites are met. Miss that, and a project can hit every construction milestone and still sit as a dark, fully built shell, waiting on one approval it started too late.

This chapter builds the four-layer jurisdictional matrix and the permit register, then works through three pinch points, air, water and backup power, as engineering-and-schedule problems. It reads the 2025-2026 NEPA upheaval (EO 14318, the Seven County decision, the repeal of the CEQ regulations) for where it helps and where it does not, and compares the EU, UK, Nordic, Middle East and APAC regimes, since the permit clock is a global variable. It ends on identifying the long poles and starting them first. Siting strategy is in Chapter 3.1; interconnection mechanics in Chapter 3.2; water sourcing in Chapter 3.7; opposition and social license in Chapter 3.11. Here those threads land as a permit register with dates on it.

No single approval here is exotic. What makes permitting hard is that a large AI campus answers to four layers of authority with different clocks, different statutes and different ideas of who is in charge, and they do not usually sequence themselves around one another. Get the layering wrong and you discover, eighteen months in, that the approval you assumed was a formality is the one holding the project.

• Federal. Triggered by a nexus, not by size alone: an agency action with substantial federal control and responsibility, such as federal-land approval, agency financing with project-specific control, a Clean Water Act §404 permit or a FERC-jurisdictional approval. A state permit issued under delegated authority is not itself a federal action. The nexus is what pulls NEPA into the timeline. The Congressional Research Service's R48762 is the best single map of which federal statutes attach and when.
• State. Environmental agencies that run delegated federal programs (the state EPA administering the Clean Air Act and NPDES on EPA's behalf), plus state-specific regimes: a state "little NEPA" (California's CEQA, New York's SEQRA, Washington's SEPA), state water-rights adjudication and, increasingly in 2026, data-center statutes on energy, water disclosure and ratepayer protection. California's package, signed September 21, 2026, goes furthest. SB 887 ends categorical CEQA exemptions for data centers, so every project needs at least an initial study and then a negative declaration, mitigated negative declaration or EIR. AB 1577 requires estimates of energy use, on-site generation and sound levels at the permit stage, then annual reports to the California Energy Commission. A project the Governor certifies as an Environmental Leadership Development Project gets streamlined judicial review. The conditions include paying the full interconnection cost, showing no net increase in fossil-fuel use and using behind-the-meter zero-carbon generation as far as possible. The project must also store four hours of zero-carbon energy at full peak demand, run on recycled water with waterless or water-efficient cooling, and enter a community benefits agreement. Some states now link the layers. Pennsylvania's Executive Order 2026-05 (August 18, 2026) covers DEP applications filed after that date for data centers over 25 MW peak demand. A project holding its own GRID Consent Order and Agreement gets rolling DEP review, yet no permit issues before it shows comprehensive-plan consistency and every required local approval. A project without one cannot start DEP review until it has documented both, plus any water-withdrawal or wastewater-discharge authorization it needs, and DEP will not issue its permits on a rolling basis. Data centers are excluded from PA Permit Fast Track. Texas added its own hold on September 21, 2026, when the governor directed TCEQ to halt permits sought by data centers until ERCOT completes its audit. Until that information arrives, no state agency is to advance approvals for data-center development, so a Texas project's state permits now wait on the audit, separately from the ERCOT RFI below. TCEQ says it has paused all air and water permits and authorizations tied to data-center infrastructure. The directive does not exempt projects that bring their own generation, so a Texas bridge plant's air permit waits too.
• Grid operator / utility. The ISO/RTO interconnection queue and the utility's load study and service agreement. Not a "permit" in the legal sense, but the hardest gate of all and the one most likely to set the in-service date. ERCOT added a step on September 14, 2026, the State and Community Impact RFI. Two groups must answer it: data centers not yet energized that hold a conditional Batch Zero classification at 60 kV or above, and unenergized substantiated projects from 25 MW up to, but not including, 75 MW that were reported in the August 19 Medium Load RFI. Developers filed water, cooling, grid-dependence, public-assistance and local-impact information, with a notarized attestation, through their utility; responses were due October 12, 2026. ERCOT expects its impact report by December 10, but that is not permission to connect: verification, eligibility, studies and approval to energize still gate service. → Chapter 3.2.
• Local. Zoning and land use, building permits, the conditional-use or special-exception process, noise ordinances, setbacks, traffic studies and stormwater. This is the layer with a public hearing, and so the layer where a technically approvable project gets stopped by politics. → Chapter 3.11.

Before a large campus can energize and operate, it needs its own register of every approval, permit and sign-off it requires across these layers. Most are routine and can run alongside construction. The danger is not the routine ones. It is failing to identify, on day one, the two or three that are both slow and serial, and then starting them last.

Air permitting surprises engineers because the trigger is not the IT load. It is the combustion equipment you add for resilience and to bridge the interconnection gap. Backup diesel gensets, and increasingly on-site gas turbines that supply bridge power before grid energization, are stationary sources of NOx, PM and CO, and for turbines, significant CO2. Once aggregate potential to emit crosses a threshold, the project leaves the fast lane of a minor-source permit and enters federal New Source Review.

Which NSR path applies depends first on attainment status. In an area that meets the national ambient air quality standards, a major new source triggers Prevention of Significant Deterioration (PSD): Best Available Control Technology (BACT) plus an air-quality modeling demonstration. In a nonattainment area (much of California, the Northeast corridor, parts of Texas), nonattainment NSR applies instead. It demands the far stricter Lowest Achievable Emission Rate (LAER) and emission offsets, meaning you buy reductions elsewhere to net out your new emissions. That can add substantial, case-specific time and turn a turbine bridge plant from feasible to impossible. A major source that operates also needs a Title V operating permit, a separate, ongoing compliance instrument layered on top of the construction permit.

So "how do we bridge the interconnection gap" is, in disguise, an air-permit question. A fleet of Tier-4 diesel gensets sized purely for emergency standby (a few hundred hours a year, non-emergency operation tightly capped) can often be engineered to stay minor-source, though Tier 4 alone does not settle it because emergency hours still count toward potential to emit. Timing depends on the agency's completeness, modeling and comment process. EPA Region 8's indicative review estimates run from about 60-90 days for a simple minor-source permit to 6-12 months for a synthetic-minor or PSD permit with comments or refined modeling, and PSD pre-application modeling and any required ambient monitoring come before that clock.

The genset arithmetic is short. Many agencies assess an emergency generator at 500 hours a year, the default in EPA's 1995 guidance, unless an enforceable limit sets fewer. At that rate a 3 MW Tier 2 engine (6.4 g/kWh of NOx plus NMHC) carries up to about 10.6 tons a year of NOx, so ten of them reach Title V's 100 tpy line. A Tier 4 Final engine (0.67 g/kWh) carries about 1.1 tons. Emergency status is also a limit on use. Under NSPS IIII an emergency engine gets 100 hours a year for maintenance checks and readiness testing. Up to 50 of those hours may go to non-emergency use, but never to peak shaving or demand response, apart from narrow dispatch by the local grid operator to protect local reliability. An engine run as bridge power is therefore a non-emergency engine and must meet the non-emergency standards, which for large new diesels means Tier 4 Final.

A gas-turbine bridge plant that runs thousands of hours to power the campus will normally clear major-source thresholds once its aggregated potential to emit is totaled. That is a calculation, not a label. The pollutant inventory, aggregation boundary, controls and federally enforceable operating limits decide it, and they decide it before you pick a schedule lane. Where it does clear, it puts PSD or, in the wrong county, nonattainment NSR on the critical path. EPA's December 2025 Clean Air Act resource page for data centers and the finalized "temporary turbine" subcategory exist because the gap between "built" and "energized" has made bridge generation a national permitting bottleneck. That subcategory sets a 25 ppm NOx limit on natural gas for turbines up to 850 MMBtu/h (aeroderivative-class units, not large frames) that stay at one location for no more than 24 consecutive months. Replacing a unit or moving it within the site does not restart the clock (Chapter 3.5). It is an emission standard, not an exemption from PSD or nonattainment NSR. Mounting a turbine on a truck does not take it out of the rule either. KKKKa excludes portable turbines certified to Title II nonroad standards, but that exclusion becomes operative only if EPA adopts such standards. The question is now in court. In NAACP v. X.AI (No. 3:26-cv-00074, N.D. Miss., filed April 14, 2026) the plaintiffs challenge the gas turbines xAI runs in Southaven to power its data centers, which Mississippi's regulator had decided needed no Clean Air Act permit under the state plan. On June 15, 2026 the United States moved to intervene and dismiss the suit, and no ruling on that motion or on the plaintiffs' preliminary-injunction motion had been reported by October 19, 2026 (Chapter 6.8).

The federal lines are 100 tons a year of any regulated pollutant for Title V and 250 tpy for PSD (100 tpy for 28 listed source categories). In ozone nonattainment areas the major-source line for NOx and VOC starts at 100 tpy and falls to 50, 25 and 10 tpy in serious, severe and extreme areas. Take a 500 MW bridge plant of about ten 50 MW simple-cycle aeroderivatives at roughly 9,500 Btu/kWh (HHV), or about 4,750 MMBtu/h of heat input. With water injection alone at the temporary subcategory's 25 ppm NOx limit (about 0.092 lb/MMBtu), its potential to emit over a full 8,760-hour year is about 1,900 tpy of NOx, which means PSD, BACT and modeling. With SCR at 2.5 ppm (about 0.009 lb/MMBtu) it falls to about 190 tpy. That is under the 250 tpy PSD line for NOx, but still a Title V major source and a nonattainment major source in any ozone nonattainment area. CO, PM2.5 and about 2.2 Mt a year of CO2 have to be checked the same way, and greenhouse-gas BACT applies once the plant is PSD-major for another pollutant. Controls and hour limits move the same plant between those regimes, so the calculation comes before the schedule.

Water shows up twice in the lifecycle: as a sourcing question (can you get the water? Chapter 3.7) and as a discharge and disclosure question, which is the permitting side covered here. The cooling architecture chosen in Part 5 determines which regimes attach. An evaporative or open-loop system that discharges warm, mineral-concentrated blowdown needs an NPDES permit under the Clean Water Act, with thermal limits, total-dissolved-solids caps and sometimes biocide-residual conditions. If it discharges to a publicly owned treatment works, it needs a local pretreatment permit instead. A dry-heat-rejection, near-zero-water design largely sidesteps NPDES (no significant process discharge) but pays for it in power and capex. A closed circuit alone does not get you there, since a closed loop can still reject its heat evaporatively, and it does not remove construction or industrial stormwater permitting. Design out the water and you design out the discharge permit, at an energy cost: the WUE-versus-PUE tradeoff showing up as a permit. → Chapter 5.7, Chapter 15.4.

If construction discharges dredged or fill material into a wetland, stream or other jurisdictional "water of the United States," the project needs §404 dredge-and-fill authorization from the Army Corps, or from an assumed state program. Any federal permit that may lead to a discharge also needs §401 water-quality certification, or a waiver, from whichever authority certifies for that water: the state, an authorized Tribe or EPA. A nationwide (general) permit clears in months. An individual permit for a significant fill can run one to two years and frequently drags a federal NEPA review along with it. Wetlands are a quiet but potent long-pole trigger, and a reason to screen them out at the land-diligence stage in Chapter 3.8.

Two frontiers are moving. First, WUE-disclosure law: a growing set of US states and the EU now require operators to report water consumption, turning a private operational figure into a public, comparable, contestable number and a lever for opposition. Second, PFAS. The "forever chemicals" at the heart of two-phase immersion coolants carry both supply risk and environmental liability, and 3M finished leaving PFAS manufacturing at the end of 2025. Fluid chemistry and remaining supplier availability now belong in the cooling-fluid decision, because a fluid choice is a long-tail environmental-liability choice. Chapter 5.5 compares the cooling architectures.

The National Environmental Policy Act does not regulate data centers. It regulates federal actions. A purely private project on private land with a state-issued air permit and a non-federal interconnection may never touch NEPA. The trigger is the federal nexus: an agency action such as federal-land approval, federal funding or financing, a federal permit (including some Clean Water Act §404 actions) or a federal transmission or interconnection approval. Significance and scope depend on the agency and the action. When a nexus exists, the action sorts into one of three tiers. A Categorical Exclusion needs no EA or EIS, but the agency must still confirm an applicable category and clear extraordinary circumstances, and documentation and duration vary by agency and action. By statute, an Environmental Assessment must by default be finished within one year. A full Environmental Impact Statement gets two years by default, and it remains the main target of lawsuits. The clock starts at the first of these that applies: the agency deciding it needs the document, its notice of intent, or notice that a right-of-way application is complete. The lead agency can extend either deadline after consulting the applicant, but only by as much time as the work needs. These are document-completion clocks, not the whole development schedule. Alongside NEPA ride the Endangered Species Act (Section 7 consultation) and the National Historic Preservation Act (Section 106 review), each capable of adding months.

Three developments in 2025-2026 reshaped federal review, and a scheduler needs to know which of them actually shorten a project's timeline. (1) The Seven County Infrastructure Coalition v. Eagle County decision (Supreme Court, unanimous 8-0 judgment, May 29, 2025) tells courts to defer substantially to an agency's reasonable choices on how broad and detailed an EIS should be. An agency does not have to study the effects of separate upstream or downstream projects it has no authority to regulate, and a court cannot block an approval because it left them out. The opinion explicitly names data centers. (2) Executive Order 14318 (July 2025) directs agencies to create new Categorical Exclusions for "Qualifying Projects," meaning at least $500M capex or >100 MW of new load. It also directs a rebuttable presumption concerning some federal financial assistance below 50% of project cost. The responsible agency still decides whether its action is subject to NEPA under the governing statute and current effective procedures. (3) The CEQ rescinded its long-standing NEPA implementing regulations, leaving procedure to each agency. Taken together, a qualifying project with a manageable nexus gets through federal review faster. A fourth change is pending. The Senate's bipartisan permitting bill, the Bipartisan American Affordability and Jobs Act of 2026 (text released September 30, 2026), would cut the time to sue under NEPA from six years to 150 days. A court that finds a NEPA flaw would largely be limited to sending the review back without vacating the approval. It needs 60 Senate votes and then the House, and the Senate returns after the November 3 election. Passage would shrink the time a federal-nexus permit stays exposed to NEPA suits from years to months, although a Clean Air Act or Clean Water Act claim could still stop a project.

The caveat matters. None of this grants grid service or removes the utility study and upgrade path. The reforms touch the air permit only at the edges. EO 14318 also tells EPA to speed up Clean Air Act permitting. On January 15, 2026 EPA finalized a temporary-turbine NSPS subcategory. On May 13, 2026 it proposed widening the non-emitting construction a project may start before it holds a major NSR permit, and that rule was still a proposal on October 12, 2026. Under either action, a major bridge plant that needs a PSD or nonattainment-NSR permit still needs it. NEPA reform is real, but for the median project it speeds up the wrong bottleneck.

The permit clock is a global variable, and the US framework does not travel. A portfolio strategist comparing clusters is comparing approval regimes as much as power prices, and the regimes diverge sharply.

European Union. The binding instruments are the Environmental Impact Assessment (EIA) Directive, the EU analogue to NEPA, which attaches to large projects and is typically administered by member states, and, distinctively, the Energy Efficiency Directive (EED). Under Delegated Regulation (EU) 2024/1364, every data center with installed IT power demand of 500 kW or more must report about 31 data points, including PUE, WUE, ERF and REF, into a European database each year (deadline 15 May, for the prior calendar year). Member states may lower the threshold but not raise it. The Commission adopted a delegated regulation setting up a common rating scheme on September 21, 2026. Parliament and Council were still scrutinizing it on October 12, and the first individual sustainability labels are expected in 2027. Next come minimum performance standards, which could make an inefficient design non-compliant. Comments on them close December 14, 2026, and the Commission intends to put forward a legislative proposal in Q2 2027. Germany's Energieeffizienzgesetz already hard-codes PUE caps and waste-heat-reuse obligations. A pending September 2026 government bill (Drucksache 21/8027) would keep the new-site 1.2 PUE and the 10/15/20% reuse floors but give new facilities four years instead of two to reach them, and would relax the existing-site PUE limits to 1.6 from 2027 and 1.4 from 2030 and widen the heat-reuse exemptions, so check its status before fixing a German commissioning plan. → Chapter 15.7.

European cities. In Europe the local gate is often the city's land-use plan, and two of the largest hubs, Frankfurt and Amsterdam, now use it to ration data centers. Frankfurt's city council adopted its data-center concept on June 9, 2022. It sorts the city's commercial and industrial areas into suitable, restricted and excluded zones for third-party (colocation) data centers, and the city is writing those zones into binding local plans (Bebauungspläne) one area at a time. The concept shapes only plans adopted or amended after it, and the same decision told the city to prepare a waste-heat plan and binding design and resource standards. Amsterdam went further. Its 2020 policy allowed 670 MVA of new connection capacity to 2030 in four clusters. On June 12, 2025 the council replaced it with "no, unless", backed by a citywide zoning plan that bans any new data center or expansion above 2,000 m² and 5 MVA. An exception needs an out-of-plan permit, a site in a designated cluster and the policy's sustainability conditions; in the four historic clusters the application or pre-consultation must also predate December 28, 2023. After an appeal the council amended the plan on September 2, 2026, and that amendment can be appealed to the Council of State until October 28, 2026. Above the city, Dutch national rules have confined hyperscale campuses (more than 10 hectares and 70 MW) to Eemshaven and Middenmeer since January 1, 2024. So in either city the first diligence item is the parcel's zoning designation, before any power study: a parcel in a Frankfurt exclusion zone, or an Amsterdam project over the threshold that fits none of the plan's exceptions, has no permit path to schedule.

United Kingdom. In England, data centers can now opt into the Nationally Significant Infrastructure Projects (NSIP) regime by ministerial direction, and ministers had directed three proposals into it by July 2026. Under that route a Secretary of State decides on a fixed timetable. Otherwise town and country planning permission applies and the local planning authority decides. Record which route the project takes. The government designated data centers Critical National Infrastructure in 2024-2025. Scotland, Wales and Northern Ireland run their own systems.

Nordics. The siting attraction (free cooling, firm hydro and nuclear power, heat-reuse offtake) comes paired with rigorous but predictable environmental permitting and, increasingly, an expectation, sometimes a requirement, of waste-heat recovery into district heating. The regime is slower than "by-right," but the predictability is itself a feature: you can underwrite the timeline. → Chapter 5.9.

Middle East (UAE, Saudi Arabia). Sovereign-led development compresses approvals dramatically. A single empowered authority or economic-zone regime can collapse the multi-layer matrix into one fast track. The trade is water-scarcity constraints, with cooling and water-source requirements set for the specific jurisdiction and project, and the geopolitics of chip access covered in Chapter 3.12.

APAC. The spread is enormous. Singapore ran a multi-year moratorium and now admits new capacity only through a selective, efficiency-gated allocation. Japan couples strict environmental review with grid-constrained siting. Malaysia (Johor) and India are growth markets that court projects with incentives, so treat approval speed as a site-specific question. According to MIDA (August 28, 2026), Malaysia's Data Centre Task Force clears a project only if it has secured power and water and can show green compliance, and it puts operators that support the local supply chain first.

The table lists the non-US rules a designer must have pinned down for the site, and who owns each record. The key numbers below give the statutory thresholds and start-date cohorts. The designer still needs the operator's own applicability record, its meter plan and the evidence for any exception. Keep the EED heat-use test, which turns on total rated energy input, separate from EED reporting, which turns on installed IT power.

Noise is where permitting meets the neighbors, and anyone who treats it as a single dB(A) number will mis-model it. The acoustic signature of a large AI facility (chillers, dry coolers, cooling-tower fans, generator testing and the low rotational hum of dense liquid-cooling plant) is dominated by low-frequency (LFN) and tonal content that A-weighting deliberately under-counts. A facility can pass a property-line dB(A) limit and still produce a persistent tonal hum that residents find intrusive, especially at night. Communities and ordinances have responded with low-frequency and tonal penalties, 1/3-octave-band assessment and tighter nighttime limits, which turn noise from a checkbox into a real constraint. Chapter 6.8 covers the engineering response (attenuators, enclosures, equipment selection, setbacks). The point here is that the noise budget is set at the permit and zoning stage, and a design that ignores LFN until commissioning has no cheap fixes left.

Land use decides whether any of this becomes a fight, and the decisive fork is by-right versus discretionary. Where data centers are a permitted use in the zoning district, approval is administrative: fast, predictable, no hearing. California breaks this pattern, because SB 887 now makes every data center prepare a CEQA document and so puts a discretionary step even on by-right land. Where they need a special-use permit, conditional use or rezoning, approval is discretionary. It goes to a public hearing, where noise, traffic, water draw and visual impact become grounds for denial and organized opposition can sway the decision-makers. The 2022-2026 wave of zoning reform has moved many premier markets from by-right to discretionary. Loudoun County, Virginia ended by-right and routes data centers through special-exception review, and setback rules and moratoria are spreading nationally. Loudoun has since gone further: on September 15, 2026 its Board voted 7-1-1 to pause legislative data-center applications for up to 12 months, with a formal resolution set for October 20. Applications already grandfathered are exempt, so not every project is affected. Raleigh, North Carolina, followed on October 6, 2026, with a six-month pause on accepting and reviewing data-center applications while it drafts new rules, with final action targeted for April 6, 2027. A discretionary path can add 6-18 months of hearings and turns a permitting question into the social-license campaign of Chapter 3.11.

Everything above resolves to one discipline: find the two or three approvals that are both slow and serial, and start them before anything else. For the overwhelming majority of AI campuses those are (1) grid interconnection and (2) the air permit for backup or bridge generation, with NEPA, §404 and discretionary rezoning joining the list only when the site triggers them. Some states add a statewide gate. New York's Executive Order 62 (July 14, 2026) puts on hold any covered data-center application to build or expand that needs a discretionary DEC permit, unless DEC had found it complete before that date. The hold lasts until the Department of Public Service submits its report of the final Generic Environmental Impact Statement (GEIS) and findings, and the order sets no fixed end date. The order reaches facilities that use, or can use, 50 MW or more, as it defines them and minus its exclusions. Local permits are not held. On September 17 the PSC issued a positive declaration and a draft GEIS scope, and comments are due October 20, 2026. If your project needs one of the held DEC approvals, the GEIS release belongs on its critical path.

The shell, the host utility's service path and any major-source air permit each start and finish on different events. Get project-specific durations and connect them to one energization milestone. Start those paths late or in series, or begin them at groundbreaking, and you risk a building that finishes before its service and permit releases.

A completed asset waiting to begin earning operating revenue is the cost of starting a long utility or permitting path too late. For the compute operator, a 200 MW block of critical IT energized six months late forgoes about $1.2–1.3B of gross AI-cloud contract revenue (Chapter 2.2 works the figure and its limits). A landlord's exposure is its lease rent plus any delay damages the lease sets. Developers therefore open talks with the utility and start air pre-application work during diligence. They file once they hold the site control and evidence each application requires, and they treat study spend on a site they might not close as an option premium. The same cost is why bridge power (behind-the-meter gas, on-site gensets) exists: a way to start earning while the interconnection clock runs, and itself an air-permit decision.

The federal interconnection reform now underway (FERC RM26-4, under DOE's Section 403 directive, proposing a >20 MW threshold) has not produced a nationwide rule. On June 18, 2026 FERC opened Section 206 show-cause proceedings against all six RTOs/ISOs and left the docket open. August abeyances then extended the regional show-cause schedules. For PJM, FERC's August 14 order set November 16, 2026 for responses and December 16 for answers, and PJM may still make Section 205 tariff filings before then (→ Chapter 3.2). The >20 MW figure remains DOE's proposed threshold, not an adopted rule. The reform may change the applicable procedures, but it does not change the discipline: the long poles are known on day one, and they have to be started first.