A development agreement in land use planning is a binding contract between a local government and a property owner or developer that locks in the zoning rules, density limits, and other regulations applied to a specific project for a set number of years. In exchange for that regulatory certainty, the developer agrees to deliver public benefits the community could not otherwise require through ordinary permitting. These contracts are most common on large, phased projects where construction may stretch over a decade or more and both sides need firm commitments before putting money on the table.
What the Agreement Locks In for the Developer
Under standard zoning, a local government can change its land use rules at any time. A developer who spends years assembling land and arranging financing can find the rules rewritten mid-project, turning a viable plan into an illegal one. The common-law doctrine of vested rights offers some protection, but it is narrow. In most places, rights vest only after a developer obtains a valid permit and makes substantial expenditures in reliance on it, and courts define “substantial” differently from case to case.
A development agreement solves this contractually. Once it is signed, the local government generally cannot apply new zoning ordinances, density restrictions, or design standards to the project for the agreement’s duration. If the city later downzones the area or adopts tougher setback rules, those changes do not reach back into a project already covered by an agreement. For a 15-year buildout, that protection is often the whole reason the deal exists.
What the City Gets in Return
The public-benefit side is where development agreements depart most sharply from standard permits. Through ordinary zoning approvals, a city can require a developer to mitigate the direct impacts of a project. A development agreement opens the door to broader commitments negotiated as part of the deal.
Common examples include dedicating land for parks or schools, funding transit improvements, building or preserving affordable housing units, contributing to public art funds, and constructing off-site road improvements that serve the wider community. Affordable housing commitments are increasingly common in high-cost markets, where a developer might agree to set aside a percentage of units at below-market rents in exchange for guaranteed density and a long regulatory runway. These obligations go into the agreement as enforceable terms, not aspirational language.
What’s Typically Written Into the Agreement
Every development agreement is negotiated individually, but most cover the same core topics:
- Permitted uses and density, including building height limits, unit counts, floor area, and site layout.
- Which zoning rules, design standards, and infrastructure requirements govern the project, typically those in effect when the agreement is signed.
- Public improvements the developer must build or fund, such as roads, utilities, stormwater systems, or parks, and the timeline for delivering them.
- Duration. Terms typically run 10 to 30 years for large projects, though shorter or longer terms are possible depending on complexity.
- Phasing milestones for multi-stage developments. Five-year checkpoints are common.
- Financial assurances such as performance bonds or letters of credit guaranteeing the developer will actually deliver promised improvements.
- Procedures for amendments and early termination. Major changes usually go through the same public process as the original approval.
The level of detail matters. Vague language invites disputes later. The strongest agreements spell out exactly which edition of the building code applies, which fee schedules control, and what triggers the obligation to build each phase of public infrastructure.
Limits on Vesting
Developers who assume blanket immunity from all future laws are in for a surprise. State building, fire, plumbing, and electrical codes almost always still apply. If the state updates the building code after the agreement is signed, the project must comply with the new code. The same goes for federal and state environmental laws. A development agreement does not override a new stormwater regulation mandated by the EPA or a wetlands protection law enacted by the state.
Local governments also typically retain the power to modify or suspend an agreement if enforcing it as written would endanger public health or safety. If a geotechnical study reveals an unstable hillside after the agreement is executed, for example, the government is not locked into approving construction there. This safety valve exists precisely because no contract should force a community to accept dangerous development.
Constitutional Limits on What the City Can Demand
Even in a negotiated deal, there are constitutional boundaries on what a local government can require from a developer. The U.S. Supreme Court has set a two-part test that applies whenever a government conditions a land use approval on the developer giving up property or money.
First, there must be an “essential nexus” between the condition and a legitimate government interest. A city cannot require a developer to build a public park unless the development creates a need for park space. The Court established this principle in a 1987 decision involving a coastal building permit, holding that an agency cannot impose a condition on a permit unless the condition is rationally connected to a legitimate public purpose.1Justia U.S. Supreme Court Center. Nollan v. California Coastal Commission, 483 U.S. 825 (1987)
Second, the condition must be “roughly proportional” to the development’s actual impact. A small residential project cannot be saddled with the cost of a new highway interchange. The government does not need to perform precise mathematical calculations, but it must make an individualized determination that the required contribution relates in both nature and extent to the project’s impact.2Justia U.S. Supreme Court Center. Dolan v. City of Tigard, 512 U.S. 374 (1994)
In 2013, the Court extended these protections to monetary demands as well. A government cannot avoid the nexus and proportionality requirements by demanding cash instead of land.3Justia U.S. Supreme Court Center. Koontz v. St. Johns River Water Mgmt. Dist., 570 U.S. 595 (2013) If a government’s demands cross either line, the developer has grounds to push back or challenge the condition. Local governments that stay within these boundaries have broad discretion to secure meaningful public benefits.
How a Development Agreement Gets Approved and Recorded
Development agreements are not quietly negotiated and signed. Because they carry the force of local law, most states require a formal legislative adoption process, including public hearings where community members can weigh in. The typical sequence runs from staff-level negotiations to planning commission review and finally to adoption by the city council or county board. Some jurisdictions require two hearings at different stages.
Environmental review is not bypassed either. Depending on the project’s scope and location, the agreement may trigger state environmental review requirements, and any federally funded or permitted component may require review under the National Environmental Policy Act. A local government generally cannot bind itself to a project’s terms before completing the required environmental analysis.4Council on Environmental Quality. NEPA and CEQA: Integrating Federal and State Environmental Reviews
Once approved, the agreement is recorded against the property’s title with the county recorder, like a deed or mortgage. Recording puts future buyers on notice that the property is subject to the agreement’s terms and establishes that the obligations and benefits run with the land. If the developer sells, the new owner steps into the agreement and is bound by its requirements, whether that new owner is a successor developer, a homebuilder purchasing individual lots, or a lender who takes the property through foreclosure.
Compliance, Breach, and Termination
Signing is just the beginning. Most development agreements require the local government to conduct periodic reviews, typically annual, to confirm the developer is meeting milestones and conditions. During these reviews, the developer must demonstrate good faith compliance with the agreement’s terms. That means not just avoiding outright violations, but actively performing obligations on schedule.
If a review reveals the developer has fallen short, consequences escalate. The government may offer a cure period, giving the developer time to get back on track. If compliance does not improve, the government can initiate proceedings to modify or terminate the agreement. Termination typically requires a public hearing and a formal finding supported by substantial evidence, and the developer gets a chance to respond before the plug is pulled.
Because development agreements are contracts, standard contract remedies apply when either side breaches. A developer who fails to build promised infrastructure may face a lawsuit for specific performance, forcing it to actually deliver rather than simply pay damages. Courts are more willing to order specific performance in real property disputes because each piece of land is considered unique. Monetary damages are also available, and some agreements include liquidated damages clauses that set predetermined amounts for specific types of default, removing the need to prove actual losses in court.
State Law Determines What’s Possible
Development agreements are creatures of state law. Local governments have no inherent power to enter into these contracts; they need explicit authorization from the state legislature. A number of states have enacted enabling statutes that spell out the procedures, required contents, and limitations for development agreements. These statutes vary considerably. Some cap the maximum duration. Others prescribe minimum contents or limit the types of projects that qualify.
States without dedicated enabling statutes present a murkier picture. Some local governments in those states rely on general contracting authority or home-rule powers to negotiate development agreements, but enforceability is less certain. Developers operating in states without clear statutory authorization should get a legal opinion on whether the agreement will hold up if challenged. The approval process, permissible terms, maximum duration, public hearing requirements, and recording obligations all depend on the specific state’s framework, so the first question in any potential deal is what the state actually allows.