Chapter 4: Community negotiation guide: data center deals
Assess your position before sitting down - what is your leverage
Note, you can skip around to whatever works for you in these chapters.
Chapter 1: Introducing How to Negotiate a Better Deal When a Data Center Developer Comes Knocking
Chapter 2: Inevitable Was Never a Forecast
Chapter 3: Hyperscaler PR and community strategy: what wins, what fails, and why
Chapter 4: Community Negotiation Guide: Data Center Deals
Chapter 5: Noise Sources and Community Impact
This document is a practical reference for elected officials, planning commissioners, and community organizers facing data center proposals. Organized to handle the variation in leverage, resource context, and deal structure that makes one-size-fits-all advice useless.
Two principles govern everything here:
Leverage is time-dependent. A community’s negotiating position is strongest before any approval, permit, or pre-development agreement is signed. Every concession the developer needs from you — rezoning, special-use permit, utility connection approval, tax abatement vote — is a moment of leverage. Once those approvals are granted, the developer has what it came for. Negotiate before you give anything, not after.
The full bundle of protections has never been assembled in one deal. No jurisdiction has yet to combine transparency requirements, a community benefit agreement, graduated clawbacks, a sized decommissioning bond, change-of-control protections, utility rate safeguards, fiber buildout, and equipment reuse covenants into a single agreement.
That means every community negotiating today is at the frontier. The goal here is to assemble as much of the bundle as your leverage allows. This chapter 4 is like Chapter 3 in that it’s meant to be a kind of look-up guide or general assistant you can use as a baseline with reviewing your options with a developer or testing your negotiation strategy with AI.
Note: for brevity, I use the ‘developer’ instead of ‘the developer’ throughout the following.
Strength ratings used throughout this guide:
Universal — ask in every negotiation, regardless of context
High leverage — ask when you control significant approvals (rezoning, special use permits, utility connection)
Contextual — applicable when local conditions make it relevant
Emerging — legally defensible novel provision; no CBA precedent exists yet, but the mechanism and legal basis are sound
Part I: Assess your position before sitting down
Answer these questions before the first meeting with a developer or economic development officer.
What approvals do you still control?
Rezoning or special-use permit required
Maximum
Developer needs your yes vote. Everything is negotiable.
Building permits only, no zoning change
Moderate
Attach conditions to permits. Negotiate Phase 2 requirements now.
By-right approval (no discretionary review)
Minimal for Phase 1
Shift focus to future phases, utility approvals, and state-level intervention.
Utility interconnection pending
Significant
File as intervenor in utility rate case. Delay is real leverage.
Lancaster, PA is the cautionary example of discovering leverage too late: Phase 1 was by-right, so the CBA was negotiated from a position of weakness. The community got significant protections for Phase 2 but had no approval power over initial construction.
What is the developer’s timeline pressure?
Ask directly: “What is your required in-service date, and what drives it?” Common pressure points:
Tax incentive windows (state sales tax exemptions with expiration dates)
Power purchase agreement deadlines
Utility interconnection queue position (losing it means years of delay)
Capital deployment requirements from investors or parent company
Construction labor availability window: before automated construction (Roze AI, August Robotics) normalizes, local skilled trades are genuinely needed. This window is approximately 2026–2028. Use it now. (On Roze AI: SoftBank announced the venture and a planned US listing in April 2026 — Financial Times, April 29, 2026; Capacity, May 1, 2026.)
What does your local resource situation require?
PRIORITY PROVISIONS
Water-stressed region (Western states, Texas)
Water caps, drought triggers, prior appropriation documentation — non-negotiable
IOU utility (not municipal)
Utility rate provisions require PUC intervenor filing, not just local CBA
Municipal utility
Direct negotiating power over rate structure; rate protection is achievable locally
Existing district energy or potential for it
Waste heat recovery is achievable; include infrastructure requirement
Rural community
Emergency services pre-funding, fiber buildout, and jobs reality check all critical
Adjacent to residential
Noise protocol (Part VII), light controls, generator testing restrictions essential
Have you identified the operating entity? - Critical
If a shell company or code name has been presented without identifying the ultimate owner, the first provision below is non-negotiable. You are not negotiating with Tilted Gate LLC, Degas LLC, or Project Liberty. You are negotiating with the company that will operate a facility that will consume your water and power for 30+ years.
When negotiation is, and isn’t, the right tool.
A CBA cannot substitute for permitting authority you don’t have, transparency a developer has successfully denied, or utility regulation outside local control. Where permits are already issued, where the developer has refused basic disclosure, or where a document is being presented as a “community agreement” without genuine community authorship, a moratorium, formal opposition, or a procedural challenge (Part II) may do more for the community than a negotiated table of provisions. Negotiate when you have something to trade; oppose or delay when you don’t yet.
For background on how CBAs work, their history, and their limits, the Wikipedia overview is a clear, well-sourced starting point: https://en.wikipedia.org/wiki/Community_benefits_agreement
Part II: Strategic and psychological leverage
Formal authority (rezoning votes, permits) is not the only source of leverage. Friction, political risk, and procedural accountability operate independently of approval power and are available even in by-right jurisdictions.
Weaponizing friction and social risk
Strength: Universal
Developers operate on strict timelines tied to capital deployment schedules and power purchase agreement deadlines (see Part I). Communities can deliberately introduce friction: demand complete documentation before any meeting, decline to compress review timelines, and require full responses to information requests before proceeding.
Developers are skilled at pricing technical risk — engineering uncertainty, interconnection delay, construction cost overruns. They are far less skilled at pricing social and political risk. Engaging media coverage and informing the developer’s investors of unresolved community opposition raises the developer’s political risk profile until offering meaningful concessions becomes cheaper than continuing to negotiate against organized opposition.
Cross-jurisdictional coordination to prevent bidding wars
Strength: Contextual — applies where neighboring jurisdictions could compete for the same project
Developers solicit competing incentive offers from neighboring jurisdictions, using the threat of relocation to drive up subsidies and to discourage any one jurisdiction from holding firm on community protections. Neighboring municipalities and counties can coordinate in advance: agree to common minimum transparency standards, common disclosure timelines, and a shared floor on community benefit and accountability terms before any developer approaches either jurisdiction. This removes the developer’s ability to play jurisdictions against each other. The same logic scales regionally — Wisconsin’s statewide organizing coalition and the Rio Grande Valley Broadband Coalition’s four-county approach both convert isolated towns into a single negotiating front.
Imposing a procedural duty of care
Strength: Universal
Elected officials approving incentives carry a fiduciary-like obligation to the public similar to a corporate board’s duty of care. Residents can demand officials formally document: the information gathered before a vote, the economic counterfactual considered (what the same incentive package would generate if invested elsewhere), and a premortem analysis — assuming the project underperforms or fails, and identifying why in advance. Communities that frame a rushed or undocumented approval as a breach of this procedural duty — and signal willingness to pursue political accountability, including at the next election, or a citizen lawsuit on that basis — create real pressure against rubber-stamp votes.
Procedural compliance audit
Strength: Universal
Every filing, hearing notice, and permit a developer submits is a potential point of failure. Review zoning hearing notices, agenda postings, environmental filings, and permit applications against the letter of the applicable code and open-meetings law. A documented procedural defect — a skipped hearing, an inadequate notice, a missed filing deadline — can be legally sufficient grounds for denial or delay independent of any substantive negotiation. Hazle Township, PA denied a data center application on exactly this basis: the developer had skipped a required zoning hearing.
Moratorium as a due-diligence window
Strength: High leverage — requires an elected body willing to act before approvals are pending
Where the timeline is moving faster than the community’s ability to organize or study impacts, a temporary moratorium on new data center applications buys time without requiring a substantive position on the project itself. Dundee Township, MI enacted a 90-day moratorium for this purpose. Use the window to commission the independent impact assessment (Part III), build the technical advisory team, and draft the zoning and noise ordinances the community will need regardless of how this specific project resolves.
Part III: Non-negotiable process provisions
Do not trade these for monetary benefits. They are the preconditions for any meaningful negotiation.
1. Ultimate parent disclosure before any agreement
Strength: Universal
Before signing any pre-development agreement, letter of intent, NDA, or incentive application, the developer discloses in writing: the legal name of the operating entity, state of incorporation, ultimate beneficial owner (any company or individual holding more than 10% equity), and the name and title of the person with authority to bind the entity to a CBA. This disclosure is not covered by any NDA.
A substantial percentage of data center proposals arrive under shell company names. NBC News reviewed 30 proposals; NDAs covered the developer’s identity in a majority. Scioto County commissioners signed NDAs with “Tilted Gate LLC” (Google) on three separate dates before any public disclosure.
Best available model: Pima County, AZ Policy 31.3 (September 2025); Microsoft’s voluntary NDA reversal (March 2026); Wisconsin Bill 969 (passed committee 4-1).
2. Chamber / economic development NDA bypass prohibition
Strength: Universal — adopt this ordinance before a developer calls
Pass a resolution or ordinance: No person or entity acting on behalf of the municipality, including economic development corporations, chambers of commerce, or affiliated organizations, may sign a non-disclosure agreement or any similar arrangement covering a proposed development without prior authorization from the full elected body. Any such agreement must be publicly disclosed within 30 days of signing. NDAs that require assertion of FOIA exemptions on behalf of the developer are void as against public policy.
The Arkansas pattern: Google’s $4 billion West Memphis campus NDAs were signed by the chamber, not city employees. The city could then truthfully claim it had no NDAs to produce under FOIA. This provision closes that route before it is used.
Best available model: Wisconsin Bill 969 language; Pima County NDA policy.
3. 90-day pre-vote public disclosure
Strength: Universal
All project details must be publicly disclosed no less than 90 days before any vote by any public body: developer identity, facility specifications, projected power and water demands, utility infrastructure requirements, proposed incentives and abatements, and all term sheet provisions. No vote may occur before this window has passed and the independent impact assessment is published.
In Menomonie, WI, the council voted 12-0 to approve a predevelopment agreement with “Degas LLC” without the agenda or minutes mentioning “data center.” Meta announced its involvement 14 months after the NDA was signed.
Best available model: Pima County Policy 31.3 — the 90-day pre-vote disclosure requirement is the most specific enforceable model found in any US jurisdiction.
4. Developer-funded independent community advisory
Strength: Universal
As a condition of any pre-development engagement, the developer funds legal counsel and technical advisors (environmental engineer, electrical engineer, water resource specialist, acoustical engineer, and independent economic analyst) for the community negotiating team. Minimum budget: $100,000 for projects under $500 million; scaled proportionally for larger facilities. Advisors are selected by the community and owe professional duties exclusively to the community coalition and advisory board. The developer has no role in selecting, directing, or supervising these advisors. This funding is separate from and does not count toward any community benefit fund.
Without funded technical capacity, a community negotiates against attorneys and consultants with years of data center deal experience. The asymmetry is structural. The Columbia Sabin Center and the DOE CBA guidance both identify developer-funded community technical capacity as essential.
Best available models: NAACP CBA template (2026), Article on developer-funded advisory. Ashville, OH: EdgeConneX offered $100,000 for professional advisors and legal/engineering review.
5. Independent economic and environmental impact assessment
Strength: Universal
Developer commissions and pays for a full independent impact assessment before any vote: net tax revenue after all abatements (not gross), actual job creation estimates by job type and credential, infrastructure cost allocation between developer and ratepayers, water demand at 50% and 100% capacity, noise projections at the property line under all operational scenarios, grid impact, and rate effect on residential customers. Methodology approved by the community before assessment begins. Results published no less than 90 days before any vote.
Best available model: Pima County Policy 31.4; Project Blue/Tucson: Sky Island AI’s independent dashboard showed TEP load implications the developer’s materials obscured.
6. Public disclosure of forgone revenue
Strength: Universal
Require that the value of any tax abatement, exemption, or incentive granted to the facility be reported as forgone revenue in the jurisdiction’s Annual Comprehensive Financial Report (or equivalent annual financial statement), not just in the original incentive application. The original application’s projections are not audited against actual outcomes anywhere else; the annual financial report is the one document residents and bond-rating agencies actually read.
Best available model: Next City (May 2026) policy proposal: “Every state and locality that loses revenue of any kind to a data center tax abatement should report that loss in its Annual Comprehensive Financial Report.”
Part IV: Zoning, land use, and taxation leverage
Prohibiting zoning variances and special-use permits
Strength: High leverage
Developers often petition for variances — relief from height limits, setback rules, or other code requirements — citing financial hardship. A jurisdiction can foreclose this route before any application arrives by passing an ordinance or a planning commission policy that categorically prohibits variances and special-use permits for data center siting. This forces the developer to either fully conform to existing code or abandon the site, thereby removing the variance process as a backdoor around community-negotiated zoning protections.
Converting by-right approval to discretionary review
Strength: High leverage — must precede a specific application
Where data centers currently qualify as a by-right use, push a zoning text amendment reclassifying them as a conditional or special use requiring discretionary review and public hearing. Pair with a temporary moratorium (Part II) while the amendment is drafted. This is the single highest-value zoning move available in a by-right jurisdiction, because every other provision in this guide depends on the community holding an approval the developer needs.
Banning behind-the-meter fossil fuel workarounds
Strength: Universal where grid interconnection queues are long
Grid interconnection queues now run multiple years in many regions. Developers facing queue delays increasingly propose on-site, behind-the-meter gas-fired generation to power the facility independent of the grid — bypassing both interconnection review and any grid-related community benefit. Prohibit off-grid and behind-the-meter fossil fuel generation as a permit condition: the facility may be built only if the existing or upgraded grid can serve it. This closes the workaround and keeps the facility’s energy impact inside the regulatory and rate processes Part VIII covers.
Protecting agricultural and historic land
Strength: Contextual — apply where these designations exist locally
Remove the most valuable or sensitive parcels from the negotiating table entirely, rather than negotiating their protection deal by deal. Pass an ordinance prohibiting the rezoning of agricultural districts, active farmland, and designated historic sites for data center or industrial use. A categorical prohibition is more durable than a case-by-case denial by a planning commission, which can be appealed or revisited by a future commission.
Aggressive taxation on computers and peripherals
Strength: High leverage — independent of any abatement negotiation
Most community attention goes to fighting property tax abatements on the real estate itself. A separate, often larger, lever is the local tax rate on the business personal property — specifically, “computers and peripherals” — that a data center must report. Because hyperscale facilities replace servers and networking hardware on a 3–5 year cycle, this is a recurring tax base, not a one-time assessment. Some Virginia counties have raised this rate by 70% to 550%, generating ongoing revenue that does not depend on the abatement negotiation at all and cannot be clawed back the way an abated real estate tax can.
Part V: Financial protections
Clawbacks (graduated, not binary)
Strength: Universal for any deal with tax abatements
Explicitly reject language stating that job estimates “will not limit the amount or term of the tax exemptions” (present in the Amazon Wilmington proposed agreement and many others). Replace with:
Full repayment of all abatements and incentives received if the facility closes within 5 years of first operation.
Graduated clawback: 80% repayment in year 6; declining 20% per year through year 10; 0% after year 10 provided all employment and investment benchmarks were met annually.
Clawback triggered by verified underperformance on annual reporting, not just facility closure. If employment or investment benchmarks fall by more than 20%, abatements are proportionally reduced the following year.
Best model: Durham County, NC graduated clawback. Independence MO/Nebius: investment milestones with proportional fee increases for shortfall.
Community benefit fund
Strength: High leverage
Developer establishes a community benefit fund (CBF) before construction begins, sized at a minimum 0.5% of gross annual revenue or $[X] per MW of installed capacity. CBF is administered exclusively by the community advisory board. The developer has no authority over allocation. CBF is separate from developer-funded legal and technical advisory. Uses: infrastructure impacts, workforce transition, environmental protection, energy affordability, and community priorities identified by the advisory board.
Best model: NAACP CBA template Article 4. Ashville, OH: EdgeConneX offered $35M for EPA-mandated water/sewer/road infrastructure and $3M for fire department.
Exit fees
Strength: High leverage where utility infrastructure expansion is required
Developer pays an exit fee if the facility does not operate for a minimum term (10–15 years). Fee sized to cover: stranded grid infrastructure costs, decommissioning costs exceeding the posted bond, and a community restoration fund. Protects grid operators and municipalities from exposure created when a large-load commitment is made and not honored.
Best model: Brookings (January 2026) explicitly names exit fees. FERC/ComEd/Tract TSA in Morris, IL: committed revenue contributions, minimum usage commitments, and shortfall payments.
Abatement linked to operational continuity
Strength: Universal
If the facility ceases operations for 180 or more consecutive days, all tax abatements terminate immediately. PILOT payments or taxes otherwise due begin accruing from the date of cessation, not from the end of the original abatement term.
Best model: Independence MO/Nebius: 180-day operations cessation trigger tied to immediate fee adjustments.
Property value guarantee
Strength: Contextual — strongest where residential parcels border the site
Developer guarantees the appraised values of surrounding residential properties as of a baseline date prior to construction. If a covered property’s appraised value falls below the baseline at the time of sale, the developer pays the difference to the seller. Guarantee runs for the construction period plus a defined number of years of operation; coverage for any given property ends once it sells and the guarantee has been paid or determined not to apply. This provision is standard in other CBA contexts (waste facilities, large industrial siting) and has not yet been widely adopted for data centers — there is no reason it cannot be.
PILOT and CBA negotiated as a single capped package
Strength: Universal where a PILOT or tax abatement is also being negotiated
Negotiate the community benefit fund and any PILOT (payment in lieu of taxes) or abatement agreement together, with an explicit cap on total payments and an explicit statement that CBA contributions supplement rather than substitute for forgone tax revenue. Without this, a developer can cite the CBA’s community fund as justification for a larger abatement ask — effectively having the community pay for it with money it would otherwise have received as tax revenue.
Best available model: FAS, “Fair AI-Fueled Data Center Development for Communities” (June 2026): “CBA and payment-in-lieu-of-tax agreements (PILOT) must be negotiated in tandem with a cap on total payments, ensuring community investment funds supplement, and do not substitute for, any expected tax revenue.”
Part VI: Jobs and workforce
Set realistic expectations first. Hyperscale data centers employ 20–50 permanent staff. Construction generates 1–3 years of skilled trades work. Automated construction (SoftBank/Roze AI, August Robotics, DEWALT pilots) is specifically designed to eliminate local labor during the construction phase. SoftBank announced the Roze AI robotics venture and a planned US listing in April 2026, assembling a stack of robotics and compute assets and signaling an analyst day in July 2026 (Financial Times, April 29, 2026; Capacity, May 1, 2026). The construction-automation tools are already in field pilots: the August Robotics and DEWALT downward-drilling robot was unveiled in January 2026 for data center construction (DEWALT / August Robotics, January 20, 2026). The labor window is real but narrowing: as of late 2025 the construction industry faced an estimated 439,000-worker shortage driven partly by data center growth (ITIF, January 12, 2026), and prefabricated, factory-built construction is reported to cut on-site labor by roughly 20–40 percent (DC&T Global, April 2026; Buildermuse, April 2026). The construction labor argument has present value as leverage; it will not hold past approximately 2028. Use it now, and do not build a long-term economic development case on it.
What is required:
Specific job titles, required credentials, and wage floors — not “up to X jobs” but an enumerated schedule. Minimum: all operational roles pay at least 1.5x local median wage.
Project labor agreement for construction: minimum percentage of construction hours by locally-based trades (50% within a 50-mile radius where local union capacity exists).
Apprenticeship pipeline: structured pre-apprenticeship program with a local community college, established before construction begins, with employer commitment to fill a defined percentage of technical roles from program graduates.
No workforce reduction clause: no permanent layoffs during the abatement term without 90-day community notification.
Annual workforce reporting: actual headcount by job type, average wage, and local hire percentage. Deviation of more than 20% from projections triggers a clawback review.
Part VII: Environmental protections
Water
Strength: Universal in water-stressed regions; high leverage everywhere
Absolute daily cap in gallons, tied to the facility’s specific cooling technology. Require closed-loop or liquid cooling as a permit condition; liquid cooling reduces water use by 90% vs. evaporative systems.
Triennial reconciliation: actual usage compared to permitted cap every three years; cap adjusted based on five-year actual consumption data (Mesa, AZ model).
Drought-contingency triggers: automatic reduction in permitted water use triggered by drought index thresholds (Drought Monitor D1/D2/D3 levels). In prior appropriation states, document that data center water rights are junior to existing municipal and agricultural rights.
Third-party water audit annually; results are public.
Prohibition on wells competing with residential or agricultural water supply within a defined radius.
Agricultural priority covenant recorded in deed: data center water rights are junior to all existing agricultural and municipal rights in the basin.
Best models: Lancaster CBA (20,000 gal/day hard cap); Mesa, AZ (triennial reconciliation); Project Turbo/Lake Lanier Association (negotiated 98% reduction from original request); California AB 93 and AB 2619.
Noise: compliance, monitoring, and enforcement
Strength: Universal — this section requires more specificity than most communities negotiate
Data center noise is not a single problem. There are three distinct sources with different profiles, each requiring its own controls:
Cooling fans and chillers: Continuous, 24-hour operation. Produce significant low-frequency noise (LFN, primarily in the 10–250 Hz range) that travels farther than standard measurements indicate and is perceived as a physical sensation as well as a sound. Standard decibel measurements often underreport the community impact of LFN because A-weighted dB scales discount low frequencies. Standard noise mitigation (walls, berms, landscaping) reduces mid- to high-frequency sound but is largely ineffective against LFN.
Backup diesel generators: Episodic but high-intensity. Used during grid outages and for required testing. A large data center campus may have dozens of generators; testing at different times can create near-continuous episodic events in the surrounding area.
Gas turbines (on-site self-generation): Continuous when in service. Some large facilities are building or permitting on-site gas generation to avoid grid interconnection delays. Gas turbines produce both broadband noise and LFN.
Pre-construction baseline survey (required before any permit issuance)
Developer commissions an independent acoustical baseline survey at all residential property lines within [1 mile] of the proposed facility boundary, conducted over a minimum of 14 continuous days before any site work begins. The survey must capture daytime and nighttime ambient noise levels, existing LFN levels, meteorological conditions during the measurement period, and directional sound mapping. Results submitted to the municipality and published publicly. Without an established baseline, any cap on “increase from ambient” is legally unenforceable because there is no agreed-upon starting point.
Surveys must be conducted by an independent acoustical engineer selected by the municipality. Developer pays. Developer’s own consultants may not conduct the baseline survey used for enforcement purposes.
Noise caps (what to require)
Daytime (7am–10pm): no more than [X dB(A)] above the established baseline at nearest residential property line.
Nighttime (10pm–7am): no more than [X dB(A)] above the established baseline. Nighttime limits must be more stringent than daytime, typically 5–10 dB lower.
LFN-specific limit: no more than [X dB(C) or dB(G)] above baseline in the 10–250 Hz range, measured separately using C-weighted or G-weighted scale. The A-weighted (dB(A)) standard is not sufficient to protect against cooling system LFN. Lancaster’s CBA used the right principle (noise cannot exceed ambient levels at nearby homes) but did not specify an LFN-specific measurement methodology.
Limits apply to all operational noise sources: cooling systems, HVAC, UPS equipment, and generators under all modes of operation. The limit applies to the combined noise of all facility sources, not to each source individually.
Reference: Saline Township, MI settlement: “Noise at the property lines is not to exceed 55 decibels.” This is a useful floor; the LFN provision adds what most agreements miss.
Generator testing compliance protocol
Developer provides written notice to the municipality at least 72 hours before any scheduled generator test.
Permitted testing schedule: weekdays only, 8am–5pm, no more than one test event per week per facility.
Each test event: maximum duration [2 hours] unless a full-load test is required by NFPA or insurance requirements, in which case maximum [4 hours] with 7-day advance notice.
Community representative right to be present during any scheduled test.
Municipality right to conduct unannounced compliance audits: municipality or its designated acoustical consultant may enter the property perimeter during any scheduled or purported test to conduct independent measurements. The developer must provide 24 hours' advance notice of all scheduled tests to the municipality via an automated system (not ad hoc notification).
Emergency use exemption: generators may run during actual grid outages without schedule restriction, but developer must notify the municipality within 1 hour of emergency generator activation and provide run logs within 48 hours.
Continuous monitoring system
Developer installs, operates, and maintains continuous noise monitoring stations at a minimum of [4] locations on the residential property lines closest to the facility. Exact locations selected by the municipality in consultation with its acoustical engineer.
Monitoring continuously captures dB(A), dB(C), and LFN (dB(G) or octave bands) in the 10–250 Hz range.
Data is transmitted in real time or hourly to a publicly accessible dashboard on the municipal website.
Monitoring equipment is calibrated by a certified third party every 12 months. Calibration records published.
Developer must remedy any monitoring equipment failure within 72 hours. Equipment downtime exceeding 72 hours constitutes a compliance violation.
Noise violation penalties
Class A violation (operational noise exceeding cap):
First offense: written notice, 30-day cure period, $[5,000] fine.
Second offense within 12 months: $[15,000] fine, 15-day cure period, no additional warning.
Third offense within 12 months: $[25,000] fine per day of uncured violation, plus permit suspension proceedings.
Uncured violation after 60 days from first notice: developer funds an independent acoustical engineering remediation plan at developer’s cost. Municipality approves the plan. Developer implements within [90 days] of plan approval or faces permit revocation.
Class B violation (generator testing outside permitted schedule):
Per-event fine: $[10,000].
Second offense within 12 months: $[25,000] per event.
Third offense: $[50,000] per event and automatic review of generator testing permit.
Class C violation (monitoring system failure exceeding 72 hours):
$[2,500] per day beyond the 72-hour cure period.
Aggregated violation: If a facility incurs Class A, B, or C violations in more than 3 months of any calendar year, the municipality may require a comprehensive acoustical engineering audit at developer’s cost, with resulting modifications to facility operations or design as conditions of continued operation.
Community complaint mechanism
Developer establishes a noise-complaint hotline and an online portal, publicized on all facility signage and on the municipal website.
Developer must acknowledge each complaint within 24 hours and provide monitoring data for the complaint period within 48 hours.
Five or more complaints from the same residential address within any 30-day period trigger an independent noise audit at developer’s cost. Auditor selected by the municipality.
The complaint log is published monthly on the public dashboard.
Noise dispute resolution
If the community and developer dispute whether a violation occurred, an independent acoustical engineer jointly selected by both parties (the municipality selects from a list of three candidates proposed by the developer) conducts a measurement. Cost split 50/50 unless the measurement confirms a violation, in which case developer pays all costs. Resolution timeline: measurement within 30 days of dispute notice, written findings within 15 days of measurement.
Air quality
Diesel backup generators: EPA Tier 4 Final minimum.
Battery energy storage systems (BESS): full fire safety plan reviewed and approved by local fire authority before installation; updated with each expansion. Plan must address lithium-ion thermal runaway scenarios specifically.
Annual air quality assessment, publicly published.
Part VIII: Utility and rate protections
How these proceedings work: Utilities file for special contracts, large-load tariffs, or interconnection agreements with their public utility commission (PUC). These proceedings are public record. Any party whose interests are “directly and substantially affected” can petition to intervene — meaning participate with the right to file testimony, conduct discovery, and cross-examine witnesses. Municipal legislative bodies hosting a proposed facility can often file via a simpler notice of intervention (check your state’s PUC rules; Vermont and others have streamlined this for host communities).
What to require locally (in the CBA or development agreement):
Developer pays 100% of dedicated grid infrastructure required to serve the facility: substations, transmission upgrades, distribution lines. Not shared with residential ratepayers.
Minimum demand payment: the developer pays at least 85% of the subscribed capacity, regardless of actual usage (Ohio PUC model; Virginia’s GS-5 rate class).
Residential ratepayer protection fund: developer contributes annually at $[X] per MW of installed capacity. Fund administered by the municipality to offset documented residential rate increases attributable to the facility’s grid impact.
Low-income ratepayer assistance fund: separate from the general rate protection fund above, developer (or, where negotiated through a PUC rate case settlement, the large-load customers collectively) contributes directly to a fund administered by the state ratepayer advocate or a community action association, targeted at low-income customers. Sized independently of the general protection fund — this is targeted relief, not a substitute for it.
Intervenor clause: the municipality will file as an intervenor in any utility rate case affecting the facility's service territory. Developer cannot oppose the municipality’s intervention.
Key precedents: Virginia SCC GS-5 rate class (November 2025); FERC/ComEd/Tract Morris IL TSA (April 2026); NIPSCO/Amazon Indiana Cause No. 46322; Harvard Law School “Extracting Profits from the Public.” Indiana I&M settlement (Citizens Action Coalition / Indiana OUCC intervention, 2025): Microsoft, Amazon, and Google each agreed to pay $2.5 million over five years into a low-income ratepayer fund as a condition of the utility’s large-load rate case, plus a transparency-reporting requirement on the utility.
Part IX: Infrastructure in kind
Fiber and broadband
Strength: High leverage
Data centers require extensive fiber infrastructure for their own operations. The incremental cost of extending that infrastructure to serve surrounding communities is marginal.
Developer installs excess conduit and dark fiber along all utility routes and grants a perpetual indefeasible right-of-use (IRU) to the municipality for the life of the facility.
Dark fiber must extend to the nearest underserved areas (lacking 100/20 Mbps broadband service).
Alternative or addition: developer leases backhaul capacity to local ISPs at cost-plus pricing (not market rate), enabling competitive broadband for underserved communities.
Dedicated compute capacity for public interest uses: schools, community college, public health, local government — at cost, not market rate.
Best models: Connect Humanity/Rio Grande Valley Broadband Coalition (actively negotiating this model in Texas, March 2026); Arlington, VA dark fiber IRU agreement with JBG Smith.
Emergency services pre-funding
Strength: Universal
Every data center creates emergency response obligations that the local community has not budgeted for. Data centers present unique hazards: lithium-ion battery thermal runaway, diesel fuel storage, high-voltage equipment, and complex suppression systems.
Developer contributes $[X] million to local fire departments within a defined radius before construction begins. Funds cover: specialized training (BESS fire response, HAZMAT, high-voltage incident response), apparatus, and PPE.
Developer hires and pays for a full-time fire safety coordinator for the construction period and first two years of operation.
Pre-construction fire capacity assessment: local fire authority assesses current capacity vs. data center-specific requirements. Results public. Developer funds all identified gaps.
Annual fire safety review, public.
BESS installation and expansion: fire authority reviews and approves fire safety plan before any installation or expansion.
Best models: Saline Township, MI settlement: $7M to Saline Area Fire Department; $500K each to Manchester and Clinton Township fire departments. Ashville, OH: up to $3M for fire department training and equipment. Elk Grove Village, IL: data center approvals contingent on fire services agreement.
Grid and road infrastructure
All substations, transmission upgrades, and distribution infrastructure required to serve the facility: 100% developer-funded.
All road upgrades required by construction and operations traffic: developer-funded.
Where water infrastructure is inadequate: developer funds upgrades to serve the facility and the surrounding community (Ashville, OH: EdgeConneX offered $35M for EPA-mandated water/sewer infrastructure).
Part X: Ethical use and construction-phase oversight
Civil rights and ethical-use prohibition
Strength: Contextual — apply where community concerns about end use are active
A CBA can restrict not just how a facility is built and operated locally, but what it is used for. Negotiate a clause prohibiting the facility from knowingly entering into or maintaining contracts to host workloads supporting activities that violate civil rights — for example, mass surveillance programs or immigration detention operations. This is enforceable as a contractual covenant regardless of whether the underlying activity is otherwise legal; the developer is agreeing to a use restriction as a condition of the community’s cooperation, much like other CBA provisions that require cooperation in exchange for environmental or labor terms.
Pre-construction infrastructure monitor
Strength: High leverage during the construction phase
Before construction begins, require the developer to fund an independent, state-licensed civil engineer and an on-site monitor who report directly to the municipality, not to the developer. The monitor reviews the developer’s building and infrastructure plans and has standing authority to recommend approval or disapproval of construction-phase work affecting local roads, drainage, and water systems. This catches infrastructure damage and code deviations during the build — the phase most CBAs leave unsupervised between permit issuance and post-construction inspection.
Part XI: Services and assets in kind
These provisions do not yet appear in any documented CBA template. Each has a sound legal basis and a mechanism; none has a published precedent in a data center agreement. They are the asks communities are not making because no one has made them yet.
Equipment and hardware reuse
Strength: Emerging
The municipality has a right of first refusal to acquire decommissioned servers, networking equipment, and cooling hardware at the depreciated book value (acquisition cost minus straight-line depreciation) before the equipment is sold, transferred, or scrapped. Developer provides 180 days advance notice before any major decommissioning event. For hardware the municipality acquires: developer provides data destruction certification at developer’s cost before transfer. For hardware, the municipality declines: developer connects community with certified refurbishment programs (Human-I-T model); no electronics to landfill without ITAD certification.
Developer’s data security interests are fully protected by the destruction certification requirement. Server hardware holds no data and has high residual value for schools, libraries, and nonprofits. A right of first refusal costs the developer nothing unless exercised.
Mechanism: The Confluence Technology Center (CDRPA) RFP documents a public agency's recovery and sale of decommissioned data center equipment at book value. Human-I-T documents the community distribution pathway.
Waste heat recovery for community benefit
Strength: Contextual (colder climates, cities with district energy potential); Emerging elsewhere
The developer conducts a waste-heat feasibility assessment within 90 days of the permit application. If feasible, the developer implements waste heat recovery within 18 months of facility operation, providing heat at no cost to the municipality for public buildings, affordable housing, or community facilities, up to the system's technical capacity. If waste heat is sold to a district energy operator, the municipality receives 30% of gross revenue. If not currently feasible, the developer contributes to a waste-heat infrastructure fund at $[X] per MW of installed capacity, to be held for future connection.
This is not hypothetical. Stockholm Open District Heating (2014–present): 30+ data centers heating 25,000+ apartments annually. Amazon Seattle: 5 MW of waste heat serves 4 million sq ft of space heating. Amazon Tallaght, Ireland: waste heat heats County Hall and TU Dublin campus. Equinix/Markham, Ontario: 14 million sq ft of mixed-use development heated. The technology works at scale; the missing piece is the contractual requirement.
Building shell reuse covenant
Strength: Emerging
If the facility is decommissioned, the developer may not demolish the building shell without first offering the municipality a right to purchase the shell at depreciated replacement value. Offer stands for 180 days. If the municipality acquires: developer removes specialized infrastructure (electrical, cooling, battery banks, HVAC) at developer’s cost before transfer. Permitted uses: public broadband infrastructure, school or library technology hub, manufacturing, emergency services, general commercial or industrial. Covenant runs with the land and binds successors.
The Independence, MO/Nebius “green field restoration” requirement is actually worse for the community than a reuse covenant: the building gets demolished. A 500,000-sq-ft structure with heavy power infrastructure already on-site has substantial value as a community asset if the specialized equipment is removed. Brookings (January 2026) explicitly asks whether “an abandoned data center can be repurposed as a community asset, including a youth center or incubator for aspiring tech entrepreneurs.”
Compute access for public interest uses
Strength: High leverage where the developer needs community cooperation on the timeline
Developer provides dedicated compute capacity (minimum X GPU-hours/month, negotiated based on facility scale) for public-interest uses: school districts, community college research, public health analysis, and local government. At cost, not market rate, to qualifying public entities. Duration: life of the facility or 20 years, whichever is shorter. Annual reporting on access provided by the institution.
Data centers generate value by converting physical infrastructure into compute workloads at revenue multiples of 30–40x (Anjney Midha, Stanford CS153, May 2026). Communities providing the physical substrate receive none of that value unless specifically contracted for it. Connect Humanity (March 2026): “dedicating server capacity for local innovation, supporting research and startups.”
Renewable energy with local benefit
Strength: High leverage where renewable commitments are developer priorities
Beyond “100% renewable,” require:
Local sourcing: minimum 50% of renewable energy sourced from projects within 50 miles, creating local construction and maintenance employment.
Community offtake: excess clean energy generation sold to the municipal grid at cost-plus 10%, not market rate.
Developer partners with municipality on siting and developing new local renewable projects if the existing local supply is insufficient.
Part XII: Long-term protections
Decommissioning bond (sized and posted)
Strength: Emerging — the most important novel provision in this guide
A surety bond, letter of credit, or cash escrow sized to the estimated cost of full decommissioning: removal of all specialized electrical infrastructure, cooling systems, battery banks, and mechanical equipment; environmental remediation; and site preparation for next use. Sizing: engineer’s estimate at permit issuance, with a minimum of $[X] per MW of installed power capacity. Posted before construction begins. Reviewed and adjusted every five years using an updated engineer’s estimate. Remains in effect until decommissioning is completed and certified by a licensed engineer.
Anticipate and address the developer’s objection: Developers will argue that the data center shell has residual value (e.g., logistics conversion), reducing the net decommissioning cost. Counter: the specialized infrastructure — cooling systems, power distribution, battery banks, HVAC — must be removed regardless of what happens to the shell, and the removal cost is not offset by the shell's salvage value. Document these cost components in your engineer’s estimate.
Why posted is different from contractual: The Independence MO/Nebius agreement includes a contractual decommissioning obligation. Contractual obligations do not survive insolvency. A posted bond does.
Best available models: Taft Law memo (May 7, 2026): the first structured five-issue legal analysis of data center decommissioning bonds; used to anticipate developer objections. Amherst, MA solar decommissioning fund agreement: engineer-estimated, posted within 60 days of commercial operation, reviewed every five years.
Change of control and successor obligations
Strength: Universal
No assignment, transfer, or sale of the facility or the entity holding it without the prior written consent of the municipality. All CBA obligations bind successors, assignees, and any acquiring entity. Municipality’s consent may not be unreasonably withheld; the primary condition is that the successor commits in writing to all existing CBA obligations. Developer must notify the municipality within 30 days of any proposed change in ownership exceeding 25% of equity or any change in the ultimate beneficial owner.
Without a successor clause, a developer who cannot meet its obligations sells the facility to an entity not bound by the CBA. The community renegotiates from zero.
Best models: NAACP CBA template: explicit no-assignment-without-consent; obligations binding on successors, assigns, heirs, and administrators. Thomas Gaultier CBA negotiation guide: “successor clauses ensure obligations transfer if the project changes ownership.”
Mandatory performance review at 5-year intervals
Strength: Universal
Developer submits to a public performance review every five years covering: actual vs. projected employment by job type and wage, actual vs. permitted water and energy use, infrastructure cost allocation, community fund contributions and disbursements, and decommissioning bond adequacy. Results published within 60 days. Material underperformance (more than 20% shortfall across multiple benchmarks) triggers an automatic clawback review and accelerated bond review.
Part XIII: Sequencing the negotiation
Stage 1: Transparency before money
Before any non-opposition commitment, secure:
Developer-funded community advisory team in place
Ultimate parent disclosed in writing
Independent economic and environmental impact assessment commissioned
90-day disclosure rule in effect
Pre-construction noise baseline survey commissioned
At Stage 1, the community makes no commitment not to oppose the project.
Stage 2: Project-specific mitigation
After the impact data is available:
Negotiate the full demand menu based on actual project specifications
Scale each provision to the documented impact it mitigates
Non-opposition tied to completion of Stage 2 and execution of a binding CBA
Critical rule: Do not commit to non-opposition at Stage 1. The NAACP template: “any commitment not to oppose the project should be conditioned on completion of all stages.”
Non-opposition clause structure. Tie any non-opposition commitment to two sequential conditions, not one. First, condition non-opposition on completion of the Stage 1 transparency requirements above. Second, treat the specific dollar amounts and mitigation commitments as a separate, later negotiation that occurs only after the independent impact assessment discloses actual environmental and infrastructure impacts. Signing a single non-opposition agreement that bundles both conditions together lets the developer lock in community silence before the impact data exists to know what mitigation is even needed.
Part XIV: Enforcement — what makes a CBA real
A CBA without enforcement is marketing. A community benefit agreement (CBA) is a binding contract in which a developer commits to specific protections and benefits in exchange for the community's cooperation. See Glossary at the bottom for a link to understand CBAs. These are important to know.
WHAT IT DOES
Third-party audit rights
Community can commission audits at developer’s cost; the auditor is selected by the community
Public dashboard
Real-time or annual data on water use, energy use, noise (including LFN), jobs, and community fund; hosted on municipal website
Graduated penalties
See noise section for structure; the same principle applies to all provisions
Phase-linkage
Developer may not commence Phase 2 while in material breach of Phase 1 obligations
Successor clause
All obligations bind future owners
Joint Implementation Committee
Quarterly meetings, public minutes
Community standing to sue
CBA grants the community coalition (not just the municipality) standing to enforce — important where the municipality may face political pressure not to act
Presumptive evidence clause
A documented non-compliance finding by the Community Advisory Board or an independent auditor constitutes presumptive evidence in any enforcement action, arbitration, or litigation — shifting the burden to the developer to rebut it rather than the community having to re-prove the violation
Fee-shifting / developer-paid enforcement costs
Developer pays the community’s reasonable attorney fees and costs in any arbitration or litigation made necessary by the developer’s material non-compliance, not just in a fully successful enforcement action
Dispute resolution
Arbitration before litigation; the community’s arbitration costs are covered by developer
The asks no one is making yet — legally sound, without precedent
These provisions have no published CBA precedent as of June 2026. Each is legally defensible. These are the asks communities are not making because no one has made them yet.
Equipment/hardware reuse (right of first refusal at book value)
Data destruction certification protects developer; residual value serves the community
Communities provide infrastructure that created the asset; they deserve optionality on its reuse
Building shell reuse covenant
Covenant runs with land; specialized equipment removal at developer’s cost
Green-field restoration destroys community value; reuse covenant preserves it
Waste heat recovery obligation
Feasibility assessment + implementation + revenue sharing
Proven at scale in Stockholm, Amazon, Equinix; the only missing is the contractual requirement
Compute access for public interest
GPU-hours at cost to schools, public health, and local government
Marginal cost is minimal; communities provide the infrastructure that generates the value
Sized and posted the decommissioning bond
Surety bond posted before construction; in effect until decommissioning is certified
Posted bond survives insolvency; contractual obligation does not
Chamber NDA bypass prohibition
Ordinance passed before developer arrives
Closes the Arkansas pattern before it can be used
Renewable energy local sourcing
50% sourced within 50 miles as a permit condition
Turns developer’s clean energy mandate into local jobs
LFN-specific noise monitoring
dB(C) or dB(G) measurement at property line, continuous monitoring
Standard A-weighted measurements miss the primary community impact of cooling systems
Noise baseline survey before permits
Independent acoustical engineer, 14-day continuous measurement
Without a baseline, “no increase from ambient” is unenforceable
Procedural duty of care / premortem requirement
Officials document counterfactual analysis and failure-mode review before voting
Converts a “trust us” approval into a discoverable, challengeable record
Cross-jurisdictional coordination agreement
Neighboring jurisdictions agree on a common floor before any developer approaches either
Removes the bidding-war dynamic developers rely on to erode net community benefit
Categorical variance / special-use prohibition
Ordinance passed before any application arrives
Forecloses the hardship-variance backdoor around negotiated zoning terms
Civil rights / ethical-use prohibition
Contractual covenant restricting workload types (e.g., surveillance, detention)
Enforceable regardless of the legality of the underlying activity
Pre-construction infrastructure monitor
Developer-funded, municipality-reporting civil engineer with construction-phase review authority
Covers the supervision gap between permit issuance and post-construction inspection
Presumptive evidence clause
CAB/auditor non-compliance finding presumptively valid in enforcement proceedings
Shifts the burden of re-proof from the community to the developer
PILOT/CBA decoupling cap
CBA and PILOT negotiated together with a cap and an explicit non-substitution clause
Prevents the community fund from being used to justify a larger abatement
Property value guarantee
Developer guarantees appraised value of bordering residential parcels as of a baseline date
Standard in other industrial-siting CBAs; not yet broadly adapted to data centers
This guide is not legal advice, and I am not an attorney. It is a civic research and discussion resource meant to help communities ask better questions and negotiate from a more informed position. Before relying on it in any actual decision, please verify local facts and consult qualified legal, engineering, financial, environmental, or policy professionals as appropriate.
This guide was assembled as a contributed effort, to the best of my ability, with the assistance of AI. You are welcome to reuse it, adapt it, and move it into any useful form to help your efforts. Consider it open, in the spirit of Creative Commons CC BY 4.0 Attribution. Check my work. If you find an error or something I’ve missed, I’d be glad to hear it, offered in the same spirit it was made: as a contribution to the effort.
