top of page
Glossy 3D 48PEGASUS Logo.png

Data Centers, Energy Use, and Local Backlash

Policy choices and implementation

A permission framework, not a blanket verdict

Policy design · Proposed framework · Local authority varies

Separate the decisions
A data center is simultaneously a land-use proposal, a major utility customer, a construction project, and an ongoing industrial operation. Permission in one arena should not be represented as approval in every other arena. A locality can approve a site without promising electric service; a utility study does not establish compatibility with neighboring homes.

Establish the public objective
The recommended objective is development that pays its attributable costs, fits the location, and operates within measurable limits. This is different from either maximizing announced investment or prohibiting a technology category. DOE identifies cost allocation, stranded investment, resource adequacy, and technology risk as distinct large-load rate-design issues.
[111]

Use a decision ledger
For every proposed campus, maintain a ledger identifying the approving body, governing standard, evidence received, unresolved issue, and next decision date. Classify commitments as legally binding, conditional, voluntary, or aspirational. A press release, a utility reservation, and an enforceable permit condition should never receive the same status.

Assign the burden of proof
Require applicants to demonstrate feasibility with project-specific studies before receiving irreversible commitments. Give agencies enough resources to evaluate those studies independently. Applicants should know the evidence requirements early, while residents should be able to see what remains uncertain and what would cause approval to be withheld.

Adopt gates rather than promises
Recommended gates are site suitability, utility readiness, construction authorization, commissioning, and operating compliance. Each gate should have an accountable decision-maker and documented completion criteria. Expansion should reopen affected gates when electrical demand, water demand, generation equipment, or neighboring exposure materially changes. These are proposed governance practices, not a claim that every jurisdiction already requires them.

Moratoria versus targeted siting controls

Choice architecture · Time-limited pause · Predictable exit

What a pause can accomplish
A temporary moratorium can create breathing room when existing ordinances do not address the scale or characteristics of incoming projects. It is most credible when tied to a defined information gap, a funded work program, and an end date. An indefinite pause without deliverables can preserve uncertainty rather than resolve it.

What targeted rules can accomplish
Siting controls can distinguish locations and operating designs instead of treating every facility identically. Loudoun adopted changes in March 2025 moving certain previously by-right data-center uses into conditional or special-exception review. Its ongoing standards project separately addresses use-specific requirements. That is an example of procedural restructuring, not a nationwide template.
[112]

Compare the risks
A pause may prevent commitments before a community understands consequences, but it can also delay compatible projects and displace demand elsewhere. Immediate permissive zoning may shorten development schedules while exposing residents to poorly characterized impacts. Neither approach removes the need to resolve electric capacity, water supply, or enforceable operating conditions.

Recommended pause protocol
If counsel confirms authority, define covered applications, treatment of existing rights, essential exemptions, the study schedule, and objective expiration criteria. Publish interim findings. Avoid implying that a local pause suspends separate state or federal proceedings. Reconcile the measure with statutory deadlines and vested rights before adoption.

Recommended exit protocol
Replace a pause with mapped suitability criteria, complete-application requirements, measurable performance conditions, and a review pathway for modifications. Evaluate success by whether decisions become better supported, not whether the pause produces universal approval or rejection. Local counsel should assess the specific ordinance, procedural requirements, and challenge risks.

A siting screen that includes the whole system

Land-use screening · Cumulative effects · Alternatives

Screen before negotiating
Begin with a spatial screen of residential receptors, schools, water constraints, flood exposure, habitat, cultural resources, transportation access, and existing industrial uses. Add substations, transmission corridors, fuel infrastructure, and potential expansion parcels. A campus boundary is too narrow if its enabling infrastructure creates substantial impacts elsewhere.

Avoid false precision
A suitability score is a screening aid, not a substitute for judgment. Distinguish exclusion criteria from issues that can be mitigated and from preferences that merely improve a proposal. Publish data dates and missing layers. Do not turn an unknown water constraint into a favorable score simply because the database lacks an entry.

