How Town Planning Works | TPW-0109 — The Development Agreement: How Cities and Developers Lock Phasing, Infrastructure, Rights and Obligations Into a Long-Term Deal

Series ID: TPW-0109

A master-planned district can take longer to build than the political administration that approved it.

Roads may arrive in year two. A school may be needed in year six. A wastewater plant may need expansion before the next phase. Parks, affordable housing, transit, drainage and utility upgrades may each depend on thresholds that occur at different times.

Meanwhile, the developer needs enough certainty to buy land, finance infrastructure and commit to a plan that may not finish for twenty years.

Ordinary zoning alone can struggle with this time horizon.

That is where a development agreement can enter: a legally structured agreement between a public authority and a landowner or developer that sets out how a defined development will proceed, which rules and entitlements apply, what infrastructure and public obligations must be delivered, how phasing works, and how the agreement can be reviewed or changed over time.

The instrument varies dramatically by jurisdiction. In California, development agreements are expressly authorised in state planning law. Other places use different statutory bases, contracts, planning obligations, infrastructure agreements or master-development arrangements. The exact legal form is local. The planning problem is global.

The reader job: understand how long projects turn planning promises into durable obligations

This article explains the planning mechanics of development agreements: certainty, phasing, infrastructure, public benefits, vested rights, milestones, finance, amendments, monitoring, transparency and exit.

Neighbouring owners already cover adjacent territory. The Time Layer owns sequencing across the town. The Financial Machine Behind the Map owns the broader relationship between land, infrastructure and finance. The Regeneration Agency owns long renewal coordination. The By-Right Approval owns ordinary compliance under fixed rules.

The Development Agreement owns a narrower question: when one large or complex development needs commitments that must survive many years, how can the public and private sides make those commitments explicit enough that infrastructure, rights, obligations and timing remain legible after people, markets and governments change?

The agreement exists because long projects carry two kinds of uncertainty

The developer faces public-policy uncertainty. Will zoning change? Will standards change? Will a later administration reinterpret what was approved? Will infrastructure obligations expand after land has been purchased and finance committed?

The public faces delivery uncertainty. Will the promised road actually be built? Will the park arrive before the houses are occupied? Will affordable units appear in the phase where they were expected? Will a project stop after profitable parcels are completed, leaving costly infrastructure or community benefits unfinished?

A development agreement tries to reduce both uncertainties at once.

Certainty is valuable because time has a cost

California’s development-agreement statute states the logic unusually clearly: uncertainty can waste resources, increase development cost and discourage comprehensive planning, while greater assurance can strengthen the planning process and reduce economic cost.

The principle applies more widely. Land acquisition, design, borrowing, utilities and construction all depend on time. If major rules can shift unpredictably after investment begins, risk is priced into the project.

But certainty for the developer should be matched by certainty for the community. The public needs equally clear commitments about infrastructure, mitigation, public space, housing and performance.

A development agreement is not simply permission to build

The underlying land-use entitlement still matters.

A development agreement may accompany a rezoning, specific plan, subdivision, master plan or other approval. It does not automatically substitute for environmental review, building code, subdivision law, utility approvals or other statutory requirements.

Its job is usually to organise the long-term relationship around an approved development framework.

This distinction protects the instrument from becoming a private route around public planning.

The legal authority must be explicit

Because a development agreement can bind future actions, extend over many years and affect valuable property rights, the public authority needs clear legal power to enter it.

The statutory basis should identify who can sign, what subjects may be included, what hearings or findings are required, whether the agreement must be adopted by ordinance, how it is recorded, and how modification or cancellation works.

California Government Code sections 65864 through 65869.5 provide one well-known framework. Local jurisdictions then adopt procedures for application, hearing, periodic review and amendment.

Elsewhere, the structure may be different. The planning principle is the same: a long-term agreement should rest on visible authority, not improvised bargaining.

The agreement should identify the property precisely

A development agreement needs a legal geography.

Which parcels are covered? Does it bind later subdivisions? What happens if one parcel is sold? Are off-site infrastructure parcels included? Does the agreement apply to future annexed land?

