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.
Nevada: inspect the evidence.
Counts are records, not unique projects. Records can overlap across trackers.
Colovore Reno 1 data center Record-specific: Near Tahoe Reno Industrial Center · incentive approved
The Nevada Governor's Office of Economic Development approved $4.08 million in tax abatements for Colovore Reno 1 LLC to establish a data center in Storey County east of Reno, announced Wednesday 5 August 2026. Colovore plans 10 jobs at an average hourly wage of $59 within five years, and the facility is projected to generate $16.8 million in new taxes over the abatement period $30 million capital equipment investment committed under the state abatement MW not disclosed; Colovore specializes in liquid-cooled colocation
GOED approval announced Wednesday 5 August 2026; reported 7 August 2026; single-outlet report (Las Vegas Sun)
Las Vegas Sun ↗Fallon Paiute-Shoshone Tribe data center moratorium Record-specific: Fallon Paiute-Shoshone Tribe · moratorium
Fallon Paiute-Shoshone Tribe, Nevada, enacted a local data center moratorium or ban, recorded in SAVRN's moratorium tracker as dated May 2026. First tribe in Northern Nevada to ban data centers on tribal lands; resolution brought by tribal council secretary Philip Johnson. The measure has no end date by design.
Enacted May 2026
kunr.org ↗Fleet Data Centers Reno-area hyperscale facility (SV RNO) Record-specific: · construction
A 252-acre property in Storey County, Nevada carrying a turnkey data center and electrical substation of 230 MW utility capacity and 200 MW critical IT capacity. The February 2026 offering states the facility is 100% leased on a 197-month triple net lease to an AA- investment grade rated tenant with a market capitalization in excess of $3 trillion. The release does not name the tenant, and no tenant is named here. Fleet Data Centers applied to the Public Utilities Commission of Nevada to build two private gas-engine plants totaling more than 360 MW to power its Peru Ridge and South Valley campuses at the Tahoe Reno Industrial Center for two to three years until NV Energy can provide permanent service; NV Energy said it signed a large-load electric service agreement for South Valley in May 2026. A PUCN decision was expected 8 September 2026; the outcome was not confirmed.. On 17 September 2026 the Public Utilities Commission of Nevada approved Fleet Data Centers' Peru Ridge and South Valley methane-fired plants (Peru Ridge Self-Generation Project 218 MW and a temporary 144 MW South Valley plant, per applications filed 20 April 2026; more than 360 MW together), to serve projects at and near the Tahoe Reno Industrial Center for two to three years until NV Energy can provide permanent service, subject to NDEP and Storey County permits. The Las Vegas Review-Journal reported on 23 September 2026 that the second data center covered by the 17 September PUCN approval is Fleet's Peru Ridge campus, served by a 218 MW plant on 23.4 acres near Peru Drive in the Tahoe Reno Industrial Center. Fleet is a subsidiary of Denver-based Tract Capital. Both plants are slated to start construction in early 2027, take about six months to build and run for two to three years; a Storey County building permit and an air permit are still required. The paper said Bloomberg had reported Nvidia as the South Valley tenant, which both companies declined to comment on. South Valley received $23.35 million in tax abatements in February 2026. Temporary on-site natural gas plant (South Valley, 144 MW, 37.4 acres at 8990 USA Parkway) approved by the PUCN on 17 September 2026 pending NDEP air and Storey County building permits, to operate two to three years until NV Energy provides permanent service; NV Energy large-load electric service agreement signed May 2026; dedicated electrical substation $3.8 billion of 5.875% senior secured notes due 2031 priced 13 February 2026 to fund a portion of development and construction 230 MW utility capacity, 200 MW critical IT capacity; the recorded figure is critical IT capacity
Date not recorded
Fleet Data Centers ↗ EIN Presswire ↗ Nevada Current via Yahoo ↗ Nevada Current via Yahoo News ↗ Nevada Current ↗ The Nevada Independent ↗ Northern Nevada Business Weekly ↗ Las Vegas Review-Journal via MSN ↗Henderson 180-day data center moratorium proposal (declined) Record-specific: City of Henderson · other
On 21 July 2026 the Henderson City Council declined a proposed 180-day moratorium on new data center applications. Council instead directed staff to strengthen the development agreement framework so future applicants must address water consumption, electrical demand, noise and site-specific concerns. Officials noted new projects could see effective delays while the framework is developed.
Moratorium declined 21 July 2026
News 3 Las Vegas ↗ KLAS 8 News Now ↗Humboldt County data center moratorium Record-specific: Humboldt County · moratorium
Humboldt County, Nevada, enacted a local data center moratorium or ban, recorded in SAVRN's moratorium tracker as dated July 2026. Temporary moratorium on data center applications through 13 July 2027 while the county updates land-use rules on water, power and infrastructure; multiple developers had approached the county and its code did not address data centers. The measure runs to 13 July 2027.
Enacted July 2026
thenevadaindependent.com ↗Hyperscale data center and natural gas plant on BLM land near Henderson (Paradise Hills area) Record-specific: Bureau of Land Management / City of Henderson · withdrawn
A Texas-based developer canceled a proposed 1,000 MW hyperscale data center and natural gas plant on 680 acres of BLM land near the southeastern tip of Henderson, close to the Paradise Hills community. In a statement on Thursday 24 September 2026 the developer said it had consulted with the city and BLM and withdrew its application because of the city's planned urban development in the same area. Skylar Opportunities LLC is an affiliate of Skylar Capital Management, the company behind the Boulder City Townsite project on BLM land (row 180).
Application filed November 2025; withdrawal announced 24 September 2026
Las Vegas Review-Journal ↗ Las Vegas Review-Journal via MSN ↗Keystone Data Center (265 Keystone Avenue) Record-specific: Reno · under_construction
Centra's 91,200-square-foot downtown data center at 265 Keystone Avenue was submitted in November 2024 and approved by the Reno Planning Commission in January 2025. The city lists planned use of 7 MW of power and 2 acre-feet of water a year. Building permits were issued and the project is under construction; Centra's website says it will be ready to deliver 4.4 MW in the fourth quarter of 2026. As an already permitted project it is not affected by the Reno citywide moratorium. Not disclosed 7 MW per the City of Reno comparison chart; Centra's website lists 4.4 MW ready for delivery in the fourth quarter of 2026; 91,200 sq ft
Application November 2024; approved January 2025; under construction; single outlet (Reno Gazette-Journal)
Reno Gazette-Journal (via MSN) ↗Monarch Data Center Record-specific: Yerington · approved
Lyon County commissioners voted 3-1 to approve a planned unit development rezoning for the Monarch Data Center and associated gas-fired power plant near Yerington, after the Planning Commission recommended approval 4-3 on 15 July 2026. The Sierra Club Toiyabe Chapter opposed the project over water, energy, air quality and noise impacts Commissioner Dave Hockaday cast the lone no vote and Commissioner John Cassinelli recused. Developer Copia Power has a year to file its final PUD and still needs state transmission and environmental permits. The Walker River Paiute Tribe and Yerington Paiute Tribe vowed to challenge the decision in court Associated gas-fired plant with 500 MW of natural gas generation and 500 MW of battery storage per KRNV Not disclosed in the fetched coverage Project requires at least 1,000 MW of power per KOLO; 4.6 million sq ft in eight two-story buildings up to 95 feet on 505.40 acres
Approved 3-1 on 6 August 2026; reported 6 and 7 August 2026
KRNV News 4 ↗ KOLO 8 News Now ↗Nevada campuses (Storey and Clark counties) Record-specific: · expansion
Google plans to invest more than $400 million in Nevada this year to support its data center campuses in Storey and Clark counties, bringing total investment in the state to more than $2.2 billion since 2019. The document's correction note confirms the Nevada figure is >$400 million in-year and >$2.2 billion cumulative, correcting a summary-table typo of $400B. More than 450 MW of new clean energy contracted more than $400 million this year; total investment in the state more than $2.2 billion since 2019 More than 450 megawatts of new clean energy contracted
In-year investment; cumulative since 2019
The Nevada Independent ↗Oppidan Data Center (9630 N. Virginia Street, North Valleys) Record-specific: Reno · under_construction
The Oppidan Data Center application was submitted in November 2024 and approved in March 2025. The 61,500-square-foot building sits on North Virginia Street near Stead Boulevard, down the street from the Webb Data Center. The city lists 8 MW of power and 8 acre-feet of water a year. Building permits were issued and the project is under construction; no opening date has been announced. Not disclosed 8 MW per the City of Reno; 61,500 sq ft
Application November 2024; approved March 2025; under construction; single outlet (Reno Gazette-Journal)
Reno Gazette-Journal (via MSN) ↗Pahrump Valley data center ban (Nye County Bill No. 2026-11) Record-specific: Nye County · moratorium
County commissioners voted 5-0 on 18 August 2026 to adopt Bill No. 2026-11, amending Nye County Code Title 17 to prohibit data center development in the Pahrump Valley and Hydrographic Basin 162, an over-appropriated basin. A separate motion setting a 14 September 2026 public hearing on land use standards for data centers elsewhere in the county passed 4-1. A proposal to put the ban to a special election died without a motion. Earlier in September 2026 CDDC, LLC and 9 of a Kind, LLC, which own nearly 911 acres along Carpenter Canyon Road and State Route 160 planned for the Manse Technology Campus (MTC Project), petitioned the Nye County district court to reverse the ban (Ordinance No. 631), allow the project to proceed and award attorney's fees, arguing the ordinance disregarded their investment made in reliance on existing zoning and violated their property rights. Commissioner Ian Bayne, who proposed the ban, said he remained confident in it. No initial court date had been scheduled as of 25 September 2026.
Adopted 18 August 2026; developer petition for judicial review filed September 2026 (reported 24 and 25 September 2026)
Pahrump Valley Times ↗ KTNV ↗ Las Vegas Review-Journal ↗Pyramid Lake Paiute Tribe data center moratorium Record-specific: Pyramid Lake Paiute Tribe · moratorium
Pyramid Lake Paiute Tribe, Nevada, enacted a local data center moratorium or ban, recorded in SAVRN's moratorium tracker as dated August 2026. Tribal Council passed permanent ban on data centers on tribal homelands; Chairman Steven Wadsworth cited water sovereignty and protecting endangered cui-ui fish. Part of Water Over Data Alliance tribal coalition demanding free, prior, and informed consent for data centers in Truckee River watershed. The measure has no end date by design.
Enacted August 2026
kunr.org ↗Reno citywide data center moratorium Record-specific: City of Reno · moratorium
The Reno City Council voted 6-1 to adopt a pending moratorium at a 14 May 2026 special meeting, then approved the final moratorium 6-1 in early June 2026. The moratorium runs through 31 August 2027 and cannot be lifted until new regulations are adopted. Council directed staff to draft rules on water and energy use, noise, air quality, community benefits and allowed locations. Already permitted data centers are not affected.
Final moratorium approved 6-1, reported 1 June 2026; runs through 31 August 2027
News 4 (KRNV) ↗ Data Center Bans ↗Switch Nevada AI campus Record-specific: · announced
Switch announced a $3bn AI campus in Nevada and has expanded credit facilities to $10bn since the take-private. $3bn AI campus
Date not recorded
DCD ↗Townsite Data Center Record-specific: Boulder City area, Clark County · court_halt
The Interior Board of Land Appeals stayed construction of the Townsite Data Center on 1 September 2026, an 88.5-acre facility the Bureau of Land Management approved on public land roughly 25 miles southeast of Las Vegas near Boulder City, and reported as the first AI data center approved on federal public land. The board found BLM likely acted unlawfully when it amended an existing right-of-way grant in June 2026 to permit a data center without a project-specific environmental review. Opponents cited projected electricity and water demand, soil disruption, light pollution and habitat loss for the Mojave desert tortoise. BLM had until 21 September 2026 to respond. This is an interim stay, not a final decision, and no capital figure has been disclosed. In a filing on Monday 21 September 2026, BLM asked Interior Board of Land Appeals Administrative Judge David Gunter, who granted the stay, to set aside its approval of the right-of-way amendment so the agency can conduct additional review of the application. Townsite Solar 2 LLC supports the motion, the Center for Biological Diversity and the Sierra Club are neutral, and Boulder City opposes it, with its response due 5 October 2026; the city said the motion does not commit BLM to an environmental assessment or public involvement and its approval would lift the stay.
BLM right-of-way amendment approved 26 June 2026; IBLA stay issued 1 September 2026; BLM motion to set aside and remand filed 21 September 2026; Boulder City response due 5 October 2026
Outdoor Life ↗ NationofChange ↗ Alaska Native News ↗ Las Vegas Review-Journal ↗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