Require genuine alternatives
Ask applicants to compare a smaller first phase, different equipment placement, alternative cooling, and alternative access routes. The objective is a feasible lower-impact configuration, not an exercise proving that the preferred design is inevitable. Describe costs and residual impacts rather than asserting that every mitigation is free.

Make setbacks functional
Use buffers to achieve a documented outcome, supported by acoustic modeling, visual analysis, fire access, and maintenance needs. A setback alone may not control elevated equipment or transmission impacts. Loudoun’s standards initiative includes both data centers and utility substations, illustrating why related uses belong in the same planning conversation.
[112]

Decision deliverable
The recommended staff report should identify suitable, unsuitable, and conditionally suitable elements; summarize alternatives; and show the remaining impact envelope at full approved buildout. Record why the selected configuration is preferable. Where material evidence is missing, defer that decision rather than masking uncertainty with a generic condition to study the issue later.

Protecting households through utility cost recovery

Affordability · Cost causation · Commission jurisdiction

Separate the bill components
Electric affordability analysis should distinguish customer-specific facilities, shared distribution, transmission, generation or purchased power, and administrative costs. A developer paying for a substation does not establish that all other customers are protected. Conversely, every system investment near a project is not automatically caused exclusively by that project.

Establish a counterfactual
Ask the utility to compare a documented no-project case with staged project cases. Show timing, capacity, financing assumptions, and the allocation of residual value. DOE’s large-load guidance explicitly identifies fair cost allocation and underutilized infrastructure risk as policy questions. The recommended response is transparent analysis rather than a universal surcharge chosen without evidence.
[111]

Test departures from plan
Model cancellation before construction, delayed occupancy, partial utilization, early closure, and successful full operation. Include a case in which other customers later use some infrastructure. A defensible agreement should recover attributable costs without charging the departing customer twice for assets whose value has already been recovered elsewhere.

Use the proper forum
Local governments should participate in relevant commission proceedings and obtain independent technical advice rather than promising retail rates through zoning. The regulator, utility, and applicant must establish which tariff and contractual instruments can implement protections. Municipal or cooperative arrangements may follow different governing structures.

Public-facing test
Publish a plain-language bill-impact assessment showing assumptions and uncertainty, alongside protected confidential exhibits where necessary. State what the mechanism protects against and what it does not. A minimum bill can address underutilization risk without guaranteeing that fuel prices, regional capacity prices, or every household bill will remain unchanged.

Large-load tariffs: commitments that survive a slowdown

Contract design · Collateral · Exit protection

A concrete precedent
Ohio’s consumer advocate reports that the July 2025 [*REDACTED*] settlement required large new data centers to pay for at least 85 percent of contracted capacity for terms reaching twelve years. It also notes subsequent industry appeals. The example illustrates the direction of risk protection; it should not be copied without checking the current approved tariff and case status.
[113]

Match commitment to exposure
The recommended contract term should reflect the life and recoverability of investments actually undertaken for the customer. Evaluate minimum billing demand, ramp schedules, credit support, cancellation payments, and termination obligations together. A long nominal term offers little protection if the obligor is an inadequately capitalized subsidiary with broad escape clauses.

Define milestones
Specify when capacity becomes reserved, when deposits become nonrefundable, and what evidence confirms readiness. Distinguish utility-caused delays from customer-caused delays. Avoid spending ahead of credible construction and financing milestones merely because a customer has announced a large campus.

Make collateral usable
Require periodic review of guarantees, letters of credit, or other approved security. Assign responsibility for monitoring expiry, downgrades, and corporate restructuring. The agreement should explain how additional security is requested, what happens during a dispute, and how recoveries interact with subsequent use of the assets.

Preserve proportionality
Size thresholds and aggregation rules should prevent strategic fragmentation while recognizing that smaller or genuinely flexible customers may impose different risks. Publish the rationale for distinctions. The goal is adequate protection and fair treatment, not punitive pricing based on a company’s visibility or a presumption that every data-center load has identical characteristics.

Queue discipline and staged energization

Readiness evidence · Avoid double counting · Phased service

