Visit Website →
← Back to blog

U.S. Development Agreement Process: Statutes, Steps, and Checklist

October 6, 2026
U.S. Development Agreement Process: Statutes, Steps, and Checklist

A development agreement is a voluntary, recorded contract between a landowner or developer and a local government that vests site-specific development rights and schedules infrastructure and approvals after a noticed legislative hearing and ordinance. The agreement locks in the standards that apply to a project, sets a development timetable, and documents who pays for what. Courts still require that any exactions tied to the deal meet nexus and proportionality tests, so the contract has to be built on solid legal footing from the start.

TL;DR:

  • Development agreements require strict adherence to statutory notice, approval, and recording deadlines to prevent legal challenges or invalidation.
  • Costs and timelines for application processing, hearings, legal review, and infrastructure coordination can extend over several months and should be carefully budgeted.
  • Developers should thoroughly prepare a complete application, confirm local procedures, and obtain explicit proportionality findings for any exactions requested.
  • Large, phased, or infrastructure-dependent projects are the best candidates for development agreements, especially when long-term vesting or shared infrastructure costs are involved.
  • Early feasibility studies and master land planning are essential to determine if a development agreement is appropriate and will provide the intended legal and financial protections.
Urban Planning Pros
Clarify Your Land’s Development Potential
Urban Planning Pros evaluates property documents, zoning constraints, and market direction to support informed development decisions.
Visit Urban Planning Pros

Table of Contents

Where the Authority to Negotiate Comes From

Local governments cannot negotiate a development agreement on a whim. The power comes from state enabling statutes that authorize municipalities and counties to enter into these contracts and that define the procedural guardrails around them. North Carolina's framework is a useful reference point: Chapter 160D, Article 10 requires governing-board approval by ordinance, specifies minimum agreement contents such as duration and development schedule, mandates periodic review, and requires recordation within a short window after approval.

Most states follow a similar pattern, though the details vary. A jurisdiction typically chooses between two paths. The first is adopting formal enabling procedures or a standing ordinance that spells out application requirements, notice and hearing steps, and amendment rules before any specific agreement is negotiated. The second is handling agreements on an ad hoc basis, crafting procedures project by project. The UNC School of Government notes that development agreements are legislative actions in many states, which means they require the same notice and hearing rigor as a zoning amendment, not the lighter process used for administrative permits.

Regardless of which path a jurisdiction takes, a few statutory requirements tend to recur:

  • The agreement must be approved by ordinance or resolution, not by staff sign-off alone.
  • It must be consistent with the jurisdiction's comprehensive plan or equivalent land use policy.
  • It must be recorded in the land records, usually within a short window measured in days rather than months.
  • It must specify a duration and a development schedule rather than leaving the timeline open-ended.

Landowners and developers who understand this statutory baseline early can shape their entitlement strategy around what a given jurisdiction actually allows, rather than discovering the limits mid-negotiation.

The Step-by-Step Path From Application to Recordation

The process follows a fairly predictable sequence once a jurisdiction has adopted its procedures, though the exact names of each step vary by state and municipality. Municipal code excerpts from cities such as San Diego and Berkeley illustrate the typical submittal and hearing requirements that most jurisdictions mirror in some form, including draft availability periods, planning commission review, and council adoption in accordance with local rules.

  1. Assemble the application. Most jurisdictions require a legal description of the property, evidence of ownership or an option to purchase, a conceptual site plan, a statement of consistency with the comprehensive plan, and a proposed development schedule. Only the landowner or an authorized developer with site control typically qualifies to apply.
  2. Complete a staff sufficiency review. Planning staff checks the application against the municipal code's submittal checklist and may request revisions before scheduling any public hearing.
  3. Publish the required notice. Many states require two newspaper publications, with the first appearing at least 10 but no more than 25 days before the hearing, mirroring the notice standard used for zoning text amendments. Some municipal codes also require the draft agreement to be publicly available for review, sometimes for 30 days, before the hearing date.
  4. Hold the planning commission hearing. The commission reviews the draft agreement for comprehensive plan consistency and issues a recommendation, though this recommendation is typically advisory rather than binding on the governing body.
  5. Hold the governing body hearing and vote. The city council, board of commissioners, or equivalent body holds its own noticed hearing and adopts the agreement by ordinance. This is the step that makes the agreement legally effective, not the planning commission's recommendation.
  6. Coordinate concurrent approvals. Rezoning, site plan approval, and any required environmental review often run in parallel with the development agreement rather than waiting for it to finish first. Sequencing these correctly avoids redundant hearings.
  7. Record the agreement. Once adopted, the agreement must be recorded with the land records, often within 10 to 14 days of the ordinance's effective date, which binds successors in interest to its terms.

