Field notes: the territory review where the map and the dealer council didn't agree

Every territory review has a moment where the room goes quiet. Usually it's right after someone pulls up the current boundary map next to whatever new data got commissioned for the year, and a council member who's run the same three counties for twenty years says some version of "that can't be right."

It happened again at a review a few weeks back, the kind every OEM channel team sits through once a year or so. The regional manager had an overlay showing new construction starts and equipment registrations clustered along a corridor that sat entirely inside one dealer's paper, a dealer whose actual sales activity had been flat for two cycles. The council's read was that the territory was mature, maybe even oversaturated. The data said something else: the demand had moved twelve miles east, into a stretch of boundary nobody had touched since the last redraw, and the dealer covering it on paper wasn't the one showing up in the field.

Neither side was wrong, exactly. The council was reading relationships, service calls, who shows up at the co-op meeting. The overlay was reading sites and machines on the ground, which doesn't know or care whose name is on the franchise agreement. That gap is the whole argument for doing this once a year instead of trusting the territory map to still reflect where the work actually is.

This disagreement had a shape to it, which is what made the review worth sitting through. Boundaries drawn ten or fifteen years ago tend to follow old logic: service radius from a dealership, a county line, a handshake about who got there first. Demand doesn't respect any of that. It follows construction cycles, fleet turnover, whatever's getting built or farmed or logged in a given stretch of the territory this year. When the two stop lining up, you get exactly what that council was staring at: a boundary with a dealer's name on it and almost nothing behind it worth defending, next to open ground carrying real activity and no coverage at all.

What stuck with me was watching the room shift. The council stopped arguing about whether the dealer was underperforming and started arguing about whether the boundary made sense anymore. Those are different conversations. One is a performance review. The other is a map problem, and map problems get solved by redrawing, not by another round of incentives on a territory that's already thin on demand.

A few people in the room wanted to know how the sites got flagged, how recent the registration data was, the usual pushback you'd expect when a map contradicts twenty years of windshield time. Fair questions. But the more interesting pushback came from a council member who'd been skeptical going in and ended up asking for the same cut run on two other territories he managed, because if the boundary logic was stale in one place there was no reason to assume it was fresh everywhere else.

That's the pattern worth noting going into next year's review cycle. The fight in the room is rarely about whether the data's right. It's about whether anyone's willing to say out loud that a boundary drawn under one set of conditions doesn't automatically hold when the conditions change underneath it. Dealer councils know their territories better than anyone. What they can't always see, because nobody can from the dealership floor, is the ground fifteen miles past their own service radius where a competitor's installer has been quietly working a site that's never shown up on anyone's call sheet.

If your own review is heading toward one of those quiet moments, Whitespace Mapping builds the overlay that gets put on the table before the argument starts, not after. Run it once a year and the territory review becomes a redraw conversation instead of a guessing contest.