Residents urge long pause as council hears weeks-long debate over data centers; industry and labor push back

A packed public hearing on June 16 stretched across the council docket as hundreds of residents, advocates, technical experts and industry representatives weighed in on two competing proposals to pause new data center development in Montgomery County.

Supporters of a longer pause told the council that the scale of new hyperscale, AI-focused data centers requires time to craft enforceable rules on energy, water, noise, pollution and community protections. "We support two years to work out these details," said Karen Metchus of the Montgomery Climate Coalition, arguing the county needs time for climate, water and noise standards and meaningful public review. Environmental advocates repeatedly raised concerns about water withdrawals, potential PFAS contamination, diesel backup generators, continuous tonal noise, and impacts to the Potomac watershed.

Speakers cited local and regional evidence. "Data centers use diesel backup generators that pollute the air nearby," said Madison Matthews of Sunrise Movement, and multiple witnesses pointed to experience in Virginia and other states where communities have documented water and air impacts and sought remediation or litigation. Adrienne Momin cited peer-reviewed studies and analyses attributing health and economic costs to data center-related emissions and urged stricter controls.

Developers, some unions and business groups pushed back, warning that moratoriums would chill investment and cost construction jobs. "We share your concerns and have tried to address them," said Jeffrey Farrell, representing Terra Energy's Dickerson project, saying developers had planned forest preservation, battery storage and paid transmission upgrades. The Montgomery County Chamber of Commerce and construction unions said the county risks losing jobs and tax revenue if it closes the door on new projects while surrounding jurisdictions compete for infrastructure investment.

Several witnesses proposed middle paths: one-year pauses with predefined extension triggers; moratoria tied to adopting a new zoning ordinance and companion regulatory bill; or a format that allows a project to proceed if it enters a binding community benefits negotiation that addresses energy, water, workforce and fiscal protections. Steve Shapiro of Praxis Energy described a model in which a fully negotiated, enforceable community agreement could allow a project to move forward only when it meets a long list of binding requirements.

Council members who sponsored the moratoriums told the hearing they were seeking time to develop standards rather than blanket bans. Supporters of a two‑year moratorium framed it as a period to produce a binding regulatory framework and concrete deliverables; opponents said six months was already under executive order and that further delays would impair competitiveness for life-sciences and federal research tenants that rely on local high-performance computing.

The hearing record included technical testimony on possible mitigation measures — on-site generation, hour-by-hour clean energy matching, advanced cooling technologies that minimize water use, stronger noise limits and transparent reporting obligations for developers — as well as repeated calls for independent, county‑commissioned studies on cumulative impacts.

The council did not vote on the moratorium measures on June 16. The hearing closed after more than three hours of testimony and the council signaled subsequent committee work sessions and potential amendments to draft a regulatory package.

What happens next: the council’s economic development and planning committees are expected to schedule follow-up work sessions to reconcile different moratorium language and the zoning text amendment. Proponents want a timeline that ensures the moratorium remains in effect until written regulations and enforcement mechanisms are adopted; opponents want more limited pauses tied to concrete milestones.