An attainment distribution with two peaks and a valley between them, 20% of the team past 150% while nearly half finishing under 50%, is a territory design reporting itself. A team average conceals both tails. Fair sales territory planning distributes opportunity and workload so every rep can reasonably aim at quota, and handing everyone the same number of accounts does not produce that. Scoring the territories that already exist, on metrics computable from the file, comes before moving any of them.
How to Tell If Your Territories Are Unbalanced
What a Two-Hump Attainment Curve Means
A healthy attainment distribution has one peak near 100%, with 60% of reps at or above goal. The failure pattern has two peaks and a valley where that peak belongs. None of the causes a sales leader checks first will account for it. Coaching does not move a rep from 65% to 100% when the accounts that would close the difference are in somebody else’s territory, and neither does a performance plan.
A bimodal distribution overpays as well as underperforms. The high tail earns accelerators that the design handed it. Normalizing the distribution across more than 2,000 sellers at one organization cut sales compensation cost by 5%, or $9 million a year, with aggregate performance flat.
Why 55% of Territories Are the Wrong Size
At any given time, 55% of sales territories are too large or too small for the opportunity they contain. That base rate holds across well-run companies. Anyone opening their own numbers should expect a first audit to find something wrong, and the useful question is how much.
Misaligned territories cost 2% to 7% of total sales revenue. Redesign recovers roughly that range without a change to headcount, quota methodology or strategy, which makes it the cheapest revenue available to most sales organizations.
Six Metrics That Measure Territory Balance

