State Connections
Explore a state’s data center issues, find states with similar evidence, and assemble a sourced working brief.
Matches reflect shared provisions or tracker classifications, not identical laws. Local actions keep their local scope.
Source statuses are retained as recorded. Existing tracker records have not all been freshly reverified for this view.
Start with Connected states. Review why a state matches, then add it to your working group.
Who is working through similar issues?
Open a state to inspect its evidence. Add states to a potential working group.
Use the map or state selector above to explore each state's published evidence.
West Virginia: inspect the evidence.
Counts are records, not unique projects. Records can overlap across trackers.
Fundamental Data Ridgeline Facility (Tucker County) Record-specific: West Virginia Intermediate Court of Appeals · litigation
The West Virginia Intermediate Court of Appeals dismissed two appeals by Tucker United, the West Virginia Highlands Conservancy, Friends of Blackwater and the Sierra Club challenging the state air quality permits for the Fundamental Data project. The court ruled that the final permit appeal belongs before the state Supreme Court and that it lacked jurisdiction over the draft permit challenge, which it found moot. The groups said no court has yet heard the merits and they plan to refile. Separately, on 13 August 2026 the West Virginia Division of Air Quality determined that Fundamental Data held legal site control when its August 2025 air permit was issued, resolving a procedural challenge raised by community groups in July 2026.
Site control determination 13 August 2026; appeal dismissals reported 28 August 2026
The Register-Herald ↗ Parkersburg News and Sentinel ↗ POWER Magazine ↗Google Buffalo data center campus (Putnam County) Record-specific: Buffalo · announced
Gov. Patrick Morrisey announced on 27 March 2026 that Google had purchased land at 22272 Charleston Road, at the north end of the town of Buffalo near the Kanawha River, and received approval as a multibillion-dollar High Impact Data Center Project; the Department of Commerce received Google's certification application that week. The Putnam County Development Authority said Google plans a data center campus there, and Google launched a project website in June 2026 saying the project is in early planning. On Tuesday 29 September 2026 the Putnam County Commission unanimously passed a resolution asking hyperscale developers to follow county rules as if House Bill 2014 (which removed county approval power) did not exist, including developer-funded water feasibility studies, light and sound mitigation, and payment of 100 percent of water, sewer and power upgrade costs; WCHS reported that the project already has state approval and that Google is working with the county planning commission. Residents' group Putnam United cites 128 evaporative cooling towers in Google's permit filings. Grid connection through American Electric Power (Appalachian Power); Google to fund electrical, water and sewer upgrades Described by state officials as a multibillion-dollar investment; no dollar figure disclosed (WSAZ: exact amount not given) Not disclosed; Google says cooling methods are not finalized
Land purchase and state High Impact approval announced 27 March 2026 (governor's office); Putnam County Commission resolution passed Tuesday 29 September 2026
Charleston Gazette-Mail, 27 March 2026 ↗ WSAZ, 27 March 2026 ↗ WV News, 3 June 2026 ↗ WCHS, 29 September 2026 ↗ WV MetroNews, 30 September 2026 ↗Monarch Compute Campus (Nscale West Virginia campus) Record-specific: · approved
Nscale's flagship West Virginia data center campus, anchored by a reported six-year, approximately $45 billion Anthropic compute agreement covering roughly 460 MW. The West Virginia Governor's office publicized the agreement on 27 August 2026 while describing the figure as reported rather than confirmed. Press reports place the campus in Mason County; the state release does not name a county. Figure is press-reported and not confirmed by either company; the West Virginia Governor's office likewise describes it as a reported agreement, citing Bloomberg. West Virginia approved High Impact Data Center certification for Nscale, announced 3 September 2026, with Phase One described as a projected $69.2 billion investment requiring about 2 GW of power and supporting about 4,375 construction jobs and 645 permanent jobs. Nscale's Form S-1 filed 18 September 2026 identifies the campus as the Monarch Compute Campus in Mason County, West Virginia, an approximately 2,250 acre site acquired with American Intelligence & Power Corporation on 31 March 2026 for total consideration of $792.6 million. The filing expects an initial 2 GW of gross power capacity (1.37 GW of IT load) online by the first half of 2028 and expansion to approximately 8 GW gross planned for 2031. Anthropic Services Agreements signed 25 August 2026 provide for up to approximately $44.6 billion across four tranches of NVIDIA Vera Rubin NVL72 systems; the filing gives no megawatt figure for the Anthropic deployment and states that no binding commitments for the required financings had been obtained. Approximately 460 MW contracted; NVIDIA Vera Rubin systems expected to begin coming online in late 2027 No site capex figure disclosed; anchor compute agreement reported at approximately $45 billion over six years. Site acquired 31 March 2026 for total consideration of $792.6 million per the Form S-1 Initial 2 GW of gross power (1.37 GW of IT load) expected by the first half of 2028 and about 8 GW gross planned for 2031, per the Form S-1; the S-1 gives no MW for the Anthropic deployment, so the 460 MW recorded here remains press-reported
Reported 26 August 2026; Form S-1 filed 18 September 2026
WV Governor ↗ Bloomberg ↗ TechCrunch ↗ West Virginia Office of the Governor ↗ Nscale Ltd Form S-1 (SEC) ↗Penzance Bedington campus Record-specific: Bedington, Berkeley County · delayed
Gov. Patrick Morrisey announced the $4B, 500+ acre Penzance data center near the Potomac River on Feb 26, 2026; more than 300 residents packed a March 20 county commission town hall raising transparency, water, drought, noise and light-pollution concerns amid new state law (HB 2014) stripping local zoning control.
Mar 20 2026
Therealwv ↗Ridgeline gas, solar and data center complex Record-specific: West Virginia Department of Environmental Protection · other
WVDEP Director Laura M. Crowder determined on 13 August 2026 that permit site control requirements are satisfied, clearing a contested question on air permit R13-3713; community appeals remain ongoing The Charleston Gazette-Mail identifies Laura Crowder as director of the WVDEP Division of Air Quality, not WVDEP director; her 13 August 2026 letter accepted a largely redacted July 2024 purchase and sale agreement for about 291 acres, submitted 11 August 2026, as meeting the site-control requirement.
Site-control determination 13 August 2026
POWER Magazine ↗ Charleston Gazette-Mail ↗Silicon Foundry Warwood mixed-use data center Record-specific: Wheeling · MOU approved
Wheeling City Council on Tuesday 15 September 2026 approved a binding memorandum of understanding with Silicon Foundry Energy LLC under which the company will not seek high-impact data center status by staying below 90 MW. State law bars high-impact data centers from TIF districts, so the cap preserves the city's option to bond the tax increment. Residents opposed the project at the meeting Investment not disclosed; city may place the area in a tax increment financing district at its discretion Binding cap below 90 MW, the West Virginia high-impact data center threshold; residents cited earlier statements of 20 to 30 MW and an earlier website reference to 100 MW
MOU approved Tuesday 15 September 2026
WTRF via MSN ↗ WTOV via MSN ↗ Wheeling Intelligencer ↗Starwood Digital Ventures Mason County High Impact Data Center Record-specific: · approved
West Virginia granted the project High Impact Data Center certification, announced by Governor Patrick Morrisey at the West Virginia Business Summit alongside the Nscale certification. The governor's office cites about 1,500 jobs. The governor said infrastructure costs are covered by developers rather than passed to ratepayers The project is dubbed Project Tamarack, about 20 miles north of the Nscale Monarch campus, and would use closed-loop cooling with grid power $12 billion per the West Virginia governor's office 2.16 GW power requirement per the governor's office
Announced 3 September 2026
West Virginia Office of the Governor ↗ West Virginia Watch via Yahoo News ↗Appalachian Power Record-specific: WV · pending
Appalachian Power, Google, and West Virginia manufacturers reached a settlement concerning terms for large-load customers, including potential data centers. The settlement requires Public Service Commission approval and includes minimum site capacity, contract-term, and power-purchase commitments.
Date not recorded
wvpublic.org ↗City of Wheeling (Ohio County) city: City of Wheeling (Ohio County) · approved
Wheeling City Council on Tuesday night, September 15, 2026 approved a binding memorandum of understanding with Silicon Foundry tied to its data center project at the former Centre Foundry site in the Warwood neighborhood. The MOU bars the company from becoming a high-impact data center and, according to Mayor Denny Magruder, commits it to never exceed 90 megawatts; in return the city may create or extend a TIF district. Residents at the meeting continued to oppose the project. The WTOV report does not give the vote count. A group of Warwood residents has separately filed legal action over the project, per The Intelligencer.
2026-09-15
wtov9.com ↗ www.theintelligencer.net ↗Mon Power Record-specific: WV · contested
Mon Power is asking the West Virginia Public Service Commission to approve a $2.4 billion natural gas-fired power plant near its Fort Martin Plant, with operations planned for 2031. It is also requesting a $1.18-per-month customer surcharge to help finance the plant.
Date not recorded
wvmetronews.com ↗Mon Power and Potomac Edison Record-specific: WV · contested
Mon Power and Potomac Edison are seeking approval to build the 1,200-megawatt Maidsville Energy Center, three solar projects, and an associated Generation Projects Surcharge. The initial surcharge is estimated to increase residential rates by $1.18 per month, or 0.9%.
Date not recorded
www.dominionpost.com ↗Mon Power and Potomac Edison Record-specific: WV · contested
Mon Power and Potomac Edison applied to construct a $2.48 billion, 1,200-megawatt combined-cycle natural gas plant at the Fort Martin site in Monongalia County, along with 70 megawatts of solar generation. The utilities say the project is needed to address an anticipated capacity shortfall beginning in 2029.
Date not recorded
www.wvnews.com ↗Mon Power; Potomac Edison Record-specific: WV · pending
Mon Power and Potomac Edison submitted an Integrated Resource Plan to the Public Service Commission of West Virginia covering how they will provide reliable, cost-effective power over the next decade. The preferred plan includes keeping the Fort Martin and Harrison power stations operational, exploring a 1,200-megawatt natural gas combined-cycle unit targeted for operation around 2031, adding 70 megawatts of utility-scale solar in 2028, and using short-term power purchases until new resources are online.
2025-10-01
www.firstenergycorp.com ↗Mon Power; Potomac Edison Record-specific: WV · contested
Mon Power and Potomac Edison filed an application with the Public Service Commission of West Virginia to build a 1,200-megawatt natural-gas-fired power plant adjacent to the Fort Martin Power Station, along with three solar projects. The proposed $2.48 billion project is intended largely to meet future electricity demand from data centers.
Date not recorded
www.wvnews.com ↗Monongahela Power and Potomac Edison Record-specific: WV · pending
Monongahela Power and Potomac Edison asked the West Virginia Public Service Commission for permission to build a 1.2-GW gas-fired power plant in Maidsville, West Virginia. The proposed $2.5 billion project is included in the utilities’ integrated resource plan and is intended to support growing demand, including potential data-center demand.
Date not recorded
www.utilitydive.com ↗Follow the issue to the utility and the customer.
Named organizations come from explicit record fields. Their presence is not confirmation of a serving-utility relationship, service availability, or customer eligibility.
Named parties in this state's evidence
Start from your position.
Screen an individual location ↗Address-level utility verification and service agreements belong in the site screen. Private account data and individual household identities are not part of this public dataset.
Regional grid context and rules
Open the complete grid operator watchlist ↗Explore generation and interconnection queues ↗ · Explore scarcity and market constraints ↗
See what your selected states have in common.
We bring together the shared issues and source records for the states you choose.
States appear side by side. Compare each topic, then open a cell for sources.
Add your own notes Optional
Notes are included when you open or save the comparison. Save a copy to keep them after leaving this page.
Sharing and data options
The link includes your states and issue filter. It does not include private notes. Source data downloads as JSON.
Coverage, sources and how states are connected
All 50 states are selectable. A connection requires the same documented policy mechanism or the same structured tracker classification and status. The map is a discovery tool, not a legal-equivalence score, a project-risk ranking, or a complete census. No match means no matching evidence in this view.
Existing tracker publications supply most records. Their source status and date are retained; a page load is not a new source verification. Proposed, failed, enacted and reversed records remain distinct. Explicitly unverified or pending-review rows are excluded. Narrative and status can disagree in the underlying publication; inspect both before treating a restriction as active. No state-wide effect is inferred from a local action.
Data is read from the current tracker files and published overlays. Source changes invalidate the server's cached connections. Policy mechanisms use a separately reviewed evidence set. Generation queues and broad company commitments are not assigned to a data center or customer. Federal records and records without an explicit state are not assigned to a state by inference.
Download state evidence JSON · SAVRN methodology
Underlying dataset credits
- 6abc Philadelphia
- AEP Ohio Transmission Company (filed with Ohio Power Siting Board)
- AI GridWatch moratorium tracker, CC BY 4.0 (aigridwatch.com)
- Alabama Reflector
- Alaska Beacon
- American Transmission Company LLC (filed with PSC of Wisconsin)
- Americus Times-Recorder
- Arizona Mirror
- Arkansas Advocate
- Axios Pro Energy
- Bisnow
- Bisnow National
- Bradenton Herald
- CNBC Technology
- Cardinal News VA
- Central Florida Public Media
- Chesterfield County public permit records
- Chicago Construction News
- City of Atlanta public permit records
- City of Austin issued construction permits open data
- City of Buckeye public permit records
- City of Chandler public permit records
- City of Charlotte public permit records
- City of Chicago building permits open data
- City of Fort Worth public permit records
- City of Goodyear public permit records
- City of Hillsboro public permit records
- City of Mesa building permits open data
- City of Mesa public permit records
- City of Minneapolis construction permits (CCS) open data
- City of Papillion public permit records
- City of Phoenix public permit records
- City of Red Oak public permit records
- City of Reno public permit records
- City of San Antonio public permit records
- City of Statesboro, Georgia
- City of Temple, Texas
- Clearfield City Council (Utah Public Notice Website)
- Colorado Newsline
- Colorado Public Radio
- Congress.gov (Library of Congress, public domain)
- ConstructConnect News
- Construction Dive
- CourtListener DataCenter Dockets
- CourtListener Opinions
- Data Center Dynamics
- Data Center Dynamics news
- DataCenterTracker.org, CC BY 4.0
- Dominion Energy Virginia
- EIN News
- East Bay Insiders Newsletter
- Energy Central
- FOX19 | Cincinnati
- FOX5 Vegas
- FOX6 News Milwaukee
- Facilities Dive
- Fairfax County public permit records
- Florida Phoenix
- Georgia Department of Community Affairs
- Georgia EPD air permit records
- Georgia Recorder
- GovTech
- Greensboro News and Record
- Grist
- Idaho Capital Sun
- Illinois EPA air permit records
- Indiana Capital Chronicle
- Indiana Department of Environmental Management
- Indiana IDEM air permit records
- InkFreeNews.com
- Iowa Capital Dispatch
- Iowa DNR air permit records
- KERA News
- KEYC News Now
- KGW
- KRON4
- Kansas City MO city issued permits open data
- Kansas Reflector
- Kentucky Lantern
- Law360
- Law360 Energy
- LegiScan (legiscan.com) and the state legislature
- Lehigh Valley Planning Commission
- Local News Matters
- Loudoun County public permit records
- Loudoun Times-Mirror
- Louisiana DEQ air permit records
- Louisiana Illuminator
- Maine Morning Star
- Maricopa County Air Quality Department air permit records
- Maricopa County public permit records
- Maryland Matters
- Mecklenburg County public permit records
- Michigan Advance
- Mid Bay News
- Missouri Independent
- Montana Free Press
- NBC Bay Area
- NBC4 Washington
- NC Newsline
- Native News Online
- Nebraska Examiner
- Nevada Current
- Nevada NDEP air permit records
- New Hampshire Bulletin
- New Mexico Environment Department
- North Carolina DEQ Division of Air Quality air permit records
- North Dakota Department of Environmental Quality
- North Dakota Monitor
- Ohio Capital Journal
- Ohio EPA air permit records
- Oklahoma DEQ air permit records
- Oklahoma Voice
- OpenStates v3 (openstates.org), CC BY 4.0
- Oregon Capital Chronicle
- Orlando Sentinel
- Pennsylvania Capital-Star
- Pennsylvania Department of Environmental Protection
- Pennsylvania Office of Consumer Advocate (filed with PA PUC)
- Pioneer Press
- Prince William County public permit records
- Public Service Commission of Wisconsin
- Public record (Legistar Web API, Granicus)
- Rhode Island Current
- Route Fifty
- SEC EDGAR company submissions, public domain
- SEC EDGAR full-text search, public domain
- Searchlight New Mexico
- Smithfield Township, Monroe County, PA
- Source New Mexico
- South Carolina Department of Environmental Services
- South Dakota Searchlight
- Springfield Daily Citizen
- Stafford County public permit records
- Statesman Journal
- Strisker data center notes
- Tennessee Lookout
- Texas Commission on Environmental Quality
- Texas TCEQ air permit records
- The Baltimore Banner
- The Current (GA)
- The Detroit News
- The Hill Energy
- The North State Journal
- The Pantagraph
- The Real Deal
- The Register
- The Texas Tribune
- The Verge
- Times-Standard
- Town of Culpeper public permit records
- Tuscaloosa Thread
- U.S. EPA ECHO
- Union-Bulletin
- Uprise RI
- Utah Division of Air Quality
- Utah Division of Air Quality air permit records
- Utah News Dispatch
- Utah Public Radio
- Utility Dive
- Virginia Business
- Virginia DEQ air permit records
- Virginia Electric and Power Company (filed with Virginia SCC)
- Virginia Mercury
- Visalia Times-Delta
- WBUR
- WCPO 9 Cincinnati
- WGLT
- WHEC.com
- WJON
- WKYT
- WLOS
- WLUK
- WPBF
- WQCS
- WRAL (NC)
- WUNC News
- WVPE
- Washington County public permit records
- Washington Ecology air permit records
- Washington State SEPA Register public permit records
- Washington State Standard
- Washoe County public permit records
- Wausau Pilot & Review
- West Virginia Watch
- Winston-Salem Journal
- Wisconsin Department of Natural Resources
- Wisconsin Examiner
- Yale Daily News
- citybiz
- contracosta.news
- ictnews.org
- indianapublicradio.org
- inkfreenews.com
- lex18.com
- mountaintimesoregon.com
- newmedia-wi.com
- newscentermaine.com
- thegazette.com
- tuscaloosathread.com
- wcpo.com
- www.cities929.com
SAVRN Policy Connections
How state policies connect.
Find shared policy mechanisms, compare the differences, and assemble a framework from documented state provisions.
An initial evidence set, not an exhaustive survey. A missing relationship means not documented here, never no policy. Source review verifies the cited instrument, not every later amendment or implementing action. Sources reviewed 3 October 2026.
Shared goals. Different requirements.
Each number opens the provisions connecting a state to a policy family. States can belong to several groups. A shared family is not proof of identical law.
Find states sharing a combination of policies
Choose several mechanisms to find their intersection, or include states with any selected mechanism. These matches use documented records only.
| State | Project readiness | Cost responsibility | Grid flexibility | Water safeguards | Reporting & oversight | Energy & emissions | Local authority | Environmental review |
|---|---|---|---|---|---|---|---|---|
| AlabamaNot yet documented | – | – | – | – | – | – | – | – |
| AlaskaNot yet documented | – | – | – | – | – | – | – | – |
| ArizonaNot yet documented | – | – | – | – | – | – | – | – |
| ArkansasNot yet documented | – | – | – | – | – | – | – | – |
| CaliforniaNot yet documented | – | – | – | – | – | – | – | – |
| ColoradoNot yet documented | – | – | – | – | – | – | – | – |
| ConnecticutNot yet documented | – | – | – | – | – | – | – | – |
| DelawareNot yet documented | – | – | – | – | – | – | – | – |
| FloridaNot yet documented | – | – | – | – | – | – | – | – |
| Georgia | – | 2 | – | – | – | – | – | – |
| HawaiiNot yet documented | – | – | – | – | – | – | – | – |
| IdahoNot yet documented | – | – | – | – | – | – | – | – |
| IllinoisNot yet documented | – | – | – | – | – | – | – | – |
| Indiana | – | 3 | – | – | 1 | – | – | – |
| IowaNot yet documented | – | – | – | – | – | – | – | – |
| KansasNot yet documented | – | – | – | – | – | – | – | – |
| KentuckyNot yet documented | – | – | – | – | – | – | – | – |
| LouisianaNot yet documented | – | – | – | – | – | – | – | – |
| MaineNot yet documented | – | – | – | – | – | – | – | – |
| MarylandNot yet documented | – | – | – | – | – | – | – | – |
| MassachusettsNot yet documented | – | – | – | – | – | – | – | – |
| MichiganNot yet documented | – | – | – | – | – | – | – | – |
| Minnesota | – | 2 | – | 1 | – | 1 | – | – |
| MississippiNot yet documented | – | – | – | – | – | – | – | – |
| MissouriNot yet documented | – | – | – | – | – | – | – | – |
| MontanaNot yet documented | – | – | – | – | – | – | – | – |
| NebraskaNot yet documented | – | – | – | – | – | – | – | – |
| NevadaNot yet documented | – | – | – | – | – | – | – | – |
| New HampshireNot yet documented | – | – | – | – | – | – | – | – |
| New JerseyNot yet documented | – | – | – | – | – | – | – | – |
| New MexicoNot yet documented | – | – | – | – | – | – | – | – |
| New York | – | – | – | 1 | – | – | – | 2 |
| North CarolinaNot yet documented | – | – | – | – | – | – | – | – |
| North DakotaNot yet documented | – | – | – | – | – | – | – | – |
| Ohio | – | 1 | – | – | – | – | – | – |
| OklahomaNot yet documented | – | – | – | – | – | – | – | – |
| Oregon | – | 2 | – | – | 1 | 1 | – | – |
| PennsylvaniaNot yet documented | – | – | – | – | – | – | – | – |
| Rhode IslandNot yet documented | – | – | – | – | – | – | – | – |
| South CarolinaNot yet documented | – | – | – | – | – | – | – | – |
| South Dakota | – | 2 | – | 1 | 1 | – | 1 | – |
| TennesseeNot yet documented | – | – | – | – | – | – | – | – |
| Texas | 1 | 1 | 1 | – | – | 1 | – | – |
| UtahNot yet documented | – | – | – | – | – | – | – | – |
| VermontNot yet documented | – | – | – | – | – | – | – | – |
| Virginia | – | – | – | – | 2 | – | – | – |
| WashingtonNot yet documented | – | – | – | – | – | – | – | – |
| West VirginiaNot yet documented | – | – | – | – | – | – | – | – |
| WisconsinNot yet documented | – | – | – | – | – | – | – | – |
| WyomingNot yet documented | – | – | – | – | – | – | – | – |
Choose a mechanism to see states connected by that specific policy tool.
Compare two states.
Compare documented mechanisms, then inspect each provision's scope and status. Unrecorded mechanisms remain unknown.
Inspect the provision, not just the category.
All 29 documented provisions. Open a record for its source, scope, and difference from similar tools.
Texas Verify the proposed site Documented in cited instrument
Interconnection standards must include a way to demonstrate a legal interest in the proposed location.
- Shared mechanism
- Evidence of site control
- Scope
- ERCOT large-load interconnection; applicability and exceptions in the statute.
- Important difference
- Evidence of site control does not establish that all permits or financing are secured.
- Source location
- Section 37.0561(g)
Statutory text · Source reviewed 2026-10-03
Texas Back transmission commitments Documented in cited instrument
Standards must set financial commitments supporting transmission infrastructure for covered loads.
- Shared mechanism
- Financial security
- Scope
- ERCOT large-load interconnection; applicability and exceptions in the statute.
- Important difference
- Permitted security forms and release rules depend on implementation; not a minimum energy bill.
- Source location
- Section 37.0561(h)-(j)
Statutory text · Source reviewed 2026-10-03
Texas Define emergency response Documented in cited instrument
Covered backup-equipped loads may be directed to deploy backup generation or curtail after the specified market-service sequence.
- Shared mechanism
- Emergency response
- Scope
- ERCOT large-load interconnection; applicability and exceptions in the statute.
- Important difference
- An emergency mechanism, not a general voluntary demand-response tariff.
- Source location
- Section 37.0561(e)
Statutory text · Source reviewed 2026-10-03
Texas Retain emissions limits Documented in cited instrument
Emergency direction does not authorize violation of emissions or environmental requirements.
- Shared mechanism
- Emissions safeguards
- Scope
- ERCOT large-load interconnection; applicability and exceptions in the statute.
- Important difference
- Backup generation remains constrained by applicable environmental rules.
- Source location
- Section 37.0561(e)(1)
Statutory text · Source reviewed 2026-10-03
Minnesota Assign attributable utility costs Documented in cited instrument
Commission review of very-large-customer service terms must address attributable costs and protection of other customers.
- Shared mechanism
- Attributable-cost allocation
- Scope
- Scope varies by section: data-center water provisions, public-utility service, and optional clean-energy contracts.
- Important difference
- A regulatory framework with customer-class and agreement decisions, not a uniform minimum billing percentage.
- Source location
- Section 9, subdivision 2
Session law · Source reviewed 2026-10-03
Minnesota Protect against stranded costs Documented in cited instrument
Tariff or agreement review must include protections against other customers paying stranded service costs.
- Shared mechanism
- Departure / reduced-load protection
- Scope
- Scope varies by section: data-center water provisions, public-utility service, and optional clean-energy contracts.
- Important difference
- Existing-service exceptions appear in subdivision 3.
- Source location
- Section 9, subdivision 2(3)
Session law · Source reviewed 2026-10-03
Minnesota Evaluate consumptive water demand Documented in cited instrument
Preapplication review links covered consumptive demand and permit needs to site-specific water availability.
- Shared mechanism
- Water-supply review
- Scope
- Scope varies by section: data-center water provisions, public-utility service, and optional clean-energy contracts.
- Important difference
- Facility definition and water-use/permit conditions apply together; not all withdrawals trigger this review.
- Source location
- Sections 3-4
Session law · Source reviewed 2026-10-03
Minnesota Offer optional clean-energy service Documented in cited instrument
Utilities must offer a clean-energy and capacity tariff with participating customers paying proportional resource costs.
- Shared mechanism
- Clean-energy service terms
- Scope
- Scope varies by section: data-center water provisions, public-utility service, and optional clean-energy contracts.
- Important difference
- Customer participation is optional; do not classify it as a universal clean-energy purchase mandate.
- Source location
- Section 10
Session law · Source reviewed 2026-10-03
South Dakota Recover attributable electricity costs Documented in cited instrument
Separate service terms must recover costs fairly attributable to the data center.
- Shared mechanism
- Attributable-cost allocation
- Scope
- Statutorily defined data centers; electricity providers, water providers, and local governments.
- Important difference
- Applies through provider terms rather than a published statewide minimum billing percentage.
- Source location
- Section 3
Session law · Source reviewed 2026-10-03
South Dakota Address departure and reduced load Documented in cited instrument
Cost responsibility includes costs incurred if the customer departs or materially reduces load.
- Shared mechanism
- Departure / reduced-load protection
- Scope
- Statutorily defined data centers; electricity providers, water providers, and local governments.
- Important difference
- The law states cost responsibility; it does not supply a universal exit-fee formula.
- Source location
- Section 3
Session law · Source reviewed 2026-10-03
South Dakota Obtain local supply determinations Documented in cited instrument
Water providers assess compatibility, with board review and allocation limits protecting priority uses.
- Shared mechanism
- Water-supply review
- Scope
- Statutorily defined data centers; electricity providers, water providers, and local governments.
- Important difference
- Local supply determinations are distinct from the Minnesota consumptive-use permit review.
- Source location
- Section 5
Session law · Source reviewed 2026-10-03
South Dakota Publish water-use data Documented in cited instrument
Operators report usage to the board, which makes usage data available to the public.
- Shared mechanism
- Water-use reporting
- Scope
- Statutorily defined data centers; electricity providers, water providers, and local governments.
- Important difference
- Operator reporting differs from Virginia supplier category reporting.
- Source location
- Section 6
Session law · Source reviewed 2026-10-03
Ohio Address underused infrastructure risk Documented in cited instrument
PUCO adopted a settlement aimed at protecting other customers from cost shifting due to underused data-center investments.
- Shared mechanism
- Attributable-cost allocation
- Scope
- AEP Ohio data-center tariff proceeding; not a tariff for every Ohio utility.
- Important difference
- The cited announcement directs tariff filing; consult the filed tariff for binding customer terms.
- Source location
- Decision announcement, case background
Commission decision announcement · Source reviewed 2026-10-03
Indiana Set minimum billing obligations Documented in cited instrument
The approved settlement establishes minimum billing-demand and charge provisions for covered large loads.
- Shared mechanism
- Minimum payment commitments
- Scope
- Indiana Michigan Power Tariff I.P., Indiana jurisdiction; covered large-load customers.
- Important difference
- The approved settlement differs from the original utility proposal; I&M territory only.
- Source location
- Order pp. 32-35 and ordering paragraphs p. 49
Commission order · Source reviewed 2026-10-03
Indiana Address early termination Documented in cited instrument
The approved settlement contains contract termination protections for covered large-load service.
- Shared mechanism
- Departure / reduced-load protection
- Scope
- Indiana Michigan Power Tariff I.P., Indiana jurisdiction; covered large-load customers.
- Important difference
- Customer-specific conditions and the settlement govern; not statewide terms for every provider.
- Source location
- Settlement agreement; order approval pp. 49-50
Commission order · Source reviewed 2026-10-03
Indiana Require collateral arrangements Documented in cited instrument
The approved settlement includes financial-security terms for covered large-load customers.
- Shared mechanism
- Financial security
- Scope
- Indiana Michigan Power Tariff I.P., Indiana jurisdiction; covered large-load customers.
- Important difference
- Collateral and exceptions depend on tariff eligibility and customer circumstances.
- Source location
- Settlement agreement; order approval pp. 49-50
Commission order · Source reviewed 2026-10-03
Indiana Report large-load developments Documented in cited instrument
The order addresses recurring reports and protection of confidential information.
- Shared mechanism
- Regulatory reporting
- Scope
- Indiana Michigan Power Tariff I.P., Indiana jurisdiction; covered large-load customers.
- Important difference
- Regulator access is not equivalent to public disclosure of all reported data.
- Source location
- Order p. 49
Commission order · Source reviewed 2026-10-03
Georgia Allocate infrastructure costs Documented in cited instrument
The PSC approved additional service terms addressing site and upstream power-system costs.
- Shared mechanism
- Attributable-cost allocation
- Scope
- Georgia Power covered new large-load customers; not every Georgia utility.
- Important difference
- Applies to the specified Georgia Power customer category; implementation is contract-specific.
- Source location
- Commission announcement p. 1
Commission decision announcement · Source reviewed 2026-10-03
Georgia Allow longer contracts and minimum bills Documented in cited instrument
The approved rule allows longer contracts and minimum billing for covered high-load customers.
- Shared mechanism
- Minimum payment commitments
- Scope
- Georgia Power covered new large-load customers; not every Georgia utility.
- Important difference
- Authority to impose terms is not a universal mandatory billing percentage.
- Source location
- Commission announcement p. 1
Commission decision announcement · Source reviewed 2026-10-03
Oregon Create a separate service class Documented in cited instrument
The act calls for tariffs assigning covered service costs to large energy use facilities and mitigating cost shifts.
- Shared mechanism
- Attributable-cost allocation
- Scope
- Covered large energy use facilities served by electric companies; tariff and contract provisions have distinct applicability.
- Important difference
- Separate tariff approval and transition provisions matter; a statute is not itself a completed tariff.
- Source location
- Section 2
Enrolled text; Chapter 323 confirmed · Source reviewed 2026-10-03
Oregon Require contractual minimum payments Documented in cited instrument
Covered service contracts must include a minimum payment amount or percentage determined by the commission.
- Shared mechanism
- Minimum payment commitments
- Scope
- Covered large energy use facilities served by electric companies; tariff and contract provisions have distinct applicability.
- Important difference
- The law leaves the amount or percentage to the commission.
- Source location
- Sections 5-6
Enrolled text; Chapter 323 confirmed · Source reviewed 2026-10-03
Oregon Consider clean-energy compatibility Documented in cited instrument
Commission tariff review must consider effects on clean-energy targets and compatible resource procurement.
- Shared mechanism
- Clean-energy service terms
- Scope
- Covered large energy use facilities served by electric companies; tariff and contract provisions have distinct applicability.
- Important difference
- A tariff-review criterion differs from Minnesota optional clean-energy procurement.
- Source location
- Section 2(3)
Enrolled text; Chapter 323 confirmed · Source reviewed 2026-10-03
Oregon Report load trends to lawmakers Documented in cited instrument
The commission must report on large-load trends and implications while protecting proprietary information.
- Shared mechanism
- Regulatory reporting
- Scope
- Covered large energy use facilities served by electric companies; tariff and contract provisions have distinct applicability.
- Important difference
- A legislative reporting mechanism, not disclosure of every customer contract.
- Source location
- Section 7
Enrolled text; Chapter 323 confirmed · Source reviewed 2026-10-03
Virginia Separate potable and reclaimed volumes Enacted, future effective
The future-effective code adds supplier reporting by customer category, separating potable and reclaimed water.
- Shared mechanism
- Water-use reporting
- Scope
- Registered water users supplying water offsite; categorized reporting, not universal facility-level public disclosure.
- Important difference
- Monthly data can be replaced by quarterly totals where unavailable; facility-specific disclosure is not established here.
- Effective date in source
- 2027-01-01
- Source location
- Subsection C, version effective January 1, 2027
Enacted, future effective · Source reviewed 2026-10-03
Virginia Connect electricity, water and generators Official report listed
The official report listing describes a cross-resource account of service agreements, water usage and generator permits.
- Shared mechanism
- Regulatory reporting
- Scope
- Report description covers utility agreements, water use and generator permitting; underlying report data not ingested.
- Important difference
- This confirms the report description, not completeness or accuracy of individual facility records.
- Source location
- RD637 executive summary
Official report listing · Source reviewed 2026-10-03
New York Assess cumulative development impacts Documented in cited instrument
The order directs a generic environmental impact statement for covered data-center development.
- Shared mechanism
- Environmental assessment
- Scope
- Covered data centers and discretionary DEC permits; definition and exemptions must be checked.
- Important difference
- A statewide review process differs from a project-specific approval.
- Source location
- Order section 1
Executive order · Source reviewed 2026-10-03
New York Link permit restraint to review Documented in cited instrument
The order holds covered discretionary DEC permits in abeyance subject to its scope and exclusions.
- Shared mechanism
- Interim permit restraint
- Scope
- Covered data centers and discretionary DEC permits; definition and exemptions must be checked.
- Important difference
- Applies to covered DEC applications not determined complete before the order; local-government permits are excluded. Not proof that a named project stopped.
- Source location
- Order section 1 and definition in section 6
Executive order · Source reviewed 2026-10-03
New York Review water-withdrawal rules Agency review directed
DEC must assess whether water-withdrawal rules, reporting or guidance should change for large users.
- Shared mechanism
- Water-supply review
- Scope
- Covered data centers and discretionary DEC permits; definition and exemptions must be checked.
- Important difference
- Agency review direction, not an enacted new facility-level water cap.
- Source location
- Order section 5
Executive order · Source reviewed 2026-10-03
SAVRN synthesis · proposed framework
Combine provisions into a coherent system.
Select state provisions above. The builder organizes their purposes, surfaces dependencies and tradeoffs, and preserves the source of every selection. It does not turn selected provisions into enacted law or establish which policy works best.
How relationships and coverage are defined
One relationship joins a state, an instrument, and a specific provision to a normalized mechanism. States are connected when documented provisions share a mechanism. Groups overlap; the system does not infer legal equivalence, adoption by neighboring states, policy effectiveness, or an absence of policy from missing records.
The matrix counts provisions in this dataset, not laws or affected projects. Comparison and framework selections can be shared by URL. Downloads preserve scope, source location, status, and review date. Future-effective provisions and agency review directions keep their labels.
The initial taxonomy was informed by Ahmed Saeed and Josiah Hester's Governing Datacenter Growth and research paper. SAVRN's source-backed comparison extends beyond the study. Framework purposes, dependencies, and tradeoff prompts are SAVRN analysis, not measured outcomes or statements of law.
Explore the full trackers
Go deeper into a topic. Each tracker opens in a new tab, keeping your state comparison here.
Moratorium tracker ↗Local restrictions and pauses
Delay watchlist ↗Projects and schedule risks
Grid operator watchlist ↗Utility rules and grid access
Water tracker ↗Water supply and cooling
Permits and development ↗Permits, facilities and power development
Capital Atlas ↗Capital and project activityScarcity tracker ↗Power and market constraints