Missing a notice deadline or skipping a required hearing is one of the most common ways an otherwise well-negotiated agreement becomes vulnerable to a legal challenge, so treating these dates as fixed calendar commitments rather than flexible targets matters.

What Goes Into the Contract Itself

A development agreement is a contract, and like any contract, it has provisions the parties must include and provisions they are free to negotiate. Getting the mandatory pieces right protects the vesting benefit the developer is paying for; getting the negotiable pieces right protects both sides' practical interests over the life of the project.

  • Identification and duration: a full legal description of the property, the names of all parties, and a stated term or expiration date for the agreement.
  • Development schedule: commencement and completion dates for phases, often set at intervals of five years or less for large projects, with a process for mutual-consent modifications when timelines slip.
  • Infrastructure and cost-sharing terms: which party builds which roads, utilities, or public facilities, and how reimbursement or credits against impact fees work.
  • Permitted uses and standards: the densities, uses, and design standards that are locked in for the life of the agreement, plus any mitigation measures tied to specific impacts.
  • Enforcement and amendment mechanics: how breaches are cured, how minor ministerial changes differ from major modifications requiring a new hearing, and how disputes get resolved.
  • Assignment and successor liability: whether the agreement runs with the land and binds future owners, and under what conditions a developer may assign its obligations.
  • Recordation language: a clause confirming the agreement will be recorded and specifying who bears that cost.

These terms interact. A generous development schedule is worth little if the infrastructure cost-sharing clause leaves the developer fronting costs the municipality was supposed to reimburse. Reviewing the full package with counsel and a planning consultant before signing, rather than clause by clause in isolation, catches these gaps.

Constitutional Limits on What Governments Can Ask For

Local governments have real leverage in these negotiations, but that leverage is not unlimited. Three US Supreme Court decisions set the outer boundary on land use exactions: Nollan, Dolan, and Koontz. Together they require that any condition a government attaches to development approval have an "essential nexus" to the project's impact and be roughly proportional to that impact in scope and cost.

  • Essential nexus: the condition must address a problem the project actually creates, not an unrelated public need.
  • Rough proportionality: the size and cost of the exaction must reasonably match the scale of the project's impact, not simply reflect the maximum a jurisdiction can extract.
  • Monetary exactions: Koontz extended this scrutiny to conditions involving money or off-site mitigation payments, not just land dedications.

A jurisdiction that wants an exaction to hold up should document individualized findings in the hearing record rather than apply a flat formula. A proportionality analysis tied to the specific parcel and project gives both sides something concrete to negotiate around, and it is the kind of record that survives a later legal challenge. Developers facing a requested exaction can reasonably ask the jurisdiction to produce that analysis before agreeing to the term, since a blanket citywide formula with no parcel-specific reasoning carries real legal risk for both parties.

Keeping the Agreement in Force After Approval

Signing the agreement and recording it is not the end of the obligations; it is the start of a multi-year compliance relationship. Recordation triggers the agreement's effect on successors in interest, so a buyer who purchases the property later typically inherits both its benefits and its obligations.

  • Recordation deadlines are usually measured in days, not months, and missing them can delay when the agreement becomes enforceable against future owners.
  • Periodic review, often annual, requires the developer to demonstrate good-faith compliance with the schedule; failure to do so can lead to modification or termination of the agreement.
  • Breach and cure provisions typically give the defaulting party formal notice and a defined period to fix the problem before the municipality can pursue termination or other remedies.
  • Later state or federal law changes that make compliance impossible generally trigger a modification or suspension clause rather than automatic agreement termination, since the agreement cannot override a legal requirement imposed after the fact.

What to Budget for in Time and Money

The realistic calendar runs from application completeness review, through planning commission review, to the governing body hearing and adoption, and finally to recordation. Each stage has its own notice and preparation lead time, and rushing one stage rarely shortens the overall timeline since hearing dates are fixed by publication deadlines.

  • Expect consultant costs for feasibility analysis, traffic or utility capacity studies, and site planning before the application is even complete.
  • Budget for public notice publication costs, which are modest individually but recur at each hearing stage.
  • Legal fees scale with the complexity of the infrastructure and cost-sharing terms, not just the length of the document.
  • Infrastructure financing terms, including which party fronts costs and how reimbursement credits apply, directly affect a developer's cash flow during construction.

Pro Tip: Build your internal project calendar around the published notice deadlines first, then fit consultant deliverables and legal review around those fixed dates rather than the other way around.