Treat announcements as a pipeline
An announced campus, a signed service agreement, a funded construction program, and energized load are different states. Maintain separate totals rather than adding them into one demand forecast. EPRI’s 2026 assessment explains that nominal IT capacity requires assumptions about ancillary loads, utilization, and ramp rates before it becomes a peak-demand forecast.
[114]

Verify commitment
Recommended readiness evidence includes site control, credible financing, a realistic equipment schedule, permit status, and a load profile that distinguishes initial operations from ultimate buildout. Require periodic confirmation and identify related applications that might represent alternative sites for the same underlying demand. Avoid publishing commercially sensitive details unnecessarily.

Reserve in increments
Offer phased capacity where technically and legally feasible. Tie subsequent increments to demonstrated utilization or binding commitments, not automatic calendar dates alone. A smaller first stage can reduce speculative infrastructure exposure while preserving a credible route to expansion.

Explain queue consequences
Transparent rules should describe study charges, deposits, withdrawal treatment, restudies, and the effect of a major design change. Readiness-based sequencing may improve planning, but criteria should be objective and consistently administered. Otherwise, discretion can advantage sophisticated applicants and undermine confidence among smaller customers.

Decision checkpoint
Before each major utility expenditure, reconcile the forecast with current project evidence and disclose material changes to the relevant decision-maker. Do not silently replace withdrawn demand with another speculative project to preserve a capital plan. A forecast revision is useful information, not necessarily a planning failure; the failure is refusing to update commitments when evidence changes.

Flexibility must be measurable, not promotional

Demand response · Verified delivery · No double counting

Identify the actual resource
A promise to be flexible can mean delaying computing work, moving work to another site, using batteries, reducing noncritical cooling, or starting generators. These mechanisms have different reliability and environmental consequences. LBNL’s DOE workshop summary identifies flexibility opportunities alongside cost and regulatory barriers; it does not establish that every workload can be interrupted.
[115]

Specify the service
Recommended contracts should state reducible megawatts, notice time, duration, event frequency, seasonal availability, rebound behavior, and the measurement baseline. Identify which operations remain critical. A commitment that is valuable for a short peak may not address a multiday shortage or a local transmission contingency.

Test before crediting
Require commissioning demonstrations and periodic performance tests before counting flexibility as dependable capacity. Account for simultaneous failures and correlated demand across campuses. A customer should not receive multiple credits for the same reduction unless the market rules explicitly permit that treatment.

Keep environmental accounting intact
Track whether demand reduction shifts electricity consumption to another time or place, or substitutes on-site combustion. Report generator operation and emissions under applicable permits. A reduction at the utility meter is not automatically a reduction in total energy use or pollution.

Reward real value
Compensation should reflect demonstrated system benefit and the customer’s actual obligations. Include nonperformance consequences, baseline dispute procedures, and a process for revising commitments as workloads change. Where service is interruptible, make the limitations clear to the operator and to affected public agencies. Do not promise firm reliability while planning around an interruption right that cannot practically be exercised.

Noise conditions built around lived exposure

Acoustics · Commissioning · Enforcement

Measure the right problem
Persistent mechanical sound can be intrusive even when a single headline decibel figure looks acceptable. Require qualified analysis of operating conditions, background levels, tonal characteristics, low-frequency components, and nearby sensitive receptors. The test should consider the approved equipment configuration and cumulative operation, not only a single isolated machine.

Use an established procedural model
Loudoun describes preconstruction noise studies and postconstruction testing within a specified period after initial occupancy. It also identifies tonal and low-frequency noise as subjects of further policy work. These practices illustrate the importance of both predictive review and field verification, without establishing a universal numerical standard.
[116]

Write executable conditions
Recommended conditions should specify measurement locations, instruments, weather constraints, operating states, averaging periods, reporting format, and who resolves disputed results. Limits need a legally grounded acoustic rationale. A condition to avoid unreasonable noise is harder to administer than a measurable standard with a defined test method.

Test realistic operating modes
Include normal cooling, hot-weather operation, generator testing, phased expansion, and combinations of equipment likely to run together. Differentiate lawful emergency operations from routine maintenance. Inspect barriers and silencers as installed, not merely as drawn. Require corrective action where equipment changes invalidate the approved model.

