Charging the Developer for the Roads Its Project Will Need
New development generates demand for infrastructure that existing residents would otherwise fund. Impact fees shift that cost onto the project, which is defensible in principle and contested in almost every application.
The Cost That Arrives With the Houses
A subdivision of four hundred homes creates demand for school capacity, road capacity, water and sewer connections, park land, and emergency services. Somebody has to pay for that expansion.
Historically it was funded from general revenue, meaning existing residents paid through property taxes for infrastructure serving newcomers. That arrangement became politically unsustainable in fast growing jurisdictions, and the response was the impact fee: a one time charge levied on new development at the time of permitting, calculated to cover its share of the capital cost of expanding public facilities.
The Legal Constraint That Shapes Everything
A government cannot simply charge whatever it wants as a condition of a permit, because doing so would let it extract unrelated concessions from anyone who needs approval.
American constitutional doctrine developed two tests for conditions attached to land use approvals. The first requires an essential nexus between the condition and a legitimate government interest connected to the development. The second requires rough proportionality, meaning the condition must be roughly proportional in nature and extent to the impact of the proposed development.
Together these mean an impact fee must be calculated from the actual burden a project creates. A fee that funds general municipal operations, or that charges a small project for a facility it will barely use, fails the test.
| Requirement | What It Prevents |
|---|---|
| Essential nexus | Charging for facilities unrelated to the project |
| Rough proportionality | Charging more than the project burden |
| Restriction to capital costs | Funding ordinary operations from permit fees |
| Earmarked accounts and spending deadlines | Collecting fees for facilities never built |
The nexus and proportionality tests exist because a permit is a chokepoint. A government that can condition approval on anything can extract anything, and the doctrine limits it to the cost the applicant actually imposes.
How the Number Is Calculated
A defensible fee schedule requires a study, and the methodology is more contested than the arithmetic.
The jurisdiction establishes a level of service standard, meaning the amount of facility capacity per unit of demand it intends to maintain, such as acres of park per thousand residents or lane miles per peak hour trip. It then estimates the demand a unit of development generates, calculates the capital cost of providing that capacity, and applies credits for other revenue the development will contribute toward the same facilities, principally future property taxes servicing debt on those facilities.
The credit step is the one most frequently done badly, and omitting it produces double charging: the household pays the fee at purchase and then pays property taxes servicing bonds for the same infrastructure.
Who Actually Bears It
The incidence question follows the same logic as any development exaction, and the answer depends on timing and market conditions.
Where fees are long established and predictable, they capitalise into land prices. A developer bidding on a site subtracts the known fee from what it can pay, so the landowner receives less and bears the cost.
Where fees are newly imposed or increased after land was acquired, the developer bears it on projects already committed.
And in a strongly supply constrained market, some portion passes to buyers through prices, because the fee raises the cost of the marginal unit and marginal cost sets price where supply is elastic.
Research has generally found substantial pass through to house prices in growing markets, sometimes exceeding the fee itself, which is the finding critics emphasise and supporters attribute to the value of the infrastructure being provided.
The Argument on Each Side
Supporters make a straightforward efficiency case. Growth should pay for growth. If new development is not charged for the infrastructure it requires, the cost is subsidised by existing residents, which encourages development in locations where servicing it is expensive. Pricing it correctly sends the right locational signal.
Critics argue the fees have grown well beyond genuine infrastructure cost in some jurisdictions, functioning as a growth control device operated by existing residents who benefit from restricted supply. They also note the regressive effect, since a flat fee per unit is a larger share of the price of a modest home than of an expensive one, which pushes development toward larger units.
Both descriptions are accurate in different places, which is why the legal tests matter so much. They are the mechanism for distinguishing the two.
What a Developer Should Actually Examine
Practical diligence points are narrow. Whether the fee schedule is supported by a current study, since stale studies are vulnerable to challenge. Whether credits for other revenue sources were applied. Whether fees are collected at permit issuance or at certificate of occupancy, which matters enormously for carrying cost on a long project. Whether the jurisdiction offers credits for infrastructure the developer builds directly, which is frequently cheaper than paying the fee and letting the government build it. And whether collected fees have actually been spent within statutory deadlines, since unspent funds are refundable in many states.
The Bottom Line
Impact fees make new development pay for the public capacity it consumes, which is sound economics and constitutionally constrained by the requirement that the charge be proportional to the actual burden. The methodology carries most of the honesty of the system, particularly whether credits are applied for other revenue the development will generate. Where the study is rigorous the fee is a price; where it is not, it is a tax on building collected at a chokepoint, and the difference is exactly what the nexus and proportionality tests are meant to police.