Maps, legal descriptions and ownership interests matter because the agreement may later be read by people who had no role in negotiating it.

A vague project boundary today becomes a dispute boundary later.

The development programme should be measurable

The agreement should state what is actually authorised or contemplated.

How many homes? How much commercial or industrial floor area? Which uses? What maximum density or intensity? Which plans control? What flexibility exists to shift floor area or units between phases?

Large projects need some adaptability because markets change. But flexibility should have limits. If the agreement allows unlimited redistribution, the public cannot know what infrastructure demand or built form it is committing to.

Phasing is the spine of the agreement

A twenty-year project should not be treated as one undifferentiated approval.

Phases connect development to infrastructure and public obligations. A phase may be triggered by time, dwelling count, floor area, parcel completion or a specific capital project.

The agreement should state what can proceed before each threshold and what must be complete before the next phase begins.

This turns phasing from a colourful master-plan diagram into an enforceable sequence.

Infrastructure obligations need scope, timing and ownership

A promise to provide infrastructure is incomplete.

Which road? To what standard? Who designs it? Who pays? When must it be complete? Who owns it afterward? Who maintains it before handover? What happens if the utility authority changes its technical standard?

The same questions apply to water, sewer, drainage, parks, schools, transit facilities, energy systems, broadband and public-realm works.

A strong agreement converts the broad phrase “developer to provide infrastructure” into a delivery matrix.

Some infrastructure serves more than the project

A trunk sewer, arterial road, bridge or regional park may benefit future development beyond the original project boundary.

If the first developer pays the full cost, later projects can free-ride. If the public pays everything, existing taxpayers may subsidise private development.

Agreements can include reimbursement, credit, cost-sharing or later-connection mechanisms where law permits. California’s statutory findings specifically recognise that development agreements may include arrangements for applicants who finance public facilities to be reimbursed over time.

The planning question is proportionality: who creates the need, who receives the benefit and how should cost be allocated across time?

Public benefits should not be an undefined shopping list

Development agreements are sometimes used to secure affordable housing, parks, community facilities, environmental restoration, local employment programmes, public art, transit improvements or other benefits.

These can be legitimate planning outcomes. But negotiation should remain connected to adopted policy, project impact and legal authority.

An agreement becomes harder to defend when public benefits are invented ad hoc because one project has bargaining power.

A mature system publishes policy priorities and standard methodologies so applicants understand the likely obligations before negotiation begins.

The agreement should distinguish mitigation from negotiated benefit

Mitigation addresses an impact the project creates or contributes to.

A negotiated benefit may advance a broader public objective in exchange for certainty, additional development capacity or another lawful consideration.

Mixing the two obscures accountability.

If a road improvement is required because project traffic demands it, say so. If a civic facility is part of a broader negotiated package, say that too. The distinction matters for cost allocation, legal review and public understanding.

Vested rights are a central but jurisdiction-specific issue

One reason developers seek agreements is to lock in a degree of regulatory certainty.

The agreement may specify which policies, zoning rules or development standards are vested for the term and which later health, safety, environmental or generally applicable rules can still apply.

This balance is legally sensitive. A city should not surrender future police powers casually. A developer cannot finance a long project if every core entitlement remains fully unstable.

The agreement should therefore state clearly what is fixed, what can change and under what legal conditions.

Not every rule should be frozen

Building codes, fire standards, accessibility rules, climate requirements and public-health regulations may need to evolve.

Some agreements distinguish land-use entitlements from later technical codes. Others create specific update mechanisms.

The planning principle is to freeze only what needs certainty and preserve public capacity to respond to genuine safety and legal change.

Milestones are stronger than vague completion promises

A milestone can be inspected.

Examples include completion of a road before the 500th dwelling, dedication of a park before a named phase, delivery of affordable homes proportionately with market homes, or construction of a utility upgrade before a specified occupancy threshold.

Milestones should name the responsible party, completion test and consequence of failure.

A promise that something will be delivered “in due course” is not a milestone.

Triggers should match the demand mechanism

If school demand grows with occupied homes, a dwelling or occupancy trigger may make more sense than a calendar date.

