What moved

Months in which the common panel's aggregate fee changed. Each step is one or more jurisdictions' new schedule taking effect; fee schedules turn over once a year at most, so a flat month is the normal month.

By category

Of the panel, how many jurisdictions charge each category on a single-family home, and the middle of that charge.

By state

A state gets its own chained index once its panel has reached ten jurisdictions. Until then its median is shown and marked thin.

How it is built

The atom. For each jurisdiction and each month-end, the per-dwelling-unit impact fees in force on a single-family home: citywide, the collected rate, without water, wastewater or power capacity charges. Where a later schedule restates a line, the latest effective date wins; where a schedule prints size tiers, the plain detached home at the smallest tier.

The panel. A jurisdiction counts in a month when that stack covers at least three fee categories. A total made of one fee is not a total.

The level. The median of the panel's totals. One jurisdiction, one observation, whatever its size.

The index. 100 in the first month the panel reached ten jurisdictions. Each month is linked to the last by the aggregate fee of the jurisdictions present in both, so a jurisdiction entering the panel moves the level but never the index.

Not yet in the panel: jurisdictions whose fees are charged per service unit or per meter rather than per dwelling (much of Texas), and every jurisdiction whose schedule has not been read yet. Coverage is growing; the panel size travels with every number so none of them stands alone.

Get the data

index.json holds every row this page renders. The API serves the same tables: GET /v1/fees/index, GET /v1/fees/index?state=FL, GET /v1/fees/index/categories; see the docs. The fee lines underneath, each with its source document, are on the explorer.