Territory Disputes Are Never About the Map
Notes from three client engagements where the "territory conflict" everyone wanted arbitrated turned out to be an unresolved comp, credit, or hiring-freeze problem wearing a map's clothing.
Every time a manager calls me in to referee a territory fight, the request is the same: come and look at the map, tell us where the line should sit. I've done this as a paid engagement three times now, not just a Friday-afternoon favour, and the map has been innocent in all three. What was actually broken was a commission rule nobody had written down, an account list that hadn't been touched since the last reorg, and a quota still calibrated for a territory that no longer existed. Redraw the map on any of those and you've spent a fortnight negotiating boundary lines to paper over a rule that will produce the identical fight again by Q3.
Case one: the credit split nobody wrote down
A 90-rep enterprise software vendor brought me in because two of their best AEs had stopped speaking to each other over a single logo — a £400k strategic account both of them had touched. The VP framed it as "we need clearer named-account boundaries." What we found, three commission statements into the investigation, was that there was no written rule for co-sell credit on multi-threaded accounts. The manager who'd verbally agreed a 50/50 split with both reps two years earlier had since left. Her replacement had assumed the standard rule was "source of lead gets 100%, support gets a spiff," because that's what his last company did. Neither rep was lying. They were both operating on a real rule — just two different ones, held in two different heads, and never reconciled because nobody had thought to check.
The fix had nothing to do with territory. It was making the credit rule explicit, in writing, before the next co-sold deal — and retroactively settling the disputed one at 60/40 based on who'd actually built the technical win. If your org runs multi-threaded or overlay coverage on any accounts, Commission Statement Decoder is worth running the actual statements through before you assume the rule everyone's operating on is the same rule.
Case two: the account list that lied
A SaaS scale-up had moved from geographic territories to vertical segmentation eight months before I arrived. Sensible change, well-reasoned, properly announced in an all-hands. What didn't happen: nobody re-tagged the account master in the CRM. Half the book was still carrying its old geo-territory field. Two reps — one healthcare-vertical, one still nominally "Midwest" — discovered independently that they'd both been prospecting the same 40 accounts for four months. Both had pipeline logged against them. Both had legitimate touches. The dispute that reached me was framed as "whose patch is this," but the honest answer was that the patch itself was a stale record nobody owned.
This is the most common version of the three, in my experience, because segmentation changes are announced as strategy decisions and executed as one-time CRM projects, with no owner assigned to keep the tagging current as accounts get created, renamed, or re-classified afterwards. The map was fine on the day it was drawn. It just wasn't maintained.
Case three: the quota that survived the reorg
A mid-market fintech merged two regional teams into one after a leader departure. Headcount went from nine reps to seven, account count per surviving rep went up by roughly 30% — on paper a straightforward and defensible consolidation. Nobody rebalanced quota. One rep, who'd inherited a chunk of a departed colleague's book, was still carrying his original number from before the merger — a number set when his book was two-thirds the size it now was. He wasn't fighting for territory because he wanted more accounts. He was fighting because losing any account, even a dead one he'd never worked, felt like losing ground against a target that had quietly become 15% harder to hit without anyone saying so out loud.
That conversation needed to happen months earlier, and it needed to be a real quota conversation, not a territory conversation. A structured version of it — the kind that actually surfaces "has anything changed since this number was set" before defensiveness sets in — is what Quota-Setting 1:1 Conversation Script is built for.
Why the map gets blamed
| Rank | Underlying cause | Why it ranks here |
|---|---|---|
| 1 | Undocumented credit-split or overlay rule | Most common in my sample and the hardest to see, because both reps are being truthful about a rule that genuinely exists — just not the same rule for both of them |
| 2 | Stale account list after a segmentation or systems change | Second most common; the strategic decision gets communicated once and never operationally maintained, so the map drifts from the record silently |
| 3 | Quota untouched after a reorg or headcount change | Least common of the three but the slowest to surface, because reps rarely name "my quota feels wrong" directly — it comes out sideways, as territorial aggression |
Three checks before you touch the lines
- Pull the actual commission statements for both reps on the disputed account. If the split logic isn't written down anywhere both reps can point to, you have a rule problem, not a map problem.
- Check the last date the account list or segmentation was updated against the current CRM record. If there's a gap of more than a quarter between a structural change and the last full re-tag, assume the list is lying to at least one rep.
- Check whether either rep's quota has been touched since the last org change that affected their book. If the answer is no, you're not mediating a territory dispute. You're mediating a quota grievance wearing a territory costume.
If you run all three checks and the map genuinely is the problem — two reps with clean credit rules, a current account list, and fairly set quotas, still fighting over the same ground — then redraw it, and do it properly: announce the change with the reasoning attached, not just the new boundary, using something like Territory Realignment Announcement Script so it reads as a decision rather than a rumour. But check the other three first. In three for three, I never had to.