The Questions Communities Are Really Asking

When someone shows up to a meeting about a proposed data center, they aren't thinking about global compute demand or the future of the Internet. They're thinking about their own electric bill, whether they'll hear the equipment from their yard, whether their well will still produce enough water, and whether their home will still be worth what they paid for it. Those personal questions deserve to be answered first, before any conversation about jobs or tax revenue. What follows is what a specific answer to each one looks like - a real number, how it's protected or enforced, and who's accountable if something changes.

1. Will my electric bill go up?

A specific answer starts with two facts the electric utility can state directly - whether this facility's load is served by dedicated new infrastructure or draws on shared capacity, and whether the tariff structure requires the large customer to pay its own interconnection cost rather than spreading it across residential rates. For example: "This facility is served by a new substation the developer funded in full. Under [the utility]'s approved large-load tariff, customers above [Z] megawatts pay 100 percent of their own interconnection costs, and residential rates aren't used to fund it." Where that kind of tariff isn't yet in place, the more honest answer is a commitment to push for one and to publish the rate case docket number so residents can track it themselves, with the state public utilities commission as the body that approves and enforces it.

2. Will this be noisy?

A specific answer sounds like this: "This facility is designed to operate at 55 decibels or less at the property line, about the level of moderate rainfall, confirmed by quarterly third-party sound testing with results posted publicly." Getting there means siting equipment away from the property line, adding sound walls or a landscaped berm where homes sit closest, and limiting generator testing to specific weekday daytime windows announced ahead of time, with a named member of the operations team as the point of contact if something sounds off outside those hours.

3. Will the data center interfere with my view?

A specific answer names the numbers that govern what a neighbor will see: "Building height is capped at [X] feet and set back [Y] feet from the nearest residential parcel, screened by a landscaped buffer of mature trees. Exterior lighting is fully shielded and dark-sky compliant, so it doesn't spill onto neighboring properties at night." Commitments like these only mean something once they're written into the site plan and zoning approval rather than offered as a verbal assurance, which is what makes the local planning authority, not the developer, the one enforcing them.

4. Will we have clean air?

The real air-quality question with a data center is almost always about backup diesel generators, and it deserves a direct answer instead of silence. For example: "Backup generators meet EPA Tier 4 emissions standards, the cleanest tier commercially available, and run only for maintenance testing during permitted daytime hours, capped at [X] hours a year under the facility's air permit." Where testing volume is meaningful, on-site air monitoring with public results adds another layer of accountability. The state environmental agency, not the operator, issues that permit and enforces it.

5. Will we have enough water for our needs, and will that water be clean?

A specific answer - "This facility's cooling system recirculates water through a sealed closed loop, drawing new water only to replace what evaporates, up to [X] gallons a day. That water comes from [a reclaimed or non-potable source] rather than the municipal drinking supply, and any water the facility discharges meets the same permitted quality standards as any other commercial discharge in the area." Not every site or era of design uses closed-loop cooling or reclaimed water, and the honest answer says so plainly rather than implying it everywhere. The operator owns the design and discharge compliance; the municipal or regional water authority oversees allocation and quality.

6. Will my water bill go up?

A specific answer: "This facility is billed under the municipality's industrial water rate class, separate from residential billing, and the developer funded the $[X] upgrade to water or wastewater infrastructure needed to serve the site rather than that cost showing up in residential water bills." Keeping large-user infrastructure costs out of the residential rate base is a negotiated condition of service that the municipal water department sets and enforces, not something that happens by default.

7. Will the value of my house go down?

This is the question with the least settled evidence, and claiming certainty either way undermines trust faster than admitting what's known - assessed-value studies comparing communities with and without a nearby data center are still limited, and the honest read of them is that visibility and distance matter more than the presence of the facility itself. Where a market study or assessed-value comparison exists for comparable projects, citing it directly, and naming its limits, is more useful than either a reassurance or a scare. That's also why the screening, setbacks, and lighting commitments described above matter here too - the projects most associated with a measurable value effect tend to be the ones visible from the road or a backyard, not the ones set back and buffered.

8. Will my taxes go up to pay for this?

The honest answer depends on which taxing structure a given jurisdiction uses, and it should name that structure specifically rather than defaulting to whichever sounds best. Some data centers are simply added to the property tax rolls at their full assessed improved value, generating new revenue for the county and school district without any special agreement. Others operate under a negotiated payment-in-lieu-of-taxes (PILOT) agreement, common where a jurisdiction wants predictable, guaranteed revenue in exchange for a phased abatement.  A specific answer names both numbers, for example: "This project guarantees the county and school district a minimum of $[X] annually under its PILOT agreement, with the abatement stepping down over [Y] years until the facility reaches full assessed value." Still others sit inside a tax increment financing district, where a defined share of new tax revenue is earmarked for specific infrastructure improvements in the surrounding area rather than the general fund. Whichever structure applies, the number that answers "will my taxes go up" is whether the developer is also funding the road, water, and power upgrades the site requires, since that's the cost that would otherwise fall to a local bond or a rate increase. A project that covers its own infrastructure costs, on top of whichever tax structure applies, gives a resident a straightforward answer. The county assessor and taxing authorities set and enforce these terms. The developer is accountable for the infrastructure costs it agreed to cover.

9. How does this benefit our community, long term?

Once the questions above have specific, checkable answers, the conversation about how a project benefits the community more broadly becomes a real discussion rather than a way of skipping past what residents asked. A specific answer names the mechanisms, not the category: "This project commits to a local-hire target of [X] percent of construction jobs, and a community benefit agreement funding [a specific, named local priority the community or city has already identified, such as a school facility or a downtown revitalization project]." None of that replaces the personal answers above, and it shouldn't be presented before those are addressed. What keeps the relationship going once the ribbon is cut is a stated communication cadence, kept whether or not there's news to report, and a point of contact who stays reachable for the life of the facility, not just its construction.

None of these answers are complicated to give, and the fact that they aren't is the point: a community shouldn't have to extract a specific number, a name, or a commitment from a developer one meeting at a time.

RadiusDC's approach to community engagement starts from that premise, that a resident's questions deserve full, specific, and honest answers up front, tradeoffs included alongside the benefits. That's the standard we hold every project to, and it's the same standard we'd want a neighbor to hold us to.

Part 1 of this series looks at why broad industry comparisons are losing ground with residents, and why specificity works.

About Radius DC

Meeting the colocation demands of tomorrow, RadiusDC owns and operates facilities in strategically located population centers throughout North America. Serving a wide variety of network operators, carriers, MSOs, and content providers, RadiusDC supports the increasingly urgent requirement to expand IT infrastructure to the network edge. For more information, please visit radius-dc.com.

‍