On April 21, 2026, the St. Louis Board of Public Service voted unanimously to grant a conditional use permit for a $3 billion data center at the old Famous-Barr warehouse. The developer had a sustainability page. Every developer does. What the board approved was a different document: a term sheet the city could take to court, recorded against the land, with dollar penalties attached to missed jobs and missed tax revenue, and an occupancy permit the city can revoke.
That is the whole distinction. A data center community benefits agreement is not a longer press release. It is a contract. If your project is heading toward a hearing, or your county is about to host one, the difference between the two is the difference between a vote and a moratorium.
what a community benefits agreement actually is
A community benefits agreement (CBA) is a legally binding contract between a developer and a host jurisdiction or community coalition. It lists specific, measurable commitments the developer makes in exchange for approval, and it gives the community a way to collect when those commitments slip.
Three tests separate a CBA from a promise:
| test | what it means | what fails the test |
|---|---|---|
| enforceable | Signed by parties with standing. Breach has a defined consequence: liquidated damages, permit hold, revocation, or a lawsuit the host can win. | "We are committed to being a good neighbor." |
| recorded | Filed in land records or with a public authority, so the obligation follows the property through a sale, a refinance, or a new tenant. | A pledge on a corporate website that can be edited Tuesday. |
| recourse | Someone other than the developer holds the remedy, and a breach is public. In St. Louis that someone is the city. A neighbor coalition as a signatory is stronger still — and rarer. | A voluntary ESG report with no third party and no penalty. |
A community benefits agreement is a contract the host community can enforce. A press release is a promise the developer can revise.
Brookings made the same case in early 2026: data center CBAs should be legally binding, developed with the host community, and never hidden behind a non-disclosure agreement. Read their argument alongside this one; it covers jobs, rates, and digital access well. This post is about the terms most CBAs still leave out: the water, the farm, and the living buffer.
two people at the same table
Hold both of these at once, because a CBA has to.
The neighbor who was burned. In Lee County, North Carolina, residents were invited in 2025 to weigh in on rezoning 430 acres for what the applicant's representative described as a "light industrial business park." On June 8, 2026, a Virginia developer announced a $900 million, 90-megawatt data center on the same acres. About 150 people came to the July 13 commissioners' meeting; nearly 2,500 signed a petition asking for a moratorium and for the public records behind the site. Their first grievance was not megawatts. It was that they had been told a different story. No sustainability PDF repairs that.
The developer who needs a clock. In Joliet, Illinois, Hillwood and PowerHouse sat through a public hearing that ran past midnight on a Monday in March 2026. On Thursday the council voted 8-1 to approve an annexation agreement for a 795-acre campus, within fifteen minutes of opening the meeting. The developer had committed up to $100 million to the city: $20 million within 30 days of closing, then $20 million tied to permits in each of four phases. That structure is a clock. The developer knows what it owes and when. The city knows when it can stop issuing permits.
The neighbor wants recourse. The developer wants certainty. A press release gives neither. A CBA gives both.
what st. louis put in writing
The Armory Innovation District package shows what "enforceable" looks like line by line. From the city's release and the recorded conditional use provisions, the developer must:
- Use a closed-loop cooling system with air-cooled chillers to minimize water consumption.
- Pay any new large-load water rate set by a cost-of-service study, fund a hydraulic model study, and make other water customers whole for any detrimental impact.
- Source at least 50 percent of the facility's load from renewables within five years of operation.
- Enclose generators in acoustically treated structures, test them only in daytime windows and never on bad-air days, and report waste heat annually.
- Not seek local tax abatement for the data center or the Armory.
- Contribute $30 per square foot of approved development to a city fund for greenways, digital access, distributed energy, and weatherization. The city estimates that at roughly $15 million; the St. Louis Business Journal reported $15.7 million on a different square-footage assumption. This post uses the city's number.
- Pay $15,000 in liquidated damages for every $100,000 the project falls short of projected annual tax revenue by 2029, and $2,000 per job short of escalating minimums for 20 years.
- Record the CBA with the Land Clearance for Redevelopment Authority as a property agreement for the life of the site. The city can revoke the occupancy permit and seek financial compensation in court.
- Publicly disclose tenants, unless national security prevents it.
The board chair said on the record that a recorded, legally binding property agreement for the life of the site "generally is not something that we entertain." They entertained it because a month of public objection had made the alternative impossible.
Notice what the list contains: engineering, money, process, and on-site design (cool roof or green roof, greenway screening, stormwater and heat-island work). Those are developer-cost measures on the pad. What it does not contain is a funded watershed, a protected acre of farmland, or a living buffer off the site, in the basin the campus drinks from. On a dense urban site served by a public water utility that wants the customer, that gap is smaller. In a farm county it is the hearing.
joliet: approved with a package, not approved because opposition vanished
Joliet is sometimes told as a story where a big enough check made the hearing go quiet. It did not. The public hearing ran six and a half hours. The lone no vote came from the councilwoman whose district borders the site, who called that part of the city "the dumping ground for what other districts don't want." The 795 acres are farmland, and they are going into the campus.
What Joliet did get is an annexation agreement with a payment schedule, sidewalks, streets, emergency-services planning, and utility coordination, structured so each phase pays before it builds. That is a CBA in function under a different title. It is also a city-services agreement. The living systems on and around those acres are not line items in it as reported. That is not a criticism of Joliet. It is the gap every county now negotiating a campus can close.
press release vs cba vs funded line item
The contrast is the argument. The third column is where ensurance enters, and only there: as a way to make a living-system commitment inside the CBA pass the same three tests the rest of the agreement passes.
| question | press release | community benefits agreement | ensurance-backed line item in the cba |
|---|---|---|---|
| who signs | Nobody. Marketing publishes it. | Developer and the city, county, or authority. | Same parties. The line item names a place and a funded instrument. |
| where it lives | A web page. | Land records or a public authority's files. | The CBA, plus a public record of the funding anyone can check. |
| if it is missed | It is edited. | Liquidated damages, permit hold, revocation. | Same remedies. The funding is already committed, so a breach is visible early. |
| water | "Committed to water stewardship." | Closed-loop cooling; cost-of-service rate; make other customers whole. | Fund the same-basin wetland or recharge project the campus draws on, up front, with reported outcomes. |
| farmland | "We respect the region's agricultural heritage." | Rarely addressed. Sometimes a setback. | Fund conservation easements on nearby working acres at a stated ratio, held by a land trust. |
| noise and the night | "State-of-the-art acoustic design." | Setbacks, enclosures, decibel limits, testing windows. | Fund a living buffer that attenuates and shades, in addition to setbacks, not instead of them. |
| tax abatement | "Millions in new tax revenue." | A clause not to seek local abatements; penalties if revenue falls short. | Nothing to add. Ensurance does not fix tax math. |
| transparency | Quarterly ESG PDF. | Public conditions, tenant disclosure, annual reporting. | Funding and outcomes public by default: a trust answer before it is a technology answer. |
| time horizon | Until the next rebrand. | Life of the property, if recorded. | Path to permanent protection of the named system, outlasting the lease and the tenant. |
the tax-abatement row deserves its own paragraph
Nothing generates hearing-room anger faster than a trillion-dollar tenant asking a county for a break. It does not matter that the payment in lieu of taxes looks large on the slide. Residents do the division: acres in, permanent jobs out, and a company worth more than the state asking for less. St. Louis defused that row by having the developer agree in writing not to seek local abatements, and by attaching liquidated damages to the revenue projections themselves.
Ensurance cannot fix the tax math and cannot make an abatement popular. What it can do is sit inside a CBA that already fixed the tax math, as the environmental half of the same deal, so the community is not asked to choose between a fair fiscal package and a funded watershed. In a well-built agreement they are two rows of one document.
secrecy is the fastest way to lose
Lee County is the illustration, not the exception. The pattern is a rezoning described in general terms, an NDA-covered tenant, a name that says "technology park," and a reveal after the entitlement is in hand. Sometimes that is a tenant's confidentiality requirement passed down the chain. Either way the community reads it as deception, and the minutes of the earlier meeting prove it.
Brookings is blunt: CBAs should not sit under non-disclosure agreements, because transparency is how a community understands both the costs and the benefits. St. Louis wrote tenant disclosure into the agreement. Joliet negotiated in public for months. The developers who keep the trust are the ones whose commitments live somewhere the neighbors can read.
which approval can carry the clause
A funded line item has to ride on a vehicle that can take conditions. A conditional use permit and a recorded annexation agreement can. A general-use rezoning often cannot — Lee County's own record is the lesson: voluntary buffer promises could not be codified because binding conditions do not attach to that kind of approval. Arrive with the clause and the vehicle. A jurisdiction also cannot demand anything it likes; these land as developer-offered commitments inside a conditional approval, which is why nexus and proportionality still apply.
write the living systems into the agreement
Here is the door. Most CBAs now handle the money half of the hearing well: the fund, the jobs, the rates, the abatement clause. The living-system half, the reasons communities actually block campuses, still arrives as engineering (closed-loop) or as aspiration (stewardship). The move is to write those systems into the CBA as funded line items that pass the same three tests as everything else.
An ensurance-backed line item names the place: this basin, these acres, this buffer. It funds that place up front, so the money is committed before the vote rather than pledged for later. It reports publicly, so the county, the neighbors, and the tenant verify the same numbers, and nobody has to believe the sustainability page. Watersheds, working farmland, and living cover exist whether or not anyone signs anything. Ensurance is how a campus funds those systems in the same basin it draws from. It is not what those systems are.
The funded, checkable form of that commitment is a certificate: a line item the developer holds, tied to a named living system, with proceeds routed to its protection. A certificate is a funded, publicly checkable commitment to a named living system — not a title instrument and not a demolition bond.
Three line items a county can ask for, and a developer can offer, on day one:
1. Same-basin watershed. The CBA already requires closed-loop cooling and a hydraulic make-whole. Add a funded commitment to the wetlands or recharge area the campus depends on, through accounts like inland-wetlands.ensurance or clean-water.ensurance, with groundwater and flow metrics reported annually. The water spoke of this series, data centers drink water, ensurance refills the glass, goes deeper.
2. Farmland at a ratio. For a campus that will take working acres, the CBA states a protection ratio and funds conservation easements on nearby farmland through rural-open-space.ensurance, held by a qualified land trust and recorded like the rest of the agreement. The farm spoke, data centers don't have to eat the farm, covers the structure.
3. Living buffer. Setbacks and enclosures stay in the CBA. Alongside them, fund a deep vegetated buffer that attenuates sound, shades the edge, and doubles as habitat. The noise spoke, the cheapest noise wall is a forest, has the numbers. A buffer does not erase a 24/7 hum or a generator test. Do not let anyone tell the neighbors it does.
The clause is not exotic. Prior to issuance of the first building permit, developer shall fund a living-system line item — priced like the rest of the CBA, whether as a share of the community fund or on the order of the city's $30 per approved square foot — toward permanent protection of [named watershed, easement acres, or buffer] through [named instrument], and shall publish annual outcome metrics; failure to fund or report constitutes a default subject to the remedies in section [x]. One sentence, in a document St. Louis has already shown a board will approve.
Where we stand. The instruments are live and the data center solutions page is live. Volumes are small, and no county has yet recorded an ensurance-backed line item in a data center CBA. The first one will be a template. The developer who brings it arrives with the funded place instead of negotiating it after the vote fails.
what to do next
If you are a developer or land assembler, read the St. Louis conditions in full, then read how to get a data center approved faster for the hearing-package checklist that maps living-system line items to each objection.
If you are a county, city, or econ-dev staffer, start from Brookings' CBA framework for jobs, rates, and access, then add the three line items above. Ask the developer which basin the campus drinks from and which acres it displaces. The answer belongs in the agreement.
If you are a neighbor, ask one question at the hearing: where is this written, and what happens if they miss it? If the answer is a web page, you already know what you have.
If you are a tenant whose logo will sit on the building: if you lease the hall, you inherit the fight.