A development agreement is a recorded contract between a property owner or developer and a local government that freezes the zoning, density, and design rules governing a project for a fixed number of years, in exchange for the developer’s commitment to fund or build specified public benefits. The appeal for the developer is regulatory certainty: once signed, the local government cannot change the rules mid-project, even if it later amends its zoning code. The appeal for the local government is the ability to negotiate infrastructure, affordable housing, or other contributions it might not be able to require through ordinary permitting. Roughly a dozen and a half states have enacted enabling statutes authorizing these contracts, and while the details vary, the mechanics are consistent enough to describe in general terms.
What the Agreement Actually Locks In
Outside of a development agreement, a local government can change its zoning rules at any time through its police power, and developers have limited ability to object. A development agreement converts that regulatory relationship into a contractual one. The land use rules in effect at signing are frozen for the project, so the developer can secure financing and build in phases without worrying that new density limits or design mandates will derail construction years into the timeline.
The state enabling statute is what makes this possible. Without express legislative authority, a municipality generally cannot bind itself to forgo future regulatory changes, because doing so looks like contracting away its police power. The enabling law resolves that tension by authorizing the agreement and defining what it can cover. States with such statutes include Arizona, California, Colorado, Florida, Hawaii, Idaho, Louisiana, Maryland, Nevada, New Jersey, Oregon, South Carolina, Texas, Virginia, and Washington, among others.
The freeze is not absolute. If a state or federal law enacted after signing makes compliance with the agreement’s terms impossible or illegal, the local government can typically modify the affected provisions. Health and safety emergencies can also justify overriding the frozen rules without the developer’s consent. And the developer can always accept new rules voluntarily. Outside those narrow exceptions, the vesting holds for the full contract term.
Constitutional Limits on What the Local Government Can Demand
The developer’s side of the deal is usually a package of exactions: road improvements, park land, utility extensions, affordable housing set-asides, impact fees. The Constitution places real limits on how far a government can go in demanding these things, and those limits shape the negotiation.
In Nollan v. California Coastal Commission, the Supreme Court held that any condition attached to a development permit must have an “essential nexus” to a legitimate government purpose related to the project’s impact. A condition unrelated to the problem the government claims to be addressing is, in the Court’s words, “an out-and-out plan of extortion.”1Justia. Nollan v. California Coastal Commission, 483 U.S. 825 (1987) A city can require a developer to widen a road the project will congest. It cannot demand an unrelated parcel of beachfront in exchange for a building permit.
Dolan v. City of Tigard added a second requirement: the exaction must be “roughly proportional” to the development’s actual impact. No precise formula is required, but the government must make an individualized determination that the burden imposed on the developer matches the harm the project creates in both nature and extent.2Justia. Dolan v. City of Tigard, 512 U.S. 374 (1994) Requiring ten acres of parkland to offset one acre of park demand is a proportionality problem.
Two later decisions extend the reach of these tests. Koontz v. St. Johns River Water Management District held that demands for money are subject to the same nexus and rough proportionality analysis as demands for land.3Justia. Koontz v. St. Johns River Water Management District, 570 U.S. 595 (2013) The Court’s 2024 decision in Sheetz v. El Dorado clarified that these limits apply to exactions imposed by legislation, not only to those imposed case-by-case by permit administrators.4U.S. Congress. Amdt5.10.7 Per Se Takings and Exactions If a local government demands infrastructure contributions that bear no reasonable relationship to a project’s impacts, the developer has grounds to push back or challenge the demand.
Core Terms the Contract Has to Cover
State enabling statutes usually require development agreements to address a defined set of elements. The specifics differ from state to state, but most agreements contain the following:
- Duration. The agreement states how long it lasts. Terms of 10 to 20 years are common for large multi-phase projects, and some statutes cap the maximum at 20 years.
- Permitted uses and intensity. The agreement identifies what can be built, including residential density, commercial intensity, and the maximum height and footprint of structures.
- Public benefit obligations. The developer’s commitments to fund or construct roads, parks, utility extensions, affordable housing, or other improvements appear here, along with payment schedules and completion milestones.
- Applicable regulations. The agreement identifies exactly which local ordinances and policies are frozen for the term, so there is no ambiguity about which version of the rules controls.
- Periodic review. Most statutes require the local government to review compliance at least once every 12 months. The developer typically bears the burden of demonstrating good-faith compliance.
Agreements also commonly address phasing schedules, impact fee calculations, and the conditions under which the developer can assign its rights to a new owner. Vague drafting is where most disputes start, so specificity at signing saves both sides from expensive litigation later.
How the Agreement Gets Approved
Approving a development agreement is more involved than issuing a standard zoning permit. The process is deliberately public and legislative, because the local government is making a binding commitment that restricts its own future regulatory discretion.
Application and Staff Review
The developer submits a formal application with a draft agreement and supporting materials describing the project’s scope, timeline, and proposed public benefits. Planning staff review the draft for consistency with the jurisdiction’s general or comprehensive plan and prepare a report recommending approval, denial, or modifications. Much of the real negotiation happens at this stage, and for complex projects it can take months.
Public Notice and Hearings
Before approval, the local government must give public notice and hold at least one public hearing. Most jurisdictions require published notice in a local newspaper, with the first notice appearing at least 10 days before the hearing. The notice must identify the property’s location and describe the proposed land uses. Some jurisdictions require hearings before both the planning commission and the governing body; others require only a hearing before the governing body. The draft agreement should be available for public inspection when notice is published.
Environmental Review
In states with environmental quality statutes modeled on California’s CEQA, or at the federal level under NEPA, approving a development agreement can trigger environmental review. The lead agency generally cannot commit to an agreement with significant environmental impacts before completing that review.5Council on Environmental Quality. NEPA and CEQA: Integrating Federal and State Environmental Reviews In practice, review often runs parallel to the agreement negotiations and has to be completed before final approval.
Legislative Approval and Recording
The governing body approves the agreement by adopting an ordinance or resolution, usually making findings that the agreement is consistent with the adopted general plan and serves the public interest. Because this is a legislative act, it may be subject to referendum in some states.
Once approved, the agreement is recorded with the county recorder’s office. Recording is not a formality. It puts future buyers, lenders, and title companies on notice that the property carries the agreement’s terms and obligations. A recorded development agreement runs with the land, so it binds not just the original developer but every subsequent owner.
Paying for the Public Infrastructure
Agreements often address how the developer will be reimbursed for building public infrastructure that benefits the broader community. One common mechanism is tax increment financing. The municipality designates the project area and earmarks the increase in property tax revenue generated by new development to repay the developer’s infrastructure costs. TIF is authorized by state law in nearly all 50 states.6FHWA Center for Innovative Finance Support. Tax Increment Financing Fact Sheet
The important part is that the developer typically spends its own capital upfront. Reimbursement comes later, as the increased tax revenue materializes. If the project underperforms or property values do not rise as expected, the developer absorbs the shortfall. The agreement should spell out which infrastructure costs qualify for reimbursement, the maximum amount, and the timeline for payments. Treating TIF as guaranteed money rather than performance-dependent reimbursement is a common way to run into cash-flow trouble.
Compliance, Breach, and Transfer
The annual review is where the local government checks whether the developer is holding up its end. The developer must demonstrate good-faith compliance with construction milestones, infrastructure commitments, and fee payments. If the local government finds the developer out of compliance, it typically must give written notice specifying the deficiency and a reasonable cure period, generally no less than 30 days. Failure to cure can lead to modification or cancellation of the agreement after a public hearing.
If either side materially breaches, the other has options. Specific performance, where a court orders the breaching party to do what the contract requires, matters here because real property is considered unique and money damages alone may not make the injured party whole. Many agreements require mediation or arbitration before litigation. Liquidated damages clauses sometimes appear, particularly for missed construction deadlines, setting a predetermined daily or weekly amount the developer owes for delay. For the clause to hold up, the amount has to be a reasonable forecast of the actual harm from delay, not a penalty.
Any substantive amendment goes through the same approval process as the original: notice, hearing, and legislative action. Minor technical corrections may be handled administratively, but changes to core terms get the full treatment. An agreement can end when the term expires, when the parties agree in writing to terminate, or when the local government cancels it after a noncompliance finding. Some agreements also include automatic termination triggers, such as failure to start construction within a set number of years.
Because the recorded agreement runs with the land, it transfers automatically to new owners. If the developer sells or assigns its interest, the new owner steps into the original developer’s shoes and inherits every obligation. Many agreements require notice of any transfer and proof that the new owner has the financial capacity to perform. Whether the original developer is released from liability depends on how the assignment provision is drafted, so that language deserves close attention.
When a Development Agreement Is the Right Tool
Development agreements are sometimes confused with conditional rezoning, planned unit developments, or variance approvals. The distinction matters. Conditional rezoning attaches specific conditions to a zoning change but does not freeze the underlying rules, and the local government keeps full authority to amend its code later. A PUD approval gives design flexibility but usually offers no guarantee against future regulatory changes either.
The unique value of a development agreement is the contractual freeze for the full term. Because both parties are bound by contract, the developer gains enforceable rights that survive changes in political leadership, planning priorities, and local ordinances. That protection has a price, both in the public benefits the developer must provide and in the time and expense of the approval process. For small projects on short timelines, the overhead rarely pencils out. For large multi-phase developments that will stretch over a decade or more, the regulatory certainty can be the difference between a financeable project and one that never breaks ground.