Territory Planning
Territory Planning in Salesforce is the process of designing, modeling, and optimizing the sales territories that determine which reps cover which accounts, prospects, and geographic regions.
Definition
Territory Planning in Salesforce is the process of designing, modeling, and optimizing the sales territories that determine which reps cover which accounts, prospects, and geographic regions. Salesforce supports this through two product layers: Enterprise Territory Management (the platform feature that assigns Account ownership to Territory records, drives sharing rules, and routes new records) and Salesforce Maps Territory Planning (the advanced add-on for visualizing territories on a map, modeling balancing scenarios, and applying geographic and demographic data).
Mature Territory Planning combines both layers. Enterprise Territory Management defines the live operational territory structure that governs day-to-day Account ownership. Salesforce Maps adds the planning tools that let revenue operations teams model new territory structures, balance workload across reps, account for travel time and geography, and stage changes before activating them in production. Territory Planning happens annually for most orgs and quarterly for fast-growing or seasonal businesses; it is one of the most consequential annual activities for any Salesforce sales operation.
Territory Planning in Salesforce: process, tools, balancing, and cutover
Why Territory Planning matters more than it looks
Sales territory design is one of the highest-leverage decisions an operations team makes. A well-designed territory structure puts the right rep in front of the right account, balances workload so no rep is overloaded or under-utilized, accounts for travel time and geography for field-based sales, and reflects the business strategy (focus on a specific industry vertical, a specific customer size, a specific product line). A poorly-designed structure produces uneven rep performance, account-rep mismatch, and rep attrition. The platform tools (Enterprise Territory Management, Salesforce Maps) are the mechanical layer; the business decisions about who covers what, why, and when are the actual planning work. Treat the technical tools as support for the strategic decisions, not as replacements for them.
Enterprise Territory Management and the live territory data model
Enterprise Territory Management is the platform feature that makes territories operational. The Territory Model is the org-wide configuration; each Territory is a node in the model with an assignment rule (which Accounts belong) and a set of assigned users (which reps work it). Account ownership in a territory-managed org is governed by these rules: a new Account that matches a Territory rules gets the matching reps as Account team members; the primary Account Owner is set by the rule or by an explicit assignment. Sharing rules driven by Territory Hierarchy determine which records each rep can see. Territory Models support multiple coexisting versions for planning purposes; only one model is active at any time in production.
Salesforce Maps Territory Planning and the modeling layer
Salesforce Maps Territory Planning sits on top of Enterprise Territory Management and adds geographic visualization, what-if modeling, and balancing analytics. Operations teams pull Accounts onto a map, draw territory boundaries with polygons or radius selections, and see real-time metrics on workload balance per rep (total Account count, total expected revenue, total travel time, prospect coverage). The tool runs balancing algorithms that optimize for whatever metric the team weights highest. After modeling, the team exports the new territory structure into Enterprise Territory Management as a new Territory Model version and activates it on the agreed cutover date. Salesforce Maps Territory Planning is a separate add-on license, not included in standard Sales Cloud.
Balancing metrics and the optimization criteria
Good territory planning balances multiple metrics simultaneously. Account count per rep should be roughly equal so no rep is overloaded. Expected revenue (or pipeline value, or quota attainment potential) should be balanced so quota is achievable for every rep. Travel time matters for field reps; territories that span huge geographic areas penalize reps with long drives. Specialization matters too: an industry-specific rep should not have generalist Accounts in their territory if the strategy is vertical-focused. Most algorithms optimize a weighted combination of these metrics. Operations teams set the weights based on the business priorities for that planning cycle (revenue-focused, geography-focused, vertical-focused). The weights are debate-worthy and worth documenting explicitly.
Cutover, change management, and rep communication
Activating a new territory structure is one of the highest-impact changes an Operations team can make. Reps lose Accounts, gain Accounts, and may need to hand off in-flight Opportunities. Done badly, the cutover destroys momentum and damages morale. Done well, it produces the balanced workload the plan promised. Standard practice: communicate the new structure to reps a week or two in advance, schedule the cutover for a low-activity period (typically a weekend or the first week of a quarter), provide a clear handoff procedure for in-flight Opportunities, and run a dedicated support channel for the first month to handle questions. Track post-cutover metrics carefully; if a rep pipeline drops significantly after a territory change, investigate before the quarter ends.
Annual planning cadence and the operating rhythm
Most enterprise sales operations run a major Territory Planning exercise once a year, typically aligned with the fiscal year start. The cycle is: months before, gather data on rep performance and Account metrics; design and model new territories with the Operations team and sales leadership; review with the field for input; finalize the model; communicate to reps; cut over at the start of the new fiscal year. Mid-year adjustments happen for specific changes (a new product launch creating a new specialty role, a rep departure forcing reassignment, a major customer move) but the bulk happens annually. Smaller or faster-moving orgs run quarterly planning instead. Document the cadence and the responsible team in the operations runbook so the discipline persists across team turnover.
Running a Territory Planning cycle end to end
Running a Territory Planning cycle is a multi-week project. The four-phase routine covers: gather data and define the planning criteria, model territories in Salesforce Maps Territory Planning, review and refine with sales leadership, and cut over to the new Territory Model in Enterprise Territory Management. Each phase has its own owners and stakeholders; the Operations team runs the project, sales leadership owns the strategic decisions, and IT supports the cutover. Plan the cycle as a discrete project with weekly milestones, not as continuous work that competes with daily Operations tasks.
- Gather data and define the planning criteria
Pull current Account distribution, rep workload, expected revenue per rep, travel time per rep (for field sales), and quota attainment data for the prior period. Identify imbalances: reps with too many or too few Accounts, reps with disproportionately high or low pipeline, geographies with poor coverage. Define the criteria for the new plan: target Account count per rep, target revenue per rep, geographic boundaries, vertical specialization, max travel time. Document the criteria in a planning brief signed off by sales leadership. The criteria are the source of truth for the modeling work; without them, the modeling becomes endless and inconclusive.
- Model territories in Salesforce Maps Territory Planning
Open Salesforce Maps Territory Planning. Pull Accounts onto the map. Draw territory boundaries that match the planning criteria. Run the balancing algorithm with weights matching the criteria from step 1. Review the resulting allocation: which reps gain or lose Accounts, where the metrics balance, where they do not. Iterate the boundaries and the algorithm weights until the result meets the criteria. Save the model as a candidate. Generate a per-rep impact report showing each rep old and new Accounts. The model is candidate state; it does not affect live data until activated.
- Review and refine with sales leadership
Share the candidate model with sales leadership and (selectively) with field managers. Walk through the per-rep impact report and the balancing metrics. Capture feedback: specific Accounts that should not move, specific reps with extenuating circumstances, geographies that need special handling. Iterate the model based on feedback. Hold a final approval meeting where sales leadership signs off on the model in writing. The approval should be a documented artifact for the project history, not just a verbal agreement; signed approval prevents re-litigation after activation.
- Cut over to the new Territory Model
Pick a cutover date during a low-activity window (typically a weekend or the first week of a quarter). Communicate the change to reps at least a week in advance, including their specific new Account list and any handoff procedures for in-flight Opportunities. Export the candidate model from Salesforce Maps Territory Planning into Enterprise Territory Management as a new Territory Model version. On the cutover day, activate the new model; the platform reassigns Accounts based on the new rules. Monitor closely for the first week. Run daily standups to address rep questions. Track pipeline metrics post-cutover; intervene early if any rep performance drops significantly.
- Salesforce Maps Territory Planning is a separate license, not included in Sales Cloud. Confirm the license before planning a project that depends on the modeling features.
- Activating a new Territory Model reassigns Accounts immediately. Cut over during a low-activity window and communicate to reps in advance; surprise reassignments destroy momentum.
- In-flight Opportunities do not automatically reassign with their Accounts. Build a handoff procedure for Opportunities in active negotiation; track them explicitly through the cutover.
- Territory Planning is a strategic decision dressed in platform tools. The tools support the decisions; they do not make them. Spend at least as much time on the planning brief as on the modeling.
- Sales leadership approval should be written, not verbal. Verbal approvals get re-litigated after activation when reps complain. Get the model signed off in writing as a project artifact.
Trust & references
Straight from the source - Salesforce's reference material on Territory Planning.
- Enterprise Territory Management OverviewSalesforce Help
- Salesforce Maps Territory PlanningSalesforce Help
- Working with Territory ModelsSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Territory Planning?
Q2. What factors matter?
Q3. What tools support it?
Discussion
Loading discussion…