Prolepsia forecastYes / no

Will Indiana enact a data center moratorium by December 31, 2028?

As of 14 November 2026, Prolepsia puts the chance of yes at 14%.

14%chance of yes

Yes 14%No 86%
Prolepsia forecast made

How Prolepsia reasons

The report Prolepsia wrote with this forecast.

How forecasts are made · Track record

TL;DR

The forecast is 13.7% Yes and 86.3% No on Indiana enacting a qualifying statewide data-center moratorium by December 31, 2028. Stronger ratepayer protections, incentive changes, and local restrictions remain better supported than a mandatory statewide suspension.

Key evidence

  • The legislative precedent is weak. Berkeley Lab’s October 2026 review reported moratorium bills in approximately a dozen states, with none enacted by statute at that point. This is an unfinished, mixed group of proposals, not a clean statistical passage-rate sample (Berkeley Lab).
  • Indiana has chosen study rather than suspension. HEA 1406 required examination of incentives, utility costs, water supply, and environmental impacts, with recommendations due November 1, 2026. The requirement itself does not stop development (legislative synopsis).
  • Political turnover has not removed the main gatekeepers. Republicans retained legislative control and selected Ben Smaltz as speaker-elect. Eric Koch remains Senate Utilities chair, preserving continuity at a consequential committee (House announcement, Senate appointments). Governor Braun has continued defending data centers as an economic opportunity (Indiana Public Radio).
  • The backlash is real. October polling found 69% opposed new construction and 18% supported it, although only 5% named AI/data centers their top concern. Those results measure construction sentiment, not support for this exact statewide remedy (poll reporting). Incoming legislators David Boyd and Natasha Baker have expressed support for moratoria, creating advocates without establishing a passage coalition (candidate survey).

Uncertainties

The strongest Yes pathway is a short statutory pause attached to broader safeguards legislation, potentially with specified projects grandfathered. A permanent ban is unnecessary. A grid, water, or electricity-cost controversy could make that compromise attractive during the remaining 2027 and 2028 legislative opportunities.

The completed state study’s recommendations remain unverified. No qualifying Republican endorsement or operative 2027 moratorium bill was verified, but that does not establish that private drafting is absent. The decisive distinction is whether legislation suspends development by default: tougher permitting conditions, local pauses, executive action, and tax-incentive freezes alone do not resolve Yes.

Read the full report

TL;DR

The forecast is 13.7% Yes and 86.3% No on Indiana enacting a qualifying statewide data-center moratorium by December 31, 2028. The central outlook is continued development under stronger safeguards, not a statewide statutory suspension. The key risk is a temporary, grandfathered pause that wins Republican support in response to electricity-cost, grid, or water concerns.

Context

As of November 14, 2026, Indiana faces a clear conflict between data-center recruitment and public resistance. Local governments have imposed restrictions, opponents have gained legislative footholds, and the election has changed leadership. Yet Republicans retain legislative control, and Governor Mike Braun continues to describe data centers as an economic opportunity (election reporting, Braun’s remarks). No qualifying statewide enactment was verified in the available record.

The resolution is narrower than a general question about whether Indiana will restrict data centers. It requires an enacted statute or constitutional provision that mandatorily suspends a covered activity statewide, encompassing all new data centers or a category including every new facility above 100 MW of requested or nameplate interconnection capacity per facility. Local restrictions, executive orders, incentive freezes alone, and ordinary conditional permitting do not qualify. Temporary suspensions and specified grandfathering can qualify. Enactment by the deadline controls, not the effective date or later implementation.

Evidence

The historical starting point is the gap between proposing a statewide moratorium and enacting one. NCSL’s September 15, 2026 inventory covered 16 states considering moratoria, with none marked enacted. Berkeley Lab’s October review likewise reported bills in approximately a dozen states and no statutory statewide enactments. The inventories differ in timing and scope. They are not independent trials and cannot support a mechanical passage rate. They do show that widespread concern had not yet translated into a common statutory response (NCSL inventory, Berkeley Lab review).

Two analogues explain why that distinction matters. Maine’s LD 307 reached the governor but was vetoed on April 24, 2026, with the veto sustained on April 29. New York’s July 14 statewide pause took the form of an executive order. The former illustrates the final enactment hurdle; the latter illustrates a restrictive action that would not satisfy Indiana’s market rules (Maine legislative record, New York announcement).

Indiana’s own enacted policy points toward conditions and investigation rather than cessation. The Department of Revenue’s April 2026 synopsis describes HEA 1210’s local-payment conditions attached to certain data-center exemptions. It also confirms that HEA 1406 required a study of incentives, utility costs, water supply, and environmental effects, with recommendations due November 1, 2026. Neither provision establishes a default development halt. The study creates an opening for further legislation, but its existence is not evidence that lawmakers have chosen a moratorium (legislative synopsis).

