Questions to Ask Before a Data Center Is Approved

Questions to Ask Before a Data Center Is Approved

Before taking a position on a proposed data center, identify the exact decision, the complete project, the infrastructure it requires, who pays, what can be enforced, and what happens if the project expands or fails. The best public questions request a document, a number, a responsible authority, and a remedy.

This guide is a preparation tool, not legal advice. Zoning, utility regulation, environmental permits, public records, Tribal authority, hearing procedure, confidentiality, and appeal rights vary by jurisdiction. Use the current public notice and agency record, and confirm deadlines with the responsible clerk or agency.

First ask what is being decided

A public meeting may concern only one part of the project. A zoning body may decide whether the land use is allowed. A utility regulator may decide a tariff or service agreement. An air agency may decide a construction permit. An economic-development authority may decide an incentive.

One approval does not necessarily settle another.

flowchart TD
    A["Public notice or project announcement"] --> B["Identify the legal decision"]
    B --> C["Identify applicant, owner, operator, utility customer, parcel, and phases"]
    C --> D["Collect studies, contracts, permits, and public terms"]
    D --> E["Match each promise to an authority and enforcement method"]
    E --> F["Submit questions before the deadline"]
    F --> G["Compare approval conditions with measured operation"]

Read the notice for the case number, applicant, property, decision maker, record location, comment deadline, hearing date, and contact. If any of those are unclear, ask the clerk before debating the merits.

Establish the project identity

Large developments often involve a landowner, developer, operator, utility customer, tenant, and affiliates. A brand named in a press release may not be the legal applicant.

Ask for the legal names of the property owner, applicant, campus developer, facility operator, electric customer, water customer, parent or guarantor, and any entity receiving public assistance. Ask which obligations transfer if the project or land is sold.

The project description should show the parcel, acreage, number and size of buildings, phases, ultimate buildout, cooling systems, requested power, expected load ramp, water sources, generators or turbines, construction schedule, roads, and expansion rights.

A site plan for the first building is not a complete answer if the approval authorizes a multi-phase campus.

Use the question-and-document worksheet

The table below can be copied into a hearing note, records request, or reporting plan. The named records are categories. Their exact titles will differ.

The worksheet is most useful when each answer includes a source date and a named person or body with authority.

Ask for both MW and MWh

A power request stated only in megawatts is incomplete. Megawatts describe power or capacity. Megawatt-hours describe energy over time. The US Energy Information Administration explains that one megawatt maintained for one hour produces or consumes one megawatt-hour.

Ask for requested capacity, expected peak demand, annual energy, load factor or utilization assumption, load ramp by phase, and the date each phase expects service.

Then ask what the utility must build. A nearby transmission line or substation does not prove that capacity is available. The utility's studies and regulatory filings should identify constraints, facilities, schedule, and cost.

Berkeley Lab's large-load rate brief identifies the risk questions that should appear in the record. The tariff or agreement should address cost allocation, underused infrastructure, collateral, minimum payments, reliability, and exit.

Ask for a water balance

"Low water" is not a complete answer. Request a simple balance showing sources, uses, consumption, discharge, and conditions.

The record should state peak-day and annual volumes for each phase. It should separate potable, reclaimed, surface, and groundwater. It should distinguish withdrawal from consumptive use and explain drought restrictions, backup supply, wastewater volume, treatment, and infrastructure.

The US Geological Survey defines consumptive use as water that does not return to the immediate local water environment. The EPA explains that reclaimed water is treated for an intended reuse. Neither term should be inferred from a generic gallons figure.

Ask the water utility whether current rights, treatment, storage, and pipes can serve the project alongside expected residential, industrial, and drought needs. Ask who pays for upgrades and ongoing operation.

Reconcile the air-permit equipment list

Ask for every generator, engine, turbine, boiler, fuel system, and other relevant emission source. The equipment described by the developer should match the equipment evaluated by the permitting authority.

The EPA's data-center air resources explain that stationary engines and turbines can be subject to federal standards. Most permits are issued by state or local agencies. EPA's Clean Air Act Permitting System can help locate permit actions from participating authorities.

For each unit, ask about purpose, fuel, rated capacity, expected and allowed operating hours, startup, testing, controls, pollutants, combined emissions, modeling, monitoring, and enforcement.

A backup label does not answer how often equipment may operate. A permit does not prove zero emissions. The permit identifies the authorized conditions that can later be compared with operation.

Make noise measurable

Cooling equipment, fans, pumps, transformers, and generators can create different sound patterns. A single daytime A-weighted average may not capture constant or low-frequency sound.

The Virginia JLARC report found that most Virginia data centers did not generate noise complaints, while some sites near homes produced persistent concerns. It recommended authority for preapproval sound modeling and consideration of low-frequency metrics.

Fairfax County's adopted amendment uses pre- and post-construction studies with building, equipment, screening, and setback requirements.

Ask where measurements occur, which frequencies and operating conditions are included, how background sound is handled, whether simultaneous equipment operation is modeled, and what happens after a verified complaint.

The required remedy matters as much as the limit.

Test incentives against net public value

Ask for the gross value of every exemption, rebate, grant, land term, utility contribution, and public infrastructure commitment. Then ask for expected revenue, service costs, jobs, wages, procurement, milestones, reporting, audit rights, and clawbacks.

A company investment figure is not public revenue. A tax-receipt figure is not net fiscal value. A construction-job count is not a permanent operations count.

The agreement should define each promised outcome, the baseline, the measurement period, who verifies it, and what happens if performance falls short. It should also say whether obligations survive a sale, affiliate transfer, refinancing, expansion, or change in operator.

Ask who can enforce every answer

A public statement may be sincere and still be unenforceable. For every important commitment, identify the document that contains it, the party bound, the authority responsible, the reporting schedule, the cure period, and the remedy.

A zoning condition may govern land use. A tariff may govern electric payments. An air permit may govern equipment and emissions. A development agreement may govern incentives and jobs. A community agreement may create other obligations. These instruments do not substitute for one another.

[[How Community Benefits Agreements Can Govern Data Center Projects]] explains agreement anatomy and remains under a professional-review hold. Use qualified local counsel when authority, enforceability, public records, representation, or deadlines matter.

Keep expansion and closure in the first decision

Ask which changes require a new study, permit, hearing, agreement, or public notice. The list should include more buildings, higher load, a different cooling system, more water, new generators, changed fuel, ownership transfer, and a different operating model.

Then ask what happens if the campus never reaches full load. Utility assets may remain. Public infrastructure may still need maintenance. Incentive assumptions may fail. A large building may be difficult to reuse.

The initial record should contain load-ramp protections, successor obligations, decommissioning duties, financial security where appropriate, environmental closure, equipment removal, and a plan for public infrastructure.

Make the next comment specific

A useful public comment can be concise. Identify the case and decision. Cite the missing or conflicting record. Explain why it is material to the authority's legal task. Ask for a dated answer, condition, continuation, or other action that the authority can take.

Avoid assuming bad faith. A precise record request is harder to dismiss and easier for reporters, officials, and other residents to verify.

If the site itself is still uncertain, use [[How to Evaluate a Data Center Site]]. For the complete cost map, use [[How Data Center Costs Reach Local Communities]]. E076 then moves from scrutiny into design through cooling, clean power, siting, and governed community terms.

This guide was freshly written from the preserved E075 transcript and current official sources reviewed on July 27, 2026. AI assistance was used for research organization, drafting, and validation. Publication remains unauthorized.