If a regional utility upgrade has a fixed construction schedule, a date may matter. If transport demand depends on commercial floor area, the trigger might track that floor area.

Good phasing connects obligation to the variable that creates need.

Finance and phasing must be tested together

A front-loaded infrastructure package can make the first phase financially impossible.

A heavily back-loaded package can let the project externalise early impacts onto the community.

The agreement should test cash flow, financing capacity, public capital schedules and realistic absorption. The objective is not to maximise obligations at the earliest date. It is to ensure infrastructure arrives before unacceptable deficit while keeping delivery feasible.

This is where planning and development economics have to speak to each other.

The agreement needs rules for market change

Twenty-year plans encounter recessions, interest-rate shocks, demographic shifts, new technologies and changes in demand.

A district planned around office space may later need housing. Retail assumptions may change. Construction cost may rise. A transport technology may alter parking demand.

If every change requires reopening the entire agreement, the project becomes brittle. If changes are unlimited, the public bargain loses meaning.

The agreement should define administrative modifications, substantial amendments and changes that require a new public process.

Materiality should be defined

A door moving is not the same as replacing a promised school site with housing.

The agreement can set thresholds: minor parcel-line adjustment, limited unit transfer or technical infrastructure change may be approved administratively; major land-use shifts, density increases or removal of public obligations return to the governing body.

Materiality rules prevent both bureaucratic paralysis and silent project transformation.

Periodic review keeps a long agreement alive

Many development-agreement systems require periodic review.

The purpose is not to renegotiate the deal every year. It is to verify whether each party is complying, update schedules, identify upcoming obligations and record approved changes.

A public compliance report can become the institutional memory of a project that outlives individual staff.

Monitoring should track obligations, not just construction volume

A dashboard that reports 3,000 homes built but does not report park delivery, sewer capacity, affordable units or road milestones tells only half the story.

Each material obligation should have a status: not yet triggered, due, underway, complete, delayed, modified or in dispute.

The agreement itself should be translated into an operational monitoring table.

Transparency is essential because the agreement can resemble private law

A long negotiated document can be difficult for residents to understand.

Publish the agreement, maps, exhibits, amendments, compliance reports and milestone table. Provide a plain-language summary of what the project may build and what the public is promised in return.

The more the agreement departs from ordinary code rules, the more important transparency becomes.

The public hearing should focus on the actual bargain

A hearing can become dominated by the project’s architecture while the most important long-term decisions are buried in exhibits.

What rules are vested? What infrastructure is promised? What costs move to the public? What deadlines matter? What happens if the developer defaults? What public benefits depend on later phases?

These are the questions the agreement is designed to answer, and they should be visible during approval.

Security may be needed for critical obligations

If the public depends on a private party to deliver infrastructure, the agreement may need financial security or other assurance before later phases proceed.

Bonds, letters of credit, escrow, guarantees or phased permit holds may be available depending on local law and the type of obligation.

The planning principle is simple: a promise that becomes essential to public safety or service should not depend solely on goodwill.

Default provisions should be proportionate

Not every delay should terminate a twenty-year agreement.

The document should identify notice, cure periods, remedies and escalation. Minor administrative breaches can be corrected. Serious failure to deliver required infrastructure may justify suspension of later approvals. Persistent material breach may trigger stronger remedies.

A credible agreement explains what happens when things go wrong before they go wrong.

Force majeure needs limits

Major projects encounter events outside either party’s control.

Natural disasters, war, supply-chain disruption or government action can make a deadline impossible. Agreements often include force-majeure concepts, but the clause should not become a universal excuse for market underperformance.

Define covered events, notice requirements, documentation and how schedules are extended.

Ownership transfer should not erase obligations

Large developments are often sold in pieces.

The original master developer may sell parcels to builders, investors or institutions. The agreement must state which obligations run with the land, which remain with the master developer and how responsibilities transfer.

Otherwise the public can discover that the entity that promised a road no longer owns the land needed to build it.

The agreement should coordinate with subdivision and land dedication

Roads, parks, utility sites and school sites often depend on subdivision.

Dedication timing, easements, rights of way and parcel creation should align with the phase plan. An agreement that promises a park on land that can later be separately sold has a structural weakness.

