Most approvals are permissions. A development agreement is something different. It is a CONTRACT between a city and a property owner, adopted by ordinance, that fixes the rules applicable to a project for a stated term.
That single feature, freezing the rules, explains why these agreements exist, why they are negotiated hard, and why they can outlive the officials who signed them.
The problem they solve
Large projects take years. Entitlement, financing, engineering, phasing, and construction can span multiple cycles of a city council and multiple rounds of code amendments.
Without some form of assurance, an applicant faces a real risk: invest heavily under one set of rules, then have the standards change before the project is built. Under ordinary California law, rights generally vest quite late in the process, which leaves a long window of exposure.
A development agreement addresses that by contract. The city agrees that specified rules will govern the project for the term. In exchange, the city obtains commitments it could not otherwise require.
What each side gets
The applicant typically receives:
- Assurance that the land use rules, standards, and often the fees applicable to the project are those in effect at a stated date.
- A defined term long enough to phase construction.
- Certainty about processing, phasing, and the sequence of subsequent approvals.
The city typically receives:
- Public benefits negotiated rather than exacted, which can go beyond what a city could lawfully require as a condition.
- Enforceable commitments on phasing, timing, and construction of improvements.
- Ongoing review, since agreements commonly require periodic compliance review.
- Remedies, because breach of a contract is enforceable in ways a condition is not.
That first city-side item is the heart of it. Conditions of approval must bear a defined relationship to a project's impacts, a constraint described in conditions of approval. A negotiated agreement is a different legal footing, and it is why development agreements sometimes carry commitments that look unusually generous.
How one is adopted
Development agreements are legislative acts, not administrative ones.
- The agreement is negotiated between staff and the applicant, usually in parallel with the project entitlements.
- It receives environmental review along with the project.
- It goes to the planning commission for recommendation and then to the city council for adoption by ordinance, both at noticed public hearings.
- Because it is adopted by ordinance, it may in some circumstances be subject to referendum.
- Once effective, it is recorded, so it appears in the chain of title and binds successors.
That recording is what makes the agreement travel. A subsequent purchaser of the project site takes it subject to the agreement, benefits and obligations together.
Vesting is narrower than people assume
An agreement freezes the rules it says it freezes, and no others. Read any agreement and go straight to the vesting language.
Common carve-outs include building, fire, and life safety codes, which typically continue to apply as amended, and state or federal requirements the city has no power to freeze. Processing fees are frequently excluded even where impact fees are locked.
Agreements also typically preserve a city's ability to apply new regulations where necessary to protect health and safety. That reservation is standard and is genuinely used.
Vested rights can also arise outside a development agreement, most familiarly through a vesting tentative map filed under the subdivision process described in subdivision and parcel maps. The two mechanisms are related in purpose and different in scope.
Annual review and default
Most agreements require periodic review, commonly annual, in which the city determines whether the owner has demonstrated good faith compliance.
That review is a public proceeding and it is one of the more useful places for a resident to engage, because it recurs. A finding of noncompliance can trigger cure periods, modification, or termination depending on the agreement's terms.
Agreements also commonly address assignment, amendment, and what happens on expiration. Expiration matters: when the term ends, the project falls back to whatever rules then apply, which can leave unbuilt phases governed by an entirely different code than the built ones.
What a neighbor should read
If a development agreement accompanies a project near you, the document is public and the useful sections are predictable.
- Term. How long the rules are frozen.
- Vested rules. Exactly what is locked, and what is expressly excluded.
- Public benefits. What the applicant committed to, and when it is triggered.
- Phasing and timing. Whether improvements you care about are tied to a phase, and to which one.
- Review and default. How compliance is checked and what happens when it fails.
Timing triggers deserve particular attention. A commitment to build a public improvement at a later phase is a different thing from a commitment to build it first, and the difference determines whether the benefit arrives before or after the impact.
Comment on those specifics is far more useful in the record than general opposition, for the reasons described in our guide to the planning commission.
What a homebuyer should know
Development agreements normally attach to project sites rather than to individual existing homes, but a buyer in a newer development can inherit downstream obligations created by one, typically through recorded covenants or association documents.
The check is the same as for any recorded interest: pull the title report, order the underlying documents, and read what binds the parcel. Our article on easements and recorded rights covers that routine.
The practical takeaway
A development agreement converts a discretionary relationship into a contractual one. It buys certainty for the applicant and extracts commitments for the public, and both halves are enforceable in a way ordinary approvals are not.
These are complex legal instruments and their effect depends entirely on their own text and on state law. Read the recorded document and obtain legal advice where an outcome matters to you.
For the wider approval framework, start at our City Development hub, and read specific plans versus base zoning for the other instrument that sets project-specific rules.
Anthony Grynchal has been licensed in California since November 2009.
Frequently asked questions
What does a development agreement actually freeze?
Only what its own text says. Land use standards and impact fees are commonly locked, while building, fire, and life safety codes, state and federal requirements, and processing fees are frequently excluded from the vesting language.
Is a development agreement the same as conditions of approval?
No. Conditions are imposed and must bear a defined relationship to a project's impacts. A development agreement is a negotiated contract adopted by ordinance, which can include commitments a city could not require as a condition.
Does the agreement survive a sale of the project site?
Yes. Development agreements are recorded and generally bind successors, so a purchaser takes the site subject to both the benefits and the obligations.
Can residents participate after an agreement is adopted?
Yes. Most agreements require periodic compliance review, commonly annual, which is a recurring public proceeding where performance against the agreement's commitments is examined.

Written by
Anthony Grynchal
Anthony Grynchal is a California real estate professional with eXp Realty, licensed since November 2009 (California DRE# 01873626), and the Designated Local Expert™ for Claremont — where he has lived for more than 33 years.
More about AnthonyPublished · Updated




