Why You Should Oppose Kilpatrick's Data Center Amendments

A single council vote can freeze an entire market. That's not hyperbole — it's exactly what's at stake with the amendments proposed by Councilmember Kilpatrick, which would grandfather in every data center project currently known to be in the pipeline. For developers, landowners, and clean energy advocates who have spent years positioning for the infrastructure boom, this deserves serious attention.

Here's the problem: grandfathering provisions sound harmless on the surface. In practice, they can lock in outdated standards, reward projects that don't meet current expectations, and make it significantly harder to hold future development accountable. If these amendments pass, the precedent they set could reverberate through local infrastructure policy for years.

Understanding Kilpatrick's Amendments

The core of what Kilpatrick is proposing centers on exempting known data center projects from whatever new regulatory framework the council is working toward. The mechanism is a grandfather clause — a provision that shields existing or pipeline projects from new rules by treating them as pre-approved under the old standard.

Grandfather clauses aren't inherently corrupt, but they are almost always a gift to whoever has the most projects already in motion. In a sector where large hyperscalers and well-capitalized developers have been aggressively staking claims to land and power capacity, that's a very specific group of beneficiaries.

The stakeholders pushing back are asking council members to vote NO — and for good reason. Any regulation that draws a hard line around existing projects creates a two-tier system: established players operate under relaxed rules, while newer entrants face the full weight of compliance. That's not a level playing field. It's a moat.

What Grandfathering Actually Does to a Project

Let's be precise about what grandfathering means in this context, because the term gets thrown around loosely.

When a project is grandfathered, it is shielded from new regulatory requirements that come into effect after a certain date. For data centers, that could mean exemptions from updated energy efficiency standards, grid interconnection requirements, water usage disclosures, noise ordinances, or environmental impact thresholds — depending on what the new regulations actually contain.

The danger isn't just that these older projects escape scrutiny. It's that they continue operating and expanding under outdated frameworks while the market around them evolves.

Consider what that means practically. A data center grandfathered under a 2023 framework could be running at scale in 2030, drawing significant power from the local grid, generating heat and noise in a residential-adjacent industrial zone, and paying none of the compliance costs that newer facilities are required to absorb. The community bears the externalities. The developer pockets the margin.

For infrastructure policy to work, rules need to apply uniformly. Carve-outs create perverse incentives — developers rush to get projects "known" before a regulatory deadline, even if those projects are speculative or underfunded, just to secure exempt status. That distorts the market and degrades the quality of the development pipeline.

The Developer Perspective: Short-Term Gain, Long-Term Risk

There's a non-obvious angle here that's worth taking seriously: even developers who stand to benefit from Kilpatrick's amendments should think twice.

Regulatory uncertainty is consistently ranked as one of the top concerns for infrastructure investors. When rules are inconsistent — when some projects play by one set of standards and others play by another — it introduces friction into every future transaction. Lenders and institutional investors hate that. Title due diligence gets complicated. Community opposition intensifies when neighbors see two-tiered treatment.

Projects that earn their approvals under a clean, uniform regulatory framework are ultimately more bankable. They're easier to permit, easier to finance, and easier to exit. Chasing a grandfather exemption today might feel like winning, but it can quietly undermine the project's long-term viability.

There's also a reputational dimension. The data center industry is already under pressure from communities concerned about power consumption, water use, and land impacts. Amendments that appear designed to shield specific projects from accountability hand critics exactly the ammunition they're looking for.

Risks to the Broader Regulatory Environment

Kilpatrick's amendments don't exist in a vacuum. Local data center regulations are evolving rapidly across the country, driven by a combination of grid stress, community pushback, and state-level policy shifts. Northern Virginia, the world's largest data center market, has seen counties grapple with exactly these questions — how to accommodate massive power demand while protecting existing communities and infrastructure.

What happens at the local council level sets precedent. A successful grandfather clause in one jurisdiction becomes the template developers use to lobby for the same protection everywhere else. Infrastructure policy gets made incrementally, and each increment matters.

The stakeholders who lose in this scenario aren't abstract — they're the communities, utility ratepayers, and future developers who will live with these decisions long after the current pipeline has been built out.

Opponents of the amendments are right to flag the urgency. Council meetings move fast, and amendments that seem procedural often carry significant long-term consequences. If this vote passes without sufficient opposition, unwinding the damage becomes far harder than preventing it.

How to Make Your Opposition Count

Opposing amendments like these requires more than sentiment — it requires showing up in the right ways, at the right moments.

The most direct action is contacting your council member before the vote. Generic emails get triaged. Phone calls and in-person meetings get remembered. If you're a developer, landowner, or industry professional, lead with specifics: explain what uniform regulation means for your business model, why you're not asking for special treatment, and why you believe the market functions better when everyone operates under the same rules.

Industry associations and advocacy groups working in clean energy infrastructure, data center development, or land use are also natural allies here. Coordinated opposition — multiple voices making the same substantive argument — carries more weight than a flood of form letters.

If you have standing to speak at the council meeting, take it. Frame the argument not just in terms of fairness, but in terms of what good infrastructure policy looks like: transparent, consistent, and designed to serve the public interest over the long run.

Document the timeline. Note which council members support the amendments, which oppose them, and who stays quiet. Accountability in local government depends on constituents paying close enough attention to remember.

What Comes Next

The trajectory of data center regulation at the local and state level is moving toward more scrutiny, not less. Power demand from AI workloads alone is projected to add tens of gigawatts of load to the U.S. grid over the next decade. Communities are increasingly aware that data centers are not passive neighbors — they draw enormous resources and reshape local infrastructure priorities.

Councils and planning boards that get ahead of this — that build clear, enforceable, uniformly applied frameworks now — will be better positioned to attract responsible development while protecting their constituents. Councils that take shortcuts, like blanket grandfather clauses, will find themselves managing the consequences for years.

Watch the upcoming council meetings. Track how this vote lands. And if you have a stake in how data center development gets regulated in your community, make that stake visible before the vote, not after.

The window to influence these decisions is almost always narrower than it looks.

Explore more about the InfraSale Marketplace and how you can get involved.

Internal Link Suggestions

• [INTERNAL LINK: grandfather clauses]
• [INTERNAL LINK: infrastructure policy]
• [INTERNAL LINK: data center development]