How Town Planning Works | TPW-0116 — The Development Exaction: How Permit Conditions, Land Dedications and Mitigation Stay Connected to the Impact a Project Creates

Series ID: TPW-0116

A development permit can be worth millions.

That gives government an unusual kind of leverage.

An applicant may need the approval badly enough to accept almost any condition attached to it: dedicate a strip of land, widen a road, build a path, fund a signal, restore a wetland, provide a drainage easement, construct a bus stop, pay for an off-site improvement or reserve land for a public purpose.

Some of those conditions can be entirely reasonable. A project that creates a new access problem should help solve the access problem. A development that blocks a planned public path may need to preserve the connection. A subdivision that requires a new stormwater facility may need to provide the land and infrastructure necessary for it.

But the permit process can also become a place where unrelated public wishes are loaded onto the applicant simply because the authority has bargaining power.

That is the planning problem behind development exactions.

The exact legal doctrine varies by country and jurisdiction. In the United States, exactions have a particularly developed constitutional framework through cases including Nollan, Dolan, Koontz and, most recently, Sheetz v. County of El Dorado in 2024. The U.S. Supreme Court has repeatedly focused on the relationship between a permit condition and the development impact it is supposed to address, using the ideas of an essential nexus and rough proportionality. Other jurisdictions use different statutory, administrative-law, compensation or planning-obligation frameworks. The planning principle is broader than any one legal system: a project-specific obligation should be connected to a project-specific reason.

The reader job: tell mitigation from leverage

This article explains how conditions, dedications and negotiated mitigation can be structured so they solve real development impacts without turning the approval process into an unbounded bargaining table.

Neighbouring articles already own related mechanisms. The Development Impact Fee owns generally applicable fee schedules that spread growth-related capital costs across a class of development. The Development Agreement owns long-term negotiated obligations on complex projects. The Site Plan Review owns the physical review of one site. The Equity Audit owns distribution of benefits and burdens.

The Development Exaction owns a narrower question: what may the planning authority reasonably require from this project, as a condition of approving this project, because of the effects this project creates?

An exaction can take several forms

Land dedication: a strip for street widening, a public path, drainage corridor, park edge or other right.
Easement: a right of access, utility, drainage or public passage over private land.
Physical improvement: a sidewalk, signal, intersection change, water main, sewer extension, landscape buffer or habitat work.
Monetary contribution: funding toward an identified improvement associated with the project impact.
Operational condition: limits on access points, delivery hours, loading arrangements, noise controls or other measures tied to the project’s operation.
Mitigation measure: an action required to reduce an environmental, traffic, drainage, safety or community impact identified during review.

The common feature is that approval is conditioned on the applicant providing, doing or accepting something beyond the bare permission to develop.

Not every permit condition is an exaction in the same legal sense

A planning approval may contain many ordinary conditions.

Use approved materials. Install the required fire access. Build in accordance with the plans. Limit operating hours. Complete landscaping before occupancy. Meet the adopted drainage standard.

Some legal systems reserve the term exaction for conditions requiring money, property or public improvements. Others use it more broadly.

The terminology matters legally, but the planning discipline should be similar: every condition should have an identified purpose, authority and implementation test.

The first test is purpose

Why is this condition being imposed?

If a subdivision adds vehicle trips to an intersection, the public purpose may be safe and functional access. If a project interrupts a drainage path, the purpose may be flood protection. If new development creates a missing pedestrian link between a station and a public street, the purpose may be network continuity.

A condition without a clear public purpose is difficult to defend and difficult to administer.

The second test is connection

The required action should address the problem the project creates or intensifies.

A project that increases pedestrian movement can reasonably be asked to provide a safe frontage connection. That is different from requiring the same project to fund an unrelated park on the other side of the city because the municipality happens to need a park.

In U.S. constitutional law, the Nollan line of cases expresses this idea through the requirement for an essential nexus between the condition and the governmental interest that would justify denying or regulating the project.

The word nexus is legal vocabulary for a planning instinct every competent reviewer should already have: explain the chain from impact to obligation.

The third test is scale

Even a related condition can be too large.

Suppose a 40-home development contributes five per cent of the future traffic at an intersection. Requiring that project to reconstruct an entire regional interchange may address a related transport issue, but the burden can still be disproportionate.

In the United States, Dolan v. City of Tigard introduced the phrase “rough proportionality” for certain permit exactions. The authority must make an individualised determination that the condition is related in nature and extent to the impact of the proposed development.

The exact legal test is jurisdiction-specific. The planning principle travels well: do not make the last project through the door pay for a whole pre-existing problem.

Existing deficiencies belong on a separate line

Imagine an intersection that already fails badly before a new development arrives.

The project may worsen the problem and therefore justify a proportionate contribution to an improvement.