Infrastructure handover needs acceptance criteria

Public ownership begins after private construction only when the facility meets the required standard.

The agreement should define inspections, as-built information, defects, warranty periods and who maintains the facility before formal acceptance.

Handover is a planning issue because future public budgets inherit the asset.

Lifecycle cost matters

A developer may offer an impressive park, road or facility whose long-term maintenance cost is high.

The public should assess not only capital value but operating burden. Who pays for landscaping, pumps, retaining structures, lighting, community facilities or specialised materials after handover?

A public benefit that creates an unsustainable maintenance liability can become a future budget problem.

The agreement should not become a substitute for updating obsolete zoning

If every major project requires a bespoke agreement to become feasible, the base planning system may be too rigid or outdated.

Development agreements are useful for exceptional scale, phasing and infrastructure complexity. They should not be necessary for ordinary infill that could be handled by clear zoning and objective standards.

Repeated negotiation is feedback about the code.

A worked example: a 15-year new district

Imagine a former industrial area planned for 8,000 homes, employment space, two parks and a new transit interchange.

Phase 1 can use existing road and sewer capacity, but Phase 2 requires a trunk sewer. The first primary school is needed by a dwelling threshold. The major park is expensive and should be delivered proportionately rather than after the final market phase.

A development agreement might therefore link the 2,000th dwelling to sewer completion, require land dedication for the school before a named subdivision, phase park construction at 25, 50 and 75 per cent of residential build-out, define affordable-housing delivery by phase, lock the approved land-use envelope for a stated term, require annual compliance reports and define which design adjustments can be approved administratively.

The agreement does not replace the plan. It makes the plan’s timing and obligations durable.

The negotiation team should include the people who will later administer the agreement

A common institutional mistake is to negotiate with one team and administer with another.

Lawyers, senior executives and elected officials may focus on headline terms while day-to-day implementation later falls to planners, engineers, building officials, finance staff and utility agencies.

Those operational departments should test the draft. Can they determine when a trigger has occurred? Can they inspect the promised work? Is the data available? Does one obligation conflict with another agency’s capital plan?

An agreement that cannot be administered without constantly asking the original negotiators what they meant is not finished.

The schedule should include dependencies, not only dates

A Gantt chart can show when each item is expected. A dependency map shows what must happen first.

The school site cannot transfer until subdivision creates the parcel. The transit interchange cannot open until road access and utilities are complete. The later housing phase cannot connect until the sewer upgrade is commissioned. A park cannot be accepted until irrigation and drainage systems pass inspection.

Writing these dependencies explicitly makes delay easier to diagnose. Instead of asking why Phase 4 is late, the monitoring team can identify which prerequisite failed.

Community benefit delivery should be proportional to private build-out

If every public benefit is placed in the final phase, the community carries execution risk.

The developer can complete the profitable early parcels while the park, affordable housing or civic facility remains dependent on later market conditions. At the other extreme, requiring every benefit before the first building can make the project impossible to finance.

Proportional delivery can balance these risks. Affordable homes can track market homes. Public space can open in stages. Community facilities can be tied to population thresholds. The agreement should explain the logic rather than hiding benefits in a distant end state.

Land-value change should be acknowledged without pretending it can be calculated perfectly

Public decisions can increase land value. New zoning, infrastructure, station investment and public-space upgrades may make development more valuable.

Development agreements sometimes become one place where public authorities seek contributions toward infrastructure or community outcomes connected to that value creation.

The difficult part is avoiding arbitrary negotiation. The authority should rely on adopted policy, feasibility evidence, infrastructure cost and lawful contribution mechanisms rather than simply asking how much the project can pay.

A transparent methodology makes the public bargain more defensible and reduces the advantage of applicants with stronger negotiating teams.

A development agreement should not hide fiscal risk off the balance sheet

A city may promise reimbursements, tax sharing, infrastructure credits or future payments.

Those promises are public liabilities even if no cheque is written today.

Finance staff should model the long-term fiscal effect under several scenarios: fast build-out, slow build-out, partial build-out and project failure. What happens if reimbursement obligations arrive before the expected tax base? What maintenance costs begin after public facilities are accepted?