Provide a remedy pathway
Create a complaint channel with response deadlines and independent verification where warranted. Protect residents from having to finance technical proof themselves. Fund enforcement capacity through legally available mechanisms, and establish escalation procedures before operation begins. Do not promise that vegetation alone will control industrial sound or that a compliant model guarantees no resident will notice the facility.

Water conditions that survive drought

Water accounting · Cooling choice · Seasonal limits

Ask for a water balance
Require estimates of withdrawals, consumptive use, discharge, source quality, and seasonal peaks. Separate potable supply, reclaimed water, and other sources. Identify the operational assumptions behind each figure. A facility’s annual average can obscure its impact during the hottest period, when community demand and cooling needs may rise together.

Compare designs honestly
DOE’s federal data-center cooling guidance explains how evaporative systems remove heat and identifies water-efficiency opportunities. Policy should evaluate the entire cooling design rather than assuming liquid cooling necessarily means high consumptive water use, or that a closed internal loop eliminates water used elsewhere in heat rejection.
[117]

Establish a drought hierarchy
Recommended supply agreements should define drought stages, reporting triggers, conservation obligations, curtailment expectations, and the authority to activate them. Test whether the operator’s proposed backup strategy is practical. Switching abruptly to another source can transfer rather than solve the community’s constraint.

Price infrastructure transparently
Identify treatment, storage, pipeline, pumping, and wastewater investments attributable to the project. Separate capacity reservations from actual consumption charges. Evaluate who pays if demand never materializes and whether other users benefit from the upgrades. Reclaimed water may be useful, but its availability, treatment requirements, and conveyance cost require evidence.

Verify performance
Install appropriate meters and report seasonal totals alongside operating load so comparisons remain meaningful. Require a review when equipment, water sources, or approved demand changes substantially. Avoid an unconditional water guarantee based only on current average supply. The defensible condition is a source-specific operating envelope supported by utility and environmental review, not a generic promise to be water positive.

Air permitting and backup power choices

Source inventory · Emergency distinction · Cumulative operation

Inventory all combustion
The permit review should identify every proposed engine, turbine, fuel source, exhaust location, operating mode, and expansion stage. Include temporary equipment where relevant rather than assuming its label determines regulatory treatment. Coordinate the inventory across building, land-use, and air-permitting records to prevent inconsistent descriptions of the same project.

Keep operating categories distinct
EPA maintains data-center-specific Clean Air Act resources addressing stationary engines and related permitting questions. Emergency operation, routine testing, demand-response participation, and continuous generation can have different regulatory implications. The applicable air authority should confirm the authorized operating envelope; a commercial contract cannot independently make a use legally emergency operation.
[118]

Evaluate the alternatives
Compare battery duration, cleaner engines, fuel choice, dispatch restrictions, and workload flexibility against reliability requirements. Do not call an alternative emission free merely because it moves combustion off site. Distinguish local pollutant exposure from broader greenhouse-gas accounting and identify the uncertainty in both.

Coordinate local exposure review
Recommended analysis should consider exhaust dispersion, nearby receptors, simultaneous testing, and other permitted sources using the standards required by the responsible regulator. Establish who reviews modeling changes when the equipment count grows. A campus may be built in phases while the surrounding community experiences the combined operating effect.

Monitor the permitted reality
Retain equipment identifiers, maintenance and testing logs, fuel records, operating hours, and required emissions-test results. Define incident notification and corrective-action responsibilities. Enforcement should follow applicable permits and law, with clear escalation for repeated violations. Avoid treating the existence of an air permit as evidence that nuisance, noise, water, or land-use questions have also been resolved.

The permit stack and its critical path

Agency coordination · No implied approval · Record discipline

Build one coordinated register
List land-use approvals, building and fire requirements, utility agreements, air permits, stormwater coverage, water and sewer authorizations, and any aquatic-resource approvals. Record which agency decides each issue, the prerequisites, public participation opportunities, and expiration or renewal requirements. The register is a management tool, not a claim that every project requires every listed authorization.

