A sales territory plan defines which accounts each seller should cover, why those accounts belong together, and whether the team has enough capacity to serve them. A useful plan makes ownership and exceptions clear before you divide a spreadsheet or announce a new quota.
Use this worksheet when a founder-led sales motion is becoming a team effort, account ownership is overlapping, or a new segment needs coverage. It is an operating plan across accounts, not the account plan for one customer or the close plan for one opportunity.
Choose a coverage rule before drawing a map
A territory does not have to be geographic. You might group accounts by location, company segment, industry, product, or a named-account assignment. The right rule depends on how your team actually reaches and serves buyers.
Salesforce distinguishes territory planning from territory management: planning establishes the territories; management handles their ongoing coverage. Its examples also distinguish mapped field-sales territories from non-geographic account groupings.
Start with one main rule and only the additional conditions needed to resolve real ambiguity. “Northeast manufacturing accounts with fewer than 500 employees” is testable. “Strategic accounts with strong potential” needs a definition before it can assign anything.
| Selling motion | Possible rule | Question to test |
|---|---|---|
| In-person coverage | A defined region plus an account segment. | Can the owner serve the required travel and meeting pattern? |
| Specialist sales | An industry, product, or technical use case. | Does the assignment use a real skill difference rather than a convenient label? |
| Named strategic accounts | An explicit account list with a named owner. | What happens when a parent company, subsidiary, or new division appears? |
| Small shared team | A simple routing rule with an escalation owner. | Can every seller explain how a new account receives an owner? |
Build an inventory you can reconcile
Use stable company identifiers, not names alone. A parent company and its regional subsidiary can look like two prospects while sharing a buying process. Conversely, separate business units may require distinct coverage even when their names look similar.
For each account, capture the segment, current relationship owner, relevant geography, active work, and the source date. Mark uncertain fields. Do not assign an account to a territory merely because enrichment produced a plausible industry or employee count.
Keep current customer commitments visible during reassignment. A clean new territory list should not strand an implementation promise, leave two people contacting the same buyer, or silently change a customer's point of contact.
Compare workload, not account counts alone
Illustrative example: a fictional two-seller team has 60 accounts. Forty need a light qualification pass; 20 have active, multi-person evaluation work. Dividing the list into 30 accounts each may look even while creating very different workloads.
The team uses temporary planning weights of one unit for a qualification account and three for an active evaluation account. These are invented workload assumptions for this example, not industry benchmarks or a revenue forecast.
| Assignment | Qualification accounts | Active evaluations | Illustrative workload units |
|---|---|---|---|
| Initial seller A allocation | 10 | 20 | 10 × 1 + 20 × 3 = 70 |
| Initial seller B allocation | 30 | 0 | 30 × 1 = 30 |
| Revised seller A allocation | 20 | 10 | 20 × 1 + 10 × 3 = 50 |
| Revised seller B allocation | 20 | 10 | 20 × 1 + 10 × 3 = 50 |
The revised split balances this simple model. It does not prove equal opportunity, achievable quotas, or equal effort in practice. Review account fit, seller expertise, time zones, travel, and existing relationships before accepting it. Observe actual work and revise the weights instead of treating the first calculation as a permanent score.
Copy the territory planning worksheet
| Planning field | Working entry | Review evidence |
|---|---|---|
| Objective and period | The coverage problem and planning horizon. | Why the current assignment needs a change. |
| Assignment rule | Primary condition, secondary condition, and exclusions. | Example accounts that pass, fail, and need a decision. |
| Account ownership | Stable account ID, current owner, proposed owner, and effective date. | Owner acceptance and unresolved parent/subsidiary questions. |
| Workload | Account mix, estimated effort, capacity assumptions, and dependencies. | Observed work or explicit assumptions, not unexplained scores. |
| Exceptions | Named accounts, conflicts, unassigned accounts, and temporary coverage. | A decision owner and review trigger for each exception. |
| Handover | Open commitments, source links, customer communication owner, and next action. | The receiving owner can explain what must happen next. |
| Readout | Coverage gaps, duplicate ownership, capacity concerns, and approved changes. | A before/after assignment register and an accountable reviewer. |
Test the rules before changing ownership
- Run the rule on a small sample. Include a new account, an existing customer, a subsidiary, an out-of-segment account, and one with missing information.
- Reconcile coverage. Count assigned, multiply assigned, and unassigned accounts. Explain every intentional exception.
- Review capacity and continuity. Ask whether each owner can serve the account mix and whether existing commitments survive the handover.
- Approve the change set. Keep proposed assignments separate from changes actually applied.
- Check the result. Confirm ownership and open actions after the update. Retain the old assignment version so mistakes can be investigated.
Do not judge a new territory by a few days of closed revenue. Coverage rules, opportunity quality, sales-cycle timing, and seller tenure can change the comparison. Start with observable assignment and follow-through checks before making causal claims.
Try this with Aurora AI, Claude, or Codex
Review this proposed sales territory plan using only the approved account data.
Explain the assignment rule in plain language.
List unassigned accounts, duplicate owners, and rule exceptions.
Keep observed workload separate from our estimated planning weights.
Flag existing commitments that need a handover owner.
Return a proposed change register and five test cases.
Do not infer missing account attributes or promise revenue outcomes.
Do not change CRM ownership or contact customers.Finta can keep relationship context and follow-through connected while your team reviews the plan. Keep the assignment logic and capacity model in your approved working document. This guide does not claim that Finta provides a territory-optimization engine or automatically rebalances seller quotas.
For the next layer of work, use the account planning workflow and sales forecasting methods guide. They answer different questions: which account work deserves attention, and what the available evidence says about a forecast.
Prepared by Finta Editorial Team. Sources checked October 28, 2026. The workload model is a fictional teaching example, not a measured customer result or recommended quota methodology.