These are working thresholds drawn from practice. No standards body publishes them. Each gives a banded reading that a territory either meets or does not, and together they are what it takes to balance sales territories with any consistency.
Potential Variance and Quota Attainment Variance
Because it measures the opportunity each territory contains, potential variance identifies a design problem before any rep touches the territory. Under 10% deviation from the team average is balanced. Between 10% and 15% is a watch zone where the outliers should be investigated individually. Above 15% is structural and triggers a rebalancing audit. For a team averaging $1M per territory the acceptable band is $900K to $1.1M. A $700K territory next to a $1.4M territory is a design failure, and coaching the $700K rep will not close it.
Hitting the team average on total potential does not make a territory workable. High-potential accounts are worth $200K to $500K of annual capacity, medium accounts $50K to $100K, and low accounts under $25K. A territory with one $500K account and nothing else is fragile at any total, since one renewal decision moves the entire number.
Leadership sees quota attainment variance before anything else, and the potential number predicts it. The coefficient of variation on a 12-month rolling attainment average, meaning the standard deviation divided by the mean, should stay under 15%. A team reading 105/98/103/99/102 is balanced. A team reading 140/65/135/72/138 has a spread no amount of individual coaching will close.
Workload Balance and Pipeline Concentration
Workload is the measure most organizations skip because account count looks like a serviceable proxy for it. Calculate required activity by tier, with high-potential accounts needing 4 quarterly touches, medium accounts 2 and low accounts 1, then sum the annual visits and divide by 12 for the monthly requirement. Workload variance is acceptable up to 15%. Between 15% and 25%, travel time starts explaining the difference. Past 25% a rebalance has to weight geography into the build.
Account count cannot see the driving. A rep running 30 meetings a month with 10 hours of travel and a rep running 15 meetings with 20 hours of travel have comparable account counts on the spreadsheet and incomparable working weeks. A team averaging 22 monthly meetings per territory should not have anyone below 19 or above 25.
A high-potential territory can still be a bad assignment on pipeline concentration alone. A territory is diversified while its top five accounts stay under 40% of pipeline. From 40% to 50% it justifies added accounts or a split, and past 50% it is a critical dependency. Once the top two accounts pass 50%, the territory depends on two renewal decisions.
Forecast Accuracy and the Gini Coefficient
The territories nobody can forecast are almost always the ones with too few accounts for the misses to average out. That is what makes forecast accuracy a measure of balance. Take the absolute difference between forecast and actual, divided by forecast, then read the result against these bands:
Under 5% is strong.
5% to 10% is acceptable.
10% to 20% is weak and generally a sign of imbalance or concentration.
Above 20% means the number is not a forecast.
Borrowed from income-inequality measurement, the Gini coefficient summarizes the whole distribution in one figure. Rank territories by potential from low to high, plot cumulative potential against cumulative territory share, and take twice the area between that curve and the diagonal. Below 0.20 is the balanced target. Between 0.20 and 0.35 is moderate imbalance where some reps are structurally disadvantaged. Above 0.45 means the design is working against performance. Most organizations that measure it are between 0.25 and 0.40.
Diagnose in order, starting with Gini. Above 0.35 it points first at potential variance for the root cause, then at attainment variance for the symptom, then at workload and concentration for the operational consequences.
How to Rebalance Territories by ZIP Code in Maptive
Score Your Existing Territories on the Balance Metrics
Potential variance and workload variance mean nothing until they exist per territory. Put your territories on the map, click one to open its pop-out, then click Customize Metrics. The drop-down that appears holds every column header in the file. Sum applied to the revenue column gives the potential figure. Group Count applied to the account column lists the individual values and produces the roster. Average, High Value and Low Value are the other options on a numeric column, and demographic metrics for the United States and Canada are available from the same panel.
Metrics set on one territory apply to every territory in that tool, so one configuration produces a comparable readout across the whole map. Sum of revenue plus a count of accounts is usually enough to compute potential variance and workload variance directly, without exporting anything.
The fill calculation is a separate choice from the metric. Percentage Ranges suits a map whose point is how extreme the top territory has become. Value Ranges is the better default everywhere else.
Weight the Balancing Variables
The Auto Territory Builder requires at least one balancing variable before it will produce anything, drawn either out of the uploaded spreadsheet or out of the census demographics available inside the tool. Every variable selected also takes an importance weight. Whoever selects more than one has to resolve the criterion argument at that panel, before the build runs.
Make total sales dominant with population secondary and the map comes out visibly unlike the one produced by weighting the two equally. The weighting argument gets settled at that panel whether or not anyone has it out loud, so set the weights explicitly and do not accept the default.
ZIP code territory maps give the finest usable grain for a build of this kind. Nearly 42,000 US ZIP codes means the unit of correction is small enough to close a variance gap without disturbing a whole county. The last few percentage points of variance still come out by hand, moving individual ZIP codes between adjacent territories once the automated run has done the bulk of the work.
Which Criterion Sales Territory Planning Should Favor
The weights an automated build asks for come from the criteria that compete in every rebalance:
Market and account potential.
Call workload, meaning account count and the activity each account requires.
Drive time and geographic feasibility.
Coverage obligations on strategic accounts, wherever they fall.
Criterion weights are inputs that each organization sets for itself. No sales territory alignment formula transfers between organizations intact. Field motions weight drive time heavily, since a territory nobody can physically cover is not a territory. For an inside-sales motion the binding constraint is calendar hours, which puts account count and required call cadence at the top of the weighting. Strategic enterprise motions put revenue potential and required visit frequency above both. A handful of accounts justify whatever travel they need.
Skipping this step produces the most common failure in the discipline, optimizing one number and paying for it in another. High potential without the hours to work it produces nothing, and equal account counts across unequal drive times hand two reps the same target and two different working weeks.
Weight disruption as a criterion of its own. Every account that changes hands resets a relationship and complicates incentive compensation, so measure the share of business changing hands alongside potential and workload.
Territory What-If Modeling With Constraints
With the weights fixed, the remaining question is how many territories they support. Territory what-if modeling in Maptive is done through Optimize with Constraints. Check the option, check the column to constrain, then set the band by typing values or dragging the slider. Constraints apply only to columns already selected as creation variables, so a missing column means going back a step.
The constraint resolves a headcount question disguised as a fairness question. Bounding total sales between a minimum and a maximum, then letting the tool report how many territories satisfy the band, answers directly how many reps the market supports at the balance level you say you want. Software in the sales performance management market is bought to produce that answer. The number of territories that satisfy the band moves with where the band is set. A fairness level therefore carries a headcount price. That price also bears on the prior question of whether a territory should be split rather than rebalanced, which the closing section takes up.
A distribution graph appears below the map once a run finishes, showing how each balancing metric came out across territories. Put that graph in front of the reps before the assignment list. A rep shown the assignment first argues about the assignment, and a rep shown the distribution first argues about the method.
Fair Transitions After a Rebalance
Notice, Joint Calls and the Supervised Handoff
Account retention through a territory change is a process variable more than a relationship variable. Well-executed transitions retain 94% to 96% of accounts against 78% to 82% for poorly managed ones, and organizations that skip the joint introduction call account for most of the 10 to 15 points between them.
The difference comes from five stages:
Advance notice of 3 to 4 weeks, delivered by the current rep and not through a corporate template.
Joint calls, since the departing rep’s explicit endorsement transfers a portion of their credibility.
A one-page narrative account brief, which does the context transfer the CRM record cannot.
A supervised handoff where the new rep leads and the original rep observes. This is the stage most organizations skip and the one that decides the outcome.
Structured follow-up, with a check-in in week 1, a progress review in week 3 and a relationship health assessment in week 6.
Timelines vary with deal size, and compressing them is the most common cause of churn after a change. Enterprise accounts above $500K in annual recurring revenue need 6 to 8 weeks and 2 to 3 joint calls each. For mid-market accounts between $100K and $500K, 4 to 6 weeks and 1 to 2 joint calls are enough. Accounts under $100K need 2 to 4 weeks, with a joint call for the top 20% and CRM notes for the remainder. Add 4 to 6 weeks if the receiving rep is also new to the company.
Quota and Commission at Cutover
Splitting a $2M quota into two $1M quotas is arithmetic. Build each new quota from trailing 12-month revenue, probability-weighted pipeline and a growth factor based on account potential. Reps spend the quarter in which the change takes effect building relationships. That quarter underperforms regardless of how well the change is executed. A reduced quota or objective-based compensation for that quarter is an allowance the plan should make in advance.
Commission needs a written rule in place at the announcement, and unresolved credit is one of the documented reasons why your reps are leaving. The common convention gives full commission to the originating rep on anything already at proposal stage, sets a defined cutover date for new pipeline, and treats a referral a rep earned inside their old territory as theirs wherever the account itself is located.
The transition guarantee does more work than any other measure here and gets cut the most often. If a rep’s income drops more than 10% in the first quarter after a rebalance, make them whole with a draw. Fair territories sometimes mean handing a tenured rep a patch with less embedded revenue, and that rep will object, with reason. A draw budgeted alongside the analysis is already approved when the announcement goes out, and one raised afterward becomes a second negotiation with finance.
Should You Split a Territory or Rebalance It?
This question comes before the transition work above. Notice periods, joint calls, the cutover commission rules and the transition guarantee apply to a split, a rebalance and a full redraw alike, and the numbers decide which of the three applies before any of them is executed.
Three Signals a Territory Has Outgrown One Rep
A decision to split sales territories adds headcount, so it needs to earn itself. Three signals justify one:
Account overload. More than 80 to 120 named accounts, with the threshold moving down as deal complexity and cycle length go up. Past that point reps triage instead of selling, and high-potential accounts receive the same attention as low-potential ones.
Travel crowding out selling. Travel consuming more than 30% of available selling hours.
Revenue concentration. More than 60% of territory revenue coming from under 20% of accounts.
Why a Rebalance Is the Default Answer
With none of those signals firing, the answer is redistribution of the coverage you already have. Moving 5 to 10 ZIP codes between adjacent territories preserves about 95% of account relationships while correcting the imbalance, and it can be done in an afternoon.
Delay is expensive on its own terms. One imbalanced territory in a five-person team costs roughly 1.7% of the team’s annual productive capacity for every month it persists, about 10% of capacity over six months. Waiting for the annual cycle turns a ZIP code adjustment into a redraw, which is the case for quarterly instead of annual reviews.
When a Full Redraw Is Unavoidable
Some situations do require a full redesign of the territories. A merger, a product launch that changes which accounts matter, a headcount change large enough to alter the territory count, or eleven months of accumulated drift will all defeat incremental fixes. The cost is known and should be budgeted in advance. A rep who loses an entire territory takes 9 to 15 months to recover productivity.
If a full redraw is unavoidable, lock the key accounts in place as explicit exceptions and let the optimization run around them, which keeps most of the relationship damage out of the result while leaving the rest of the map free to move.
Frequently Asked Questions
Equal shares of what is the question to answer first. Equal account counts are the easiest split to defend and the one that leaves the attainment spread untouched, because accounts differ in value and in the hours they consume. Divide on opportunity and on workload together, with the balance between the two set by the sales motion, and expect the last few points of variance to come out by hand.
Balance is measured on more than one axis, and a territory can pass on one axis while failing on another. Potential should deviate less than about 10% from the team average. The coefficient of variation on rolling quota attainment should stay under 15%, and workload variance under the same figure. No territory should depend on its top five accounts for more than 40% of pipeline. None of those are published standards, so a territory falling a little outside one of them is a question and not a verdict.
Sort the reps by attainment and look at the whole histogram. A single cluster near 100% is a working design. A split into a high group and a low group with a hollow between them is a design that has already decided who wins. The same conclusion arrives from the opportunity side when the Gini coefficient on territory potential comes back above 0.35.
The older guidance of every three to four years, with annual passes in fast-moving industries, has given way to an annual strategy pass with quarterly correction. Drift is the trigger rather than the calendar. A quarterly review moves a handful of ZIP codes between neighbors and takes an afternoon. Skip four of those in a row and the same repair becomes a redraw.
55% of them at any given time are too large or too small for the opportunity they contain. That figure has been stable across decades of territory-design research, which means a first audit turning up problems is the expected result and says nothing unusual about the company running it.
Two bills arrive and only one of them is revenue. On the revenue side the cost is 2% to 7% of total sales, recoverable by redesign at unchanged headcount and unchanged quota methodology. The compensation side is billed separately. A distribution with a heavy high tail pays accelerators the design itself created, and normalizing one large sales force cut compensation cost by around 5% with aggregate performance unchanged.
Rebalance, unless the territory has genuinely outgrown one person. Three readings say it has. The named-account count runs past 80 to 120, with the threshold dropping as deals get more complex. Travel eats more than 30% of available selling hours. More than 60% of revenue comes from under a fifth of the accounts. Absent those, redistributing coverage that already exists is cheaper and reversible, while a split puts another head on the payroll.
Potential, call workload, drive time and any coverage obligation attached to a strategic account, weighted against one another rather than ranked once for every company. An inside-sales team weights calendar hours highest. A field team weights the driving, and an enterprise team will accept a long trip for a single account. Add disruption to the list, since the share of business changing hands is a cost the other four criteria do not price.
Color the ZIP boundaries by whatever owner column the file already carries, so the design in force is visible before anything moves. Run the automated build on the variables that matter to your motion, with weights you set yourself. Close the last few percentage points by moving individual codes between neighboring territories, which is the part the automation leaves for a person.
Running a proposed design against the real file before anyone is told about it. The version that answers a business question constrains one variable, usually total sales, to a stated band, then reports how many territories can satisfy it. Move the band and the headcount answer moves with it, each setting carrying its own fairness level.
Publish the rule with the announcement and not after it. Convention gives the originating rep full commission on anything already at proposal stage, fixes a cutover date for new pipeline, and keeps a referral with the rep who earned it wherever the account ends up. Budget the transition guarantee at the same time. A draw covering an income drop of more than 10% in the first quarter is approved money when the news goes out, and a second negotiation with finance when it is not.
Three to four weeks where accounts are transferring and the outgoing rep has introductions to make, with two weeks the absolute minimum otherwise. A team meeting is the right vehicle, and it should cover the reasoning with the data behind it, each rep’s new boundaries shown on the map, the effective date, and the treatment of deals already in flight.