Separate concurrency from dependence
Some studies can proceed concurrently; others depend on a stable site plan or equipment specification. Recommended scheduling should identify decisions that would become invalid if the design changes. Starting earthwork before resolving a consequential constraint can create sunk-cost pressure that distorts later review.

Preserve agency responsibilities
USACE describes separate Clean Water Act Section 404 permitting and public notice processes for regulated aquatic impacts. Local zoning approval does not substitute for those determinations. Similarly, federal involvement and environmental-review requirements depend on the particular authorization, funding, and project circumstances, not simply the presence of a data center.
[119]

Create a modification rule
Require the applicant to notify the coordinating office when load, footprint, water demand, generation equipment, or access changes materially. The office should route the change to affected authorities rather than deciding outside its expertise that it is harmless. Maintain previous versions so reviewers can reconstruct the decision record.

Close the loop before operation
Use a commissioning checklist that records required inspections, executed agreements, monitoring installation, emergency coordination, and unresolved conditions. Distinguish permission to occupy a building from authorization to operate every proposed system. Publish an understandable status summary while protecting genuinely sensitive security information. A green status should mean the specified requirement is complete, not that someone expects completion soon.

Construction impacts deserve their own playbook

Sediment control · Roads and access · Temporary impacts

Plan for the disruption period
Residents experience truck traffic, grading, dust, lighting, and noise before a campus begins operation. Require a construction logistics plan identifying haul routes, delivery windows, worker parking, emergency access, and responsibilities across contractors. Consider overlapping construction projects rather than reviewing each schedule as if it were the only activity in the area.

Control runoff early
EPA explains that construction stormwater permitting generally applies to qualifying discharges associated with disturbance of at least one acre, including smaller sites within a larger common development plan. Determine the responsible permitting authority and coverage requirements for the actual project. Do not divide phases on paper to avoid evaluating the common plan.
[120]

Establish a baseline
Recommended preconstruction documentation should record relevant road conditions, drainage features, sensitive access points, and agreed monitoring locations. Use dated photographs and a complaint log. Baselines help distinguish project damage from preexisting problems and make restoration obligations less contentious.

Give residents usable notice
Publish major delivery windows, road closures, blasting proposals where applicable, and a staffed contact route. Notification is not permission to exceed a condition. Require contractors to escalate safety incidents and repeated nuisance complaints to an accountable owner representative, not merely another subcontractor.

Tie completion to restoration
Inspect stabilization, drainage performance, road repairs, removal of temporary installations, and unresolved damage claims before releasing relevant securities where lawful. Preserve inspection access and documentation after contractors demobilize. A construction bond should have an identified beneficiary, trigger, and renewal process. Its amount should reflect a defensible scope of remaining work rather than an arbitrary percentage of the project’s headline investment.

Community benefits without buying permission

Benefits agreement · Measurable delivery · Independent oversight

Keep obligations separate
A community benefit should not be used to excuse an unacceptable impact or replace an obligation already required by law. Separate mitigation, infrastructure cost recovery, taxes, and genuinely additional benefits in public materials. This prevents the same expenditure from being counted several times as a generous contribution.

Learn without importing obsolete rules
DOE’s 2024 community-benefits cost guide addressed particular federal financial-assistance programs and emphasized defined commitments. It is a historical design reference, not proof that its federal priorities remain a universal current requirement. Local agreements need their own authority, enforceable terms, and fair process.
[121]

Prioritize durable public value
Potential commitments include workforce training, independently administered community grants, emergency-service capacity, or infrastructure that also serves residents. Evaluate the recipient’s ongoing operating costs. A donated building or technology system can become a liability if there is no sustainable budget to maintain it.

Write an auditable agreement
Recommended terms identify the payer, beneficiary, amount or service, schedule, performance evidence, ownership of improvements, and remedy for nonperformance. Include assignment obligations so a sale does not erase commitments. Distinguish a binding agreement from a memorandum expressing intentions.

