Tommy N. Turner
Independent researcher and writer. Institutional governance, public policy.
Data Centers in Virginia, Georgia and Tennessee
Primary-document research on the data center buildout: state fiscal policy, utilities and generation, transmission, water, gas supply, county land-use decisions, and the organizations on every side. Every work is built from filings, orders, dockets and minutes, deposited on Zenodo with a DOI, and free to read under a CC BY licence. 48 works. Suggested starting points are marked with a star.
Statewide references
The fiscal and inventory foundation, the argument that runs across the county cases, and the census of who took part.
- What Virginia Is Spending, What Virginia Is Getting: The Commonwealth Data Center Reference
What Virginia Is Spending, What Virginia Is Getting (v5.2) is the comprehensive statewide reference on data center development in Virginia and the anchor volume for a series of county case studies.
The anchor reference for the county case-study series. - Governing the Demand Shock: Local Institutional Variation in Virginia's Data Center Boom (Report)
Virginia hosts the largest concentration of data centers in the world, and between roughly 2018 and 2026 the industry moved out of its Northern Virginia core into more than two dozen counties and independent cities.
The compact report. The book edition carries the full narrative. - Governing the Demand Shock: Data Centers, Local Power, and the Distribution of Cost in Virginia
On a Tuesday night in late May 2026, the Hanover County board voted four to three to turn away a 900-megawatt data center, walking away from the largest taxable investment ever offered it, and on water.
Book edition of the report, written for a general reader. - Who Showed Up: A Census of the Organizations Around Data Center Siting in Virginia, 2014 to 2026
Of 49 refusals, withdrawals, pauses and tightened rules tested, the census can place a named organisation, dated, before the decision in 14; in 27 it can place no one. Of 129 entries on the opposition, reform and litigation side, 30 state a founding date, so the record supports no growth curve. Thirteen of 58 localities market themselves to data centers on their own economic development pages, and nine of those are places whose boards refused, paused or tightened.
A census of every organised body found engaging data center siting in Virginia, on every side, December 2014 to 26 September 2026. Records presence and dates and does not assert cause. Register deposited separately (22998217); saved source pages held in a restricted record (22996886), released on request. Any organisation named may report an error in its row. - Below the Curve: What Virginia Counties Chose Not to Measure
Of the 75 adopted local noise instruments in this volume's census, 67 carry no tonal provision and 65 no low-frequency provision, so most cannot register the low, steady hum people living beside data centers describe. The volume follows the choices about the measuring instrument that produced that gap, made in public, at stated prices, for stated reasons, in Loudoun, Prince William and Chesapeake.
Supplement to the Commonwealth Data Center Reference (20679292). The county noise ordinance census workbook and a source companion are deposited in the same record. References the Loudoun (22374193), Prince William (20673498) and Pittsylvania (22968398) case studies and Governing the Demand Shock (20692386). - Data Center Maps: A Register of What Exists, What Works, and Where It Fails
146 resources that map, track or inventory data centers, nationally and in depth for Virginia, Georgia and Tennessee, each graded from recommended to avoid for research. No resource is a census: trackers that publish state counts disagree by wide margins, change between editions without notes, and mix buildings, campuses, projects and permits as their unit of record. The gap no map fills statewide is the local zoning decision, ordinance or moratorium behind each site.
Register v0.1, resources checked 28 September 2026. The full report and register (PDF) is mirrored here; the two-page briefing and the filterable workbook, with a sheet for each state, are on the Zenodo record. Prince William County's Build-Out Analysis map is named as the closest existing template for a better map. - Counting Data Centers: The OpenStreetMap Inventory Behind a National County-Level Comparison
A September 2026 trade association report sorts more than 3,200 U.S. counties into four groups by how many data centers each contains, and runs its comparisons of housing, employment and electricity outcomes across those groups. The counts reproduce exactly from the cited source in four checks; the arithmetic is correct. The findings here are narrower and prior — what a county-level count built from the IM3 Open-Source Data Center Atlas can actually support.
Working paper. Methodological note on the OpenStreetMap-derived facility file (Pacific Northwest National Laboratory) that underlies a widely-cited national inventory.
Utilities, generation and transmission
Who builds the power, who reviews it, and who pays for the wires.
- Thirteen Cooperatives: Virginia's Distribution Cooperatives and the Arrival of Load Larger Than the System
Thirteen electric distribution cooperatives serve Virginia — the figure most often cited is eleven. Data-center load is arriving on several of them. This reference walks identity and jurisdiction, wholesale supply (nine of thirteen through Old Dominion Electric Cooperative), the seven-case affiliate sequence in which one cooperative was twice refused authority to serve hyperscale load through an unregulated affiliate, and the four large-load rate schedule cases side by side against the investor-owned regime that preceded them.
Reference companion to the Commonwealth Data Center Reference (20679292). Also addresses Va. Code § 56-234 D (2025 Acts of Assembly, chapters 499 and 598), which reframes the affiliate question. References the Mecklenburg (20673484), Botetourt (20673512), Culpeper (20673529), Google–CFS (20679935), and Governing the Demand Shock (20692386) volumes. - Built for Someone Else: Generation, Load, and the Exception in Virginia
Virginia's generation-siting statute reaches two of the four routes now serving data centers, applies its full test to one, and does not reach the other two at all. Built on 108 primary documents, each hashed. Evidence snapshot 24 August 2026.
Companion volume to the Commonwealth Data Center Reference (concept 20679292). Source manifest deposited separately as concept 22099427. - Concentrated Benefit, Dispersed Burden: Who Carries Virginia's Data Center Transmission, and What the Cost-Allocation Record Does Not Trace
Virginia's data centers consume roughly a quarter of the Commonwealth's electricity, and PJM attributes a ten-gigawatt increase in forecast Dominion-zone load by 2029 primarily to them.
Volume I in the Concentrated Benefit, Dispersed Burden series — Virginia transmission cost allocation. Companion Zenodo dataset: 21959988 (utilities transmission-siting geographic data). - What the Record Does Not Say: Interstate gas supply for Virginia generation, and a question no forum wrote down
FERC certificates interstate gas capacity on a precedent agreement, declines to weigh what the gas is for, and treats a shipper's decision to subscribe as beyond the scope of its review — a matter for state regulators. Virginia's SCC approved a 944-megawatt gas plant without writing down what the fuel costs or what capacity factor was assumed. The question no forum wrote down.
Working paper. Companion to Built for Someone Else (22096613); supporting eleven-docket dataset deposited as 22757119. - When the Operator Builds the Plant: The Google–CFS Power Purchase Agreement and What It Means for Virginia's Energy Market
Documents the June 30, 2025 Google–CFS power purchase agreement and Eni's September 22, 2025 offtake for the 400-megawatt ARC fusion plant in Chesterfield County — the Fall Line Fusion Power Station. Not a technology profile; examines the commercial instruments themselves and the equity stakes both buyers hold in the developer.
Water
What the withdrawal rules reach, what they record, and where a utility-supplied data center disappears from the record.
- No Field to Land In: How Three States' Water Withdrawal Forms Make Utility-Supplied Data Centers Illegible
A data center that buys treated water from a public utility is, in Virginia and Tennessee by express clause and in Georgia by definition, not a person who withdraws water. Reads the reporting forms each state prescribes, field by field, and asks where on them a delivery to such a facility would be recorded. There is no field built to take it.
Cross-state water-reporting analysis (VA, TN, GA). Documents the record void created by the utility-supplied-exemption plus form-field absence combination. Companion to the Virginia and Georgia water volumes. - A Line Drawn on a Highway: Virginia's Groundwater Boundary, the Rivers Beyond It, and the Data Center Load the Regime Does Not Reach
Virginia regulates groundwater by asking three categorical questions and never asking how much. Data centers answer all three in the way that exempts them. 89.9% of Virginia's 286 inventoried data-center facilities sit outside every declared groundwater management area, and the boundary is Interstate 95.
Companion volume to the Commonwealth Data Center Reference (concept 20679292); extends the coastal-aquifer thread from Two Systems (21816008) to the full groundwater and surface-water regime. - Where the Instrument Stops: Virginia's Groundwater Ceiling, Its Grandfathered Rivers, and the Load Outside Both
DEQ said it in the SJ 25 study: the strip of Coastal Plain sediment west of Interstate 95 "is disregarded, and I-95 is treated as the approximate western edge of the VCP aquifer system." Virginia drew its regulatory boundary at the same road and regulates as though it were real.
Executive brief synthesizing three deposited water volumes (21556435, 21816008, 22105181). Carries four findings that none of the three volumes makes alone. - Two Systems, One Drought: Virginia's Groundwater Ceiling, Its Rivers, and the Water the Energy Buildout Actually Uses
Virginia's coastal aquifer is capacity-bound; its river system is drought-stressed. The Commonwealth is solving a problem in one by adding to the other, and the data-center buildout is arriving before that trade has been priced.
- The Aquifer Says No: DEQ's SJ 25 Groundwater Study and the Data Center Question East of I-95
In July 2026 the Virginia Department of Environmental Quality published its study of the groundwater supply east of Interstate 95, ordered by the 2024 General Assembly under Senate Joint Resolution No.
- Declared, Not Measured: Volumetric Permit Triggers and Sub-Threshold Industrial Water Demand in Georgia
Georgia's 100,000-gallon-per-day groundwater permit trigger runs per person and turns on a quantity that, before a permit issues, exists only as the withdrawer's declaration. A measurement-coincident threshold — the regime regulates what it can already see. Sixteen data-center Development of Regional Impact filings were made between January 6 and July 22, 2026.
Extends the Virginia water thread (references 21816008 and 22105181) into Georgia. Data centers are the occasion; the design property is stated independently as a limiting case of Bennear (2008).
Virginia county case studies
Thirteen localities, read from their own packets, minutes, ordinances and agreements.
- Case Study: Loudoun County, Virginia — The Endgame Case: What It Costs to Change the Rules After the Industry Is Load-Bearing
On March 18, 2025, the Loudoun Board of Supervisors voted 7–2 to require a special exception before a data center could be built in the districts where the use had been permitted by right. The reform never reached the Route 28 corridor, where commercial and industrial zoning is frozen by state statute until 2037. A point-geometry join puts 51 percent of Loudoun's built data-center square footage inside that district — a constraint the county publishes on its own website and that went unmentioned across fourteen months of rewriting the ordinance.
The Endgame Case. Loudoun as the diagnostic county — what it costs to change the rules after the industry is load-bearing. isSupplementTo the Commonwealth Reference (20679292); references every other county case in the series. - Case Study: Prince William County — Governance Capture, the Revolving Door, and the Democratic Correction
The largest data-center proposal in American history was filed at the Supreme Court of Virginia three hours before deadline, then withdrawn on July 2, 2026. No court ever reached its merits. Documents how the county got there: the sitting supervisor who signed a contract to sell his own land to one of the developers ten days before joining the application, the board chair with a disclosed six-figure position in the parent company of the other developer, and the primary that reset the board.
- Case Study: Henrico County — How Two Neighborhoods Forced Virginia's Second-Largest Data Center Jurisdiction to Change Course
Henrico County, Virginia spent two decades recruiting the data center industry and eighteen months learning to govern it.
The first case study in the county series. - Case Study: Hanover County — Mountain Road, Tract, and the Search for Leverage
On the night of May 27, 2026, the Hanover County Board of Supervisors refused Tract's Mountain Road Technology Park: 427 acres, 900 megawatts, and the most contested land-use decision the county had…
- Case Study: Chesterfield County — The $0.24 Rate, the Thirty-Year Lock, and the Two-Corridor County
Chesterfield built its data-center strategy on a single number: the equipment tax rate set at $0.24/$100 in April 2019 — a deliberate undercut of Henrico's $0.40 and the lowest in Virginia. Google assembled roughly 1,640 acres, Chirisa committed $2 billion, and Commonwealth Fusion Systems selected Battery Brooke for the world's first grid-scale commercial fusion plant. The rate is locked for thirty years.
- Case Study: Pittsylvania County — The County Turned Down One Data Center Plan, Then Rezoned for a Bigger One
In April 2025 Pittsylvania County refused to rezone 763 acres for a private gas plant and data centers. Nine months later the same board made data centers by right on 3,500 acres at the Berry Hill megasite, in a district whose text says the county's own data-center standard does not apply there. Within eight weeks the regional industrial authority had approved a sale contract defining the buyer's project as no less than 3,300 megawatts with onsite gas generation. Noise: 52 dBA offered by the refused applicant, 77 dBA adopted, and that only beside residential zoning.
Refusal, then entitlement by ordinance on the county's own motion. Traces the Berry Hill loop and substation built by Appalachian Power under the business-park pilot statute. isPartOf the Commonwealth Reference (20679292). Evidence snapshot 25 September 2026. - Case Study: Mecklenburg County — Boydton, South Hill, and What Fifteen Years of Data Centers Actually Bought
Every other report in this series documents a Virginia county deciding on promises.
- Case Study: Botetourt County — Project Raspberry, the Water Authority, and the Wave That Crossed the Blue Ridge
On June 24, 2025, Botetourt County announced that Google had bought 312.55 acres of the county's flagship business park at Greenfield for $14,055,406.37, plus $4 million for county initiatives.
- Case Study: Culpeper County — The Quiet Successor
Culpeper County holds one of the largest accumulations of data center entitlements in Virginia's diffusion ring: roughly 12 to 13 million square feet built or approved across eight campuses, and…
- Case Study: Louisa County — The First Overlay, the Amazon Retreat, and the $17 Billion Bet
Louisa County, Virginia invented the instrument that the rest of central Virginia is now copying, and then walked away from its central feature before the first imitator finished drafting.
- Case Study: Goochland County — The Overlay, the Lawsuit, and the Template
Every county documented in this series so far decided data centers project by project.
- Case Study: Orange County and the Town of Orange — Convergence at Two Scales: One Industry, Two Governments, and the Entitlement Neither Can Reach
In the spring of 2026, two governments whose chambers sit blocks apart in the same small town regulated the same industry in the same season, with different instruments, on different timelines, and…
- Case Study: The Fredericksburg Ring — Five Jurisdictions, One Corridor, and the I-95 Path South
Since 2022, the five jurisdictions surrounding the Rappahannock River fall line (Spotsylvania, Stafford, Caroline, and King George counties, and the independent City of Fredericksburg) have approved…
Georgia and Tennessee
Statewide reports and the federal record for the two companion states.
- What Georgia Is Spending, What Georgia Is Getting: A Statewide Data Center Report
Georgia built the second-largest data center market in the United States without ever deciding to.
- What Tennessee Is Building, and What It Is Not Regulating: A Statewide Data Center Report
Tennessee entered the data center era without deciding to, and built one of the densest hyperscale concentrations in the South with the thinnest governing apparatus this series has documented.
- What the Certificate Points At: Fuel disclosure, sealed cost, and one Georgia certification of 9,885 megawatts
On the same day in July 2025, Georgia Power filed two applications with the Georgia Public Service Commission seeking certification of capacity summing to 9,885 megawatts — 7,999 from the 2029–2031 All-Source RFP and 1,886 from a supplemental portfolio. Both were granted in full. The certified cost is sealed for both classes; every cost cell in the two tables is redacted. What differs between the two classes is the fuel.
Working paper, Georgia companion to What the Record Does Not Say (22754150). Shares the eleven-docket register 22757119 as supplement; part of the Built for Someone Else (22096613) source apparatus. - Sufficiently Analogous: Federal need review for a gas shipper with no state regulator, in two Tennessee certificates
Asked who reviews the Tennessee Valley Authority's decision to contract for firm interstate gas capacity for two new power plants, FERC answered in two orders and one sentence: state commission oversight is not a prerequisite for section 7 approval, and "Congress has oversight power over federal agencies, including TVA, and we find this sufficiently analogous to state commission oversight." The certificates covered the same 400-mile route inside sixty days.
Working paper. Extends What the Record Does Not Say (22754150) and What the Certificate Points At (22754180) into Tennessee. Shares the eleven-docket register 22757119 as supplement. - The Whole Record: What the Tennessee Valley Authority Publishes When Nothing Requires It
TVA builds transmission lines across seven states and files no siting case for any of them. The GAO reported this to Congress in 1982 and proposed statutory fixes; none were enacted. What TVA chooses to publish is the public record — this volume measures it.
Volume II in the Concentrated Benefit, Dispersed Burden series (Vol I = concept 21895588). 264 pages across fifteen chapters. Codes eighteen TVA project pages and reconstructs the categorical-exclusion record from 11,899 determinations. - Getting the Record: A Guide to Requesting TVA Transmission and Siting Documents
Companion to The Whole Record: What the Tennessee Valley Authority Publishes When Nothing Requires It — concept DOI 10.5281/zenodo.21996375, version 1.0 published 26 August 2026 at 10.5281/zenodo.21996376.
Practitioner guide companion to The Whole Record (21996375). Walks how to request TVA transmission and siting documents where no state PUC docket exists, given TVA's disclosure practice and NEPA categorical-exclusion pattern.
Construction labor
Building trades membership in the metros where hyperscale construction concentrated, from federal union filings.
- Membership grew faster than employment: A sixteen-year panel of inside electrical construction in hyperscale data center metros, 2010 to 2025
Rebuilds and extends the eight-year panel of Where the Electricians Went into a sixteen-year panel opening in 2010. Inside-electrical-construction union membership in hyperscale data center metros grew faster than employment across the same period. Reports the widened window and the effect on the central estimate's significance.
Research note, version 1.0. Own concept DOI; supersedes findings of 22310705's earlier v1.0 (which remains citable). Companion measurement paper is 22861996; shared replication dataset is 22862472. - Counting a trade in one metropolitan area: union membership for inside electrical construction from federal filings, 2010 to 2025
Union density is published for metropolitan areas and, within them, for private construction. It is not published annually for a single trade inside a metropolitan area, and the surveys that would support that measurement do not carry the resolution. This paper builds the missing series from federal LM-2, LM-3 and LM-4 filings for a single trade — inside electrical construction — 2010 to 2025.
Measurement paper. Companion research note is 22866646; shared replication dataset is 22862472. - Where the electricians went: Hyperscale data center construction and building trades membership in federal union filings, 2018 to 2025
Published employment figures for data-center construction come from the industry or from unions testifying on projects. This paper builds an independent series from federal LM-2 filings and IBEW jurisdiction maps: an eight-year panel of inside electrical construction membership for 89 metropolitan locals. Median treated local grew 33.7 percent between 2018 and 2025 against 13.2 percent elsewhere — a 25.8-percentage-point regression difference, randomization p below 0.001.
Working paper v0.1 with complete replication package. Uses federal union filings as an independent labor-measurement source. Effect concentrated in metros with hyperscale campuses; removing top-five-fastest-growing locals leaves 9.0 points and no significance.
Across the corpus
One essay above the research threads, page-referenced to the deposited works.
- Who Was Assigned to Ask How Much: Institutions, Their Records, and the Fact Nobody Had a Field For
Institutions govern through what they write down, and across water and gas regulation, county zoning, municipal finance, and the citations generative search displays, the decisive fact is reliably the one nobody had a field for. Three kinds of failure, one question asked of each: who was assigned to ask how much.
Working paper, version 1.2. Cites twenty-two works in this corpus; the related-works list below is the essay's bibliography.
Datasets
Registers, replication materials and source manifests behind the reports.
- Who Showed Up: Register of the Organizations Around Data Center Siting in Virginia, 2014 to 2026
The register behind Who Showed Up: A Census of the Organizations Around Data Center Siting in Virginia, 2014 to 2026 .
Register behind Who Showed Up (22996870): 223 rows (221 live), 23 columns, every value with the page it was read from and the date; codebook, counts-and-gaps file, conflict log, browser-pass record and a manifest of the 611 saved source pages. v1.3, evidence snapshot 26 September 2026. - Transmission Siting Disclosure Capture: TVA, Oncor/LCRA and Dominion Energy Virginia, August 2026
A point-in-time capture of publicly published transmission line siting geographic data, retrieved 15 August 2026 by anonymous query against public ArcGIS REST endpoints.
Point-in-time dataset capturing which utilities publish vs. withhold transmission-siting geographic data (TVA, Oncor/LCRA, Dominion Energy Virginia). - Source manifest and datasets for 'Built for Someone Else: Generation, Load, and the Exception in Virginia'
The data apparatus for Built for Someone Else: Generation, Load, and the Exception in Virginia (Virginia Data Center Series — Analytical Volumes, Version 1.0), concept DOI 10.5281/zenodo.22096613.
Source manifest for Built for Someone Else (concept 22096613) — 125 files including 108 primary source documents, each SHA256-hashed with URL of origin. - Interstate Gas Supply Register: Georgia, Tennessee, Virginia, v1.4
Tennessee, carried as a declared gap in every deposited version until now, is closed.
Interstate Gas Supply Register v1.0 — eleven FERC certificate dockets for interstate natural gas capacity serving Georgia, Tennessee and Virginia, compiled 11–13 September 2026. The unit is the docket, not the state. Companion dataset to What the Record Does Not Say (22754150). - Replication materials: by-right zoning, early vesting and the reach of local reform in Henrico County, Virginia, 2009 to 2026
Version 1.1, September 26, 2026.
Replication materials (v1.1) for a single-case documentary study of Henrico County's June 10, 2025 ordinance ending by-right approval of data centers — what the reform reached and who got a hearing. Supplement, tables, figure data and working notes. Cited from the study's data-availability statement; parent manuscript under journal review. References the Henrico case study (20671031). - IBEW local union membership panel, 2010-2025: replication dataset for two studies of inside electrical construction
Version 1.0, 20 September 2026.
IBEW Local Union Membership Panel, 2010–2025 (v1.0). Annual reported membership for IBEW local unions built from Form LM-2, LM-3 and LM-4 filings. Data + scripts + classification inputs + retrieval logs. Shared replication dataset for Where the Electricians Went (22310705), the measurement paper 22861996 and the sixteen-year research note 22866646. - Virginia Data Center Research & Industry Directory
Version 3.0 incorporates three months of portfolio work since v2.1 (March 22, 2026) and a full June 2026 re-verification of every entry.
Contact directory across Virginia data-center research