Sales Force Territory Plan: The Complete Playbook

A practical guide for operators responsible for the sales-force territory plan, with the decisions, evidence, controls, examples, and operating rules needed to make it work.

By Kevin Davis, Co-Founder & CEO

Seven steps, in dependency order. Skip step four and every downstream decision becomes an argument. That position is useful only when the planning team can translate it into inputs, decisions, controls, and a result the field can understand.

BoogieBoard treats the sales-force territory plan as part of a governed change process. The model must connect market strategy with account-level evidence, productive capacity, explicit decision rights, and controlled activation. The objective is not to remove judgment. It is to make judgment visible and repeatable.

The central position is: Lock before you model. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• Balance Goal: a measurable objective for healthy opportunity, quality, workload, or continuity.
• Account Locking Criteria: the published rules for assignments that should not move.
• Territory Logic: the rules that determine where accounts and roles belong.
• Scenario: one complete current-state or proposed territory design.
• Current State Analysis: a defined input used when evaluating the sales-force territory plan.

The framework reflects BoogieBoard's consulting work and interviews with more than 300 companies. It is practitioner evidence used to form hypotheses, not a controlled causal study. For the sales-force territory plan, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for the sales-force territory plan: Research on commercial territory design treated multiple balance requirements, compactness, contiguity, and feasibility as simultaneous planning criteria.

What Is The Sales-Force Territory Plan?

A sales-force territory plan is the approved design and operating system for markets, roles, accounts, capacity, ownership, quota context, and change. The useful distinction is between data, policy, and judgment. Data describes the accounts and roles. Policy states the repeatable rule. Judgment chooses among legitimate tradeoffs. When those layers are blended in a spreadsheet formula or a private manager request, the sales-force territory plan becomes difficult to explain and impossible to audit consistently. In the sales-force territory plan, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

The sales-force territory plan is a governed coverage decision, not a label applied after accounts have already moved. It connects Balance Goal, Account Locking Criteria, and Territory Logic to a defined role and market. The output should tell stakeholders what is being decided, which evidence is allowed, who approves exceptions, and how the result will be operated after launch. The the sales-force territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Core Components: The Sales-Force Territory Plan

Run seven dependency-ordered stages: stakeholders, structure, data, goals and locks, current-state assets, scenario design, and activation. A complete model needs a population, a measurable objective, a source of truth, an owner, an acceptable range, and an effective date. Balance Goal describes one part of the decision; Account Locking Criteria and Territory Logic keep it connected to capacity and execution. Missing any one of these components pushes the unresolved choice downstream, where it usually appears as an account-level exception. The the sales-force territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Document inputs and outputs separately. Inputs include account attributes, hierarchy, current assignments, opportunities, customer obligations, capacity, and quota. Outputs include the territory roster, summary health measures, account-level changes, exception records, and activation instructions. That separation lets reviewers challenge an assumption without rebuilding the entire design. Use one current-state baseline to keep every the sales-force territory plan scenario comparable.

Common Models and Variations: The Sales-Force Territory Plan

Speed comes from resolving dependencies upstream, not skipping them. A fast ungoverned carve creates longer correction work after launch. No model removes judgment. Geographic, named-account, segment, industry, customer, and hybrid structures each solve a different constraint. Use the fewest logical layers that express the strategy, then state where a deliberate override is allowed. Complexity should correspond to a real customer or operating need, not inherited convention. Use one current-state baseline to keep every the sales-force territory plan scenario comparable.

The model in this subsection is useful only when its organizing rule matches the selling motion. Compare options by opportunity, workload, continuity, explainability, and maintenance burden. A structure that looks simple at launch can create expensive exceptions when accounts change segment, sellers leave, or related companies need coordinated coverage. For the sales-force territory plan, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Balance Goal: The Decision Test

Modeling assignments before goals and lock criteria makes every stakeholder request a new scenario. Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. For the sales-force territory plan, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Account Locking Criteria: The Decision Test

A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Keep account-level results beside the the sales-force territory plan summary so Account Locking Criteria remains inspectable after approval.

Territory Logic: The Decision Test

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. Give the the sales-force territory plan decision a source date, an owner, and a condition that would trigger revision.

Scenario: The Decision Test

A practical test is to pick one surprising account and trace it end to end. Explain why it is in the segment, why it belongs in the territory, whether it is locked, which goals it affects, and what happens when the seller changes. If the answer requires several private spreadsheets, the model is not yet governed. Before activating the sales-force territory plan, show managers the effect on Territory Logic and every downstream rule that depends on it.

Current State Analysis: The Decision Test

Use this module to make the hidden decision explicit. State the role, population, evidence, rule, exception path, and operating consequence. The objective is not a perfectly clean model; it is a model whose compromises are visible enough to approve, communicate, and improve. For the sales-force territory plan, document the effect on Balance Goal before the model advances.

How to Put Sales-Force Territory Plan Into Practice

A team documents current logic, validates hierarchy, defines three Balance Goals, applies opportunity locks, compares two scenarios, and activates one with seller handoffs. How to Put Sales-Force Territory Plan Into Practice means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. The the sales-force territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. Use one current-state baseline to keep every the sales-force territory plan scenario comparable.

Define Roles and Comparable Populations

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. Use one current-state baseline to keep every the sales-force territory plan scenario comparable.

Define Roles and Comparable Populations means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. For the sales-force territory plan, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

See Balance in the Planning Workflow

The relevant product workflow is Even Out Quotas and Workload. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.

Scenario Results show customer and prospect mix, prospect grade, quarterly ARR, account locks, and rep capacity in one review surface.

