Data Center Moratoriums: Verify the Project Before Forecasting Equipment Demand

Correction, October 18, 2026. Our earlier version incorrectly described Maine’s LD 307 as an enacted moratorium and asserted that blocked projects and their equipment orders necessarily move to other states. We have replaced those claims and withdrawn the resulting state-specific stocking recommendations. We also corrected the EIA comparison: April’s commercial-sales growth figures describe different forecast years, not an upward revision to 2026. The title, descriptions and source list have been updated with the body.

Maine’s proposed data-center moratorium did not become law through LD 307. The governor vetoed it on April 24, 2026, and the Legislature sustained that veto on April 29. That final disposition replaces the premise on which this article originally based its procurement recommendations. (Maine Legislature, LD 307)

A policy announcement belongs in a procurement forecast only with a clear account of the project and purchasing decision it affects. A pause, a cancellation and a relocation are different outcomes. This article no longer presents Ohio, Texas or Indiana as verified destinations for displaced projects or recommends increasing inventory on that basis.

What Maine’s records establish

The governor’s veto message describes the amended bill as proposing a pause on municipal and state permitting for data centers with a load of 20 MW or more, through November 1, 2027. Those were proposed terms in a vetoed bill. They are not evidence that a statewide pause took effect. (April 24 veto message)

On April 29, the governor instead established the Maine Data Center Advisory Council through Executive Order 5. The order directs ratepayer-protection work and calls for the council’s public report by January 29, 2027. Its operative provisions establish agency responsibilities and a council; they do not enact LD 307’s proposed permitting moratorium. (Executive Order 5; April 29 announcement)

The distinction matters for a supplier tracking a particular development. The disposition of LD 307 does not establish that every Maine project has its required permits, available grid capacity or a purchase commitment. Those questions require that project’s records. Likewise, an advisory council’s future report is not a scheduled equipment order.

National energy forecasts do not locate equipment orders

EIA’s October 2026 Short-Term Energy Outlook forecasts total U.S. electricity consumption of 4,288 billion kWh in 2026 and 4,356 billion kWh in 2027. September’s figures were 4,270 and 4,349; April’s were 4,244 and 4,381. These are the same total-consumption series, distinct from electricity sales to customers. October is higher than April for 2026 and lower for 2027. National annual energy does not establish a local peak load, project relocation or equipment order. (October Table 7a; September Table 7a; April Table 7a)

These figures provide national context. They do not identify a developer changing sites, a utility accepting that replacement site, or a manufacturer transferring an order. Our earlier article supplied no verified chain of project records supporting its state-by-state relocation forecast. We have removed that forecast, the unverified national-count comparisons and the claim that cancelled projects’ equipment was already being redirected.

Check the project, the grid work and the purchase separately

For a specific opportunity, ask for evidence at each step before treating a policy change as equipment demand:

• Policy: identify the operative bill, order, permit decision or tariff, its current disposition, and the facility it covers. Record an effective date separately from a proposal or reporting deadline.
• Project: establish whether the developer is continuing, delaying, cancelling or moving the named project. For a relocation, identify the replacement site and the developer’s commitment to it.
• Grid work: obtain the applicable utility or interconnection documents describing the connection, required upgrades, responsibilities and milestones. An application alone does not establish a completed connection.
• Purchasing: confirm the buyer, approved equipment specifications, order or solicitation, delivery dates, and any cancellation or transfer terms. Do not infer those terms from a news report about a permitting pause.

Keep unresolved steps visible in the forecast. If a project is paused but the supplier has not confirmed a change to its order, record the order’s status as unconfirmed. If a developer announces a new site, check the new site’s connection and equipment requirements before carrying the old site’s quantities into the sales pipeline.

Inventory decisions need project evidence

Our recommendation is to tie inventory changes to documented customer requirements and supplier commitments. A moratorium headline alone does not justify raising safety stock in a different state, releasing an existing allocation, or assuming that a cancelled order remains in a manufacturer’s queue.

For each affected quote, record the customer, location, equipment scope, required date and next confirmation needed. Revisit the forecast when the project or purchase record changes. That produces a procurement decision a buyer can check against the actual job.

Subscribe to The Feeder for the weekly procurement newsletter.