Protect the process
Disclose negotiations and conflicts according to applicable law. Include affected neighborhoods, not only established organizations or the easiest representatives to reach. Benefits should not require residents to surrender legitimate complaint rights or suppress evidence. Report delivery publicly against the original promises. A modest, reliable commitment is more useful than a large announcement that cannot be enforced or evaluated.

Fiscal realism: taxes, incentives, and downside cases

Net public value · Replacement cycles · Incentive discipline

Start with net revenue
Estimate property and equipment taxes, fees, abatements, public infrastructure spending, administration, and service costs across time. Keep local revenues separate from state revenues. Virginia JLARC found substantial potential local tax benefits alongside economic activity concentrated in initial construction; that combination supports a multiyear fiscal assessment rather than a headline investment comparison.
[122]

Model uncertainty explicitly
Recommended cases should vary buildout timing, assessed values, equipment replacement, tax treatment, and operating continuity. Show how much of the budget depends on a single taxpayer. Do not present projected tax receipts as guaranteed cash before the facility exists or assume a construction job remains after commissioning.

Ask the incentive question
What additional public benefit does the incentive purchase compared with the project proceeding without it? Identify the evidence for relocation or cancellation risk. An incentive should have a purpose beyond matching another jurisdiction’s offer, particularly when electric or water capacity is already scarce.

Condition rather than prepay
Where authorized, tie incentives to verified investment, operation, and specific deliverables. Include reporting, recovery provisions, sunset dates, and treatment of ownership changes. Counsel should assess enforceability and statutory constraints. Avoid promising clawbacks that the locality has neither the authority nor practical ability to collect.

Protect the budget
Consider reserving part of unusually concentrated revenue for stabilization and infrastructure replacement rather than immediately funding permanent recurring obligations. Publish the net present-value assumptions and a plain-language downside case. A project can still be attractive under conservative assumptions; disciplined analysis makes that conclusion more credible and exposes proposals whose apparent benefit depends on unrealistic optimism.

Jobs and procurement: count the right outcomes

Construction versus operations · Skills pipeline · Local access

Distinguish workforce categories
Report construction job-years, peak on-site workers, permanent employees, contractors, and indirect estimates separately. Explain whether a number describes people, positions, or cumulative labor over several years. JLARC’s Virginia assessment emphasizes construction as a major source of economic activity, so permanent-employment expectations should not be inferred from construction spending.
[122]

Connect training to actual roles
Recommended workforce agreements should identify occupations, qualifications, training providers, expected openings, and employer participation. Avoid enrolling residents in expensive programs based on vague assurances of future technology jobs. Electrical, mechanical, controls, safety, and facilities skills may be useful across employers even if a particular campus expands more slowly than expected.

Remove procurement friction
Publish realistic opportunities for local firms, including bid timing, insurance requirements, bonding, payment terms, and qualification assistance. Break opportunities into accessible packages where practical without compromising quality or safety. A local-spending target is not meaningful if only firms already able to navigate complex prime-contractor systems can compete.

Verify rather than advertise
Collect evidence of hiring, retention, wages where disclosure is appropriate, apprenticeships completed, and payments to local suppliers. Define the geographic meaning of local before announcing results. Prevent double counting through multiple subcontracting tiers and distinguish a branch mailing address from substantive local economic activity.

Balance ambition with fairness
Hiring or purchasing preferences must be evaluated under applicable law and contract requirements. The objective is broader access and durable skills, not unsupported guarantees that every job will go to a nearby resident. Establish a corrective process when commitments fall short, and report explanations honestly rather than substituting new metrics that make the original promise disappear.

A defensible public process

Early disclosure · Accessible evidence · Reasoned findings

Engage before the deal hardens
Publish the proposal, the decision pathway, and the major unresolved questions while alternatives remain possible. A public meeting held after infrastructure commitments and private negotiations are effectively complete may satisfy a calendar requirement without providing meaningful influence. Explain which decisions the locality controls and which belong to other bodies.

