Spanberger order bans data center NDAs

Virginia's governor has signed an executive order that bans non-disclosure agreements for data center projects and orders a review of the diesel backup generators that keep campuses running when the grid stumbles. Governor Abigail Spanberger's office calls the resulting Data Center Accountability Framework the most comprehensive and aggressive data center accountability effort in the country, a description from her own office rather than from an outside scorekeeper, and the package also pushes the state's data center noise regulations toward faster completion, hands local governments a planning and community engagement toolkit, and creates a Virginia AI task force to examine workforce displacement, data privacy and cybersecurity. It stops no projects; it changes what has to be said in public.

The order lands where the volume is: Northern Virginia is the world's busiest data center market by Data Center Dynamics' account, and the counties inside it have been tightening for months. Prince William County is shrinking the by-right district where projects get approved without a full planning review, and Loudoun County has paused new applications for twelve months. A state framework arriving on top of county-level brakes changes the negotiating arithmetic, because a developer that clears one board no longer knows whether the rules it satisfied will still be the rules.

Spanberger, who took office earlier this year, is less an outlier among governors than the third move in a sequence. New York's Kathy Hochul introduced a one-year moratorium in July, citing power and water consumption, and Texas's Greg Abbott paused all data center projects in the state while ERCOT works through the interconnection requests it has received. Virginia's order is a different instrument from either; anyone underwriting a campus inside the Beltway now has to price the gap between what a developer says in private and what it must put on the record.

NDAs, per Data Center Dynamics, have often been used to keep the details of new campuses out of view, and the executive order bans them for data center projects. The coverage does not describe which agreements the ban reaches, whether it binds private parties or only the localities that sign off on projects, or what it does to contracts already in force. Those questions decide whether the framework bites, because a disclosure rule aimed at tenant identity, acreage and power demand behaves nothing like one that ends at the county's own files.

The direction of travel is visible in the other state that acted. PWD reported in September on Abbott's halt, where community and ratepayer support ended up in the same diligence binder as the interconnection agreement, with the permit turning into a disclosure document in its own right. A state-level NDA ban pushes the same logic without touching the queue. If tenant identity enters the record at the planning stage rather than after a lease is signed, the pricing gap that separates anchored projects from unanchored ones stops being an analyst's estimate and becomes a public fact. That cuts both ways for developers: a committed hyperscaler or AI lab tenant becomes a marketing asset in front of a skeptical board; a site assembled around an unnamed or unsigned tenant has to defend its numbers to an audience that can now read them.

Backup generators are the least glamorous line item on a data center budget and the most detectable one from a neighbor's porch. A diesel fleet is what stands between a campus and a grid event, and it is also what a community can hear and smell, which is why the order calls for a review of generator impacts with diesel units named specifically. Whether that review ends in emissions limits, replacement obligations, or a report that recommends nothing binding is not described in the coverage. The answer matters more to existing campuses than to pipeline projects, because a retrofit mandate is harder to finance than a specification attached to a building that has not been drawn yet.

Noise works the same way. The order makes noise a state concern and calls for state noise regulations to be developed faster. If a single standard replaces a dozen local negotiations, developers gain a number they can build to and counties lose a lever they have been using at the hearing stage. The framework's planning and community engagement toolkit points the opposite way at first glance, because it hands local governments a template, not a constraint; a county with a better playbook extracts more from the applicant sitting across the table.

The AI task force sits apart from all of this. Its stated remit runs to workforce displacement, data privacy and cybersecurity, the software and labor side of the same boom rather than the megawatt side, and its creation puts Virginia in the position of writing rules for the models its data centers train alongside rules for the buildings that house them.

Abbott's pause put 49.8GW of Texas projects waiting on a December deadline; Virginia's order leaves a comparable pipeline moving while it rewrites the paper trail behind it. Loudoun's twelve-month pause has no start date in the coverage, so the county's reopening remains an open question for anyone modeling deliveries into 2027. Prince William's by-right district is being resized rather than eliminated; how much acreage remains outside the full planning process will determine how many projects skip the hearing the state's new toolkit is meant to make more useful.