Development Agreements for Data Center Projects: What They Cover

A development agreement is a binding contract between a local government and the owner or developer of a specific property. It sets out what the project may build, under which rules, on what schedule and with what obligations on each side. It is usually approved by the city council or county board after public notice and a hearing, adopted by ordinance or resolution, and recorded against the land so it binds future owners.

Many states have statutes that expressly authorize development agreements and set their limits, such as the maximum term, required contents and approval procedure. Other states have no specific statute, and local governments rely on general contracting authority, conditional zoning, annexation agreements or proffer systems to reach similar results. The name also varies. Some jurisdictions call it a development agreement, others a master development agreement, a pre-annexation agreement or a project agreement. The legal effect depends on the state, not the title.

A data center campus differs from a typical subdivision or warehouse in ways that make a long-term contract useful:

• Long build-outs. A campus may be built in several phases over many years, following the utility’s power delivery schedule. Without vesting, each later phase could face new zoning standards.
• Large infrastructure. Roads, water and sewer extensions, and sometimes reclaimed water lines need to be sized and paid for before the full campus exists.
• High public interest. Officials often want enforceable commitments on noise, buffers, generator testing, water use or community benefits, beyond what the zoning code requires.
• Coordination with incentives. Tax abatements or payment-in-lieu-of-tax arrangements usually sit in separate agreements, but their investment and job thresholds need to line up with the development schedule.

For the local government, the agreement gives certainty that promised improvements and commitments will be delivered. For the developer, it gives certainty that the rules will not change partway through a multi-phase investment. It also often supports a rezoning request; our guide to zoning for data centers covers how conditional rezoning and planned developments work.

Not every agreement includes every term, and some states limit what can be required, for example by restricting exactions to costs reasonably related to the project’s impacts.

Vesting is the core benefit. Under most development agreement statutes, the land use rules in effect when the agreement is approved govern the project for its term, even if the jurisdiction later amends its zoning code, adopts new data center standards or enacts a moratorium. That matters for a campus whose later buildings may not start for years.

Vesting has limits. Agreements generally cannot freeze building, fire and life safety codes, which update on their own cycle. Many statutes let the jurisdiction apply new rules needed to address a serious threat to health or safety, or rules required by state or federal law. Fees and utility rates may or may not be fixed, depending on how the agreement is written. The term itself is limited; state statutes often set a maximum, and phased projects need milestones that match a realistic schedule rather than a hopeful one.

Infrastructure terms are usually the most negotiated. Common arrangements include the developer building a road or water main to public standards and dedicating it, oversizing a line for future users with reimbursement from later connectors, or the jurisdiction committing to build a public improvement by a date. Each of these needs clear specifications, cost responsibility and a fallback if one side does not perform.

Electric service is the gap. Investor-owned utilities are regulated by the state utility commission, and many cooperatives and municipal utilities have their own governing boards, so a city or county development agreement usually cannot commit electric capacity. Power is secured through the utility’s own process and contracts, covered in large-load tariffs and electric service agreements. Where a city owns the electric utility, power terms may be negotiated alongside the development agreement, but they are often still handled in a separate utility contract.

A project may end up with several overlapping documents. Zoning conditions or proffers attach to a rezoning or special use permit. A development agreement sets long-term rules and obligations. A tax abatement or payment-in-lieu-of-tax agreement handles property tax treatment. An annexation agreement may set the terms for bringing the land into a city. These need to agree with each other on phasing, investment amounts and dates. Mismatched milestones across documents are a common source of later disputes. Our guide to data center tax incentives covers clawbacks and thresholds in more detail.

1. 01Confirm the state enabling statute, the maximum term and the approval process, including any referendum exposure.
2. 02Check that the vested rules cover what the full campus needs: height, building area, accessory structures, substations and generator yards.
3. 03Make phase milestones achievable even if power arrives later than planned, with extension rights.
4. 04Define infrastructure specifications, cost shares, reimbursement terms and what happens if the public side does not deliver.
5. 05Read operational commitments against the engineering: sound limits, buffers and water source must be achievable with the cooling design.
6. 06Check assignment rights for affiliates, buyers of individual phases and lenders.
7. 07Review default, cure and termination provisions, and whether termination unwinds the zoning approval.
8. 08Assume the agreement will be public. Draft operational and community commitments with that in mind.

Commitments made in a development agreement are also part of the public conversation, which our guide to community engagement for data centers addresses.