
Data Centers, Energy Use, and Local Backlash
Project and community case studies
Loudoun County: changing the approval pathway
Virginia · Decision: March 18, 2025 · Local zoning, not utility approval
Dated decision
Loudoun’s Board initiated its data-center standards review in February 2024 and divided the work into two phases that July. On March 18, 2025, Phase 1 changed areas where data centers had been allowed by right to conditional or special-exception treatment. The county also adopted transition rules allowing some applications accepted before February 12, 2025, to proceed without the new special exception. Its official guidance warns that eligibility depends on each project’s circumstances. [74]
What the case establishes
The change did not erase existing facilities or automatically invalidate every pending application. It changed the decision pathway for future development while preserving specified transition cases. Phase 2 addresses additional standards. In September 2026 the board separately began considering a pause on legislative applications; that procedural step should not be confused with an already effective blanket moratorium. [75]
Comparative interpretation
Loudoun illustrates a mature market moving from broad development permission toward case-by-case public review. The potential benefit is a clearer forum for weighing compatibility, infrastructure and community conditions. The cost is less scheduling certainty for applicants whose business assumptions were built around administrative approvals.
Neither result can be inferred from the phrase “data-center friendly.” A jurisdiction can welcome investment and still require legislative review. Conversely, a restrictive new rule may have little immediate effect on projects protected by transition provisions.
Decision lesson
For any comparable proposal, establish the application acceptance date, governing zoning edition, transition eligibility and remaining public votes before describing its status. Treat local approval, utility service and construction commencement as separate milestones. This is an analytical lesson from the dated record, not a finding that every Loudoun project has stopped or that all existing permissions have expired.
Fairfax County: measurable compatibility standards
Virginia · Adopted September 10, 2024 · Effective September 11, 2024
Dated decision
Fairfax adopted a data-center zoning amendment on September 10, 2024, effective the next day. The county’s summary identifies equipment screening, revised size thresholds, residential separation, distance from Metro stations, architectural standards and pre- and post-construction noise studies. Some larger developments require a special exception, with different treatment in designated industrial districts. These are land-use standards, not a judgment about the commercial viability of any particular operator. [76][77]
Why it differs from a ban
The county retained pathways for development while narrowing where and how it can occur. The adopted text also contains transition provisions for previously accepted or approved applications. A map of potentially eligible industrial land therefore cannot substitute for a project-specific review of the applicable rules. [77]
Comparative interpretation
Fairfax’s approach is more operationally specific than a general statement of community concern. It creates items that reviewers can check before construction and revisit afterward. That can improve predictability for residents and developers, although a study requirement only works if its assumptions, measurements and remedies are credible.
The transit-distance provision also makes the case about competing land uses. Industrial computing space can produce investment and tax receipts, but land near transit may support housing, employment density or other planning objectives. Those opportunity costs should be evaluated openly rather than hidden inside a generic economic-development label.
Decision lesson
A balanced comparison should distinguish the value of clearer standards from the additional cost of complying with them. It should also ask who reviews post-construction evidence and what happens if actual impacts differ from the approved forecast. The transferable principle is a closed loop between approval conditions and operating performance, not an assumption that screening or a one-time study resolves every neighborhood concern.
Prince William Digital Gateway: plan designation is not zoning
Virginia · County update: August 5, 2026 · Procedural status matters
Dated record
Prince William County’s August 5, 2026 update states that, following the Virginia Court of Appeals’ July 29 order, the Digital Gateway rezoning approvals were void and the properties reverted to their prior zoning. The comprehensive-plan amendment remained in place. The county said a future rezoning would require the normal application review and public hearings. This official distinction is central to understanding the project’s status. [78]
Separate decisions
The county’s record identifies the comprehensive-plan action adopted on November 1, 2022 and the subsequent rezoning applications. Those are different instruments. A planning policy can continue to support a future use while the legal permission for that use must be pursued again. The August update also described consequential changes to zoning maps and property assessments. [78]
Comparative interpretation
The case demonstrates why headline capital commitments are a poor substitute for entitlement diligence. A board vote may be significant without being the final, durable authorization needed to build. Litigation and procedural defects can alter the status of a project even when the underlying development concept remains part of the adopted plan.
This is not evidence that every contested data-center project will fail. It is evidence that public notice, hearing procedure and the distinction between policy and regulation are economically material. Both supporters and opponents benefit when status reporting identifies the specific instrument and date rather than simply calling a project “approved.”
Decision lesson
Use a milestone ledger: comprehensive plan, zoning, permit, utility agreement, construction and operation. Record court orders alongside administrative actions. For comparative analysis, separate the benefits claimed for a proposed development from benefits already realized. Do not convert an August 2026 county status update into a claim about later proceedings without checking the new record.
Virginia’s JLARC review: benefits and burdens use different denominators
Statewide evidence · Report: December 9, 2024 · Economic activity is not permanent payroll
What the official review found
Virginia’s legislative audit described substantial economic contributions alongside land-use and infrastructure pressures. The University of Virginia’s summary of its economic work reports an estimated 74,000 jobs, $5.5 billion in labor income and $9.1 billion in annual state GDP associated with the industry. Those are broad economic-impact estimates, not a count of employees inside data-center buildings. [80]
JLARC also found that roughly one-third of facilities were near residential areas and described shortcomings in some local planning and noise controls. It reported $928 million in data-center sales-tax savings in fiscal 2023 and discussed alternative ways to use the exemption as a policy instrument. These are findings of the December 2024 review, not independently updated 2026 totals. [79]
Comparative interpretation
The useful lesson is not to choose the largest benefit number or the most alarming impact. Construction employment, continuing operations, indirect supplier activity and local tax receipts answer different questions. Likewise, a state-level economic benefit does not show whether a particular neighborhood bears a disproportionate burden.
A capital-intensive project can create substantial purchasing and tax activity without employing as many permanent workers as a similarly sized labor-intensive business. That does not make its benefits fictitious; it changes the appropriate comparison. Incentive evaluation should use net public returns over time, not investment announcements alone.
Decision lesson
Compare projects using consistent geography and time periods. Separate one-time construction activity from recurring revenue and ongoing service costs. State explicitly whether a number is direct, indirect or induced. For community impacts, pair aggregate findings with site-independent local indicators such as compliance outcomes and household rate exposure. This framework supports a more useful discussion than either unconditional promotion or a blanket presumption that all data-center investment is harmful.
PJM forecasting: a pipeline is not the same as delivered demand
Regional grid · 2026 forecast edition · Planning projections, not metered load
Dated planning evidence
PJM’s explanation of its January 2026 long-term forecast projects average annual summer-peak growth of 3.6 percent over the following decade. It identifies data centers as the principal driver while also naming electrification, vehicles and manufacturing. PJM says it strengthened the evidence required for large-load requests, including realistic construction timing and financial commitments. [81]
Its forecast-development page publishes the report, supporting data and process materials. This matters because a regional forecast is an assembled planning product, not simply the sum of every announced campus. The published vintage and assumptions should travel with any chart based on it. [82]
Comparative interpretation
This case connects local siting decisions to regional consequences without assuming every proposed facility is inevitable. Overbuilding around speculative demand can leave costs to recover from someone; underbuilding can constrain economic activity and reliability. Forecast discipline is an attempt to manage both errors.
A planning adjustment is not the same as a final customer contract, and a contract is not the same as fully utilized equipment. Phasing, commissioning and operating utilization can materially change the timing of demand. County-level announcements and utility-level forecasts should therefore be reconciled before they are combined.
Decision lesson
For each forecast, record its date, horizon, geography, peak-versus-energy metric and treatment of uncommitted projects. Track revisions rather than treating a single release as permanent truth. For energy-market discussion, distinguish electricity requirements from the fuel mix used to meet them. Even strong regional load growth does not by itself prove a specified increase in oil consumption or oil prices. The analytically defensible claim is that credible large-load growth changes planning requirements and the value of timely supply, transmission and demand-side options.
[*REDACTED*]: financial commitments before infrastructure expansion
Ohio · PUCO approval: July 9, 2025 · Tariff effective July 23, 2025
Dated decision
[*REDACTED*]’s official tariff page states that PUCO adopted its data-center settlement on July 9, 2025 and that the resulting tariff became effective July 23. The Ohio Consumers’ Counsel describes minimum capacity-related payments for new large data centers over a term of up to twelve years. The utility’s implementation page also organizes new projects into study tranches rather than treating every request as immediately serviceable. [83][84]
Continuing contest
The Consumers’ Counsel reports that industry groups appealed in November 2025. An adopted tariff and an unresolved challenge can coexist. The public record supports describing a specific approval and implementation pathway; it does not support treating the policy as permanently uncontested or applicable to every Ohio utility. [84]
Comparative interpretation
The economic objective is to align infrastructure commitments with credible customer obligations. Minimum payments, credit support and exit provisions can reduce the risk that infrastructure is built for a customer that does not arrive or leaves early. They can also make marginal projects less financeable and reduce flexibility for customers whose demand develops slowly.
That tradeoff should be acknowledged rather than characterized as simply pro-growth or anti-growth. Stronger obligations may shrink a speculative queue while improving the credibility of the remaining projects. Conversely, a shrinking queue is not direct proof of weaker underlying demand for computing services.
Decision lesson
A community should understand the serving utility’s tariff before assuming a rezoning will translate into construction on a promised schedule. A developer should distinguish reserved electrical capacity from actual consumption, including any ramp-up period. A consumer advocate should examine which costs are assigned to the customer and which remain shared. Ohio provides a concrete case for evaluating allocation rules, not a universal percentage that can be transplanted unchanged into other states.
New Albany, Ohio: approval must be followed by operating accountability
Municipal implementation · Complaints documented 2025–2026 · City FAQ accessed November 19, 2026
Evidence after construction
New Albany’s official FAQ acknowledges resident complaints involving operating data centers, including concerns reported near [*REDACTED*]’s campus in September 2025 and [*REDACTED*]’s campus in July 2026. The city describes ongoing mitigation and communication with the companies. The current FAQ gives a December 2026 target for [*REDACTED*]’s permanent solution; that is a scheduled remedy, not evidence of completion. [85]
A differentiated record
The same resource explains the city’s land-use framework, business-park planning and the division of responsibility among local government, utility providers and environmental regulators. The case therefore contains both an affirmative development strategy and evidence of impacts requiring follow-through. Neither side should be omitted from a fair account. [85]
Comparative interpretation
This case is useful because a project can comply with its original approval process yet still generate issues that need attention as equipment and operating conditions change. Community acceptance is not a one-time asset acquired at a hearing. It depends on response time, credible measurement and visible resolution.
Public FAQs can improve access to information, but they should distinguish company explanations, city findings, future schedules and completed work. A promised fix should not be reported as an achieved result. Similarly, the existence of complaints alone does not establish a violation; it establishes a need for examination through the applicable standards.
Decision lesson
For comparable communities, maintain a public record of complaint categories, response dates, measurement findings and closure status without exposing sensitive facility details. Specify which office owns each issue so residents are not redirected indefinitely between entities. Evaluate construction-phase and operating-phase effects separately. This gives developers a predictable accountability process and residents evidence that conditions attached to growth remain meaningful after the initial investment announcement.
Georgia: special contracts as a cost-allocation tool
State utility regulation · Rules adopted January 2025 · Implementation reported September 2026
Dated regulatory approach
Georgia’s PSC reports that January 2025 rules enabled minimum billing requirements and longer contracts for new large-load customers. The commission requires new data-center contracts to be provided at least thirty days before execution, and it approved related pricing changes in April 2025. Its annual report describes the rule’s application to new customers above 100 MW and the intention to address costs beyond the customer’s immediate site. [86][87]
What the record does not say
These protections concern [*REDACTED*]’s regulated service arrangements. They are not a statewide local-zoning approval and do not establish that every proposed campus will be built. Nor does the regulator’s stated purpose, by itself, prove the realized financial result for every future household bill.
Comparative interpretation
Georgia’s case places the utility contract between the investment announcement and the expensive infrastructure commitment. The potential advantage is that the customer’s obligation can reflect its scale and timing. The potential drawback is that complex special contracts are harder for the public to compare than a simple published rate.
A useful review separates customer-specific facilities from shared system costs, identifies the duration of protection and asks what happens if the customer reduces demand. Contract review should also be understood alongside planning approval: a financially strong contract cannot resolve a local land-use dispute, while a local approval cannot determine utility rates.
Decision lesson
Compare this approach with Ohio’s separate tariff class rather than assuming one mechanism is inherently superior. The questions are similar: credible demand, payment responsibility, early departure and transparency. For reporting, keep the commission’s policy objectives distinct from measured outcomes. The strongest public assurance is a documented allocation mechanism with enforceable obligations and periodic reporting, not a general statement that growth will necessarily lower bills for everyone.
Atlanta: preserving transit-oriented land for other uses
Municipal land use · Council vote: September 3, 2024 · Location restrictions, not a regional prohibition
Dated decision
Atlanta’s City Council announced approval of two ordinances on September 3, 2024. One defined data centers and prohibited them within 2,640 feet of a high-capacity transit stop; the other prohibited them within the BeltLine Overlay District. The council identified the measures as 24-O-1222 and 24-O-1218. [88]
The relevant geography
This was an action by the City of Atlanta, not a prohibition covering the entire metropolitan market or Georgia. It concerned the suitability of certain urban locations, rather than a conclusion that data processing has no economic value. A regional inventory should not label every surrounding community as subject to the same municipal restriction.
Comparative interpretation
Atlanta makes the opportunity cost of land explicit. A facility can be economically productive while still being a weak fit for land intended to support transit ridership, mixed-use activity or walkable development. Comparing capital investment alone can miss those alternative uses.
The decision also shows why development may be redirected rather than eliminated. Restricting one location can shift proposals to other industrial areas or jurisdictions. That can protect a specific planning objective while moving infrastructure and environmental questions elsewhere. Whether the regional result is better depends on the receiving location and its own standards, not just the departure from the restricted district.
Decision lesson
A sound comparison asks what public objective the land is supposed to serve and what alternative development is reasonably feasible. It should distinguish a broad industrial district from a transit-focused location and apply those distinctions consistently. For developers, the lesson is to screen municipal use definitions early. For elected officials, it is to explain why the rule follows adopted planning priorities rather than presenting every restriction as opposition to technology. The case supports targeted spatial policy, not a claim that all cities should use Atlanta’s exact distances.
Georgia’s generation decision: commitments, backstops and revisions
[*REDACTED*] service territory · Commission vote: December 19, 2025 · Approximately 10 GW in the announced package
Dated decision
On December 19, 2025, Georgia’s PSC announced unanimous approval of an agreement for a major generation expansion serving large-load growth. The announcement describes a utility financial backstop for 2029–2031 and notes that staff had questioned the risk of building before all anticipated customers had signed. It expressly says the PSC does not approve data-center locations or construction. [89]
Keep source versions visible
The December release states 9,885 MW, while the commission’s September 2026 fact sheet states 9,985 MW. This report therefore describes the package as approximately 10 GW rather than silently selecting or reconciling the figures. The later fact sheet also reports additional contractual developments. These different dated documents should not be treated as identical snapshots. [86][89]
Comparative interpretation
The policy problem is how to build ahead of demand without placing all forecast risk on existing customers. A financial backstop can help allocate that risk, but its duration and conditions matter. Protection through a specified year is not equivalent to protection over an asset’s entire useful life.
The growth case is that timely resources may allow new economic activity and spread some fixed costs across more usage. The caution is that customer contracts, resource construction and realized demand do not necessarily proceed at the same speed. An approval is a commitment to a regulated pathway, not proof that every projected benefit has already occurred.
Decision lesson
For comparable cases, report approved capacity separately from operational capacity and forecast consumption. Identify who bears shortfall risk and for how long. Keep annual updates versioned so revised figures are not blended into a misleading trend. This approach preserves the legitimate scale of the decision while avoiding false precision about its ultimate delivery or effect on rates.
Texas SB 6: making large-load growth a system-planning issue
Texas / ERCOT region · Enrolled legislation: 2025 · Implementation requires rules and procedures
Dated legislative framework
Texas Senate Bill 6’s enrolled text addresses planning, interconnection, operation and costs for certain large electrical loads. It directs the Public Utility Commission to establish large-load interconnection standards, includes customer contributions to interconnection costs and creates mechanisms for large-load demand management. The House Research Organization’s May 26, 2025 analysis explains the bill’s development rationale and concern about stranded infrastructure. The enrolled act, rather than that earlier analysis, is the controlling legislative text. [90][91]
Scope matters
The legislation addresses the ERCOT region and specified customers; it is not a municipal rezoning approval or a guarantee of service to every announced project. It also should not be read as a blanket ban on data centers.
Comparative interpretation
Texas illustrates a shift from treating each load request as a bilateral development opportunity toward assessing its wider system consequences. The balancing act is familiar: preserve investment opportunities while establishing commitments sufficient to support reliable, economical planning.
Growth supporters can reasonably value clearer interconnection processes and more credible project queues. Other customers can reasonably seek protection from speculative requests that prompt costly work and then disappear. These objectives are not inherently incompatible, but the implementation details determine how much risk and flexibility each party retains.
Decision lesson
For project comparisons, distinguish the law’s enactment from the adoption of implementing rules and from an individual project’s completed study. A campus described as “announced” may still face several independent gates. Public reporting should identify those gates without exposing operational details. The useful analytical comparison is with Ohio and Georgia’s customer-commitment mechanisms: all address allocation and credibility, although their market structures and legal instruments differ. It would be misleading to copy a tariff percentage from one state and assume Texas uses the same model.
ERCOT: why preliminary demand figures need a qualification
Texas grid planning · Forecast release: April 15, 2026 · Methodology update: May 2026
Dated forecast process
ERCOT’s April 15, 2026 release describes a preliminary 2026–2032 outlook assembled from its base economic forecast and information from transmission and distribution companies working with medium and large customers. ERCOT explicitly presented the results for further discussion and refinement. [92]
Its May 2026 CEO update describes a request to adjust the forecasting method, including an approach that discounts utility-reported figures using historical realization rates. The document also discusses timing implications for the capacity-demand-reserves reporting process. This is evidence that forecast quality and realization assumptions were active policy questions, not that every reported load had become a firm operating requirement. [93]
Comparative interpretation
The distinction between a request, a commitment and an operating load is particularly important when the proposal pipeline grows quickly. Raw requests can be useful signals of interest while still being unsuitable as a one-for-one forecast of future consumption. Alternative sites, phased construction and changing customer plans can produce divergent outcomes.
The opposite error is to dismiss all proposed load because some portion will not materialize. Forecasting is a decision under uncertainty, and the public needs to see both the range and the method used to convert project information into planning assumptions.
Decision lesson
When comparing ERCOT with PJM, align the forecast vintage, horizon, definitions and treatment of project maturity before comparing headline numbers. Do not present a preliminary pipeline total as an observed peak. Track later revisions as new evidence rather than as automatic proof of institutional failure. For an investment presentation, the defensible conclusion is that demand growth is large enough to require revised planning processes; the amount, timing and resource response remain conditional on projects reaching their successive milestones.
Chandler: a local ordinance built around notification and sound
Arizona · Unanimous adoption: December 5, 2022 · Effective January 5, 2023
Dated local action
Chandler’s January 11, 2023 announcement documents a unanimously approved data-center zoning amendment. It defines data centers as a primary use permitted through planned-area-development zoning and distinguishes smaller ancillary uses. The city also introduced neighborhood communication, pre-construction sound studies, mitigation obligations and annual sound reviews during the first five operating years. [94]
Why the sequence matters
The announcement links the rules to changes in the industry and growing neighborhood concerns. Its significance is the combination of land-use classification and post-approval follow-through. The dated ordinance should not be represented as the complete current code without checking subsequent amendments, and this historical case does not establish the outcome of a later individual application.
Comparative interpretation
Chandler’s approach resembles Fairfax’s emphasis on measurable compatibility but gives particular weight to communication over time. The pre-construction baseline creates a reference point; the later reviews ask whether actual performance matches the intended standard. Those steps are stronger together than either a public meeting without measurements or a technical report that residents cannot access.
For developers, a defined process can clarify expectations and reduce disputes about what was promised. For neighbors, its value depends on the quality of evidence and the credibility of enforcement. A communication protocol is useful only if there is a responsible party and a practical route to resolving problems.
Decision lesson
Evaluate the complete cycle: baseline, design, approval, operation, measurement and remedy. Keep public summaries understandable and avoid implying that any one cooling approach universally eliminates environmental impacts. The transferable lesson is that a locality can permit a specialized industrial use while requiring a specific accountability framework. It is not evidence that all data centers in a desert climate have identical water, noise or electricity profiles.
Arizona’s commission workshop: discussion is not an adopted tariff
Arizona utility policy · Public workshop: April 16, 2026 · Distinguish options from final decisions
Dated regulatory record
The Arizona Corporation Commission held a large-load and data-center workshop on April 16, 2026 under Docket E-00000A-25-0069. Its official notice established an open-meeting forum, and its subsequent summary discussed a possible hybrid approach using a universal large-load tariff and customer-specific energy-service agreements. The commission described the importance of assigning costs to large customers while supporting economic development. [95][96]
What is established
The record verifies a public regulatory discussion and the options considered. It does not, by itself, verify that a universal tariff was adopted at that workshop. The distinction is essential when a policy proposal is repeated in market summaries as if it were already enforceable.
Comparative interpretation
Arizona highlights the choice between standardization and tailoring. A common tariff can make requirements easier to compare; a special agreement can reflect unusual project characteristics. Either can be protective or inadequate depending on its terms. The instrument’s name does not answer questions about stranded costs, duration or reporting.
The public forum also creates a place to distinguish utility questions from municipal ones. City officials can influence land use, but a local development agreement does not necessarily govern a regulated utility’s recovery of system costs. Conversely, a satisfactory power arrangement does not settle whether a particular use fits a community plan.
Decision lesson
Build policy-status tables with separate fields for proposal, hearing, adoption, effective date and judicial review. Attach the relevant document to each change. This avoids overstating certainty and lets businesses plan around genuine regulatory progress. The case is valuable precisely because it captures a decision-making stage: it shows the questions a growing market must resolve, rather than providing a finished answer that can be generalized to every Arizona service territory.
Oregon POWER Act: a distinct class for large computing loads
Oregon · Legislation: HB 3546, 2025 · Utility-by-utility implementation
Dated state framework
Oregon’s Department of Energy describes HB 3546 as requiring new terms and a separate service classification for qualifying large energy-use facilities. The law’s definition includes facilities able to use at least 20 MW and primarily engaged in the specified computing-infrastructure category. The department identifies cost shifting and related risks as the policy concern. [97]
In a November 2026 release, the Oregon PUC reported approval of a [*REDACTED*] framework under the law. That implementation record is distinct from the statute itself and from other utilities’ proceedings. The threshold does not mean every commercial electricity user is placed in the same class. [98]
Comparative interpretation
Oregon offers a useful comparison with the Ohio tariff case. Both use classification and service terms to recognize that very large computing loads can differ from ordinary commercial customers. Oregon’s legislative route, however, establishes a statewide framework implemented through utility proceedings rather than a single utility case standing alone.
The benefit of classification is analytical clarity: regulators can examine the costs and risks of a defined group instead of hiding them in a broad average. The limitation is that classification is only the beginning. The allocation method, contract terms and exceptions determine the practical result.
Decision lesson
Report the statute, utility proceeding and approved schedule separately. Do not apply one utility’s rate impact to customers of another utility or to every facility in the state. For local leaders, an electricity policy is also not a substitute for evaluating land-use, water or fiscal effects. A balanced assessment recognizes that additional demand can help spread some existing costs while new infrastructure can add others. The central question is whether the approved mechanism assigns those effects transparently and withstands changing utilization over time.
Port Washington: zoning and fiscal agreements are separate gates
Wisconsin · Zoning step: April 15, 2025 · Fiscal record: November 2025
Dated municipal sequence
Port Washington’s April 23, 2025 FAQ states that its Common Council approved a new zoning district on April 15 to establish a framework for a potential data-center development. Its November 4 fact sheet states that a development agreement with [*REDACTED*] had been approved and describes further annexation, zoning and tax-incremental-district actions. The city characterized the district as a way to deliver infrastructure benefits while shielding taxpayers from project costs and risk. [99][100]
The TID No. 5 resolution is a separate official fiscal instrument, including statutory findings and intergovernmental arrangements. That separation matters: a new zoning category, a development agreement and a financing district are not interchangeable approvals. [101]
Comparative interpretation
The case shows how a large development can require a sequence of coordinated public decisions. Supporters may view that package as a way to capture investment and improve infrastructure. Skeptics may focus on whether the financial commitments are enforceable if growth, valuation or timing falls short.
A city’s statement that an arrangement protects taxpayers should be reported as its policy position, not as a guarantee that no risk exists. The economic evaluation depends on the actual agreement, the timing of revenue and expenditures, and the obligations that survive a delay or ownership change.
Decision lesson
Review the development agreement and financing plan together. Separate projected assessed value from collected revenue and distinguish a tax increment from unrestricted revenue available for other services. Publish understandable milestone updates so residents can see which decision is before the council and which has already occurred. The transferable lesson is neither that tax-increment financing is always beneficial nor that it is automatically a subsidy without return; it is that the complete contractual and fiscal sequence must be examined.
Northern Indiana: large investment announcements need performance accounting
Indiana / New Carlisle region · State announcement: April 25, 2024 · Planned investment and jobs
Dated economic-development record
Indiana’s Economic Development Corporation announced on April 25, 2024 that [*REDACTED*] planned an $11 billion data-center campus in north-central Indiana and at least 1,000 new jobs. The state described a package including data-center sales-tax exemptions and performance-based credits tied to investment and employment. These were announcement-stage commitments, not a contemporaneous statement that all capital had been spent or all positions filled. [102]
Why the case matters
The size of the announcement made it important to state and regional development policy. It also creates a need for careful longitudinal reporting. A later operating milestone at part of a campus does not necessarily establish completion of the entire announced program.
Comparative interpretation
The case illustrates the difference between an incentive offer and a realized public return. Performance-based provisions can improve accountability, but the relevant questions are what triggers the benefit, how performance is verified and what happens if commitments are missed. An exemption’s nominal duration is also not the same as its present-value cost.
Construction, continuing operations and supplier activity should be tracked separately. Local communities may value the addition of a large taxpayer and associated work while still questioning land-use change, public infrastructure commitments or the number of durable jobs relative to capital intensity.
Decision lesson
Create a scorecard that follows the project through actual investment, employment, tax payments, incentive use and publicly funded services. Keep company, state and county measures distinguishable so numbers are not counted twice. Compare the result with plausible alternative development rather than with vacant land forever. This framing neither discounts a major investment nor assumes that a headline dollar figure proves the package’s value. It converts the announcement into a set of measurable commitments that can be assessed over the years in which the project develops.
Louisiana: keep separate utility applications separate
Richland Parish / [*REDACTED*] · Initial approval: August 2025 · Additional docket: 2026
Dated approvals and applications
[*REDACTED*]’s August 20, 2025 release reports LPSC approval of an agreement for generation and transmission investments connected to [*REDACTED*]’s Richland Parish development. The utility presented the agreement as supporting both the customer and the wider system. That is an identifiable approval milestone, not proof that the approved resources were already operating. [103]
The commission’s Order U-37882-A, decided August 12, 2026, concerns a different proceeding. It describes a March 2026 application for additional resources associated with [*REDACTED*] subsidiary [*REDACTED*] and refers separately to the earlier U-37425 approval for Laidley. The August order addresses a procedural document dispute; it should not be misreported as final approval of every resource sought in the newer application. [104]
Comparative interpretation
Louisiana demonstrates how a single corporate brand can sit over multiple legal entities, phases and utility dockets. Treating them as one undifferentiated “approved campus” can materially overstate progress or double-count capacity. Conversely, continuing review of an expansion does not negate a prior authorization.
The economic attraction is a potentially large addition to regional investment and demand. The public-interest question is how costs, timing and benefits are divided when utility assets serve a very large customer. A utility’s promotional account is primary evidence of its position, but not independent proof that every promised benefit will occur.
Decision lesson
Maintain a docket-level crosswalk identifying the customer entity, requested action, decision date and decision type. Separate application, procedural order, settlement approval and operation. Avoid adding capacity numbers from related announcements until overlap has been resolved. This discipline is especially important for a staged development whose energy arrangements evolve over several years, because the same brand name can appear in records describing materially different commitments.
Saline Township: conditional service approval and contested public trust
Michigan · MPSC decision: December 18, 2025 · Utility authority differs from land-use authority
Dated decision
Michigan’s PSC reviewed [*REDACTED*]’s request for special contracts with [*REDACTED*] for a proposed Saline Township data center. Its December 18, 2025 order addressed a 1.383 GW service arrangement. The commission’s issue brief distinguishes its authority over utility rates and terms from other approvals associated with the development. [105][106]
A documented disagreement
On the same day, Michigan’s Attorney General criticized the expedited, ex parte process and the limited public visibility of contract details. That statement is evidence of a public official’s objection, not a judicial finding that the order was unlawful. The approval and the criticism should both be represented accurately, without treating either as the other’s final resolution. [107]
Comparative interpretation
The case exposes two different meanings of protection. Regulators can conclude that contractual conditions protect other customers while critics argue that the review process does not provide enough access to test that conclusion. The disagreement is partly about economics and partly about the legitimacy of the procedure.
Speed has real value when equipment, financing and construction schedules must align. Transparency and a credible opportunity to challenge assumptions also have value, especially where commitments are large and long-lived. A balanced account should not imply that expedited review is automatically reckless or that a conditional approval eliminates all legitimate questions.
Decision lesson
Identify exactly what was approved, the conditions attached and the forum responsible for other permissions. Separate public comments, agency findings and later legal actions. For communities evaluating similar projects, accessible explanations of risk allocation are important even when some commercially sensitive details remain confidential. The lesson is to make the reasoning inspectable enough to sustain public confidence, while avoiding claims that utility-service approval alone demonstrates local consent or completed construction.
Susquehanna and PJM: a specific rejection can lead to broader rulemaking
Pennsylvania / PJM · FERC actions: November 2024 and December 2025 · Co-location is not exemption from cost allocation
Dated regulatory sequence
FERC’s November 1, 2024 Susquehanna proceeding addressed proposed changes to a particular interconnection agreement for co-located load. The disposition should not be reduced to a permanent national prohibition on pairing generation and data centers. The specific filing and its governing requirements were the issue. [108]
On December 18, 2025, FERC unanimously directed development of new PJM transmission-service pathways for co-located arrangements. Commissioners’ official explanations emphasize flexibility alongside reliability and protection against unjustified cost shifts. They also identify further compliance and rate-development work rather than suggesting every implementation detail was already settled. [109][110]
Comparative interpretation
The attraction of co-location is understandable: customers seek timely power and generators seek durable demand. But physical proximity alone does not determine whether other users provide services, bear costs or lose access to output they previously relied upon. The commercial arrangement and the regulated service framework must be considered together.
This is a useful counterexample to simplistic claims that private power arrangements sit entirely outside public review. It also cautions against assuming that regulatory uncertainty means the idea is impossible. A rejected filing can prompt a clearer framework, while a framework can still require individual compliance and approvals.
Decision lesson
For comparative project reporting, distinguish a bilateral supply contract, a grid-service agreement and a final regulatory determination. Specify the decision date and avoid carrying a 2024 outcome forward as if later actions did not exist. The defensible economic conclusion is that access to suitable power is a central development constraint and that clear allocation rules can influence investment timing. It does not follow that any particular fuel, generator or campus has an automatic entitlement to favorable treatment.
Browse: White Papers · Reports · Downloads
