Data center contractors say new state rules extend permitting without cooling demand

Data center contractors have taken up a new discipline this year: listening. As local residents and public officials press on power, water and land use, builders with the largest books of hyperscale work say they are giving community concerns more attention than they once did — and, Construction Dive reports, the scrutiny has done little to cool demand even as new restrictions and growing opposition add complexity to development.

The restrictions are specific and arriving quickly: in September, Virginia Gov. Abigail Spanberger signed an executive order that bars projects with anticipated peak demand of at least 25 megawatts from receiving state assistance through expedited permitting and site development programs, among other measures. It also directs state agencies to address noise, emissions, water use, electricity demand and other impacts over the next several months, expedites noise rules, orders a review of diesel backup generator impacts and creates a state AI task force.

Pennsylvania moved first, in August, when Gov. Josh Shapiro signed an executive order on energy affordability and environmental protection giving local communities a greater role in development.

Texas chose a different instrument: Gov. Greg Abbott directed the Texas Commission on Environmental Quality to halt all permits sought by data centers until the Electric Reliability Council of Texas completes its audit, and under the same directive data centers must cover all electrical infrastructure costs and must not use water needed by local communities, according to a Sept. 21 news release.

Three governors, three mechanisms, one target: Virginia attaches a megawatt threshold to state assistance, Pennsylvania widens the local government's seat at the table, and Texas stops issuing permits until its grid operator finishes a review. Each governs the permission to build — the planning and entitlement phase that runs before ground is broken — and read together they are less a wall than a set of gates, each placed where a developer needs something from the state.

Pushback is arriving alongside the spending, not after it: concerns about power and water from residents and public officials are climbing in step with construction outlays on these projects, making objections a feature of the current cycle rather than a reaction to a finished one. Contractors describe themselves as more attentive to those concerns than they once were, and they also say the attention has not yet cost them work — both can be true in the same quarter.

The three orders also preview how the map is fragmenting: Virginia's rule is a condition on state assistance, Texas's is a condition on a permit, and Pennsylvania's is a condition on process — three different points at which a state can insert itself between a developer and a site. A team running a multistate pipeline now faces a different consent regime in every jurisdiction it enters; for a developer, consent work no longer ends at the property line but follows the project into every jurisdiction the pipeline touches, and New York, meanwhile, has imposed a moratorium rather than a condition.

The two kinds of pressure are not the same, and contractors treat them differently: local opposition is variable, depending on the site, the neighbors and the nearest water source, and can be managed project by project — roughly what the industry means when it talks about listening. State restrictions are systematic, applying to every project that crosses a threshold or sits inside a jurisdiction, and the officials who write them are not in the county hearing room; those are the changes getting contractors' attention, and the contractors are the ones who will have to absorb them.

Chris Teddy, national director of mission critical at JE Dunn Construction, told Construction Dive the scrutiny is concentrated in some markets and centers on power availability, water usage, land use and the overall community impact of large-scale developments. His formulation — that it 'doesn't necessarily stop projects from moving forward, but it can extend timelines and add complexity during the planning and entitlement phases' — is worth reading slowly.

Kim Roy, chief executive of HITT Contracting, the Falls Church, Virginia, general contractor that has built data centers for more than 25 years, put it more plainly: asked whether community opposition or state restrictions are affecting HITT's construction schedules, she said she hasn't seen it reach that point. 'I don't see it,' she told Construction Dive; 'I mean, at that point, it's just listening and addressing the concern. It really doesn't affect our build schedule.'

The two statements describe different parts of the same pipeline: Teddy is talking about entitlement and Roy about the build schedule. A project that has cleared its permits and broken ground will finish regardless of what a governor signs next; a project still in planning and entitlement is exposed to every order. The friction lands at the front of the queue, which is why contractors holding a full book of awarded work can report that nothing has changed.

There is a reason the builders sound calm: a contractor's schedule is set by projects already awarded and underway, and the consent questions for those were answered well before a crew arrived. The order book reflects the last cycle of approvals, says little about the next one, and it is the next one that the new state rules govern; entitlement friction is a problem for the pipeline rather than the backlog, which is why it can be acknowledged calmly and still matter enormously to the people who fund the pipeline.

Texas is where the consequence is scheduled to appear: Abbott's directive folded community and ratepayer support into the same diligence file as the interconnection agreement, and December's audit will show which developers actually did the work. The mechanism is distinctive — it converts grid access into a state grant, and the audit's ownership questions turn a permit application into a disclosure document. This publication's tracking shows 49.8 gigawatts of Texas projects waiting on that deadline.

New York points in a different direction: the state's moratorium on hyperscale data centers, reported by Data Center Dynamics, has developers looking to behind-the-meter generation — fuel cells and storage — as the answer inside a jurisdiction that has paused new approvals. That trade solves the permission problem and creates another one, because a data center that supplies its own power has moved the risk out of the state's interconnection queue and onto its own balance sheet, where the fuel contract, the uptime guarantee and the capital cost all sit with the developer.

The shape is familiar in the energy business, where a project milestone without a named buyer is a developer absorbing risk rather than a project reaching bankability, and digital infrastructure is meeting the same logic from the other side. Siting consent rather than capital now decides what gets built, and the new state orders are the mechanism: they make permission the scarce input, which shifts value toward developers that already hold permitted sites and away from those still assembling them. A project that cannot get consent is development inventory, not infrastructure.

Why the friction is not yet visible in HITT's schedules may be a matter of timing: the company is based in Falls Church, Virginia, and Virginia's executive order landed only in September. A contractor whose commitments run through projects already permitted and under construction would not expect to feel a new entitlement regime for months; the projects now being built were entitled under the old rules, and the ones that will test the new ones have not yet filed. That is inference rather than reportage, but the calendar supports it.

For investors who underwrite these assets, the practical question is how consent risk gets priced: a rule with a number attached — Virginia's 25-megawatt line — is something a developer can model, building below it or above it and forgoing the state's help, whereas a moratorium is harder because it carries no threshold and no schedule. The market has been willing to extend infrastructure treatment to data center assets on the strength of tenant demand; what the new state orders test is whether that treatment survives when the permission to build is a variable the developer does not control, and the question for the next financing cycle is whether unentitled capacity gets written down or simply waits.

Roy's confidence may prove well placed — demand is demand, and contractors with awards in the sector have earned the right to stay calm. But the orders signed this fall are young, and the build schedules they will eventually touch are not yet on anyone's calendar; the first hard answer arrives in December, when Texas finishes its audit and finds out how many of its 49.8 gigawatts did the diligence the state now asks for.