But the project did not create the entire historic deficiency.

A fair analysis separates three quantities: existing demand, background growth and project-generated demand.

That separation matters for infrastructure finance and for public trust. Otherwise the authority can postpone maintenance and capacity investment, then transfer the accumulated bill to whichever development applicant appears next.

A dedication is not free just because money does not change hands

Requiring a strip of land for a road or public path has economic value.

The land may reduce developable area, alter site design or constrain future use. That is why land dedications require the same disciplined reasoning as monetary contributions.

The question should be: what width and location are necessary to address the project’s effect and implement an adopted network?

“We might want more land later” is not a planning analysis.

Street widening is a classic exaction problem

A parcel fronts a two-lane road. The long-term plan shows a wider corridor. The proposed development will add traffic.

Should the project dedicate land? Build its frontage? Fund a share of the corridor? Preserve space for a cycleway? Install a signal?

The answer should come from network planning and impact analysis, not a ritual requirement applied without context.

If the future road is in an adopted plan and the project materially contributes to the need, a condition can be easier to justify. If the widening is speculative and the project’s effect is negligible, the case becomes weaker.

Frontage improvements are often the most direct obligations

Sidewalks, curb ramps, street trees, drainage, driveway consolidation and frontage utilities are physically adjacent to the project.

That direct relationship can make them sensible project conditions.

But even frontage standards should be proportional and coordinated. A small infill project should not be forced to build a disconnected fragment of an elaborate streetscape that cannot function until neighbouring parcels redevelop unless there is a credible interim design.

The condition should produce a useful piece of public realm now or preserve a coherent part of a funded future network.

Off-site mitigation needs a stronger explanation

Sometimes the best place to mitigate an impact is not on the project site.

A downstream drainage improvement may solve the hydraulic problem more effectively than a site-only facility. A nearby intersection may be the real traffic bottleneck. Habitat restoration may be ecologically stronger if it connects to a larger protected area.

Off-site mitigation can therefore be rational.

The farther the obligation moves from the site, however, the more important the causal explanation becomes. The authority should show how the project contributes to the impact, how the off-site measure addresses that impact and why the required share is appropriate.

A project can mitigate demand without building new infrastructure

Physical construction is not always the best response.

A transport impact can sometimes be reduced through fewer parking spaces, transit passes, bicycle facilities, car-share provision, staggered operating hours or a travel-demand programme.

A water impact can be reduced through efficiency standards, reuse or landscaping choices. A flood impact can be reduced through building placement and permeable surfaces. A noise impact can be reduced through loading management.

Mitigation should solve the impact, not mechanically maximise concrete.

Conditions should be measurable

“Improve the pedestrian environment” is a policy direction.

“Construct a 2.5-metre clear footpath along the project frontage before first occupancy” is an administrable condition.

A permit condition should identify what is required, where, to what standard, by when, and how completion will be verified.

Ambiguous conditions generate negotiation after approval, precisely when leverage and financing pressure are highest.

The trigger matters

An improvement needed because of occupants does not always need to exist at grading permit.

Another improvement may be essential before construction begins because later installation would require reopening a road or disturbing occupied buildings.

Conditions can be tied to subdivision recording, building permit, construction commencement, a unit threshold, first occupancy or later phase.

The trigger should match the moment the impact or dependency becomes real.

Security protects the public when construction is deferred

Sometimes a project is allowed to proceed before every required improvement is complete.

A bond, letter of credit, escrow or other security can ensure the authority has a remedy if the developer fails to finish the work.

The security amount should reflect realistic completion cost, including the public agency’s potential cost if it has to take over an incomplete project.

This connects the exaction to the subdivision-improvement logic in The Subdivision Plat.

A generally applicable fee is not the same as an ad hoc exaction

A development impact fee is usually established through an adopted methodology and schedule that applies to a defined class of development.

A project-specific exaction is typically negotiated or imposed during review because of the circumstances of that project.

The legal distinction can be important and has evolved in U.S. law. In Sheetz v. County of El Dorado, decided April 12, 2024, the U.S. Supreme Court held that the Takings Clause does not exempt permit conditions from constitutional scrutiny simply because the condition was imposed by legislation rather than administratively. The Court did not resolve every question about how proportionality applies to broad fee schedules, leaving important issues to lower courts.

For planners, the lesson is practical even outside the United States: adopting a fee or condition through legislation does not eliminate the need for a defensible relationship between development and burden.

Standard conditions can improve fairness

If the same issue appears repeatedly, the authority should consider a standard rule rather than renegotiating it project by project.

For example, every redevelopment along a designated main street may need the same frontage treatment. Every subdivision in a basin may need the same drainage standard. Every large employment project may need bicycle parking under the same adopted rule.

