Schaffer Solutions

A Neutral Field Guide for Residents

Data Centers Are Coming to Your Community. Here Is What You Actually Need to Know.

Not the hype. Not the fear. Just the facts, the real trade-offs, and the exact questions to bring to the next city hall meeting so you can help shape a deal that works for both sides.

Fact-checked and source-cited Built for any US community Kansas City metro context included Printable toolkit inside

If you have been on social media lately, you have seen the two loudest versions of the data center story. One says they are economic miracles with no downside. The other says they are environmental disasters that will drain your water, spike your power bill, and roar day and night. Both versions are getting a lot of clicks. Neither is preparing you for the meeting where the real decisions get made.

The truth is more useful, and more actionable. A modern data center can be a quiet, water-light, well-paying neighbor that pays its fair share, or it can be a loud, thirsty, cost-shifting problem. The difference is not luck. It comes down to design choices and, above all, what a community gets in writing before the project is approved.

The goal of this guide is not to tell you to support or oppose a project. It is to make sure that when you walk into city hall, you are the most informed person in the room.

Below you will find the concerns that come up most often, each laid out the same way: the fear, the facts, an honest verdict, and the single best question to ask. Then comes the centerpiece, a Win-Win Mitigation Blueprint showing what a genuinely good deal looks like, followed by a printable City Hall Toolkit you can carry into the meeting.

Before You Trust Your Feed

Most of what goes viral about data centers on Facebook and Nextdoor is built to alarm, because outrage travels faster than facts. That does not make every concern wrong. As this guide shows, several are legitimate. It does mean that a screenshot from a neighbor two states away is not evidence about the project in your county, and a comment thread is not a public record. Treat a viral post as a reason to investigate, not a verdict. Bring the questions in this guide to the people who actually have the answers, and judge the project in front of you on its own facts.

The Concerns

The Questions, Answered Honestly

Each concern is real. What matters is separating the part that is legitimate from the part that is overblown, and knowing what to ask. Click any card to open it.

The Centerpiece

The Win-Win Mitigation Blueprint

A good data center deal is not a fight one side wins. It is a set of enforceable commitments that let responsible development proceed while protecting the people who live nearby, and paying fairly for the growth it creates. Here is what "good" looks like, with real benchmarks communities have already secured. Open any term.

The common thread across every category: a promise is only as good as its enforcement. The strongest protection is a signed Community Benefit Agreement with public reporting, real penalties, and independent verification, not a friendly assurance at a podium.

Bring This With You

The City Hall Toolkit

Print this page, or save it to your phone. These are the questions that separate a vague pitch from a real commitment, plus the green flags and red flags to listen for.

Your City Hall Checklist

Questions to ask, and signals to watch for, at the public meeting.

Eleven Questions to Ask

  1. What cooling technology will you use, and what is the guaranteed maximum annual water draw, in writing? Is it closed-loop or zero-water?
  2. What is the enforceable noise limit at our property lines, who measures it and how often, and what is the penalty and required fix if it is exceeded?
  3. Is there a large-load tariff so the data center pays for its own capacity and transmission upfront, with no cost shift to residential ratepayers?
  4. Beyond property taxes and PILOT, what dedicated community investment fund will you commit for roads, business improvements, and city projects, how much per year, and for how many years?
  5. Where will the electricity come from, and is it matched with new clean generation rather than straining existing supply?
  6. How many permanent jobs, at what wage, and are the tax incentives clawed back if those numbers are not met?
  7. What emission controls are on the backup generators, and how often will they be tested?
  8. What are the setbacks from homes, schools, and water sources?
  9. Is there a signed Community Benefit Agreement, and what is actually enforceable versus a verbal promise?
  10. Will there be a community advisory board and a public dashboard tracking water, power, jobs, and tax?
  11. What is the decommissioning plan, who pays if it closes early, and are we protected from stranded bond debt?

Green Flags vs. Red Flags

Green Flags (good signs)
  • Closed-loop or zero-water cooling with a hard cap
  • Enforceable dB limit plus independent post-construction testing
  • Large-load tariff that shields residential bills
  • A multi-year community fund scaled to the project
  • Signed CBA with penalties and a public dashboard
  • Decommissioning bond on file
  • Company decision-makers present at the meeting
