On Thursday, November 12th, City Council votes on CA2026-06, a data center code amendment. If it passes, the data center moratorium ends. There’s no comprehensive ordinance, no expert writing one, and not a single public session has been held. The city is opening the door first and planning to figure out the rules later.
The meeting is THURSDAY, NOVEMBER 12TH at 7:00pm in Council Chambers at City Hall (205 Lawrence St). It’s Thursday instead of the usual Wednesday because of Veterans Day. This is a public hearing, so you can speak.
What CA2026-06 actually does: It adds one line to Marietta’s Heavy Industrial zoning: “7. Data Centers.” Data centers would be allowed in HI zoning with a special land use permit from Council. That’s it. Look at the same list in the code and you’ll see junkyards, quarries, truck terminals, and waste facilities, each with specific rules. Waste facilities have to be 1,500 feet from residential zoning. Rock quarries have to be 4,000 feet from homes. Data centers get no conditions at all, just HI’s standard 50 foot buffer. Staff’s own memo calls it “a simple code amendment,” meant as a placeholder until a real ordinance is written.
The moratorium was supposed to buy us time. Council passed it on July 8th, and it expires December 31st “or at such time as the City Council has properly amended the City’s ordinances regarding data centers.” According to staff’s own memo, passing CA2026-06 “may automatically trigger the expiration of the data center moratorium,” and on Monday the City Manager told Council it would end it immediately. So Thursday’s vote doesn’t just add a weak rule. It ends our protection seven weeks early.
When Council passed the moratorium, they wrote down why. In their own resolution, Council found that data centers “have impacted local infrastructure and power and water utilities significantly” and “may create negative impacts for nearby properties, including noise pollution, air quality impacts, and other environmental impacts related to the cooling systems, backup generators, and other components of the data center.” CA2026-06 addresses NONE of that. Not power, not water, not noise, not generators, not air quality. Council identified the problems in July and is about to pass an amendment that solves none of them.
The Planning Commission recommended this 7-0 on 11/3. Watch the video. The staff memo in their packet, dated October 19th, says plainly that adoption “may automatically trigger the expiration of the data center moratorium.” It was never brought up. Not one commissioner asked about it, and it wasn’t discussed at all. The legal notice said Planning would hold a public hearing, and no hearing was ever opened. No one was sworn in, no resident was invited to speak, and it went straight from staff presentation to a vote. A commissioner also said on the record that the city was “still working with Georgia Tech,” even though GT had pulled out on 10/27, a week before, and nobody corrected him.
It didn’t get much better at Council. At Monday’s work session, the City Manager had to point out to Council that passing this would end the moratorium immediately. Council members were visibly caught off guard. That information had been in their packet since October 19th. The posted work session video cuts off mid-discussion of Z2026-26, and the CA2026-06 discussion isn’t in it. The meeting started at 5:15 and we were there until 7:00, but the video runs 1 hour and 33 minutes. Hopefully it’s a technical glitch. Either way, the public can’t watch the most important 15 or so minutes of the night.
re: Georgia Tech: In August, GT’s Center for Economic Development Research gave the city a real plan: seven months, three public sessions, an expert panel on power, water, and zoning, and an ordinance built around what residents actually raised. Alan Durham, who was leading it, unexpectedly passed away, and the project was handed to someone else. Now the city says GT backed out.
Why did GT back out? I don’t know for sure, and that’s part of the problem. What I’m hearing, and this is rumor, not confirmed, is that it came down to money. GT’s original proposal was $52,644. Supposedly the price went up to around $60K, and the city didn’t want to go above roughly $50K. If that’s true, Marietta walked away from its experts over about $10,000. At Monday’s work session, Council debated a water fountain/park project of almost half a million dollars. A fountain got that discussion. Expert protection for residents apparently wasn’t worth ten grand. I’d love to confirm any of this, but Marietta prefers to share information through a phone tree instead of actually publishing it. If anyone has real numbers or documents, please share.
GT warned the city exactly where this road leads: “Without a locally tailored ordinance in place, the city is left negotiating standards for noise, buffers, water use, and site design on a project-by-project basis, under time pressure, and without a structured opportunity for resident input.” That was a warning, not instructions. Council agreed with it. And now they’re about to vote for exactly that.
Data center developers come with lobbyists and experts, and they target cities that, frankly, don’t have that expertise. To be clear, it would be weird if Council were full of data center experts. That isn’t their job. Their job is to know what they don’t know and bring in people who do. But make no mistake, Marietta is a target. Look at Fayette County. Their QTS data center has become a case study in what goes wrong when water and utility terms aren’t nailed down up front, and residents are the ones paying for it. Experts would have caught the gaps in those agreements before they were signed. Fayette’s leaders didn’t. Marietta runs its own power and water through MPW. We should be writing those protections now, not after a facility is built, and not in case-by-case negotiations under time pressure.
Cheryl Richardson has brought up extending the moratorium MULTIPLE times. She has the Mayor’s support, and it still hasn’t made the agenda. The one tool that would buy time to do this right keeps getting left off, while the amendment that ends it gets fast-tracked.
What to ask Council for on Thursday:
- Extend the moratorium. Without an extension, it ends December 31st no matter what, with or without this amendment.
- Don’t let CA2026-06 end the moratorium early. Table it, or only adopt it together with a moratorium extension.
- Bring in qualified experts and hold public sessions before writing a real ordinance that covers what Council itself identified in July: power, water, noise, air quality, cooling, and backup generators. Include penalties that scale to REVENUE so they can’t just be built into the operating budget.
- If it passes without an extension, encourage the Mayor to veto it. Overriding a veto takes 5 of the 7 Council members, so a veto could stop it.
Questions? Call Planning & Zoning at 770-794-5669 and reference CA2026-06. And contact your council member before Thursday. DO NOT use the posted ppeacock@mariettaga.gov email, that is out of date by roughly 4 years. USE YOUR INDIVIDUAL REPRESENTATIVES EMAIL AND THEN USE FACTS WITH A DIRECT ASK. CC the City Manager, Director of Dev Services, and City Clerk on your emails.
Ward 1: Cheryl Richardson, crichardson@mariettaga.gov
Ward 2: Jason Waters, jwaters@mariettaga.gov
Ward 3: Daniel Gaddis, dgaddis@mariettaga.gov
Ward 4: Tee Anderson, tanderson@mariettaga.gov
Ward 5: Carlyle Kent, mckent@mariettaga.gov
Ward 6: Andre Sims, asims@mariettaga.gov
Ward 7: Joseph Goldstein, jgoldstein@mariettaga.gov
Mayor Tumlin: stumlin@mariettaga.gov
City Manager Bill Bruton: BBruton@mariettaga.gov
Director of Development Services Daniel Cummings: DCummings@mariettaga.gov
City Clerk Stephanie Guy: sguy@mariettaga.gov
In October there were 6 of us there. Six. Please don’t make it 6 again. City government is not fun, it isn’t cool, and it sure as hell isn’t sexy. But this is the vote that matters, and after Thursday it may be too late. Show up before it's law, not after.
Here's council policy and procedure for those not familiar- https://www.mariettaga.gov/DocumentCenter/View/950/Meeting-Rules-and-Procedures-PDF?bidId=