Sales planning territory vs service territory: how OEMs draw the lines differently

Ask a dealer principal to show you "their territory" and you'll usually get two different maps depending on who's answering. The sales planning manager points at a PMA built around county lines and registration data. The service manager points at something looser, built around drive time and where the mobile techs go. Both are right. They're just answering different questions.
What the sales planning map is built for
A sales planning territory exists to answer one question: who gets credit for the sale, and who's on the hook for the quota. OEMs draw these boundaries off registration and VIO (vehicles in operation) data, sometimes a straight county grid, sometimes adjusted for population density or existing dealer footprint so two points don't cannibalize each other. The PMA is a sales math problem. It gets redrawn when a dealer changes hands, when a new point opens nearby, or when corporate decides a territory's too big for one rep to cover effectively.
None of that has much to do with where the machines actually sit. A PMA can run sixty miles east-west on paper while the customer sites that matter, the quarries, the municipal yards, the big ag operations, cluster in one corner of it. The boundary tells you who owns the account. It doesn't tell you where the aging iron is parked.
What the service territory is built for
Service and parts territories get drawn around a different constraint: how far a tech can drive and still hit a same-day call. Unlike the sales boundary, which runs off registration counts, this one runs off drive time, truck placement, and road conditions. It flexes around which customer sites generate enough call volume to justify a standing route. A dealer with three service bays might run four overlapping service zones that don't line up with any sales boundary at all, because the aftersales side cares about response time, not account ownership.
This is why a rep can work a PMA for years and still not have a clean read on fleet condition inside it. The sales boundary was never built to answer "which of my customer sites is close to a replacement cycle." It was built to answer "whose numbers does this count against." The service territory gets closer, since techs see the machines up close, but service data lags. A tech notes wear on a unit they're already servicing. They don't drive the yard next door that hasn't called in for parts in two years, and that yard is often the one closest to turning over its whole fleet at once.
Where the mismatch costs you a replacement window
The sites that go quiet on service calls aren't necessarily the sites with old iron. Sometimes it's the opposite: a yard running newer machines under warranty just doesn't generate service tickets yet. A sales planning manager working off call volume as a proxy for fleet age will chase the wrong accounts, the ones making noise, while the yards sitting on ten-year-old units with no complaints go unflagged until a competitor's rep drives past and notices first.
Neither territory map was designed to track fleet age by site. That's not a knock on how OEMs draw them. It's just not the job those boundaries do. What's needed is something that sits independent of the PMA grid and the service radius both: a site-by-site read on what machines are there and how fast that mix is turning over, updated on a cadence that doesn't depend on a rep's drive-by or a warranty claim showing up in the system.
That's the gap Fleet Turnover Monitor was built to close, watching customer sites on a quarterly pass and flagging which ones are closest to their next replacement window regardless of which territory map they fall into.
If your PMA and your service zone keep telling you two different stories about the same customers, it might be worth checking what the yards themselves are running.