Territory Plans: Strategies That Drive Results

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

By Tyler Thompson, Co-Founder & CTO

Publish what a healthy territory is before anyone sees their assignment. Define it after and every disagreement becomes a negotiation. 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 territory-plan strategy 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: It is a definition problem, not a fairness problem. 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.
• Territory Health: the measured condition of a complete territory against its published goals.
• Account Locking Criteria: the published rules for assignments that should not move.
• Scenario: one complete current-state or proposed territory design.
• Territory Logic: the rules that determine where accounts and roles belong.

BoogieBoard's observed prospect books range from 1 to 15 accounts for strategic AEs to roughly 250 to 1,000 for SMB AEs. Those ranges are context, not quotas: role, segment definition, service model, and account quality determine whether a book is workable. For territory-plan strategy, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for territory-plan strategy: Research in Psychology & Marketing examined how adjustments for territory difficulty affect perceptions of performance-evaluation fairness and usefulness.

What Is Territory-Plan Strategy?

A territory plan translates growth strategy into roles, account populations, goals, constraints, scenarios, ownership, and operating rules. 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, territory-plan strategy becomes difficult to explain and impossible to audit consistently. In territory-plan strategy, test the choice against Territory Health, then record any accepted exception in the decision log.

Territory-plan strategy is a governed coverage decision, not a label applied after accounts have already moved. It connects Balance Goal, Territory Health, and Account Locking Criteria 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 territory-plan strategy review is complete only when Account Locking Criteria and the affected account roster tell the same story.

A Practical Decision Lens: Territory-Plan Strategy

If healthy is defined after rosters are shown, every metric becomes a negotiating tool rather than a design standard. 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. The territory-plan strategy review is complete only when Account Locking Criteria and the affected account roster tell the same story.

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. Use one current-state baseline to keep every territory-plan strategy scenario comparable.

Common Models and Variations: Territory-Plan Strategy

Every strategy privileges some objective. Publishing the priority makes the compromise governable and testable. 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 territory-plan strategy 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 territory-plan strategy, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Territory Health: 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 territory-plan strategy, 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 territory-plan strategy summary so Territory Health remains inspectable after approval.

Scenario: 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 territory-plan strategy decision a source date, an owner, and a condition that would trigger revision.

Territory Logic: 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 territory-plan strategy, show managers the effect on Account Locking Criteria and every downstream rule that depends on it.

Territory Health: The Decision Test: Review 8

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 territory-plan strategy, document the effect on Balance Goal before the model advances.

How to Put Territory-Plan Strategy Into Practice

Define healthy territory conditions before assignments, select a small set of primary goals, apply published locks, compare scenarios, and communicate the approved logic with the roster. 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. In territory-plan strategy, test the choice against Territory Health, then record any accepted exception in the decision log.

How to Put Territory-Plan Strategy 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 territory-plan strategy review is complete only when Account Locking Criteria and the affected account roster tell the same story.

Define Roles and Comparable Populations

A team prioritizes high-fit prospect count and customer workload, accepts wider total count, locks imminent renewals, and chooses the scenario with lower family fragmentation. 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. The territory-plan strategy review is complete only when Account Locking Criteria 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 territory-plan strategy scenario comparable.

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. Use one current-state baseline to keep every territory-plan strategy scenario comparable.

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. For territory-plan strategy, 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 13

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. Keep account-level results beside the territory-plan strategy summary so Territory Health remains inspectable after approval.

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 territory-plan strategy decision a source date, an owner, and a condition that would trigger revision.

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 territory-plan strategy, show managers the effect on Account Locking Criteria and every downstream rule that depends on it.

Inputs and Assumptions 2: Territory-Plan Strategy

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. In territory-plan strategy, test the choice against Territory Health, then record any accepted exception in the decision log.

Balance Goal: The Decision Test

The common failure is optimizing the easiest field rather than the business objective. Equal account count, a generic revenue band, or one summed score can look objective while concealing fit, workload, timing, hierarchy, and service obligations. Convenience is not a rationale. The territory-plan strategy review is complete only when Account Locking Criteria and the affected account roster tell the same story.

Balance Goal: The Decision Test: Review 19

Evaluate the operating burden as carefully as the feature list. Ask who maintains the data and logic, how managers review changes, what sellers receive, and how a correction reaches the live system. The system should make tradeoffs easier to inspect without pretending software can make the business judgment. Use one current-state baseline to keep every territory-plan strategy scenario comparable.

Balance Goal: The Decision Test: Review 20

Governance begins with explicit decision rights. One Driver runs the process, one Approver chooses the final tradeoff, Contributors supply evidence, and Informed stakeholders receive the result. Publish the review cadence, correction path, exception authority, and source of truth with the approved roster. For territory-plan strategy, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	Balance Goal and comparable roles	Named data owner
Measure the current state	Territory Health and Account Locking Criteria	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 should a territory plan include?

A territory plan translates growth strategy into roles, account populations, goals, constraints, scenarios, ownership, and operating rules. Every strategy privileges some objective. Publishing the priority makes the compromise governable and testable. Use the published definitions and complete-territory result instead of relying on one universal benchmark.

When should you define territory fairness?

Define healthy territory conditions before assignments, select a small set of primary goals, apply published locks, compare scenarios, and communicate the approved logic with the roster. A team prioritizes high-fit prospect count and customer workload, accepts wider total count, locks imminent renewals, and chooses the scenario with lower family fragmentation. Publish the assumptions so another reviewer can reproduce the answer.

What data is required for territory-plan strategy?

For territory-plan strategy, assemble governed account data, current assignments, role capacity, and decision evidence for Balance Goal, Territory Health, and Account Locking Criteria. 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 territory-plan strategy be reviewed?

Review territory-plan strategy on the formal planning cadence and whenever the inputs behind Balance Goal, Territory Health, and Account Locking Criteria 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 territory-plan strategy, define Balance Goals tied to Balance Goal, Territory Health, and Account Locking Criteria 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 territory-plan strategy, a spreadsheet remains adequate while one owner can preserve Balance Goal, Territory Health, and Account Locking Criteria, 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

Publish what a healthy territory is before anyone sees their assignment. Define it after and every disagreement becomes a negotiation. 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 territory-plan strategy, compare scenarios, and make the account-level tradeoffs visible before activation.