A planning agreement becomes a fiscal document the moment it commits future public resources.

The agreement needs a strategy for partial build-out

Many master-planned projects are never completed exactly as approved.

If the project stops after Phase 2, does the area still function? Are roads connected? Is drainage complete? Did early residents receive enough park space and services? Are temporary dead ends or vacant parcels safe and maintainable?

Good phasing creates viable interim states. Each phase should be capable of standing as a coherent piece of city rather than depending entirely on a final phase that may arrive decades later or never.

Sunset clauses protect the public from eternal entitlements

A very long agreement can outlive the assumptions that justified it.

A term should be long enough to support financing and delivery, but not so long that obsolete standards remain untouchable forever. Extension should require evidence: what has been delivered, what remains, why more time is necessary and whether the public bargain still makes sense.

Sunset is not punishment. It is recognition that certainty has a time horizon.

Dispute resolution should keep technical disagreements from paralysing the whole project

Large agreements generate disagreements about cost estimates, trigger dates, completion standards and interpretation.

The contract can create staged resolution: staff consultation, senior management review, mediation, expert determination for technical matters, and formal legal remedies if necessary.

A clear dispute ladder reduces the temptation to turn every ambiguous engineering detail into a political crisis.

A worked monitoring table is as important as the legal prose

Imagine the agreement contains 120 pages and 47 material obligations.

The public-facing implementation tool should not require staff to reread all 120 pages each month. Translate obligations into a table containing the clause reference, responsible party, trigger, due date, evidence required, current status and next action.

Link every status back to the controlling clause rather than replacing the legal document.

This makes the agreement executable. Legal prose defines the obligation; the monitoring table operates it.

A development agreement audit

Authority: What law allows the public body to enter the agreement?
Property: Which parcels and ownership interests are bound?
Entitlements: Which approved plans, uses, densities and intensities does the agreement recognise?
Term: How long does the agreement remain in force?
Vesting: Which land-use rules are fixed and which future rules may still apply?
Phases: What are the project phases and what triggers each one?
Infrastructure: Which roads, utilities, parks, schools or facilities must be delivered?
Timing: What must be complete before later occupancy or permits?
Cost: Who pays for each item and how are shared facilities financed?
Reimbursement: Can a party recover costs for infrastructure serving later development?
Public benefits: Which negotiated outcomes go beyond ordinary mitigation?
Mitigation: Which obligations directly address project impacts?
Milestones: Are obligations tied to measurable dates, units or floor area?
Security: What protects the public if critical private obligations are not delivered?
Monitoring: Who tracks compliance and how often?
Reporting: Are compliance reports public and understandable?
Amendments: Which changes are administrative and which require public approval?
Market change: How can the programme adapt without erasing the original bargain?
Transfer: What happens when land or development rights are sold?
Handover: How are privately built public facilities inspected and accepted?
Maintenance: Who carries operating cost before and after handover?
Default: What notice, cure and remedies apply to material failure?
Exit: How can the agreement expire, be terminated or be replaced?
Record: Are agreements, exhibits and amendments recorded and easy to discover?
Code feedback: Is bespoke negotiation solving a truly exceptional project or compensating for a weak base code?

A development agreement is a memory system for a project that lasts longer than its negotiators

Large development is not one decision.

It is a sequence of land transactions, permits, loans, construction phases, infrastructure works, handovers and political administrations.

Without durable records, promises degrade into memory. New staff inherit partial files. New owners reinterpret old obligations. Community expectations drift away from the legal documents. Infrastructure arrives late because nobody can see the trigger that made it due.

A strong development agreement keeps the bargain legible.

It names the rights. It names the obligations. It connects growth to infrastructure. It defines what is fixed and what can change. It records the sequence. It creates review points. It explains remedies. It survives ownership transfer and staff turnover.

The purpose is not to freeze the future. It is to make long-term change governable enough that adaptation can occur without losing the commitments that made the project publicly acceptable in the first place.

Sources and further reading

Continue reading: Land, finance, development and regeneration · Full Town Planning Series Index · Urban Planning Master Edition.