How should a revenue team test a territory list before quota planning?

A pre-planning test for coverage, overlap, ownership conflicts, and workload balance in a territory list.

How should a revenue team test a territory list before quota planning?

Question and scope

This protocol tests whether a territory list is usable before the team commits to quotas. It covers account coverage, geographic and segment overlap, ownership conflicts, and the resulting workload per seller. It excludes the quota number itself, which depends on conversion assumptions and capacity. The question matters because a territory list that looks clean in a spreadsheet can create disputes as soon as sellers start working it.

The unit of analysis is one seller's assigned territory in one planning cycle. The test can be run on a proposed list or on the current list before a change. It does not assume that equal account counts mean equal work. The protocol measures the conditions that make an assignment defensible.

Define the criteria for a usable territory list

Write the criteria before looking at the list, including coverage, overlap, ownership, location, and workload. Coverage means every target account has a seller. Overlap means no account is assigned to two sellers without a rule. Ownership means the assignment matches the system of record. Workload means the expected effort fits the seller's capacity.

Add the business rules that the team uses for exceptions, such as house accounts, partner-led accounts, and strategic accounts. Write each rule as a test rather than a principle. A rule that cannot be checked will not be enforced during planning. The criteria should be short enough to explain to a seller in one page.

Test coverage and overlap

Count the target accounts with a seller and the accounts with no seller. Then count the accounts assigned to more than one seller. Report the coverage rate and the overlap rate by segment and region. A high coverage rate can hide a large overlap in one important segment.

Map the overlaps by account value and by seller pair. A small overlap between two sellers in different regions may be easy to resolve, while a large overlap between a hunter and a farmer may require a rule. Record the proposed resolution for each pattern. The goal is a decision, not a list of conflicts.

Test firmographic accuracy

Check the fields that drive assignment, such as location, employee count, industry, and segment. Compare a sample against an external source and record the date of the check. A list can be internally consistent and still be wrong about the market. The test should show which fields are trustworthy enough for planning.

Look for accounts that changed size or industry since the last cycle. A company that crossed the mid-market threshold may belong in a different territory. Do not reclassify every edge case before planning. Flag the material changes and leave the rest for the monthly review.

Test ownership conflicts

Compare the assigned seller with the owner in the CRM and the owner in the planning file. List the accounts where the two disagree. A conflict that is invisible during planning becomes a credit dispute after the first deal. Record who resolves the conflict and by what date.

Check for accounts owned by someone who has left the company or moved to a different role. These records often sit in a former seller's name and receive no coverage. Assign a temporary owner and a review date. The temporary owner should confirm whether the account belongs in the territory at all.

Run a dry assignment

Give a sample of sellers their proposed list and ask them to work three fictional scenarios. A scenario might be a new inbound lead, an existing customer expansion, or a partner referral. Ask them to name the owner and the first action. The exercise reveals ambiguity that a static list does not show.

Record the questions the sellers ask during the dry run. A question that appears across several sellers points to a missing rule. A question that appears once may be a local exception. Update the rule set and repeat the exercise with a different sample. The dry run is cheap compared with a quarter of disputed assignments.

Compare two planning scenarios

Build two versions of the territory list, such as a current coverage model and a proposed rebalance. Compare them on coverage, overlap, workload, and the number of accounts that change owner. A rebalance that improves balance but moves a large share of accounts may create more disruption than value. Show the tradeoff explicitly.

Include the transition cost in the comparison, such as the time to brief sellers and update the CRM. A plan that looks better on paper may be worse in the first month. The decision owner should see both the steady-state result and the transition cost. The test is a decision aid, not a ranking.

Test the transition plan

A territory change requires a transition plan even when the final list is better. List the accounts that move, the seller who gains them, and the seller who loses them. Record the briefing date and the owner of each move. A plan without a transition creates a gap in the first month.

Check whether any moved account has an open opportunity or a scheduled meeting. Those accounts need a direct introduction rather than a reassignment in the CRM. The buyer should hear about the change from a person, not from a system notification. The transition test protects the relationship while the plan changes.

Check the seller's view of fairness

Ask a sample of sellers whether the proposed assignment feels fair and why. Perceived fairness is not the same as mathematical balance, but it affects whether the plan is accepted. Record the specific concerns rather than a general satisfaction score. A concern about a large account may point to a real rule gap.

Do not change the plan just because a seller objects. Use the objection to test the rule and the data. If the account is genuinely misclassified, fix it. If the objection is about workload, show the calculation. The conversation should make the decision more defensible.

Write the planning memo

Write a short memo that states the criteria, the counts, the exceptions, the dry-run findings, and the decision. Include the transition cost and the next review date. A reader should be able to see why the list was accepted without reopening every spreadsheet. The memo becomes the record for the next cycle.

Keep the supporting files linked from the memo rather than pasted into it. The memo should be short enough to read before the planning meeting. If a reader disagrees, the links give them a way to check the evidence. The decision is stronger when it can be examined.

Share the memo with the sellers who will work the territory before the plan is locked. Their questions can reveal a rule that the planning team assumed was obvious. Record the answers beside the exceptions. A territory plan is easier to accept when the reasoning is visible.

Keep the memo to two pages and put the decision at the top. A reader who disagrees should be able to find the relevant evidence from the memo without asking for a folder. Record the next test date beside the decision. The memo is the memory of the planning cycle.

Limits and sources of error

The test depends on the target account list, and a biased list will produce a biased territory. It also depends on firmographic data that may be incomplete. The dry run reflects the sellers who participated, not the whole team. Report those limits beside the result.

The cited public sources describe sales management work, market analysis, and business survey practice. They do not provide a formula for a fair territory. Treat the test as a structured way to surface conflicts and assumptions. The final assignment remains a management decision.

Set a pre-planning test date

Schedule the test at least two weeks before the planning lock. That leaves time to resolve ownership conflicts and rerun the dry assignment. Put the date in the planning calendar with the owner. A test that starts after the plan is drafted becomes a justification exercise.

Record the test result in a short memo with the criteria, the counts, the exceptions, and the decision. Keep the memo with the planning file so the next cycle can compare. A territory decision that cannot be explained later will be reopened by the first seller who disagrees. A reader should be able to see why each exception was accepted or rejected.

Sources

  1. Occupational Outlook Handbook: Sales managers, U.S. Bureau of Labor Statistics. Describes sales management work and the operational context for territory coverage.
  2. Market research and competitive analysis, U.S. Small Business Administration. Provides a structured approach to market and customer analysis.
  3. Business Trends and Outlook Survey, U.S. Census Bureau. Supplies business survey context for demand and segment assumptions.
  4. Cybersecurity Framework 2.0, National Institute of Standards and Technology. Offers a risk-management framing for planning controls.
  5. Protecting Personal Information: A Guide for Business, Federal Trade Commission. Covers responsible handling of customer information in planning files.

Related GTM research