Blog

How to brief a planning commission using an annual built-up change map

Elevated view of patchwork farmland and a town in the distance, divided by a band of trees under a cloudy sky.

You've got eight minutes on the agenda, a staff report nobody read past the summary, and a commission that wants one thing before they'll approve anything else on the docket: did the boundary hold this year, or didn't it.

Most analysts walk in with the wrong artifact for that question. A zoning map shows what's allowed. A permit log shows what got approved. Neither one shows what actually got built where it wasn't supposed to. An annual built-up change map does, and it changes how the whole briefing goes.

What commissioners want from the slide

Commissioners aren't planners. Most of them read the packet the night before, if that. What lands in an eight-minute slot is a single map with the growth boundary drawn in and this year's new construction shaded against it, plus one number: hectares of built-up expansion outside the line.

That's it. Not a legend with twelve categories, not a decade of historical layers stacked on top of each other, not a methodology footnote in 6-point type. One boundary, one year of change, one number. If a commissioner has to ask "so where's the problem area," the slide failed before you opened your mouth.

Put the number in the headline of the slide, not buried in a caption. "14 hectares of expansion outside the approved boundary, concentrated along the eastern frontage road" tells the room exactly what to look at and why it matters. They can see the shape of the problem before you say a word.

Building the packet so it survives questions

The map gets you the room's attention. What keeps it is being ready for the three questions that always come, in roughly this order.

First: how do you know this is new, and not something that was always there and just missed on the last survey. This is where cadence matters. An annual read compares this year's footprint directly against last year's, which is how you tell new construction apart from something an old aerial just failed to catch. Say that plainly, once, and move on.

Second: can we trust a 3 to 10 meter pixel to tell a legal building from a shed. Be honest about what the resolution does and doesn't do. It won't resolve a single structure's setback violation. It will reliably flag a cluster of new rooftops and roads where the plan said there shouldn't be any, which is the scale a commission vote operates at.

Third, and this is the one that sinks unprepared staff: who verified this. The map is a screening layer, not a court exhibit. Say so. "This tells us where to send an inspector, not a verdict" is a sentence that earns trust rather than losing it, because it's true and because it matches what the tool is for.

Bring last year's map to the same meeting if you have it. A single year of expansion is a data point. Two years side by side, same boundary, same shading convention, is a trend, and trends are what move a commission to fund enforcement instead of filing a report.

Where this fits on the agenda

Put the change map early in your slot, ahead of the recommendation. Commissioners form their opinion from the visual, and a recommendation that lands first just becomes supporting evidence for a conclusion they've already half-formed from your tone of voice. Lead with the picture, let the number do the talking, then make the ask.

If your jurisdiction runs these briefings on a yearly cycle tied to the budget calendar, it's worth having the comparison layer ready well before the meeting date rather than compiling it from permit records and old aerials in the two weeks before the hearing. That's the manual version of this exercise, and it's the version most planning offices are trying to get off of.

Urban Growth Monitor builds that comparison layer once a year: this year's built-up footprint against the approved boundary, with the hectare figure already pulled out for the slide. If your next commission briefing is on the calendar, it's worth seeing what the map looks like before you build the deck around it.

Get started

← Back to the blog