Chapter 7 of 10
Fight at the Table
If the project is going to happen, make sure the deal works for your community.
Summary
Sometimes the fight is not about stopping a data center but about making sure the deal works for your community. This chapter covers how to negotiate effectively.
The chapter opens with Henrico County, Virginia, which negotiated a $60 million housing fund from a data center developer. That is what is possible when a community negotiates from a position of knowledge and strength.
A community benefit agreement, or CBA, is a binding contract between the developer and the community. The chapter explains how to get started, what strong terms look like, and what weak terms look like. Cedar Rapids, Iowa secured meaningful protections, while Sidney, Ohio accepted vague commitments that were nearly impossible to enforce. Timing is critical: your leverage is highest before the project is approved and decreases rapidly after.
Tax abatements create a spiral where each new project demands the same breaks as the last. The chapter explains cost-per-job analysis, why disclosure matters, and how to structure better deals. Clawback provisions are supposed to take back tax breaks if promises are not kept, but most clawbacks fail because they are poorly written. The chapter provides a strong clawback model with automatic triggers.
Decommissioning is often overlooked. Data centers have an expected lifespan of about 20 years. What happens when they close? Without a decommissioning bond, the community is left with a massive empty building and no money to remove it. The chapter explains what to require and how to size the bond.
The chapter provides a model checklist of ten conditions to attach to any data center approval: noise and vibration limits, setback requirements, water use caps, backup generator restrictions, energy and renewable commitments, visual screening, traffic management, monitoring and reporting, a community benefit payment, and a decommissioning bond.
Time is your greatest advantage. The developer wants speed; you want thoroughness. Every week of additional review is a week to improve the deal. Hiring your own experts — a noise consultant, a hydrogeologist, an appraiser — levels the playing field.
The chapter closes with common developer arguments and evidence-based responses to each one.
Key Question
"If this project is going to be approved, what conditions should the community require?"
Action Plan
Your checklist for this chapter
- 1
Negotiate a community benefit agreement
Push for a binding CBA with specific, enforceable commitments — not vague promises. Start negotiations before the project is approved, when your leverage is highest.
- 2
Demand strong clawback provisions
Ensure any tax abatement includes automatic clawbacks with specific triggers, clear timelines, and independent verification. Most clawbacks fail because they are too vague to enforce.
- 3
Require a decommissioning bond
Data centers have an expected lifespan of about 20 years. Require a bond sufficient to cover complete removal of the facility and restoration of the site, posted before construction begins.
- 4
Attach the full checklist of conditions
Use the ten-point model checklist: noise and vibration limits, setbacks, water caps, generator restrictions, energy commitments, screening, traffic, monitoring, community benefit payment, and decommissioning bond.
- 5
Hire your own experts
Do not rely on the developer's studies. Hire an independent noise consultant, hydrogeologist, and appraiser. Require the developer to fund these independent reviews as a condition of the application.
Checklists & Step-by-Step Guides
What to Push For in CBA Negotiations
- Recurring payments, not one-time gifts.
- Binding job and wage minimums.
- Hard caps on water and noise (daily limits, not annual averages).
- No NDAs on public terms.
- Annual public reporting.
- A decommissioning plan.
- Closed-loop cooling, EPA Tier 4 generators, waste management plans.
What a Strong Clawback Looks Like
- Automatic, not discretionary.
- Triggered by measurable benchmarks: job numbers, wage levels, investment thresholds.
- 20-year operating commitment.
- 5% per year reduction for unmet targets.
- Prevailing wage requirements.
- Written agreement posted on a public website.
- Agreement identifies the beneficial owner, not the shell company.
Decommissioning Bond Requirements
- Bond covers removal of all equipment, demolition, and restoration to prior condition.
- Get an independent estimate from a demolition contractor, not from the developer.
- Surety should be independent — held by a bonding company, not by the developer.
- Review the bond amount every five years.
- Build an escalation clause so the bond grows with the cost of removal.
Reference Tables
Strong Terms vs. Weak Terms
| Category | Strong Example | Weak Example |
|---|---|---|
| Employment floors | Cedar Rapids: Google must maintain 31 full-time jobs paying $26.20+/hour | Sidney, OH: Amazon received 30-year, 100% abatement for 75 jobs ($2.4–$4.7M per job) |
| Water and environmental | Lancaster, PA: CoreWeave capped at 20,000 gallons/day | Wilmington, OH: Amazon $4B campus, 30-year abatement, no water or noise provisions |
| Direct payments | Cedar Rapids: $400,000/year from Google, up to $18M from QTS | Wilmington, OH: single payment of $1.85M for a $4B project |
| Transparency | Public agreements with named beneficial owners | Ohio deal hidden for 18 months under NDA |
Cost-Per-Job Comparison
| Location | Cost Per Job |
|---|---|
| Traditional manufacturing subsidies | ~$100,000/job |
| Sidney, Ohio (Amazon) | $2.4M–$4.7M/job |
| Lockport, New York | $2.4M/job |
| Genesee County, New York | $6.4M/job |
Noise and Setback Standards by Community
| Community | Noise Standard | Setback Standard |
|---|---|---|
| Albemarle County, VA | 60/55 dB (day/night) | — |
| Aurora, IL | 59/49 dB with 24-hour monitoring | 1,500 ft chillers, 1,000 ft generators |
| Chandler, AZ | Zero net increase from baseline | — |
| Linn County, IA | — | 1,000 ft from any home |
Warning Signs
- Vague language like 'up to' or 'reasonable efforts' instead of specific numbers in agreements.
- No enforcement mechanism — no one checks compliance and no consequences for violations.
- 'Up to 200 jobs' can mean 10 jobs — if it is not a binding minimum, it is not a commitment.
- One-time payments instead of recurring payments.
- Clawback provisions weakened by discretion or exceptions.
- Tax break has no cap, no sunset, and no review.
- Developer pressuring for a decision 'by next month' — rushing benefits only one side.
Questions to Ask
- 1. If the optimistic projection turns out to be wrong, who bears the downside risk?
- 2. If the jobs do not appear, who keeps the tax break?
- 3. If the water runs short, who gets cut first?
- 4. Can we justify that per-job subsidy number to our residents?
- 5. Who checks compliance, and what happens if they violate the terms?
- 6. What happens when the facility closes?
- 7. If we require a bond for a 50-acre solar farm, why not for a 100-acre data center?
Key Facts
Henrico County, Virginia negotiated a $60 million housing fund as part of a data center deal.
Data centers have an expected useful lifespan of approximately 20 years.
Cedar Rapids, Iowa secured meaningful enforceable protections in its community benefit agreement, while Sidney, Ohio accepted vague terms that were nearly impossible to enforce.
Your negotiating leverage is highest before the project is approved and decreases sharply after approval.
Case Studies
Henrico County, Virginia — $60 Million Housing Fund
Rather than negotiating a traditional CBA, Henrico County directed data center tax revenue into a $60 million housing trust fund — an automatic funding stream that does not depend on annual political decisions. The model demonstrates what is achievable when a community structures revenue dedication rather than relying on developer promises.
Cedar Rapids, Iowa vs. Sidney, Ohio — Strong vs. Weak CBAs
Cedar Rapids, Iowa secured a community benefit agreement with specific, enforceable protections and measurable commitments. Sidney, Ohio accepted vague language and loose promises that proved nearly impossible to enforce, illustrating the difference between a strong CBA and a weak one.
Resources
Good Jobs First
Model clawback formula with 20-year operating commitment and 5% per year reduction.
National League of Cities
Free resources to help communities evaluate data center proposals.
PennFuture
Model ordinance covering water, power, noise, and aesthetic concerns.
Key Quotes
"The developer wants speed. You want thoroughness. Every week of additional review is a week to improve the deal."
"A clawback that no one can enforce is not a clawback. It is a press release."
"If the project is going to happen, make sure the deal works for your community — not just the developer."
Glossary Terms in This Chapter
Get the Full Playbook
Buy the Book
This page covers the highlights. The book gives you the full story, the complete checklists, sample documents, and the resource directory.