Territory Policy Examples and Templates for 2026

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

By Kevin Davis, Co-Founder & CEO

A policy nobody can find is folklore. Publish it, date it, and name the owner or it will be reinvented every cycle. 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 policies and templates 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: Start with a good truth to tell; communication is downstream of design. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• Rules of Engagement: published rules for ownership, collaboration, credit, exceptions, and escalation across roles.
• Account Locking Criteria: the published rules for assignments that should not move.
• Holdover Policy: the published eligibility, evidence, approval, duration, and handoff rules for temporary continuity.
• escalation path: the named sequence and decision authority for resolving an unresolved territory question.
• policy owner: the person accountable for maintaining, reviewing, and communicating an operating rule.

BoogieBoard has observed 1,000-plus-rep planning cycles involving 8 to 20 Operations stakeholders and 80 to 120 Sales-leader stakeholders. The process is a governed change program, not a private analyst exercise. For territory policies and templates, use that observation only for the claim and population it directly supports.

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

A Practical Decision Lens: Territory Policies And Templates

Policy becomes folklore when it has no owner, date, location, leadership use, or revision history and is reinvented through messages during every planning cycle. 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 policies and templates, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

What Is Territory Policies And Templates?

Territory policy is the dated, owned, accessible set of rules governing account definitions, assignment, locking, holdovers, changes, disputes, exceptions, reviews, and activation. Territory policies and templates connects an approved territory decision with informed managers, prepared sellers, live systems, temporary rules, support paths, and an accountable operating state. Rules of Engagement, Account Locking Criteria, and Holdover Policy make the transition inspectable. The territory policies and templates review is complete only when Holdover Policy and the affected account roster tell the same story.

Core Components: Territory Policies And Templates

Publish each policy with purpose, scope, definitions, rule, evidence, decision owner, effective date, review cadence, exception path, examples, related policies, and change history. 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 territory policies and templates scenario comparable.

Policy field	What to publish	Control
Purpose and scope	Decision and population governed	Named owner
Definitions	Canonical terms and governed objects	Linked glossary
Rule and evidence	Eligibility, precedence, and proof required	Reproducible examples
Decision rights	Driver, approver, contributors, informed groups	No private substitutes
Dates	Effective date, expiration, review cadence	Change history
Exceptions	Reason, approver, duration, model impact	Visible register

The Coverage Objective

A compact policy library is easier to maintain, while one enormous document centralizes reference; use linked modules with one Rules of Engagement index so dependencies remain visible. The strategic question is what the company believes creates a healthy path to market. Translate that belief into measurable Balance Goals, then test it through scenarios. The model is a hypothesis: it should be specific enough to guide a decision and humble enough to be revised when evidence changes. For territory policies and templates, name the approver, the permitted evidence, and the condition that would justify a departure from the rule.

The Evidence Standard

For The Evidence Standard, make the implicit policy inspectable at account level. Use Rules of Engagement to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

The Population Test

For The Population Test, make the implicit policy inspectable at account level. Use Account Locking Criteria to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

The Account-Level Test

For The Account-Level Test, make the implicit policy inspectable at account level. Use Holdover Policy to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Seller Impact

For Seller Impact, connect the choice to seller, customer, and operating consequences. Use escalation path to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Decision Ownership

For Decision Ownership, assign decision rights, review cadence, and correction path. Use policy owner to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Calculating and Testing Territory Policies And Templates

A holdover policy should state eligible opportunity stages, evidence, approval, maximum duration, expiration behavior, reporting, and its distinction from an account lock. A seller loses ten accounts, retains two qualified opportunities temporarily, and receives eight replacement accounts. The communication should show the business reason, Rules of Engagement, Account Locking Criteria, Holdover Policy, effective dates, and the route for one disputed hierarchy. The territory policies and templates review is complete only when Holdover Policy and the affected account roster tell the same story.

Worked Example 2: A Decision You Can Reproduce

For Worked Example 2: A Decision You Can Reproduce, show the prior state, proposed state, reason, and effective date. Use Account Locking Criteria to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

See Collaboration and Audit Trails in the Planning Workflow

The relevant product workflow is Track Territory Collaboration and Audit Trails. BoogieBoard Scenario Planning keeps the account-level assumptions, tradeoffs, and proposed assignments visible while the team completes that work.

Activity History records territory actions by user and time so teams can review how the model changed.

Worked Example 3: A Decision You Can Reproduce

For Worked Example 3: A Decision You Can Reproduce, show the prior state, proposed state, reason, and effective date. Use Holdover Policy to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Worked Example 4: A Decision You Can Reproduce

For Worked Example 4: A Decision You Can Reproduce, show the prior state, proposed state, reason, and effective date. Use escalation path to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Worked Example 5: A Decision You Can Reproduce

For Worked Example 5: A Decision You Can Reproduce, show the prior state, proposed state, reason, and effective date. Use Rules of Engagement to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Worked Example 6: A Decision You Can Reproduce

For Worked Example 6: A Decision You Can Reproduce, show the prior state, proposed state, reason, and effective date. Use Account Locking Criteria to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Activation and Change Control: Territory Policies And Templates

After go-live, track questions by class, correction time, approved exceptions, expired transitions, unassigned accounts, and unresolved customer commitments. Close the launch only when the operating state matches the promise. In territory policies and templates, test the choice against Account Locking Criteria, then record any accepted exception in the decision log.

Worked Application 7: Territory Policies And Templates

Compare a poor launch with a governed one: surprise roster and offline CRM versus manager preview, account-level report, dated policies, live assignments, office hours, and a reconciled correction queue. Use one current-state baseline to keep every territory policies and templates scenario comparable.

The Workload Test