Account Locking Criteria: The Decision Test: Review 12

The model in this subsection is useful only when its organizing rule matches the selling motion. Compare options by opportunity, workload, continuity, explainability, and maintenance burden. A structure that looks simple at launch can create expensive exceptions when accounts change segment, sellers leave, or related companies need coordinated coverage. For the sales-force territory plan, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Validate Account and Capacity Data

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. Keep account-level results beside the the sales-force territory plan summary so Account Locking Criteria remains inspectable after approval.

Validate Account and Capacity Data means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. Give the the sales-force territory plan decision a source date, an owner, and a condition that would trigger revision.

Set Balance Goals and Acceptable Variance

Set Balance Goals and Acceptable Variance means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. Give the the sales-force territory plan decision a source date, an owner, and a condition that would trigger revision.

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. Before activating the sales-force territory plan, show managers the effect on Territory Logic and every downstream rule that depends on it.

Define Locks and Model the Movable Book

The control at this stage is a decision log. Separate factual corrections from policy exceptions, preserve rejected alternatives, and attach an effective date. For the planning team, the practical test is whether another informed person could reproduce the result from the same data and rules without relying on private context. Before activating the sales-force territory plan, show managers the effect on Territory Logic and every downstream rule that depends on it.

Compare Scenarios and Approve the Tradeoff

Compare Scenarios and Approve the Tradeoff means producing one inspectable decision before advancing. Name the input, owner, output, and approval. Keep the current state as a baseline, and record assumptions that could change the result. This dependency order prevents a late preference from rewriting earlier definitions without anyone seeing the cost. For the sales-force territory plan, document the effect on Balance Goal before the model advances.

Operating and Governing the Model: The Sales-Force Territory Plan

After activation, monitor assignment gaps, source-data changes, capacity events, and Territory Health. Use defined triggers and review windows instead of constant reshuffling. A territory model should absorb ordinary hiring, departure, and account changes without becoming a new annual reconstruction project. In the sales-force territory plan, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

Balance Goal: The Decision Test: Review 18

Technology should preserve the model, not only the final owner field. Test version control, current-to-future comparison, account-level inspection, locks, scenario assumptions, approvals, effective dates, CRM deployment, and audit history. A faster spreadsheet export is not the same as a governed planning system. The the sales-force territory plan review is complete only when Territory Logic and the affected account roster tell the same story.

Calculating and Testing Sales-Force Territory Plan

Create three scenarios. Scenario A minimizes movement, Scenario B minimizes variance on the primary goal, and Scenario C protects continuity while improving the two largest outliers. Compare complete territories after qualifying locks return. Select the scenario whose residual imbalance leadership is prepared to explain and operate. Use one current-state baseline to keep every the sales-force territory plan scenario comparable.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	Balance Goal and comparable roles	Named data owner
Measure the current state	Account Locking Criteria and Territory Logic	Source date and baseline
Choose the tradeoff	Scenario comparison and complete Territory Health	Recorded approver
Activate the result	Account roster, changes, quota, and transition rules	Effective date and correction path

Frequently Asked Questions

What are the steps in territory planning?

A sales-force territory plan is the approved design and operating system for markets, roles, accounts, capacity, ownership, quota context, and change. Speed comes from resolving dependencies upstream, not skipping them. A fast ungoverned carve creates longer correction work after launch. Use the published definitions and complete-territory result instead of relying on one universal benchmark.

What comes first, locking or balancing?

Run seven dependency-ordered stages: stakeholders, structure, data, goals and locks, current-state assets, scenario design, and activation. A team documents current logic, validates hierarchy, defines three Balance Goals, applies opportunity locks, compares two scenarios, and activates one with seller handoffs. Publish the assumptions so another reviewer can reproduce the answer.

What data is required for the sales-force territory plan?

For the sales-force territory plan, assemble governed account data, current assignments, role capacity, and decision evidence for Balance Goal, Account Locking Criteria, and Territory Logic. Date the sources and publish the definitions so another reviewer can reproduce the result and separate a factual correction from a policy exception.

How often should the sales-force territory plan be reviewed?

Review the sales-force territory plan on the formal planning cadence and whenever the inputs behind Balance Goal, Account Locking Criteria, and Territory Logic change materially. Keep customer and pipeline ownership stable between reviews; reopen the model when strategy or new evidence changes the decision, not merely because a manager prefers a different assignment.

How should Balance Goals and account locks work together?

For the sales-force territory plan, define Balance Goals tied to Balance Goal, Account Locking Criteria, and Territory Logic before applying locks. Then publish Account Locking Criteria, lock only qualifying accounts, optimize the movable book, and score the complete territory so locked burden and residual imbalance remain visible.

When should a spreadsheet be replaced with a planning system?

For the sales-force territory plan, a spreadsheet remains adequate while one owner can preserve Balance Goal, Account Locking Criteria, and Territory Logic, plus versions, account detail, approvals, and deployment without manual reconciliation obscuring the rule. Move to a planning system when scenario volume, collaboration, or audit work overwhelms the decision itself.

In Summary

Seven steps, in dependency order. Skip step four and every downstream decision becomes an argument. Use the sequence above to keep the decision governed, evidence-based, and inspectable at both the account and territory levels.

See Territory Planning in Practice

Related Content

• Balance Goals: The Complete Guide to Territory Equity
• Designing Books of Business: The Complete Guide
• How to Communicate a New Territory Plan Effectively

Schedule a Live Demo to model the sales-force territory plan, compare scenarios, and make the account-level tradeoffs visible before activation.