How to Run an Effective Territory Review

A seller's guide to understanding an effective territory review, including what you should inspect in your accounts, workload, pipeline, quota, and customer relationships.

By George James, Co-Founder & CPO

Your territory shapes your accounts, workload, pipeline, customer relationships, quota, earnings, and opportunity to advance. Manage, do not redesign. Most territory activity should be maintenance, and knowing which is which saves you a quarter. This guide shows what you should check, what evidence to request, and which questions to bring to your manager. You can use them without becoming the territory designer yourself.

BoogieBoard treats an effective territory review as a governed change process connecting strategy, account evidence, decision rights, and controlled activation.

The central position is: Customers deserve a higher movement bar than prospects. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• Territory Management: the ongoing maintenance of an approved territory model without redesigning its core logic.
• Current State Analysis: a measured baseline of the live territory model, assignments, capacity, and exceptions.
• Territory Health Report: a complete-territory view of coverage, workload, opportunity, exceptions, and material risks.
• recarve: a redesign that changes territory boundaries, logic, or comparable books rather than making a routine assignment adjustment.
• manage vs redesign: the decision between maintaining an approved model and changing the model itself.

BoogieBoard's observed annual recarve ranges decline as organizations scale: roughly 2 to continuous change below 25 reps, 2 to 8 at 100-plus, 1 to 4 at 250-plus, and 0 to 2 major recarves above 1,000 reps. These are observed planning ranges, not a prescription to redesign on a fixed calendar. For an effective territory review, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for an effective territory review: Salesforce's territory-management guidance distinguishes ongoing maintenance from model design and recommends minimizing disruption while reviewing assignments and unassigned accounts throughout the year.

What Is An Effective Territory Review?

A territory review measures whether the approved model is operating as intended; it does not automatically reopen the territory logic or trigger a recarve. Separate market data, planning logic, and execution records. Source systems describe accounts, the planning layer evaluates complete scenarios, and Salesforce operates the approved model. When those responsibilities blur, an effective territory review creates conflicting truths, duplicate fields, and assignments that cannot be explained later. In an effective territory review, test the choice against Current State Analysis, then record any accepted exception in the decision log. You should be able to trace the result from your account roster to the published rule.

An effective territory review is an operating decision across data, territory structure, roles, assignments, and activation. Territory Management, Current State Analysis, and Territory Health Report must refer to durable records and published rules rather than a temporary person field. The result should tell the team which system owns each fact, how proposed changes are tested, and when an approved state becomes live. The an effective territory review review is complete only when Territory Health Report and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

Territory Management: The Decision Test

Frequent adjustment can improve a local metric but damages pipeline and customer continuity; customers therefore deserve a higher movement bar than prospects, with open commitments and relationship risk reviewed before any transfer. 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. The an effective territory review review is complete only when Territory Health Report and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

How to Put Effective Territory Review Into Practice

Review the Current State Analysis, unassigned accounts, vacancies, data corrections, customer obligations, exceptions, and Territory Health; classify each finding as maintenance, a temporary exception, or evidence that the model itself needs redesign. Use current and future states side by side. Classify feedback as a data correction, policy exception, or preference, and preserve who made the decision. For your territory, the practical test is whether another informed person can trace an active assignment back to the approved rule and scenario. Use one current-state baseline to keep every an effective territory review scenario comparable. Your manager should be able to explain the tradeoff without relying on a private spreadsheet.

How to Put Effective Territory Review Into Practice should produce one inspectable Salesforce decision before the process advances. Preserve the live state, validate identifiers and roles, model the proposed state, review account-level changes, record approval, and activate on a defined date. A late exception should not silently rewrite the rule or the baseline. For an effective territory review, name the approver, the permitted evidence, and the condition that would justify a departure from the rule. Check how the decision changes your workload, pipeline, customer continuity, and quota context.

Define Roles and Comparable Populations

A seller departure is normally a management event: place temporary coverage, preserve the territory, and fill the role. Persistent imbalance after normal changes or a new GTM motion is evidence for redesign. Define Roles and Comparable Populations should produce one inspectable Salesforce decision before the process advances. Preserve the live state, validate identifiers and roles, model the proposed state, review account-level changes, record approval, and activate on a defined date. A late exception should not silently rewrite the rule or the baseline. For an effective territory review, name the approver, the permitted evidence, and the condition that would justify a departure from the rule. Check how the decision changes your workload, pipeline, customer continuity, and quota context.

Use current and future states side by side. Classify feedback as a data correction, policy exception, or preference, and preserve who made the decision. For your territory, the practical test is whether another informed person can trace an active assignment back to the approved rule and scenario. Keep account-level results beside the an effective territory review summary so Current State Analysis remains inspectable after approval. You need an account-level correction path when the source data does not match what you know.

Validate Account and Identity Data

For Validate Account and Identity Data, produce a reviewable output before the next decision begins. Use Territory Management to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field. You should be able to see how the rule changes your accounts, role, workload, or customer responsibility.

Validate Account and Identity Data should produce one inspectable Salesforce decision before the process advances. Preserve the live state, validate identifiers and roles, model the proposed state, review account-level changes, record approval, and activate on a defined date. A late exception should not silently rewrite the rule or the baseline. Give the an effective territory review decision a source date, an owner, and a condition that would trigger revision. Ask what evidence would cause leadership to revisit your territory after activation.

Define Assignment Rules and Exceptions

For Define Assignment Rules and Exceptions, produce a reviewable output before the next decision begins. Use Current State Analysis to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field. You should be able to see how the rule changes your accounts, role, workload, or customer responsibility.

