Board debates 12‑month interim stay for data‑center applications, pauses BeltLine hearing

The Board of Aldermen spent the bulk of its July 21 meeting debating a proposed interim stay on applications for data‑center development and a related zoning text amendment that would require property proposed for annexation to be zoned at the same time as annexation.

Dozens of residents turned out to urge the board to adopt a pause before new data‑center permits can be accepted. "In 12 months, you're gonna think to yourself, wow. We've really dodged a bullet here," said Janine Kreider, who identified herself as a resident of Chachar Lane, Robertsville. Multiple speakers told the board they were worried about noise, environmental effects, and safety concerns tied to large‑scale data facilities.

The ordinance before the board would impose a 12‑month interim stay on the acceptance of applications "for any permit or approval related to the development, zoning, permitting, or use of property for data centers of all sizes," to give staff and the Planning & Zoning Commission time for study, community engagement and any necessary comprehensive‑plan updates. The draft also clarifies language in the code (sections 400.160 and 400.260) so annexation and rezoning happen contemporaneously and limits processing of planned unit district (PUD) applications outside city limits without a concurrent annexation petition.

The city attorney advised the board that the draft language could apply to pending applications depending on vested‑rights case law and recommended the board consider whether certain existing applications should be exempted. "It would apply to them, but based on the fact that I understand them, they do not have a vested right in the operation of the code as it were prior to change," the city attorney said during the debate.

Council members sparred over the duration and practical effects. Some argued 12 months was needed to assemble regulations and consultants; others said the work could be done in a shorter window and worried about the economic and legal consequences of pausing ongoing reviews. Questions included whether the city would have to refund fees if hearings were suspended and whether new district regulations could retroactively invalidate PUD approvals.

Amendments to the annexation text were advanced: councilors agreed to strike portions of the draft that would have applied the change retroactively to certain pending applications and moved the ordinance to a second reading so legal language could be tightened. The board also voted to postpone taking testimony on BeltLine's PUD until it first votes on the moratorium ordinance. After discussion the board voted 4–2 not to proceed with the BeltLine hearing until the moratorium question is resolved.

Next steps: the annexation ordinance was advanced to a second reading with amendments; the moratorium measure remained under consideration and may be further revised to address retroactivity, waiver procedures, and the proposed duration. The board directed planning staff and its attorney to develop regulations and return with recommendations; aldermen indicated the moratorium could be terminated earlier if rulemaking progresses more quickly.

What remains unresolved is whether pending applicants will be entitled to fee refunds and the precise legal language that will determine whether existing PUD applications must refile or are grandfathered. The city scheduled follow‑up work for planning, zoning and staff to craft the regulatory language and to return to the board for a final vote.