What is leapfrog development? A working definition for planners
Leapfrog development is new construction that skips over the land next to existing built-up areas and lands further out, often past a designated growth boundary, leaving undeveloped parcels in between. A subdivision goes up two or three kilometers past the edge of town, with farmland or scrub sitting untouched between it and the last contiguous block. The name describes the pattern: growth jumps, rather than spreads.
It's the opposite of infill or edge expansion, where new building fills gaps next to what's already there. Planners sometimes call the result scattered development, or use noncontiguous growth as the more technical term in a staff report. Same thing. The parcels aren't connected to the existing urban fabric, and that's exactly the problem.
Why it happens
Land near the edge of an approved boundary is often priced for its zoning, and zoning near the center tends to be tighter. A developer who can get a county variance, or who's building just outside the ministry's mapped jurisdiction, can buy cheaper land further out and still sell lots at a profit. Road access helps too. A new highway interchange or arterial extension can make a parcel ten kilometers away more buildable than one five hundred meters from downtown.
Sometimes it's not a single developer's decision at all. A village that already had a small cluster of houses attracts infill around itself, and that cluster happens to sit outside the boundary that was drawn around the main city. Nobody leapfrogged on purpose. The growth boundary just didn't account for that node.
Why it's expensive for the people who have to serve it
Leapfrog parcels need roads, water lines, and power extended past the gap, not just built at the edge. A utility department pricing out service to a scattered subdivision is usually quoting for kilometers of line that serve nobody in between. Emergency response times stretch. School bus routes get longer. And the land in the gap, the parcels that got skipped, often sits half-serviced and undevelopable for years because nobody wants to run infrastructure to a patch that's surrounded by farmland on three sides.
For a planning ministry or a development bank reviewing a municipality's growth management, this pattern matters more than the raw hectare count. Five hectares of contiguous expansion at the edge of the boundary is a different story than five hectares split across four noncontiguous parcels scattered a few kilometers past it. The second one costs more to service per household and is harder to walk back once it's built.
How it actually gets found
The trouble is that leapfrog parcels are, by definition, not next to anything a planner is already watching. Staff doing a manual review tend to check the edge of the boundary, the obvious growth corridor, maybe a known pressure point from last year's permit requests. A subdivision that popped up eight kilometers out, on a parcel nobody flagged, doesn't show up until a field inspector happens to drive past it, or until someone pulls a full aerial photo set and compares it tile by tile against last year's.
That's slow enough that by the time it's found, the roads are already graded and the first few houses are occupied. There's no undoing that. The annual comparison catches it for next year's report, but "next year" is also when the next round of leapfrog parcels shows up somewhere else nobody was looking.
What a jurisdiction-wide check actually covers
Catching noncontiguous growth before it turns into load-bearing policy means reviewing the whole jurisdiction every cycle, including land well past the edge of the boundary. A built-up change layer that flags new construction anywhere in the area, inside the boundary or three ridgelines away, catches scattered parcels the same pass it catches edge creep. Urban Growth Monitor builds that layer once a year from medium-resolution satellite imagery and lines it up against the approved boundary, so a leapfrog parcel shows up as expansion outside the line wherever it actually sits, not only where staff thought to look.
If you're trying to put a number on how much of this year's growth happened outside the plan, that's the report worth running.