The election widened that opening. Reporting projected an incoming House of 54 Republicans and 46 Democrats and a Senate of 35 Republicans and 15 Democrats. These were preliminary reported outcomes, not independently verified certified totals. Republicans retained control, but with a narrower margin and new leadership (post-election reporting).

Committee turnover matters more than the headline seat count alone. Five of the nine Republicans on the 13-member House Utilities Committee lost reelection, including chair Ed Soliday and vice chair Dave Hall. That removes established gatekeepers and creates room for different bills to receive attention. It does not establish that their successors support a statewide pause (Indiana Electric Cooperatives).

Continuity remains on the Senate side. The official November 4 House announcement confirms Ben Smaltz’s selection as speaker-elect. The November 10 Senate appointments retain Eric Koch as Utilities chair and make him majority floor leader. Those facts support a political opening, not a demonstrated reversal of the development agenda (House announcement, Senate appointments).

There are identifiable incoming advocates. David Boyd explicitly supported a statewide pause, and Natasha Baker supported a moratorium pending further study. Their presence gives the issue voices in both chambers. Candidate positions, however, do not supply operative coverage language, termination conditions, committee commitments, or a passage coalition. No winning Republican legislator’s endorsement of the particular statewide statutory suspension required here was verified (candidate survey).

Braun remains a political obstacle. The state documented his participation in the February 11, 2026 groundbreaking for Meta’s announced $10 billion Lebanon campus. He continued defending data centers at an October 19 Bloomington appearance. His October 28 South Bend position emphasized added electricity supply, developer payments, community benefits, and water recycling rather than a statewide halt. These actions indicate a preference for development with safeguards, not an explicit commitment to veto every temporary pause (Meta announcement, Bloomington reporting, South Bend reporting).

His opposition is not an absolute legal barrier. Indiana allows veto overrides with 51 House votes and 26 Senate votes. Under the reported incoming composition, unanimous Democratic support would still require five House Republicans and 11 Senate Republicans. That is possible coalition arithmetic, not evidence that such a coalition exists (official legislative-process guide).

Public opinion supplies substantial pressure. The October 8–11 Bellwether survey found 69% opposed new data-center construction and 18% favored it. It interviewed 896 registered voters; published results used 839 likely voters, with a reported sampling margin of ±3.4 percentage points. Energy-cost concern reached 90%, but only 5% named AI/data centers their top concern. The distinction is central: broad dislike does not establish that voters demand this exact statewide statutory remedy (poll reporting).

Local action confirms that opposition can organize. WFYI’s October 21 account reported 32 county moratoria, 14 regulatory ordinances, and four communities where data centers were not permitted. Those are different policy types and geographic units, not interchangeable bans. Local restrictions can encourage state action by demonstrating political demand. They can also reduce pressure for it by allowing communities to reject projects without stopping development everywhere (WFYI).

Electricity-cost allocation is a plausible trigger for a wider coalition. The AES–Google Monrovia project involves 390 MW and approximately $737.3 million in associated investment. Reporting identified approximately $73.8 million in network upgrades allocated across customers, alongside AES’s position that contractual revenues recover incremental costs. Allocation is not the same as an eventual net subsidy, and the contract is substantially redacted. The evidence supports a contested cost-recovery debate, not a proven residential subsidy (Utility Dive).

The latest infrastructure reporting reinforces the pressure without establishing a legislative route to suspension. The November 13 assessment described aging systems, funding gaps, and recommendations for investment and modernization. That supports concern about infrastructure capacity. It does not show that a statutory data-center moratorium has become the preferred response (Indiana Capital Chronicle).

What's non-obvious

More restrictions do not necessarily mean a greater chance of this particular moratorium. Strong ratepayer protections, water rules, disclosure requirements, and local control can absorb the backlash while leaving development permitted. The same public pressure can therefore produce substantial regulation and still resolve No. The useful signal is not the volume of anti-data-center activity. It is whether influential lawmakers move from regulating projects to suspending them by default.

The reverse is also true: Yes does not require a permanent ban or a complete political reversal. A short, grandfathered statutory pause can qualify. A law that suspends approvals until a specified condition is satisfied can also qualify, subject to the resolution’s objective-condition requirements. The most credible Yes route is a temporary compromise attached to broader energy or fiscal legislation. The 2027 and 2028 legislative opportunities leave time for that bargain, but the evidence does not yet show the Republican support needed to enact it.

Uncertainties

The largest substantive gap is the completed HEA 1406 study. Its recommendations were not verified. That does not establish that the report was undelivered, nor does it indicate whether it favors development, safeguards, or suspension. Its content would help distinguish a routine regulatory agenda from a state-backed case for a pause.

