What is a data center community benefits agreement?

A community benefits agreement, or CBA, is a negotiated contract that sets out what a developer will provide to a host community and how those commitments can be enforced.

Better agreements between data centers and communities. Contribute to the Open CBA.
Policy Frameworks brings existing agreements and community contributions together to develop a shared starting point.

For a data center, that can mean commitments on water use, infrastructure costs, jobs, environmental protections and community funding. The parties may include community organizations, a local government and the developer. The exact rights depend on the contract and applicable law. Columbia Law School’s agreement database describes this range of arrangements.

Published September 7, 2026 by Policy Frameworks.

A promise needs a way to check it

A useful agreement connects each commitment to a responsible party, a deadline and a way to measure delivery. It also explains who receives reports, who can challenge a missed commitment and what happens next.

A payment announcement alone leaves those questions unanswered. Read the underlying document, including its exhibits and amendments. An agreement can contain both firm requirements and softer commitments to make reasonable efforts.

What can a data center agreement cover?

These are topics to negotiate, not terms every CBA contains. Compare provisions by topic.

Not every development agreement is a CBA

A tax incentive agreement sets conditions for public financial assistance. A utility agreement sets service and infrastructure obligations. A permit imposes conditions on development. A CBA focuses on negotiated community benefits. A project may have several of these documents, and its protections may be spread across them.

Our agreement collection includes these related instruments, with their document types identified. Inclusion does not mean every record is a signed CBA or that its benefits have been delivered.

Read examples alongside their sources

The Lancaster AI Hub record examines a city-published CBA draft covering environmental commitments and community funds. The Piqua record shows how development and water agreements address different responsibilities. The St. Louis record separates permit conditions from a term sheet for a future CBA. Each record links to the original material so readers can check the wording and document status.

Why build an open framework?

Communities should be able to learn from earlier negotiations. A shared starting point can make useful language easier to find, reveal choices that deserve attention and give participants something concrete to improve.

That is the purpose of Policy Frameworks. We’re collecting existing agreements and contributions from experts and communities to develop an evolving agreement that communities can adapt. AI will help compare language; expert review will guide what goes into the draft.

An open process also gives people a way to question the starting point. Which concerns are missing? Who gets to enforce a promise? Does a clause still work when a project changes hands? Contributions can improve the questions as well as the wording.

No shared text can decide what a particular community should accept. Local priorities, representation and legal review remain essential. We have not yet published the first model agreement. See how the draft will develop.

Frequently asked questions

Who negotiates a community benefits agreement?

Typically a developer and community representatives, sometimes with a local government. The US Department of Energy describes CBAs as negotiated agreements with communities, often represented by a coalition. Who participates and whose interests they represent are important questions from the start. DOE’s CBA FAQ.

Is a community benefits agreement legally binding?

A CBA is intended to be a binding contract. Whether a particular provision is enforceable, and by whom, depends on its wording, the parties and applicable law. A draft, press release or voluntary pledge does not establish the same rights as an effective contract.

Does a CBA mean the community supports the project?

Some agreements exchange benefits for support or non-opposition. Read the actual obligations: the support of signatories does not establish that every resident supports the project. DOE’s FAQ explains this common exchange.

What is the difference between a community benefits plan and an agreement?

A plan describes intended actions. A negotiated agreement establishes contractual obligations between its parties. They can be connected, but the labels should not be treated as interchangeable. DOE discusses how plans can develop into agreements.

Can one agreement work for every community?

No. Water availability, utility capacity, local priorities and legal authority differ. An open framework provides questions and draft language to adapt through local negotiation and legal review.

Can a CBA guarantee that benefits will be delivered?

A contract can set obligations and remedies. Delivery still needs to be monitored. Look for reports and payment evidence, and distinguish a commitment in the document from a verified result.

Is the open agreement ready to use?

The first model agreement is still being developed. The existing-document library is available now. The planned draft will draw on reviewed contributions and identify changes through version history.

Who can contribute?

Anyone with relevant experience, a source document or a proposed improvement is welcome. You do not need to be a lawyer. Explain what you would change and why; editors review submissions before publication.

Who runs Policy Frameworks?

Policy Frameworks is an independent open framework powered by Shaper Collective. Read about the project and its lead, Ben Newman.

Help build a better starting point

Bring your experience to the open community benefits framework.

Contribute to the Open CBA