For The Workload Test, make the implicit policy inspectable at account level. Use Rules of Engagement to test whether the prior state, rationale, communication, effective date, and operating result agree; keep the account-level evidence visible.

Decision Worksheet

Decision	Evidence to inspect	Control
Explain the change	Rules of Engagement and business rationale	Approved narrative
Show the impact	Account Locking Criteria and Holdover Policy	Manager and seller reports
Prepare go-live	CRM, policies, temporary rules, and support paths	Effective date and named owners
Close the transition	Corrections, exceptions, expirations, and unresolved commitments	Reconciliation checkpoint

Decision Narrative

State the business change, the problem the model solves, the tradeoff leadership accepted, and the facts that would cause a later revision. For territory policies and templates, use Rules of Engagement to record the evidence, decision owner, affected account population, and condition that closes this review.

Prior-State Preservation

Freeze the current account and role state with a source date so every recipient can see what changed rather than receiving only the final roster. For territory policies and templates, use Account Locking Criteria to record the evidence, decision owner, affected account population, and condition that closes this review.

Manager Preview

Prepare managers before the field announcement with the method, account-level impact, scripts, likely questions, and limits of their discretion. For territory policies and templates, use Holdover Policy to record the evidence, decision owner, affected account population, and condition that closes this review.

Seller Impact Report

Show each seller retained, lost, gained, locked, and temporarily held accounts with effective dates and the reason behind material changes. For territory policies and templates, use escalation path to record the evidence, decision owner, affected account population, and condition that closes this review.

Customer Impact Review

Identify customer obligations and relationships affected by the plan, then assign communication and handoff owners before go-live. For territory policies and templates, use policy owner to record the evidence, decision owner, affected account population, and condition that closes this review.

Policy Readiness

Publish the definitions, rules, eligibility, evidence, approvers, dates, examples, and exception paths that recipients need to interpret the change. For territory policies and templates, use Rules of Engagement to record the evidence, decision owner, affected account population, and condition that closes this review.

Data Correction Path

Route factual account and hierarchy errors to a correction workflow that preserves evidence and returns the updated record to the approved model. For territory policies and templates, use Account Locking Criteria to record the evidence, decision owner, affected account population, and condition that closes this review.

Policy Question Path

Answer questions about how the published rule applies without allowing private messages to become undocumented policy changes. For territory policies and templates, use Holdover Policy to record the evidence, decision owner, affected account population, and condition that closes this review.

Exception Governance

Require a reason, approver, effective period, visible model impact, and expiration or review condition for every departure from the standard rule. For territory policies and templates, use escalation path to record the evidence, decision owner, affected account population, and condition that closes this review.

CRM Go-Live Check

Confirm the approved territories, roles, accounts, temporary arrangements, and effective dates are ready in CRM when the communication says they are. For territory policies and templates, use policy owner to record the evidence, decision owner, affected account population, and condition that closes this review.

Manager-Seller Consistency

Compare leadership, manager, seller, and system versions of the decision; resolve contradictions before they become field politics. For territory policies and templates, use Rules of Engagement to record the evidence, decision owner, affected account population, and condition that closes this review.

Support Capacity

Estimate question and correction volume, assign owners and response targets, and give managers a visible status path during the launch. For territory policies and templates, use Account Locking Criteria to record the evidence, decision owner, affected account population, and condition that closes this review.

Temporary Rule Register

List holdovers, interim coverage, vacancies, and other transition states with owners, dates, handoff behavior, and extension authority. For territory policies and templates, use Holdover Policy to record the evidence, decision owner, affected account population, and condition that closes this review.

Effective-Date Control

Use one approved effective date across communication, policy, CRM, quota, coverage, and reporting unless a documented transition requires otherwise. For territory policies and templates, use escalation path to record the evidence, decision owner, affected account population, and condition that closes this review.

Frequently Asked Questions

What policies does territory planning need?

Territory policy is the dated, owned, accessible set of rules governing account definitions, assignment, locking, holdovers, changes, disputes, exceptions, reviews, and activation. A compact policy library is easier to maintain, while one enormous document centralizes reference; use linked modules with one Rules of Engagement index so dependencies remain visible. Use the published definitions and complete-territory result instead of relying on one universal benchmark.

Where should territory policy live?

Publish each policy with purpose, scope, definitions, rule, evidence, decision owner, effective date, review cadence, exception path, examples, related policies, and change history. A holdover policy should state eligible opportunity stages, evidence, approval, maximum duration, expiration behavior, reporting, and its distinction from an account lock. Publish the assumptions so another reviewer can reproduce the answer.

What evidence is required for territory policies and templates?

For territory policies and templates, assemble governed account data, current assignments, role capacity, and decision evidence for Rules of Engagement, Account Locking Criteria, and Holdover Policy. 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 policies and templates be reviewed?

Review territory policies and templates on the formal planning cadence and whenever the inputs behind Rules of Engagement, Account Locking Criteria, and Holdover Policy 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 data corrections and policy exceptions be separated?

Disputes about territory policies and templates should send incorrect account facts through the data-correction path and challenges to the published rule through policy governance. Any exception needs a reason, approver, effective period, and visible effect on the complete approved model.

What must be ready before a territory change goes live?

A change involving territory policies and templates can go live only after the manager briefing, account-level report, published policy, CRM assignment, temporary coverage, support path, and effective date agree. Reconcile the live result after activation so the announcement and operating record cannot drift apart.

In Summary

A policy nobody can find is folklore. Publish it, date it, and name the owner or it will be reinvented every cycle. 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

• How to Communicate a New Territory Plan Effectively
• Balance Goals: The Complete Guide to Territory Equity
• Salesforce Territory Tracking: Complete 2026 Guide

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