Preparing and Negotiating: A Practitioner Checklist

Walking into the first meeting with municipal staff prepared changes the tone of the entire negotiation. A thin application invites delay; a complete one signals that the project is ready to move.

  1. Assemble the pre-application packet. This typically includes a current title report, a conceptual site plan, evidence of financing or site control, and a short memo showing consistency with the comprehensive plan.
  2. Identify negotiation priorities and red lines before the first meeting. Know which vesting terms and financing assumptions are non-negotiable and which schedule details have flexibility.
  3. Set up a compliance dossier from day one. Tie every expenditure and milestone to the agreement's development schedule so the annual review becomes a formality rather than a scramble.
  4. Ask municipal staff directly about their enabling ordinance. Confirm whether the jurisdiction has standing development agreement procedures or handles agreements ad hoc, since that shapes the whole timeline.
  5. Confirm the amendment process in writing. Make sure the agreement distinguishes minor ministerial modifications from major changes requiring a new hearing, since that distinction saves months later.

Pro Tip: Request the jurisdiction's proportionality findings for any requested exaction in writing before the hearing, not after the ordinance is adopted.

A clear feasibility study completed before the pre-application packet is assembled often surfaces the zoning constraints and infrastructure gaps that would otherwise emerge mid-negotiation, when they are far more expensive to address.

Feasibility study screening zoning and infrastructure

When a Development Agreement Is the Right Tool

When a Development Agreement Is the Right Tool — overview diagram

A development agreement earns its complexity on large, phased, or infrastructure-heavy projects where the developer needs years of vesting certainty to justify the capital outlay. For a straightforward single-phase project that fits existing zoning, standard permitting or a conditional use approval is often faster and cheaper, since it skips the legislative hearing cycle entirely.

The projects that benefit most share a pattern: multi-year build-out, shared infrastructure costs, and a public benefit the municipality wants documented clearly. Early feasibility work that maps zoning constraints and market demand against the proposed schedule tends to separate the projects where a development agreement pays for itself from the ones where it adds cost without adding protection.

— Jeremy Wenger

How We Help Landowners and Developers Through This Process

We built our practice around the stage before most consultants get involved: the feasibility and planning work that determines whether a development agreement is even the right tool for a given site. Our feasibility studies evaluate zoning constraints, infrastructure capacity, and market direction before a client commits to a negotiation timeline, so the application that eventually reaches planning commission reflects real site conditions rather than assumptions.

Urban Planning Pros

Through master land planning, we translate those findings into the conceptual site plans and development schedules that jurisdictions expect in a complete application. For clients who want a dedicated point of contact through the hearing and recordation process, owner representation services keep the compliance dossier and amendment tracking organized from the pre-application meeting through the annual review.

What this produces is a package built to hold up under proportionality scrutiny and survive the periodic review cycle, not just a document that clears the first hearing.

  • Feasibility studies that surface zoning and infrastructure constraints before negotiation begins.
  • Master land planning that turns site data into conceptual plans jurisdictions require.
  • Owner representation to manage the hearing calendar and compliance dossier.
  • Surveying coordination to support the legal description and site plans the agreement requires.

If you are evaluating whether a development agreement fits your project, book a feasibility study with our team before you file the application.

This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.

FAQ

What is a development agreement?

A development agreement is a voluntary, legally binding contract between a developer or landowner and a local government that vests specific development rights and standards for a defined period. It typically sets a development schedule, infrastructure obligations, and permitted uses, and it must be adopted by ordinance following a noticed public hearing under most state enabling statutes, including North Carolina's Chapter 160D framework.

What are the four types of agreements?

Development-related contracts generally fall into a few recognizable categories: development agreements that vest site-specific rights for a defined term, annexation agreements tied to bringing land into a municipality, reimbursement or cost-sharing agreements for infrastructure, and conditional use or special permit agreements tied to zoning approval. Definitions vary by state, so the exact labels used in your jurisdiction's enabling ordinance govern which category applies.

Do developers usually own the land?

Not always. Many applicants hold an option to purchase or a contract contingent on securing the development agreement and required approvals, rather than outright ownership at the time of application, since most application requirements accept evidence of site control rather than requiring a recorded deed.

What are the risks of a joint development agreement?

The main risks involve unclear cost-sharing terms, ambiguous schedules that make a breach difficult to prove or defend, and successor liability that binds a future buyer to obligations they did not negotiate. Agreements that lack a clear amendment process distinguishing minor from major changes also risk forcing both parties back through a full hearing cycle for routine adjustments.

Sources