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.
Ohio: inspect the evidence.
Counts are records, not unique projects. Records can overlap across trackers.
Address underused infrastructure risk AEP Ohio data-center tariff proceeding; not a tariff for every Ohio utility. · Documented in cited instrument
PUCO adopted a settlement aimed at protecting other customers from cost shifting due to underused data-center investments. The cited announcement directs tariff filing; consult the filed tariff for binding customer terms.
Date not recorded
PUCO decision announcement, case 24-508-EL-ATA ↗AWS 18-building campus, Trenton annexation of 601 acres from Madison and St. Clair townships Record-specific: City of Trenton and Butler County Board of Commissioners · withdrawn
Trenton, Duke Energy Ohio and Kentucky, Watson Gravel Inc. and two landowners filed an expedited annexation petition on 27 July 2026 to bring 601 acres into the city for a proposed 18-building AWS data center. Madison Township trustees voted unanimously on 24 August 2026 to reject the petition and St. Clair Township rejected it the next day, despite Amazon offering each township $5 million. On 14 September 2026 the petitioners withdrew the petition hours before a Butler County commissioners hearing, reserving the right to refile after Trenton voters decide a 3 November 2026 charter amendment banning data centers above 25 MW. Butler County's six-month data center moratorium for Madison and five other townships runs to December 2026. The annexation petitioners asked for postponement until after 10 November 2026.
Annexation petition withdrawn 14 September 2026; withdrawal acknowledged by county commissioners 15 September 2026; $5 billion value Reported by the Cincinnati Business Courier
Journal-News ↗ WVXU (withdrawal) ↗ WVXU (township votes) ↗ Local 12 (Cincinnati Business Courier) ↗ Journal-News ↗AWS Cosgray campus fuel cell facility (Hilliard permit appeal) Record-specific: Hilliard · other
The City of Hilliard withdrew its appeal, filed in 2025 with the Environmental Review Appeals Commission, of an Ohio EPA permit for a natural-gas-powered fuel cell facility at the Amazon data center off Scioto Darby Road. City Council President Emily Cole said the withdrawal is not an endorsement and that state law gives local communities limited authority over such facilities. The city had appealed in November 2025 after AWS withdrew its local application for 228 fuel cells, arguing state approval was sufficient because AEP Ohio could not supply the load for several years. The city plans air quality testing once the fuel cells operate.
Appeal withdrawn Tuesday 15 September 2026; reported 16 and 17 September 2026
WOSU ↗ WCMH via MSN ↗AWS Sidney data center campus (Millcreek Road) Record-specific: Sidney · site work underway
Demolition began on Tuesday 4 August 2026 at the historic Joslin Barn to make way for the Amazon data center on the north side of Millcreek Road, which Sidney leaders approved in fall 2025. The Dayton Daily News reported that the city granted a 30-year Community Reinvestment Area 100% real property tax exemption per qualifying building, with $46 million in PILOT payments over 14 years plus a $4 million upfront payment split between the city and schools, 75 jobs by 31 December 2030 and up to $8 million from AWS for road and utility improvements. Residents have circulated recall and transparency petitions and the city allocated more money for related litigation $3 billion investment per the city agreement as summarized by the Dayton Daily News MW not disclosed
Demolition began Tuesday 4 August 2026; incentive terms reported 28 August 2026
WDTN via Yahoo ↗ Dayton Daily News ↗AWS Wilmington data center emergency rezoning (Cosler Farm) Record-specific: City of Wilmington · litigation
On Thursday 3 September 2026 the Wilmington City Council passed ordinances as emergency measures rezoning the 471-acre Cosler Farm parcel to light industrial for a proposed $4 billion Amazon Web Services data center; emergency ordinances take effect immediately and are not subject to referendum under Ohio law. The vote was a redo after a federal judge found the city had violated open meeting rules. Resident Rachel Mary Brooks sued the city in Clinton County Common Pleas Court, arguing the declared emergency is illusory and was used to prevent a referendum; at a temporary restraining order hearing on 4 September the city agreed not to act on the rezoning for a week and not to interfere with signature gathering, and the local judge recused himself. WLWT reported that the case was set for trial at 1 p.m. on Friday 2 October 2026, and that Clinton County Citizens for Responsible Development announced on 1 October that it had gathered enough signatures for a referendum, whose fate depends on the court. No ruling was found.
Emergency rezoning 3 September 2026; suit filed by 4 September 2026; trial set for 2 October 2026, outcome not yet reported
FOX19 ↗ WLWT ↗ WCPO ↗ WLWT via MSN ↗AWS data center campus, Scioto Darby Road (Hilliard area) with AEP Ohio fuel cell plant Record-specific: Hilliard area (Norwich Township) · under_construction
On 15 September 2026 the City of Hilliard withdrew its appeal to the Ohio Environmental Review Appeals Commission of the Ohio EPA air permit for the 72.9 MW fuel cell facility serving the AWS campus on Scioto Darby Road. The city said outside counsel found narrow legal grounds and noted the Ohio Power Siting Board has exclusive jurisdiction over generation above 50 MW; AEP Ohio had withdrawn its local zoning application in October 2025. Hilliard plans post-startup air quality testing 72.9 MW AEP Ohio fuel cell facility using 228 Bloom Energy units, supplied by natural gas No campus investment figure in the fetched coverage Data center MW not disclosed; on-site fuel cell facility is 72.9 MW
Appeal withdrawn 15 September 2026
The Columbus Dispatch via MSN ↗ WOSU Public Media ↗Aligned Data Centers Pataskala campus Record-specific: City of Pataskala · rejected
Pataskala City Council voted at its 25 August 2026 meeting to accept the Planning and Zoning Commission's recommendation and deny the site plan for a 200 MW, three-building campus. Council President Brandon Galik cited unresolved power questions and incomplete design. A citizen petition carrying more than 500 signatures places a potential data center ban before Pataskala voters at the November 2026 election. Separately, the Pataskala City Council voted on 3 August 2026 to place a citizen-petitioned charter amendment banning data centers larger than 25 megawatts on the 3 November 2026 ballot, and the Licking County Board of Elections certified it on 17 August 2026.
Denied 25 August 2026; reported 26 August 2026
ABC 6 Columbus ↗ NBC4 WCMH ↗ The Reporting Project ↗ The Reporting Project (18 August 2026) ↗ The Reporting Project (6 August 2026) ↗Alignment Engine data hall (Chilpaco division, former US Paper Mill, Eastern Avenue and Canal Street) Record-specific: Chillicothe · proposed
North Canton-based Alignment Engine plans a data hall and computing-device manufacturing operation inside an existing mill building on about 6.5 acres of the roughly 490-acre former US Paper Mill campus in Chillicothe. Company slides released after September 2026 council meetings list 89 MW anticipated use at capacity, reuse of the mill's permitted wells, Paint Creek intake and on-site wastewater treatment, about 240 permanent jobs and no tax abatement request. Chillicothe City Council struck down its 60-day moratorium 8-1 on 14 September 2026 (at-risk row 208). Volato Group completed its merger with Alignment Engine, valued at about $500 million, with Chris Ensey named CEO effective 11 September 2026; the merger materials describe Alignment Engine's Ohio powered industrial campus as having about 154 MW available and a path to at least 480 MW. Existing mill power infrastructure; company says the data hall will draw no more power or water than the former mill Company slide estimates about $500 million in value (a company projection used in its tax chart, not a stated build budget) 89 MW anticipated data hall electrical use at capacity per company slides (current idle-mill demand 9 MW, legacy mill 95 MW); merger materials describe about 154 MW available today and a path to at least 480 MW; the company says 480 MW is not planned now
Community presentation early September 2026; moratorium repealed 14 September 2026; developer statements reported 21 September 2026
Hopewell Heritage Headlines, September 2026 ↗ WCHI Easy 1350, 21 September 2026 ↗ Pulse 2.0, 27 August 2026 ↗ Seeking Alpha via MSN, 17 September 2026 ↗Amazon Sunbury campus Record-specific: Sunbury, Delaware County · moratorium
Sunbury has a data-center development moratorium in place until Jan 31 (2027); residents fear council could approve the $2B Amazon facility once it expires and are collecting signatures for a fall ballot charter amendment to cap data centers at 25MW peak load.
Jun 26 2026
Dispatch ↗Amazon data center, Faircrest Street SW (Perry Township and Canton JEDD) Record-specific: Perry Township · under_construction
A 240 MW Amazon data center developed by Panattoni is under construction south of Faircrest Street SW within a Joint Economic Development District between Perry Township and Canton, and could become the largest taxpayer in Stark County. Four residents sued Perry Township trustees, Stark County, the City of Canton, the Perry school board and the developers in Stark County Common Pleas Court, alleging the October 2025 noise ordinance and a March 2026 resolution consenting to a tax exemption agreement were adopted improperly, including under Ohio's Open Meetings Act. Panattoni said it has followed all applicable requirements. Not disclosed 240 MW as reported by The Canton Repository
Under construction as of July 2026; residents' lawsuit reported 4 September 2026
The Canton Repository via MSN, 4 September 2026 ↗ The Canton Repository via AOL, 15 July 2026 ↗Archbold data center moratorium Record-specific: Archbold · moratorium
Archbold, Ohio, enacted a local data center moratorium or ban, recorded in SAVRN's moratorium tracker as dated April 2026. Emergency resolution, 6-month moratorium on data centers, advanced manufacturing, and technology storage facilities. Passed 5-0. Extended another 6 months to ~April 2027 due to uncertainty around HB 646 and state study commission. The measure has a stated duration whose end date is not recorded.
Enacted April 2026
northwestsignal.net ↗Ardent/TAC data center rezoning referendum (Wilmington) Record-specific: City of Wilmington · other
Wilmington Residents for Responsible Development secured a referendum on the city's rezoning of four parcels from rural residential to light industrial for the Ardent/TAC data center project, which is separate from the Amazon Web Services project. Organizer Jessica Sharp said the group turned in 1,529 signatures in about 25 days. WCPO reported on 17 April 2026 that the measure will be on the November 2026 ballot for Wilmington voters; the mayor said the matter was under legal review.
Referendum qualified, reported 17 April 2026; vote at the November 2026 general election; single outlet
WCPO ↗Ashville EdgeConneX campus referendum Record-specific: Village of Ashville, Pickaway County · litigation
Ashville village council adopted a preliminary agreement with EdgeConneX in April 2026 as an emergency resolution, making it effective immediately and waiving the standard 30-day period before a referendum could be sought. Residents submitted referendum signatures in May 2026; the village fiscal officer refused to forward the petition in June 2026. On 7 August 2026 the Ohio Supreme Court decided State ex rel. McNamara-Smith v. Grube, 2026-0906, 6-1, holding that the emergency resolution did not explain why a 30-day delay would obstruct the project, and directed fiscal officer April Grube to submit the petition to the Pickaway County Board of Elections for placement on the 3 November 2026 ballot. The court noted the board of elections may still determine whether the resolution was an administrative action not subject to referendum.
Ohio Supreme Court decision 7 August 2026; ballot 3 November 2026
Court News Ohio ↗ WOSU Public Media ↗Athens data center moratorium Record-specific: Athens · moratorium
Athens, Ohio, enacted a local data center moratorium or ban, recorded in SAVRN's moratorium tracker as dated August 2026. 1-year permit pause inside city limits; the mayor or service-safety director may extend it a second year. Does not reach the site that prompted it, that parcel is in Athens Township, outside the city. The measure runs to 4 August 2027.
Enacted August 2026
woub.org ↗Avon Lake data center moratorium Record-specific: Avon Lake · moratorium
Avon Lake, Ohio, enacted a local data center moratorium or ban, recorded in SAVRN's moratorium tracker as dated June 2026. Ordinance 26-60, an emergency measure effective on the mayor's approval Jun 23 and running through 22 June 2027, extendable once by up to six months. Bars consideration, approval or authorization of any data center as a permitted, conditional or accessory use, including zoning permits, building permits and certificates of occupancy, and tolls the clock on pending applications so nothing is approved by default. Excludes a data center incidental to a permitted principal use. Section 4 bars any data-center zoning framework reaching council until the city completes fiscal, infrastructure and community-impact analyses and at least two publicly noticed hearings. The measure runs to 22 June 2027 and covers permits.
Enacted June 2026
avonlake.org ↗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.
Permits and development ↗Permits, facilities and power development