Territory alignment gives every account one recorded owner and every ambiguous case a written rule. Most organizations believe they have done it. A territory spreadsheet exists and the CRM has an owner field on every record.
The two documents stop agreeing during the roughly 60 days a territory has no owner after a rep resigns. Accounts get picked up informally in that window, the owner field is never corrected, and the first anyone in operations hears about it is a commission dispute after a close.
Where Sales Territory Overlap Starts
US sales turnover has been estimated as high as 27% a year, and replacing a B2B rep takes an average of 6.2 months from the open role to a fully productive contributor. Inside that window is a stretch of roughly 60 days when the territory has no owner at all. Accounts scatter to whoever is nearest or whoever asks first, the handoff happens in a thread, and nobody treats a thread as a record change.
Every realignment after that inherits the result. Reps work accounts belonging to somebody else, and the routing table is out of date before the quarter opens. The sequence contains no decision anyone could point at and reverse. The overlap survives inside stale records and vague handoff rules until two reps turn up on the same deal.
Why Your CRM Will Not Settle Account Ownership
Operations teams expect the CRM to enforce single ownership. No CRM does that part of sales territory management on its own. Salesforce’s enterprise territory model treats accounts and territories as a many-to-many relationship, so it will assign one account to several territories and report nothing unusual. The recurring request in the Salesforce community is for a validation rule limiting an account to one territory and a restriction limiting a territory to one user. Neither exists as a setting.
Write territory filters narrow enough that a record can only match one. Associate a single user with the lowest-level territory.
The ambiguity is defensible on the platform’s own terms because overlay and specialist teams need an account in more than one territory. For an operations manager the platform will not supply single ownership at all.
Assignment logic needs industry, revenue, employee count and location present and correct on every record, so most rules of engagement fail on the data first and on the policy only afterward. Duplicate accounts, inactive records and misaligned account hierarchies send leads to the wrong rep or bounce them back as unqualified. Auditing those four fields across the account table comes before any rule of engagement gets written.
What Territory Overlap Costs Before Anyone Notices
The revenue gains attributed to better territory design run at 2% to 7%. The work behind them costs a few weeks of operations time. The alternative accrues in the pipeline for months before anyone raises the subject, in three forms.
A deal loses value when one rep works it alone to protect the turf, without bringing in the person who can close it.
A customer fielding uncoordinated approaches from two people at the same vendor concludes the vendor cannot keep track of its own accounts.
Strong reps leave organizations where the politics take more effort than the selling, the most expensive of the three costs and the hardest to attribute to its cause.
Reps Hide Deals Instead of Reporting Them
Concealment is the rational response to contested ownership. It does more damage to the data than the dispute does to the team. Reps keep dormant or lost opportunities and move the dates out to stay past the normal ownership window. Editing an account name or an address field so a record appears to fall inside a rep’s territory is a second route. The third is attaching to a deal already in progress and claiming partial credit on it.
None of that appears in a pipeline report, since every one of those moves is a legal edit made by an authorized user. The pipeline stops matching reality at the exact moment somebody needs it to establish who owns what.
Why Credit Causes Longer Disputes Than Commission
Reps in a contested account will hand over the commission and go on fighting about who is recorded on the ranking report as closing the deal. For anyone designing a fix, that means a clean split formula settles the arithmetic and leaves the dispute running.
It also means the fix has to reach the reporting as well as the comp plan. One recorded owner per account with the contribution split attached to the same record gives the ranking report and the commission run a single source to read from.
Overlapping Territories on a Boundary Map
The current state has to be visible before anything gets redrawn. Export the account list from the CRM with the owner column intact, or connect the CRM directly (Salesforce, HubSpot, Zoho, Pipedrive and Keap all integrate). Then put the accounts on a map.
The Geographic Boundary Tool in Maptive runs the audit on that export. Choose a boundary set such as ZIP codes or counties. Under fill type, choose My Group / Territory Data and aim it at the owner column. Whichever owner holds the most markers inside a boundary supplies that boundary’s color. What comes back is ownership as the data records it, and it rarely matches the territory spreadsheet. The first version of this map is usually worse than anyone expects, because it renders every uncorrected owner field from every departure over the past two years at once.
On a live CRM export, two settings change what the boundaries show. Marker Count sets ownership aside and colors each boundary by how many records fall inside it. That is the workload view, and it explains why a physically small territory turns out to be the heaviest one on the map.
Under Boundary Settings, the Sync Data tab controls how records attach to boundaries. That control matters when the export cannot be trusted to place a marker in the right place. The default checks which boundary a marker physically falls into. The alternative matches on a text column instead. Use that one for files where the address data is incomplete and a state name is the only field worth trusting.
Clicking a boundary opens its metrics. Customize Metrics adds a readout from any spreadsheet column. A Group Count on the owner column answers the ownership question directly by listing every owner inside that boundary and not only the dominant one.
How to Redraw Territories to Remove Double Coverage
Redrawing takes the overlap off the map. Maptive splits that work by size. One contested block between two reps is a manual edit, while a map out of balance across every territory is an automated rebuild. Open Map Tools and click the Territories Tool to start either one.
Reassign a Contested Area Between Two Territories
The edit removes the overlap only once the territory is saved. Saving opens a popup with three choices once a territory has been edited by drawing or by selecting boundaries.
Add the drawn area to an existing territory. The overlapping area is retained in both.
Remove the drawn area from an existing territory, which strips out any part of that territory falling inside the outline you drew.
Reassign the drawn area, which adds it to the territory you choose and removes it from every other territory it overlapped.
The third one ends double coverage in a single action. Without it, fixing a contested block means redrawing both territories and hoping the second redraw does not reopen the gap the first one closed, while the reassign option moves the disputed ZIP codes once.
Rebalance Without Starting From Scratch
A reassignment that fixes overlap usually unbalances something else. Map Tools opens the Territories menu and Create Territories opens the Auto Territory Builder. It will not run without a boundary set, a territory count, and at least one balancing variable, taken either from your own spreadsheet columns or from census demographic data. Relative importance is set before the run when several variables are selected. A run takes between 1 and 15 minutes depending on data volume and area size.
Three options separate a rebalance from a rebuild. Respect Previous Territories starts from the territories you already have and adjusts them without replacing them. That matters immediately after a contested block has moved. Pointing Respect Sales Rep Locations at a separate map of rep locations sets the territory count to match the number of reps and places each rep as close to the center of their own territory as the balancing metrics allow. Optimize with Constraints sets a floor and a ceiling on a variable such as total sales. On one worked data set a $30M to $40M constraint produced 38 territories averaging roughly $35M each.
Once the run finishes, a graph below the map shows how the chosen metrics are distributed. The spread on that graph is what the choice between geographic versus account-based territories usually turns on. Converting boundaries into territories afterward replaces the boundary fill with territory polygons and disconnects them from the underlying data, so a later refresh cannot silently redraw a territory somebody already agreed to.
Rules of Engagement for Accounts That Cross Territories
The questions that produce most disputes are the ones a map cannot answer. Each of them needs a written rule before the quarter starts.
A customer headquartered in one territory with branch locations in another. Assign relationship ownership to the rep who owns the core contact and pay them on retention and expansion, then create a separate local role paid on new project acquisition inside each branch geography.
A national account touching every territory. Replace the percentage argument with a commission pool for the account, divided by role and contribution.
An inbound lead from someone who already belongs to an existing account. The lead follows the account. The rule has to say so explicitly, because the routing engine will otherwise treat it as new business.
A parent company where a subsidiary is already a customer. This is the case where the named-account rule and the geographic rule contradict each other, so the priority order between them has to be named in advance. Left unnamed, it becomes one of the territory disputes that outlive the deal they started over.
Hybrid structures, where account-based territories are layered over a geographic grid, produce the strongest coverage and the most overlap, because routing has to evaluate several attributes at once and rank the conflicts between them. A stated priority order naming which rule wins prevents the fight.
The rules of engagement that work on a sales floor are narrow and specific. Reps may not prospect into another rep’s territory without permission, any redesign has a defined transition period, a deal spanning two territories splits commission equally, and disputes go to a named manager and not to the two reps involved. Written split agreements signed before the work begins matter more than any of them. Agreeing the terms in advance takes one conversation. The same conversation after a close usually damages the working relationship between the two reps.
How to Roll Out Territory Alignment Without Losing Reps
A reassignment made mid-quarter has to compete with in-flight deals and commission expectations. That competition is most of what a realignment costs. The change goes in at a quarter boundary or during a natural slow period, and it rolls out gradually.
A realignment memo means one thing to the person opening it, namely that their pay is about to fall. The care exists for that reason. The question reps put to public forums is what recourse exists when an employer rewrites a territory and halves a commission. A realignment handled badly produces the challenges of rules of engagement that follow a team for years. Forum replies say there is little recourse.
That is the argument for making territory alignment visible while it happens. A map showing the current state, the proposed state and the metrics behind both gives a rep something specific to argue with, which a memo announcing an outcome does not.
The disagreement survives, but it moves forward into a meeting held before the quarter opens, where a rep can still argue with a boundary and the number behind it rather than with a decision already taken.
Frequently Asked Questions
It is the process of matching accounts, geographies and reps so that every account has exactly one owner and every rep has a workable book. Three artifacts come out of it. A map that shows the boundaries, an assignment rule set that routes new records, and a written policy covering the accounts the map cannot place.
Rep turnover is the most common cause. When a rep leaves, their accounts are reassigned informally during the vacancy and the CRM owner field is never corrected. Other causes include verbal territory splits that were never documented, named accounts layered on top of geographic territories with no stated priority order, and duplicate or inactive CRM records that make routing logic misfire.
Give every account a single owner in the CRM, make the territory boundaries visible on a shared map so both reps can see them, and write down the rules for the cases the map cannot settle. Reassigning the contested geography in a territory tool removes it from the other territory in the same action, so the double coverage does not survive the edit.
Rules of engagement are the written policy that says who owns an account, who supports an opportunity, how credit is shared, and when accounts can be reassigned. Typical enforced clauses cover prospecting into another rep’s territory, transition periods during a redesign, equal commission splits on cross-territory deals, and named-manager mediation for disputes.
There is no default answer, which is why it has to be written down. Most teams give relationship ownership to the rep who owns the core contact, pay that rep on retention and expansion, and create a separate local role paid on new project acquisition within each branch geography.
Geographic territories assign accounts by where they are located. Account-based territories assign named accounts to specific reps regardless of location. Most B2B organizations run a hybrid of the two. That combination gives the best coverage and generates the most ownership conflict, because a record can satisfy the geographic rule and the named-account rule at the same time unless a priority order says which one wins.
Most teams now run annual strategy with quarterly course correction, a cadence that replaced a three-to-four-year redraw. For a fix aimed at overlap, when inside the year matters more than the cadence. Put the change in at a quarter boundary or during a natural slow period and roll it out gradually, because a mid-quarter reassignment arrives on top of in-flight deals and commission expectations, which is when a redesign generates the most resistance.
Assume the rep hears the announcement as a pay cut and design the rollout to answer that. A visible map of the current and the proposed boundaries with the metrics behind both gives a rep something specific to dispute. A defined transition period protects in-flight deals. Any deal spanning the change needs a written split agreement.
In most organizations they scatter to whoever is nearest or whoever asks first, the reassignment stays informal, and the owner field is never updated. Replacing that rep takes around 6.2 months to full productivity. Most of the damage happens in the first 60 days of that gap, before a replacement is even in the interview process. It survives afterward as a set of records nobody corrected.
Equal splits on cross-territory deals are the most commonly published clause, but a commission pool for the account, divided by role and contribution, is more durable on national accounts. Whatever the formula, agree it in writing before the work starts, because credit disputes outlast commission disputes and are harder to settle after a close.
Yes. Enterprise territory management treats accounts and territories as a many-to-many relationship, so the platform permits an account in several territories without flagging it. Single ownership has to be designed in by writing territory filters narrow enough that a record matches exactly one, and by associating a single user with the lowest-level territory.
Map the account export and color the boundaries by the owner column. A geographic boundary map shades each ZIP code or county by whichever owner has the most records inside it, which shows ownership as the data records it. A Group Count metric on a boundary lists every owner inside it rather than only the dominant one, so a ZIP code returning two names is the block to look at first.