Standardisation improves predictability and reduces the risk that two similar applicants receive materially different obligations.

But standardisation should not erase site reality

A standard condition copied onto every approval can become meaningless.

Require a bus stop where no bus route exists. Require a trail dedication to nowhere. Require a turn lane where traffic volumes do not justify it. Require a drainage facility based on a generic percentage rather than hydrology.

Templates should save administrative work, not replace professional judgment about whether the condition applies.

Voluntary offers can become involuntary in practice

Planning negotiations sometimes use the language of voluntary contributions.

That label deserves scrutiny when the applicant believes approval will be denied without the offer.

If the public authority suggests a contribution, the file should explain its policy basis and relationship to the project. Transparency protects both sides: the applicant from hidden leverage and the authority from accusations of arbitrary bargaining.

Community benefit and impact mitigation are different

A project may create an impact that must be mitigated.

A city may also want broader community benefits: affordable housing, a cultural space, public art, local employment, a childcare centre or enhanced public realm.

Those objectives can be legitimate, but the legal and policy basis may differ from project-specific impact mitigation.

Combining every public aspiration into one condition list makes the bargain harder to understand.

Separate the columns: required code compliance, impact mitigation, generally applicable fees, incentive-based benefits and negotiated development-agreement commitments.

Affordable housing requirements need their own policy architecture

Inclusionary housing systems can require or incentivise affordable homes as part of residential development.

That subject belongs principally to The Inclusionary Zone.

The exaction lesson is only that affordable-housing obligations should not appear as an improvised project-by-project demand without a clear legal and policy basis. Predictable housing policy is more durable than opportunistic negotiation.

Environmental mitigation should follow the causal chain

Suppose development removes habitat, increases runoff or exposes future residents to noise.

The mitigation sequence should be explicit: avoid the impact where practical, minimise what cannot be avoided, restore or compensate where appropriate, and monitor the result where performance is uncertain.

The condition should identify the environmental effect it addresses and the evidence supporting the required measure.

A mitigation measure without a stated impact becomes hard to evaluate later.

Monitoring conditions need a closure rule

Some obligations continue after construction: habitat management, noise monitoring, travel plans, stormwater maintenance or affordable-housing covenants.

Long-term conditions should state who reports, how often, what threshold counts as compliance, what happens after failure, and when the obligation ends if it is not permanent.

An endless monitoring requirement with no decision rule creates paperwork rather than regulation.

Small projects need proportional administration as well as proportional obligations

A four-unit infill project should not need the same traffic study as a 4,000-unit district.

Study requirements themselves can function like exactions because they impose cost before the authority knows whether a significant impact exists.

Thresholds and screening tools can identify when a full technical study is warranted.

Proportionality begins before the final condition list.

The condition should name the standard used to calculate it

If a project must contribute $420,000 toward an intersection, how was that number calculated?

If it must dedicate 3.2 metres of frontage, why 3.2 metres?

The file should contain the formula, engineering analysis, adopted cross-section, trip allocation, drainage model or other evidence that makes the requirement reproducible.

A condition that can be explained only as “this is what we usually ask for” is institutionally weak.

Credits prevent double payment

A project may construct an improvement that is also funded through an impact-fee programme.

Without a credit mechanism, the applicant can pay once through construction and again through the fee.

Where the law and programme permit, the authority should identify how project-delivered improvements are credited against broader obligations.

This is one place where The Development Impact Fee and project-specific exactions must be coordinated carefully.

Refund and release rules matter when the project changes

A development may shrink after approval.

A planned access may be removed. A land dedication may no longer be needed. An improvement may be delivered by another project or public agency.

The approval system should have a route to modify, release or credit obsolete obligations rather than leaving them frozen forever.

Likewise, security should be released promptly when the required work has been accepted.

Conditions should survive ownership transfer when necessary

Projects are sold.

If an obligation must bind successors, the legal instrument should make that clear. Some conditions attach to the land, some to the permit holder, some to recorded covenants or agreements.

The planning file should not depend on the original developer remaining in control forever.

The approval record should show the negotiation history

Why was one condition removed? Why did the contribution fall from $800,000 to $500,000? Why was a road dedication replaced by an easement?

Material changes should be documented.

This protects future staff, the applicant and the public. A transparent file lets later reviewers reconstruct the causal chain rather than treating the final condition as an unexplained number.

Pre-application meetings should identify likely exactions early

Applicants need to know the likely infrastructure and mitigation burden before they purchase land or complete a design.

At pre-application stage, the authority can flag planned road dedications, known utility constraints, required studies, likely frontage works and applicable fee programmes.

This does not guarantee the final condition list before analysis is complete. It reduces surprise and allows the project to incorporate obligations into the design rather than discovering them after finance is fixed.

The strongest mitigation is designed into the project