The next gap is operative legislation. Candidate pledges do not settle statewide coverage, the capacity threshold, exemptions, or release conditions. An actual bill, a Republican coauthor, and a hearing commitment would provide much stronger evidence than general opposition. The absence of a verified public draft is not proof that private drafting is absent.

Finally, the forecast remains exposed to an electricity-cost, reliability, or water controversy that changes the preferred remedy. Evidence that developer-funded safeguards work would support continued conditional development. Evidence that those safeguards fail could make a temporary statewide suspension attractive. These are the main competing paths; the saved forecast remains 13.7% Yes and 86.3% No.

What changed since the last forecast

This forecast is not compared to the previous run because the answer shape, model stack, or engine settings changed. Treat it as a fresh baseline.

Forecast history

How Prolepsia’s forecast has moved7 forecasts, from 15% on 6 Oct 2026 to 14% on 14 Nov 2026.6 Oct 2026: 15%10 Oct 2026: 15%17 Oct 2026: 18%24 Oct 2026: 17%31 Oct 2026: 12%7 Nov 2026: 14%14 Nov 2026: 14%
DateForecast
14% chance of yes
14% chance of yes
12% chance of yes
17% chance of yes
18% chance of yes
15% chance of yes
15% chance of yes

Sources Prolepsia read

  1. Indiana House Republicans pick new leader after big election losses • Indiana Capital Chronicleindianacapitalchronicle.com
  2. Braun talks data centers, economy at Bloomington panel – Indiana Public Radioindianapublicradio.org
  3. Which States Are Banning Data Centers?www.ncsl.org
  4. Data Center Siting: Criteria, Policies, and Recent Trendseta-publications.lbl.gov
  5. Maine legislative recordlegislature.maine.gov
  6. New York announcementwww.governor.ny.gov
  7. Legislative Synopsiswww.in.gov
  8. New legislative leaders, same commitment to electric cooperatives - Indiana Electric Cooperativeswww.indianaec.org
  9. Statement: House Republicans select State Rep. Ben Smaltz to lead caucus, serve as Speaker-elect | Indiana House Republicanswww.indianahouserepublicans.com
  10. Garten announces Indiana Senate leadership and committee chair appointmentswww.indianasenaterepublicans.com

The question

Imported from Polymarket. This yes/no question comes from a single Polymarket market.

How it resolves

This market will resolve to "Yes" if the State of Indiana enacts a law or constitutional provision that establishes a statewide moratorium on new data centers between market creation and the specified date, 11:59 PM ET. Otherwise, this market will resolve to "No". A statewide moratorium on new data centers refers to a binding policy with legal force that generally prohibits or suspends the approval, permitting, construction, grid interconnection, or operation of all new data centers, or a subset of data centers that includes all new data centers with an interconnection capacity above 100 MW per facility (requested or nameplate), throughout the state. Suspensions of tax incentives, exemption certifications, or economic development awards alone will not qualify, nor will a moratorium adopted by a local government or limited to part of the state. Specific exemptions (e.g., for specified applications, executed agreements, or interconnection requests) do not prevent a measure from generally applying to all new data centers, or a qualifying subset of new data centers, provided that data center approval, permitting, construction, grid interconnection, or operation is prohibited by default, rather than permitted subject to conditions or restrictions. Conditions on the resumption or termination of a suspension do not make a measure one that permits subject to conditions; a measure that suspends approvals, permitting, construction, or interconnection until a specified condition is satisfied qualifies. Enactment occurs when a bill becomes law under the state's constitution and laws, whether by gubernatorial signature, veto override, becoming law without signature, approval at a statewide referendum election, or any other legal mechanism by which statutes can be enacted. For an initiated or referred statute or constitutional amendment, or other voter referendum, the relevant law is considered to have been enacted on the election day on which it was approved, as reflected in the certified results, regardless of when the measure is certified or takes effect. Passage by one or both chambers, or a Governor's announced intent to sign, is not enactment. Executive orders, agency orders, and other measures which are not statutory or constitutional do not qualify as enactment regardless of legal force. A provision removed by line-item veto is not enacted unless the veto is overridden as to that item. The operative text of the measure at enactment controls; provisions amended out before enactment do not qualify. The moratorium provision must be mandatory on its face. A statute that merely authorizes a state agency or the Governor to impose a moratorium at their discretion does not qualify. A statute that directs suspension of approvals or interconnection upon a specified condition qualifies only if the condition is objectively determinable and is not deferred to be determined by the implementing agency's findings, certifications, or completion of its own proceedings. This market resolves based on the date of enactment, not the effective date. Resolution will not be affected by failure to implement a law, judicial invalidation, repeal, or expiry that follows a relevant enactment, or an effective date that comes after the date of enactment. The primary resolution source will be official information from the state government of Indiana; however, a consensus of credible reporting may also be used.