What Is a Community Benefit Agreement? – Data Center Deals With Towns
Promises are cheap at a public hearing. A developer says the site will be quiet, use little water and hire locally, and everyone nods. Five years later the original team is gone, the property has been sold twice and nobody can find where those promises were written down. Communities have started asking for something sturdier. What is a community benefit agreement, and what does a good one look like for a data center?
A community benefit agreement (CBA) is a legally binding contract in which a developer commits to specific benefits and protections for a community, usually in exchange for the community's support or for local approvals. A good one for a data center sets measurable caps on water and noise, commits to local hiring and community payments, and reports results publicly, with penalties or clawbacks if the developer falls short. It can be signed with community groups, a local government or both. Weak ones lean on "good faith" language that is hard to enforce.
What Is a Community Benefit Agreement, Exactly?
A community benefit agreement is a private contract with enforceable terms, not a policy statement or a press release. The U.S. Department of Energy describes CBAs as legally binding contracts between community groups and developers, and separates them from the Community Benefits Plans it asked for in federal funding applications.
CBAs are not new. One of the best-known early examples was signed in Los Angeles in 2001 for a sports and entertainment district near the Staples Center, with commitments on jobs, wages and affordable housing. What is new is applying the tool to data centers, which bring large tax bases but relatively few permanent jobs and real questions about water, noise and power.
How Is a CBA Different From Zoning Conditions or a Tax Deal?
The difference is who signs and who can enforce it. Zoning conditions are imposed by the local government through the land use approval. A development agreement is a contract between the developer and the government. A tax incentive agreement sets the terms of abatements or exemptions. A CBA may involve community groups directly, and it can cover things zoning law cannot easily reach.
| Tool | Parties | Typical subjects | Enforced by |
|---|---|---|---|
| Zoning conditions | Local government (imposed) | Setbacks, noise, height, screening | Zoning enforcement |
| Development agreement | Developer and local government | Roads, utilities, phasing, payments | Contract law |
| Tax incentive agreement | Developer and state or local tax authority | Abatements, job and investment targets | Clawback terms |
| Community benefit agreement | Developer and community groups, sometimes the government | Water, noise, hiring, funds, reporting | The signers, through contract law |
In practice, these overlap. A town may fold community benefits into a development agreement, or a CBA may sit alongside zoning conditions that repeat its noise limits. Check with counsel on what is enforceable in your state.
What Goes Into a Data Center CBA?
Most data center CBAs address the concerns that drive local opposition. Brookings made the case in early 2026 that community benefit agreements are necessary for data centers, recommending public, binding agreements with water caps, noise limits, job and tax dashboards and clawbacks. Common terms include:
- Water caps, stated in gallons per day, or a commitment to closed-loop or dry cooling.
- Noise limits at property lines, with monitoring and limits on generator testing hours.
- Local hiring targets, apprenticeships and contracts for local businesses.
- Payments into community funds for schools, parks, emergency services or utility bill assistance.
- Public reporting on jobs, taxes paid, water use and energy use.
- Commitments on who pays for grid upgrades, so costs do not shift to residents.
- Clawbacks or penalties if targets are missed.
The best terms are measurable. "Minimize water use" means little. "No more than a set number of gallons per day, reported quarterly" can be checked by anyone.
Are There Real Data Center CBAs?
Yes, though they are still rare. Lancaster, Pennsylvania, is widely cited as an early example. Brookings notes the Lancaster agreement includes a water cap of 20,000 gallons per day. Columbia Law School's Sabin Center, in a May 2026 review of community benefits agreements and data center development, described Lancaster as likely the first data center CBA, with about $20.25 million in contributions and roughly 300 jobs.
Brookings also points to approaches in Cedar Rapids, Iowa, and El Paso, Texas, where a planned Meta facility is associated with closed-loop cooling. The details differ from place to place, which is part of the point. A CBA is negotiated for the community it serves.
What Does a Strong Clause Look Like?
A strong clause names a number, a unit, a measurement method, a reporting schedule and a consequence. Here is an illustrative example of how the pieces fit together, not language from any real agreement:
Illustrative example: Average daily potable water use shall not exceed a stated number of gallons per day, measured at the utility meter and averaged over each calendar quarter. The operator shall post quarterly meter data online within 30 days of quarter end. Each quarter above the cap triggers a fixed payment to the community fund and a corrective plan within 60 days.
Noise clauses work the same way. They set a dBA limit at specific property lines for day and night, require a monitoring station, limit routine generator testing to set weekday hours and spell out what happens after a complaint. A clause like "the operator will be a good neighbor" has none of those parts, which is why it rarely helps anyone later.
Payment clauses should say how much, when, to whom and for what purpose. A fund managed by a named local board with public minutes is easier to trust than a vague promise of "community investment."
Who Enforces a Community Benefit Agreement?
The parties who signed it enforce it, usually through contract law. That is both the strength and the weakness of the tool. If a coalition of neighborhood groups signs, those groups need the money and legal help to monitor the developer and go to court if needed.
The Sabin Center review flagged exactly that problem: vague "good faith" language and the limited enforcement capacity of small towns. A county with a part-time attorney may struggle to audit a billion-dollar operator's water reports.
Good agreements plan for this up front:
- Independent monitoring, paid for by the developer.
- Public data posted on a regular schedule.
- Clear remedies: fixed payments, escalating penalties or required fixes.
- Terms that bind future owners if the site is sold.
Why Would a Developer Sign One?
Developers sign CBAs because they trade uncertainty for a clearer path. A signed agreement can turn organized opposition into neutral or supportive voices at the hearing, reduce the risk of lawsuits and give the project a public record of commitments it can point to.
There are costs. Payments and caps cost money, and limits on water or generator testing can constrain the design. A developer that does not yet know its tenant or cooling system may hesitate to cap water use. From where I sit: if you cannot commit to a number, you probably have not finished designing the cooling plant, and the community is right to ask.
How Should a Town Approach a CBA?
Towns get better agreements when they prepare. A short checklist:
- Decide what matters most locally: water, noise, jobs, power bills or revenue.
- Get independent technical advice on water, noise and power, not just the developer's studies.
- Ask for measurable targets with units and reporting dates.
- Insist on enforcement tools and money for monitoring.
- Make the agreement public.
- Make sure it binds successors and future phases.
Be careful about the size of what is being promised. A headline that says "up to" a certain number of megawatts may describe a final build-out years away. Learning to read a data center announcement closely helps a town figure out which phases its agreement should cover and when the benefits actually start.
A Community Benefit Agreement Turns Promises Into Terms
The test of a community benefit agreement comes years after the ribbon cutting, when the original team has moved on and someone pulls the document out of a drawer. If it names numbers, reporting dates and penalties, and binds whoever owns the site by then, it will still mean something.
If you are a developer, bring numbers you can live with. If you are a town, bring your own experts and insist on enforcement. Either way, get the agreement in writing, make it public and have counsel review it before anyone signs.