A condition that requires a retaining wall after the site plan is complete is less elegant than a site plan that avoids the unstable slope.

A condition that requires a pedestrian detour is weaker than a layout that places the entrance on the public path.

A condition that requires expensive noise barriers may be less effective than locating sensitive rooms away from the source.

Good development review uses conditions to close necessary gaps, not to repair a fundamentally poor layout after the fact.

Exactions should not become a substitute for public capital planning

A city needs a bridge.

If the bridge serves an entire district, waiting for one large development to appear and then requiring that applicant to build it is weak infrastructure governance.

Regional facilities should generally have a capital plan, funding strategy and fair method of allocating growth-related costs.

Project-specific conditions can connect a development to that strategy. They should not replace the strategy.

Exactions should not become a substitute for taxation either

Existing residents need services too.

A public authority cannot reasonably fund every general civic need by attaching obligations only to people who happen to seek development permits.

The line between growth-related infrastructure and general public expenditure should remain visible.

Development can pay a fair share of the costs it creates. The wider tax base remains responsible for the wider city.

A worked example: the new neighbourhood and the missing crossing

Imagine a 300-home project beside a school.

Children from the project will cross an arterial road at an unsignalised junction. The project materially increases pedestrian demand at that location. A safe crossing is therefore clearly related to the development.

The authority estimates that a signalised crossing, refuge design and footpath connection will cost $900,000.

But existing neighbourhoods and a planned public sports facility will also use it. The project is forecast to generate 45 per cent of the crossing demand at the relevant period.

A disciplined approach separates the questions. The nexus is strong: the project creates school-crossing demand. The total improvement is larger than the project alone needs. The project-specific obligation should therefore be based on an adopted or defensible allocation method rather than requiring the applicant to fund every public user.

The remaining share belongs in the public capital plan or another lawful funding mechanism.

Another worked example: the beautiful but unrelated park

A small office project seeks approval downtown.

The city wants to renovate a waterfront park three kilometres away and asks the applicant to contribute because the project is profitable.

Profitability alone does not establish an impact relationship.

If the project falls within a lawfully adopted district-wide park impact-fee programme, a contribution may have a clear methodology. If there is a development agreement exchanging additional entitlement for defined benefits, the legal structure may be different again.

But a one-off request attached only because the permit creates bargaining leverage is institutionally weak.

The U.S. exactions cases are useful because they expose the power problem

The specific U.S. constitutional doctrine does not govern the world.

Its planning lesson is still widely useful.

Nollan asked whether the required public easement was connected to the governmental interest used to justify the permit condition. Dolan added a proportionality inquiry. Koontz made clear that the doctrine can apply even when the permit is denied because the applicant refuses the demanded concession, and that monetary demands can also be implicated. Sheetz rejected a categorical distinction that would exempt legislatively imposed permit exactions simply because they came from legislation.

Across these cases sits one recurring concern: the permit authority should not use its gatekeeping power to obtain property or money unrelated or disproportionate to the project’s impact.

A practical development-exaction audit

Authority: What law, plan, ordinance or permit power authorises the condition?
Purpose: What public interest is the condition protecting?
Impact: What effect of the proposed development creates the need?
Nexus: How does the required action address that effect?
Scale: Is the burden proportionate to the project’s contribution to the problem?
Existing deficiency: What portion of the problem existed before the project?
Background growth: What portion belongs to other approved or future development?
Alternative mitigation: Could design or operations reduce the impact more efficiently?
Location: If mitigation is off site, why is that location functionally connected?
Measurement: Can the amount, width or improvement scope be reproduced from evidence?
Trigger: When must the obligation be delivered?
Security: If delivery is deferred, what protects the public?
Credit: Is the applicant also paying a fee for the same improvement?
Ownership: Who owns and maintains the completed facility?
Monitoring: How is long-term compliance verified?
Transfer: Does the obligation bind successors where necessary?
Modification: What happens if the project changes and the condition becomes obsolete?
Transparency: Does the file show the evidence and negotiation history?
Consistency: Are similar projects treated similarly?
Policy feedback: If the same condition appears repeatedly, should it become a general code standard or fee programme?

The permit is a gate, not a blank cheque

Planning authorities need the ability to require development to deal with its consequences.

Without that power, the public can inherit roads that do not connect, drainage that fails, unsafe crossings, missing utility corridors and impacts that private projects create while public budgets repair them later.

But the same approval power can become unfair if every public wish is attached to the applicant simply because the applicant needs permission.

The discipline is causal.

Name the impact. Name the public interest. Show the connection. Scale the response. Document the calculation. Separate project mitigation from existing deficiency and general civic spending. Make the trigger and completion test explicit.

A strong exaction is not a negotiation victory for government or developer. It is a correctly sized bridge between a private project and the public system that project changes.