A Development Agreement Operates Throughout the Project Lifecycle
A California development agreement can define the rules governing a project and allocate performance obligations across many years. Its practical effect reaches into entitlements, subdivision maps, infrastructure, fees, dedications, public benefits, phasing, financing, environmental commitments, annual compliance review, assignments, and later permits.
Government Code section 65865 authorizes cities and counties to enter development agreements with persons holding a legal or equitable interest in the property and requires local procedures for considering them. Section 65865.2 identifies required agreement content, including duration, permitted uses, density or intensity, maximum building height and size, and provisions for reservation or dedication of land for public purposes. Agreements may also address conditions, restrictions, subsequent discretionary actions, timing, public facilities, financing, reimbursements, and other negotiated project terms.
Government Code section 65866 generally ties permitted uses, density, design, improvement, and construction standards to the rules in force at agreement execution, subject to the agreement’s terms and the statute’s treatment of later nonconflicting rules and subsequent project applications. Section 65865.1 requires review at least every twelve months and places the demonstration of good-faith compliance on the applicant or successor. Section 65867.5 treats approval as a legislative act, requires adoption by ordinance, and requires consistency with the general plan and any applicable specific plan.
The recorded agreement should therefore function as an operating instrument. The project team needs a controlled source set, a term calendar, a rules schedule, an obligations register, an annual-review file, a change protocol, and a transfer package. These controls allow the parties and their professional teams to evaluate what has been promised, what remains due, what evidence exists, and which project decisions require agency action.
Begin with an Operative-Agreement Certificate
Prepare an operative-agreement certificate when the agreement becomes effective, when the project is acquired or financed, before each annual review, and after any amendment or assignment. The certificate should identify:
- the agreement title and execution date;
- the adopting ordinance and effective date;
- the property legal description and assessor parcels;
- the original parties and current successors;
- recordation date, instrument number, and county;
- all exhibits, incorporated plans, and referenced approvals;
- amendments, supplements, waivers, and administrative interpretations;
- assignments, assumptions, partial releases, and notices;
- the initial term and all extension provisions;
- conditions to effectiveness;
- annual-review date and local procedure;
- default, cure, suspension, termination, and dispute provisions;
- obligations that survive expiration or transfer; and
- open questions concerning interpretation, compliance, or property coverage.
Attach a document tree showing how every later instrument changes the original agreement. Mark superseded provisions and preserve each historical version. Counsel should approve the operative compilation and interpret legal effect.
A Ten-Part Development-Agreement Framework
2. Control Effectiveness, Term, and Extension Dates
The agreement’s execution date, adoption date, ordinance effective date, recordation date, satisfaction of conditions, and commencement of the term may differ. Build a term schedule that states each event and its documentary source.
Track:
- execution by all parties;
- ordinance introduction and adoption;
- referendum period where applicable;
- ordinance effective date;
- recordation;
- annexation or other condition to operation;
- term commencement;
- base expiration date;
- extension options and notice dates;
- extension conditions;
- tolling or suspension provisions;
- phase-specific terms;
- outside completion dates; and
- surviving obligations.
Use a written calculation with counsel’s confirmation. Set internal deadlines before every notice, extension, review, and performance date.
3. Build the Applicable-Rules Schedule
Identify each rule, regulation, official policy, standard, plan, manual, and fee regime addressed by the agreement. Section 65866 supplies a statutory framework, and the agreement may define its application in detail.
For each source, record:
- title and citation;
- version and effective date;
- subject matter;
- project component affected;
- whether the agreement fixes, incorporates, modifies, or excludes the source;
- treatment of later rules;
- treatment of state and federal law;
- relationship to building and technical codes;
- relationship to later discretionary approvals;
- required agency determination; and
- legal reviewer.
Separate rules incorporated by the agreement from approvals granted through separate ordinances, resolutions, maps, permits, and environmental actions. Keep the agreement’s applicable-rules schedule aligned with the vesting-tentative-map record and the project’s approval register.
4. Convert Party Commitments into Executable Obligations
Read the agreement clause by clause and create one register entry for each required act, payment, dedication, conveyance, construction item, report, notice, approval, or continuing duty.
Each entry should state:
- the exact obligation language;
- obligated party;
- beneficiary or reviewing entity;
- property or phase affected;
- trigger;
- due date or calculation method;
- prerequisites;
- dependencies;
- required professional work;
- evidence of performance;
- agency acceptance standard;
- cure provision;
- financial effect;
- transfer effect; and
- status.
Avoid a single entry labeled “developer obligations.” Separate each deliverable so the project team can assign, forecast, verify, and close it.
5. Coordinate Public Benefits, Infrastructure, Fees, and Reimbursements
Development agreements often address public improvements, land dedications, affordable housing, community benefits, infrastructure financing, fee treatment, credits, reimbursements, and security. Build a financial-and-performance schedule that connects each commitment to the development program and cash-flow model.
For every obligation, identify:
- amount or calculation formula;
- indexing method;
- valuation date;
- payment or performance trigger;
- phase allocation;
- eligible credit;
- reimbursement source;
- district or financing mechanism;
- security requirement;
- release condition;
- accounting evidence;
- audit or reporting right; and
- tax, financing, or disclosure review.
Link the schedule to conditions of approval, improvement agreements, fee programs, reimbursement agreements, district formation documents, public-report budgets, and transaction documents. Resolve duplicate or overlapping obligations through written legal and agency review.
6. Map Later Approvals and Decision Points
A development agreement may identify required subsequent discretionary actions and project standards while preserving agency review under the agreement and applicable law. Create an approval matrix that shows every later action needed for delivery.
The matrix can include:
- tentative and final maps;
- design review;
- site-development permits;
- grading and building permits;
- improvement plans;
- infrastructure agreements;
- utility approvals;
- environmental review and mitigation compliance;
- affordable-housing instruments;
- public financing actions;
- public-report filings;
- occupancy approvals;
- phase releases; and
- association or district handoffs.
For each action, identify the agreement provisions, applicable rules, required findings, project inputs, responsible professionals, agency body, dependencies, decision date, and appeal path.
7. Build the Annual-Review Evidence File
Government Code section 65865.1 requires periodic review at least every twelve months. The applicant or successor must demonstrate good-faith compliance. Local ordinances and the agreement may prescribe the submittal, notice, hearing, fee, affidavit, and evidence requirements.
Open the annual-review file several months before the due date. Include:
- operative-agreement certificate;
- current ownership and assignment record;
- obligation-status report;
- completed deliverables and acceptance evidence;
- payments, dedications, improvements, and security records;
- approvals obtained during the review period;
- construction and phasing status;
- unresolved agency comments;
- asserted delays and supporting evidence;
- proposed cure plans;
- updated schedule;
- certification or affidavit required by local procedure; and
- draft agency findings where appropriate.
Use the annual review as a formal project-control event. Reconcile the agreement register, conditions register, development-cost register, map schedule, public-report status, and environmental commitments at the same time.
8. Control Amendments, Waivers, Interpretations, and Changed Law
Government Code section 65868 permits amendment or cancellation by mutual consent through the applicable notice and hearing procedures. Section 65869.5 addresses later state or federal law that prevents or precludes compliance and provides for modification or suspension as necessary to comply.
Create a change protocol for:
- project-program changes;
- phasing revisions;
- land additions or releases;
- changes to permitted uses, density, intensity, height, or building size;
- infrastructure substitutions;
- public-benefit revisions;
- fee or reimbursement changes;
- schedule extensions;
- administrative interpretations;
- waivers;
- force-majeure or delay claims;
- new state or federal requirements; and
- consistency with the general plan, specific plan, and CEQA record.
Each change record should identify the agreement section, proposed revision, parties’ authority, required procedure, environmental-review path, associated approval changes, financial effect, public-hearing requirements, recordation requirements, and final effective date.
9. Manage Assignment, Transfer, and Financing
Government Code section 65868.5 requires recordation and provides that the agreement’s burdens bind successors and its benefits inure to successors. The agreement may contain detailed assignment, notice, consent, assumption, partial-transfer, lender, and release provisions.
Before a transaction, prepare a transfer matrix addressing:
- property and obligations being transferred;
- assignor and assignee;
- required agency consent or notice;
- assumption agreement;
- evidence of financial or technical capability;
- allocation of past and future obligations;
- retained liabilities;
- default status;
- annual-review status;
- security replacement;
- lender recognition or cure rights;
- recordation; and
- update of agency and project contacts.
A partial sale requires phase- and parcel-specific allocation. Confirm which obligations run with the transferred land, which remain with the master developer, and which require joint performance. Update the register immediately after closing.
10. Plan Expiration, Termination, and Closeout
The project should begin closeout planning before the agreement’s final year. Identify:
- remaining obligations;
- completion evidence;
- open agency reviews;
- unresolved defaults or disputes;
- security and deposit releases;
- credits and reimbursement receivables;
- continuing maintenance or reporting duties;
- recorded covenants or easements;
- obligations surviving expiration;
- pending permits and approvals;
- effect on vested rules; and
- required notices, certificates, releases, or recorded instruments.
Prepare a closeout memorandum signed off by counsel, project management, finance, engineering, and the agency where applicable. Preserve the final compliance record for later owners, associations, lenders, and public-report files.
The Development-Agreement Obligations Register
A complete register can include:
- obligation ID;
- agreement section;
- operative instrument and version;
- obligated party;
- beneficiary or reviewing entity;
- parcel and phase;
- obligation statement;
- trigger;
- due date or formula;
- predecessor requirements;
- dependent approvals;
- professional contributor;
- financial amount or estimate;
- fee, credit, reimbursement, or security treatment;
- evidence required;
- agency acceptance;
- annual-review period;
- assignment treatment;
- cure period;
- amendment or waiver history;
- current status;
- next action and owner;
- evidence location; and
- closure date.
Use the same stable ID in schedules, annual-review packages, payment records, public-benefit reports, transaction documents, and closeout certificates.
Seven Agreement Gates
Gate 1: Operative Record Confirmed
The ordinance, agreement, exhibits, amendments, assignments, recordation data, property description, and current parties are complete.
Gate 2: Term and Rules Verified
Effective dates, expiration, extension rights, applicable rules, later-rule treatment, and project-specific approvals have been reviewed.
Gate 3: Obligations Assigned
Every project and agency commitment has a trigger, owner, dependency, evidence standard, financial treatment, and forecast date.
Gate 4: Annual Review Ready
The compliance narrative, status register, completed evidence, open items, cure plan, certification, and local submittal requirements are complete.
Gate 6: Transfer Controlled
The assignment package allocates obligations, obtains required consent, replaces security, addresses lender rights, and updates the recorded and operating records.
Gate 7: Closeout Documented
Remaining duties, survival provisions, releases, reimbursements, final evidence, and post-expiration responsibilities are resolved.
Questions to Resolve
- What documents constitute the operative development agreement today?
- Which parcels, phases, and entities are subject to it?
- When did the agreement become effective, when does it expire, and what extension procedures apply?
- Which rules are fixed, incorporated, modified, or left to later agency action?
- What public benefits, improvements, dedications, payments, fees, credits, reimbursements, and security obligations remain open?
- Which subsequent approvals are required, and what agreement provisions govern them?
- What must the applicant or successor submit for the next annual review?
- Which compliance items lack agency acceptance or documentary evidence?
- Does a proposed project change require an amendment, administrative interpretation, waiver, associated entitlement change, or further environmental review?
- What consent, assumption, security, and recordation steps apply to a transfer?
- Which obligations survive completion, transfer, or expiration?
Practical Next Steps
Certify the Operative Agreement
Compile the original agreement, ordinance, exhibits, amendments, assignments, recorded instruments, and current property schedule.
Build the Obligations Register
Convert each commitment into a discrete action with a trigger, responsible party, evidence standard, and forecast date.
Open the Annual-Review Workplan
Work backward from the local due date through evidence collection, professional review, agency coordination, and sponsor approval.
Connect the Agreement to Project Controls
Link every term to the approval matrix, conditions register, map schedule, development-cost record, CEQA commitments, public-report process, and transaction calendar.
Prepare the Transfer and Closeout Packages Early
Identify assignment, assumption, consent, security, release, survival, and recordation requirements before the relevant transaction or expiration window.