Use current and future states side by side. Classify feedback as a data correction, policy exception, or preference, and preserve who made the decision. For your territory, the practical test is whether another informed person can trace an active assignment back to the approved rule and scenario. Before activating an effective territory review, show managers the effect on Territory Health Report and every downstream rule that depends on it. Your review should focus on documented facts and rules, not a negotiation for preferred accounts.

See Territory Management in the Planning Workflow

The relevant product workflow is Sales Manager Territory Review. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.

A manager can review mapped coverage and territory measures before requesting or approving changes.

Preserve the Current State and Model the Future State

For Preserve the Current State and Model the Future State, produce a reviewable output before the next decision begins. Use recarve to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field. You should be able to see how the rule changes your accounts, role, workload, or customer responsibility.

Use current and future states side by side. Classify feedback as a data correction, policy exception, or preference, and preserve who made the decision. For your territory, the practical test is whether another informed person can trace an active assignment back to the approved rule and scenario. In an effective territory review, test the choice against Current State Analysis, then record any accepted exception in the decision log. You should be able to trace the result from your account roster to the published rule.

Compare Scenarios and Approve the Tradeoff

For Compare Scenarios and Approve the Tradeoff, produce a reviewable output before the next decision begins. Use manage vs redesign to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field. You should be able to see how the rule changes your accounts, role, workload, or customer responsibility.

Compare Scenarios and Approve the Tradeoff should produce one inspectable Salesforce decision before the process advances. Preserve the live state, validate identifiers and roles, model the proposed state, review account-level changes, record approval, and activate on a defined date. A late exception should not silently rewrite the rule or the baseline. The an effective territory review review is complete only when Territory Health Report and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

Operating and Governing the Model: An Effective Territory Review

Governance begins with decision rights and a source-of-truth map. Sales leadership owns strategy and quota choices; RevOps owns configuration, data quality, workflow, and activation. Managers contribute field evidence, while the named Approver resolves exceptions before the effective date. The an effective territory review review is complete only when Territory Health Report and the affected account roster tell the same story. If your territory is an outlier, ask whether the difference is intentional, temporary, or a data error.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	Territory Management and comparable roles	Named data owner
Measure the current state	Current State Analysis and Territory Health Report	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

What This Means for You

Use the definitions and account-level controls above to check your assignment. Bring account IDs and source evidence when your roster, role, workload, or customer responsibility conflicts with the published rule.

Questions to Ask Your Manager

1. Which Salesforce record, territory, and role determine the accounts or customers I cover?
2. What changed from the prior state, who approved it, and when does it become effective?
3. Which source data and assignment rule produced this result?
4. Is this routine territory management or a redesign of the model itself?
5. How does the decision affect my workload, pipeline, customer continuity, quota, and collaborating roles?
6. Where do I submit a data correction or policy challenge, and when will I receive an answer?

Frequently Asked Questions

How often should you review territories?

A territory review measures whether the approved model is operating as intended; it does not automatically reopen the territory logic or trigger a recarve. Frequent adjustment can improve a local metric but damages pipeline and customer continuity; customers therefore deserve a higher movement bar than prospects, with open commitments and relationship risk reviewed before any transfer. Use the published definitions and complete-territory result instead of relying on one universal benchmark. Ask your manager to show how that standard applies to your book.

When should you redesign instead of adjust?

Review the Current State Analysis, unassigned accounts, vacancies, data corrections, customer obligations, exceptions, and Territory Health; classify each finding as maintenance, a temporary exception, or evidence that the model itself needs redesign. A seller departure is normally a management event: place temporary coverage, preserve the territory, and fill the role. Persistent imbalance after normal changes or a new GTM motion is evidence for redesign. Publish the assumptions so another reviewer can reproduce the answer. You should be able to reproduce the answer from your roster and the stated inputs.

What data is required for an effective territory review?

For an effective territory review, assemble governed account data, current assignments, role capacity, and decision evidence for Territory Management, Current State Analysis, and Territory Health Report. Date the sources and publish the definitions so another reviewer can reproduce the result and separate a factual correction from a policy exception. Request the source date when the underlying account facts look stale.

How often should an effective territory review be reviewed?

Review an effective territory review on the formal planning cadence and whenever the inputs behind Territory Management, Current State Analysis, and Territory Health Report 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. Ask when your territory will next receive a formal review.

How should Salesforce and the planning layer divide responsibility?

For an effective territory review, keep the governed source data behind Territory Management, Current State Analysis, and Territory Health Report in its approved system, compare current and future states in the planning layer, and operate only approved assignments in Salesforce. Stable identifiers, field ownership, and a dated sync prevent competing records of truth. Check that your locked accounts remain in the final health calculation.

How should territory changes be tested before activation?

Changes to an effective territory review should be tested by freezing the live Salesforce state, validating the inputs behind Territory Management, Current State Analysis, and Territory Health Report, modeling the proposed future scenario, inspecting account-level differences and exceptions, and recording approval. Activate on a defined date and reconcile the deployed result to the approved scenario. You need a system when manual reconciliation makes the rule impossible to inspect.

In Summary

Manage, do not redesign. Most territory activity should be maintenance, and knowing which is which saves you a quarter. 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

• Salesforce Territory Tracking: Complete 2026 Guide
• Designing Books of Business: The Complete Guide
• How to Communicate a New Territory Plan Effectively

Schedule a Live Demo to model an effective territory review, compare scenarios, and make the account-level tradeoffs visible before activation.