Make technical evidence usable
Recommended materials include a plain-language summary, maps, assumptions, study versions, and a question register. Provide accessible meeting formats and enough time to review consequential revisions. An executive summary should identify adverse findings and uncertainty, not function solely as a promotional introduction.

Support independent review
Use qualified reviewers with disclosed conflicts. Applicant-funded review can be structured through a public agency where authorized so that the applicant does not control the reviewer’s conclusion. Technical disagreement should be documented and resolved through evidence, not a vote on whose credentials appear more impressive.

Respond on the record
Maintain a response matrix linking substantive comments to analysis, design changes, conditions, or reasons for disagreement. USACE’s individual permitting framework illustrates the role of public notice in evaluating project impacts; local procedures must independently follow their governing requirements. Participation should inform the record even when it does not produce consensus.
[119]

Explain the final judgment
The recommended decision document should state findings, alternatives considered, conditions imposed, residual risks, and appeal or review routes. Avoid claiming unanimous support or zero impact when the record shows otherwise. A defensible process makes the basis of the decision understandable and contestable; it does not promise to eliminate political disagreement or immunize the decision from legal challenge.

Monitoring that changes decisions

Public dashboard · Thresholds and remedies · Data quality

Build a compliance register
For each binding condition, identify the metric, measurement method, responsible party, reporting frequency, reviewer, and response to failure. Separate compliance indicators from contextual information. A dashboard can show useful trends while still making clear that an attractive chart is not a regulator’s formal compliance finding.

Use a compact core
Recommended indicators include authorized and actual electrical demand, agreed water measures, generator operation, acoustic test status, construction incidents, and delivery of community commitments. Add project-specific indicators only when someone will use them. Excessive reporting can hide important failures in a mass of low-value data.

Preserve comparability
Record units, time zones, equipment boundaries, missing intervals, revisions, and operating conditions. Compare similar periods and configurations. When a campus adds buildings, distinguish changes in total impact from changes in efficiency. A lower intensity metric can coexist with a higher total burden on the community.

Design the escalation ladder
Set warning thresholds, investigation triggers, corrective deadlines, retesting requirements, and referral to the responsible authority. Reserve sanctions for the authority empowered to impose them. Loudoun’s pre- and postconstruction noise-study approach illustrates why predictive commitments need operational verification rather than remaining one-time application exhibits.
[116]

Keep public reporting credible
Publish validated summaries and describe suppressed or unavailable data. Protect security-sensitive details through proportionate controls rather than blanket confidentiality. Fund review and field verification, not just data collection. Conduct periodic independent audits of a sample of records. The test of monitoring is whether a material deviation produces a documented response, not whether the website displays an uninterrupted row of green symbols.

Expansion, transfer, and closure

Lifecycle obligations · Financial security · Change control

Plan beyond opening day
Approval should anticipate equipment replacement, ownership transfer, tenant changes, expansion, prolonged vacancy, and closure. A facility’s operating characteristics can change without a dramatic alteration to its exterior. Recommended change-control conditions should identify which modifications require notice, updated studies, amended agreements, or a new approval.

Preserve obligations on transfer
Require clear treatment of permit responsibilities, monitoring records, community commitments, utility liabilities, and financial security when ownership changes, subject to governing law. Do not assume an asset sale automatically carries every private promise. The public record should identify the responsible operating entity and an accountable contact after each transition.

Estimate closure costs
Consider removal or stabilization of hazardous materials, fuel systems, batteries, abandoned structures, and temporary installations as applicable. Determine which assets may reasonably be reused and which create residual public exposure. Avoid a generic assurance that valuable equipment makes abandonment impossible.

Secure the obligations
Where legally authorized and warranted, use financial assurance matched to a defined decommissioning or restoration scope. Review the estimate periodically and after material changes. Ensure the instrument names the correct beneficiary, survives foreseeable corporate events, and can be drawn under clear conditions. Do not confuse a parent’s current credit rating with permanent protection.

Coordinate with utility exit terms
Closure planning should reconcile physical restoration with outstanding service commitments and infrastructure recovery. DOE identifies stranded utility investment as a distinct large-load concern; local closure security should not be mistaken for a substitute for regulated cost-recovery protections.
[111] A complete exit plan identifies separate obligations, avoids double recovery, and explains who remains responsible when the project no longer produces revenue.