Red Flags (proceed carefully)
  • Vague "state of the art" claims with no numbers
  • No written, enforceable commitments
  • A one-time token grant called "community investment"
  • Broad NDAs hiding basic facts about the project
  • Evaporative cooling with no water cap
  • Grid upgrade costs shifted to ratepayers
  • Consultants sent in place of the actual company

The Kansas City Angle

This is not a distant, someone-else's-town issue for our region. The Kansas City metro has quietly become one of the country's fastest-growing data center markets, which makes an informed community more important here than almost anywhere.

Roughly ten hyperscale campuses have been proposed across the metro, in places like Smithville, Osawatomie, Kansas City Kansas, Liberty, and Tonganoxie. Meta's Smithville campus is already online, Google is building a second Kansas City campus, and Evergy now expects retail electricity sales to grow 7 to 8 percent per year through 2030, driven largely by this demand. Evergy has adopted a rate structure requiring large data centers to pay for their own capacity upgrades upfront, a model designed to keep the cost off residential bills. That is the kind of protection worth asking every developer and every commissioner to guarantee.

Close to home, one roughly $3 billion campus in our own metro is projected to deliver about $163 million to its host city and $78 million to the local school district over the life of its tax agreement. Yet its separate, discretionary community investment fund, the money the city can steer toward roads and local projects, was just $250,000. Other communities have negotiated far more. That gap is the single clearest local lesson in this guide.

~10
Hyperscale campuses proposed across the metro
7-8%
Projected annual Evergy sales growth through 2030
$250K
Discretionary community fund on one local $3B project
$20M
What Lancaster, PA secured in dedicated community funds
A closing viewpoint, in my own words

Everything above is deliberately neutral. You deserve the facts before anyone's opinion. Here is mine.

I have called this our railroad moment, and I meant it. A century and a half ago, the towns that understood the railroad and negotiated for a depot and fair terms grew into cities. The towns that fought the tracks blindly, or signed whatever was put in front of them, got bypassed or run over. The infrastructure of the AI era is arriving on that same scale. It is coming whether any one of us likes it or not.

That is why ignorance is the real threat, not the buildings. An angry, uninformed crowd gets dismissed. A prepared community gets a better deal. Ask about noise limits at the property line. Demand water caps in writing. Insist on ratepayer protection. And treat the community investment fund as a headline term, sized to the project, not a rounding error. One example sits just a few miles from where I write this: a $250,000 fund on a $3 billion campus. That is the lesson. Other towns secured tens of millions by refusing to treat it as an afterthought.

One more thing, and it matters. Preparation does not have to end in yes. I grew up in a small farm town, and I understand in my bones that some communities are not looking to become anything other than what they already are. Not every town needed to become a St. Joseph or a Kansas City in the railroad era, and not every community should chase that now. There are beautiful rural places where what gets sold as progress is a poisoned pill, where the quiet and the land are worth more than any tax projection. If your community weighs a project honestly and decides no, that is not backwardness. That is a town that knows exactly what it is. I will level with you: I am on the fence about these data centers myself. If one were proposed within a mile of my own home, I would want every protection in this guide in writing before the first shovel hit the ground.

The environment does not have to lose for the economy to win. Zero-water cooling, matched clean power, and honest noise mitigation already exist. A real financial stake for the city already exists in other deals. The only question is whether your community insists on all of it.

Use this guide. Bring the questions. Get the commitments in writing. Then decide. That is not anti-business. That is how you make sure progress includes you.

And if your city, county, or community group wants a hand preparing before a decision like this, I am easy to find at schaffer.solutions. The guide is yours either way.

Johnathan Schaffer
Chief Executive Advisor, Schaffer Solutions · Read "The Railroad Moment Nobody Is Talking About"

Sources and Further Reading

Where These Facts Come From

This guide is provided as a neutral public education resource by Schaffer Solutions. Figures are drawn from the sources above and reflect reporting available as of July 2026. Noise levels, water use, electricity costs, and financial terms vary significantly by facility design, site, and local policy, so treat the numbers as directional and verify specifics for any project in your area. Nothing here is legal, financial, or engineering advice. The closing viewpoint is the personal opinion of the author; the remainder of the guide is intended to be impartial.