A ninety-day implementation playbook

Recommended schedule · Institutional capacity · No rushed approvals

Days one through thirty
Assign a lead coordinator and inventory legal authority, current applications, existing approvals, utility constraints, and staff capacity. Publish a simple map of decision responsibilities. Assemble planning, utility, environmental, emergency-service, finance, and legal expertise. Identify imminent deadlines that cannot safely wait for a broader policy exercise.

Establish the evidence package
Prepare proposed application requirements covering phased load, cooling, water balance, generation equipment, acoustics, construction logistics, and fiscal assumptions. Ask the relevant authorities to identify gaps and duplication. Use a common project identifier across agencies. This is a recommended work program, not a substitute for statutory review procedures or a promise that permits can be decided within ninety days. The evidence package operationalizes DOE’s distinctions among cost, capacity, and stranded-investment risks.
[111]

Days thirty-one through sixty
Test the proposed framework against a representative project and a cancellation scenario. Identify which conditions are enforceable, who would inspect them, and what monitoring would cost. Consult residents and applicants separately as needed, then disclose substantive concerns and proposed responses.

Days sixty-one through ninety
Finalize the policy package for the legally required adoption process. Deliver a permit register, model study scopes, an affordability-review checklist, a public reporting template, and a funded enforcement plan. Separate immediately usable administrative improvements from ordinance or tariff changes requiring a longer process.

Define success conservatively
The initial outcome should be better questions, clear accountability, and fewer unsupported commitments. Do not measure success solely by approvals issued or investment announced. Review the framework after its first applications and correct requirements that produce little decision value. Retain safeguards for unresolved high-consequence risks rather than allowing the schedule itself to become the reason for approval.

Decision matrix: approve, condition, defer, or reject

Explicit findings · Residual risk · Review triggers

Approve when the record supports it
Approval is most defensible when the location is suitable, required studies are complete, service arrangements are credible, cost responsibilities are defined, and operational limits can be monitored. The recommended finding should explain why residual impacts are acceptable under the applicable standards, not merely repeat that the project has economic value.

Condition what can be controlled
Use conditions for specific, feasible measures within the approving body’s authority. Identify performance evidence and a remedy. Conditions should not postpone resolution of a fundamental feasibility issue until after irreversible construction. A promise to obtain water later is different from an enforceable limit within an established water-supply plan.

Defer genuine uncertainty
A deferral should identify the missing evidence, who must provide it, and what decision it will inform. Avoid endless requests unrelated to governing criteria. Conversely, do not treat a consultant’s unsupported confidence as a substitute for the study needed to resolve a consequential uncertainty.

Reject with reasons
Where the record demonstrates an unacceptable location, unresolved essential capacity, or inability to meet governing standards, explain the basis and alternatives considered. Distinguish a rejection of this configuration from a judgment about every data center. Applicable notice, findings, and appeal requirements still matter when opposition is strong.

Revisit material changes
Set review triggers for major expansion, altered generation, water-source changes, persistent noncompliance, and ownership events where relevant. Maintain a clear boundary between enforceable conditions and voluntary aspirations. The overall policy position is neither automatic permission nor automatic exclusion: authorize only the development whose costs, impacts, and obligations can be understood and responsibly managed over its full life. This is an analytical synthesis, not an adopted regulatory standard.
[111] [112]

Exhibit 14 · Who bears the downside?

Distinguish estimates from enforceable obligations. This workflow begins with costs that do not arise in the without-project baseline, then tests the cost if demand fails to arrive.

48PEGASUS Research original conceptual exhibit. Not empirical data.

Exhibit 15 · Siting and staged approval

Advance a phase only when its verified infrastructure, permits and monitoring can support it. A materially changed scope returns to the applicable review process.

48PEGASUS Research original conceptual exhibit. Not empirical data.

Previous chapter

Next chapter

Back to the report

Browse: White Papers · Reports · Downloads

bottom of page