Recarve vs Adjust: A Practical Guide

A practical guide for operators responsible for the decision to recarve or adjust territories, with the decisions, evidence, controls, examples, and operating rules needed to make it work.

By Tyler Thompson, Co-Founder & CTO

Manage when a rep leaves. Redesign when the model is wrong. Knowing the difference saves you a quarter. 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 decision to recarve or adjust territories 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: Territory fatalism is a choice; 'it is what it is' is wrong. The sections below turn that position into definitions, alternatives, procedures, examples, controls, and an operating decision.

Working Definitions

• 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.
• Territory Management: the ongoing maintenance of an approved territory model without redesigning its core logic.
• disruption: the share and consequence of account, role, or relationship movement caused by a proposed change.
• Scenario: one complete current-state or proposed territory design.

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 the decision to recarve or adjust territories, use that observation only for the claim and population it directly supports.

Independent evidence provides a separate check for the decision to recarve or adjust territories: Research on territory realignment found that managerial actions during implementation influence seller motivation and performance.

A Practical Decision Lens: The Decision To Recarve Or Adjust Territories

The decision fails when leaders call every account move a recarve or label every structural problem maintenance, because the organization either churns constantly or accepts avoidable imbalance as fate. 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 the decision to recarve or adjust territories, test the choice against manage vs redesign, then record any accepted exception in the decision log.

How the Alternatives Differ: The Decision To Recarve Or Adjust Territories

Adjustment protects continuity and speed but can preserve structural problems; redesign can correct the model but imposes disruption, communication, quota, customer, and activation costs. Compare alternatives against the same population and definitions. One option may improve recarve, another may protect manage vs redesign, and a third may reduce disruption. Do not let each option use a different denominator or source date; that turns scenario review into a presentation contest. The the decision to recarve or adjust territories review is complete only when Territory Management and the affected account roster tell the same story.

Why the Decision Matters: The Decision To Recarve Or Adjust Territories

The business consequence is clearest when a company cannot separate execution from starting conditions. If opportunity and workload are invisible, attainment becomes an ambiguous signal. A measured territory does not explain every result, but it gives leadership a defensible denominator for capacity, quota, and performance conversations. Use one current-state baseline to keep every the decision to recarve or adjust territories scenario comparable.

manage vs redesign: The Decision Test

For manage vs redesign: The Decision Test, connect the choice to seller, customer, and operating consequences. Use Scenario to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field.

Territory Management: The Decision Test

For Territory Management: The Decision Test, connect the choice to seller, customer, and operating consequences. 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.

disruption: The Decision Test

For disruption: The Decision Test, connect the choice to seller, customer, and operating consequences. 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.

Scenario: The Decision Test

For Scenario: The Decision Test, connect the choice to seller, customer, and operating consequences. 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.

Common Failure Modes: The Decision To Recarve Or Adjust Territories

The common failure is representing a durable coverage relationship with temporary person fields. That makes vacancies, overlays, hierarchy, effective dates, and prior states hard to see. recarve, manage vs redesign, and Territory Management need an explicit model and audit trail, not naming conventions that only one administrator understands. For the decision to recarve or adjust territories, document the effect on recarve before the model advances.

manage vs redesign: The Decision Test: Review 9

For manage vs redesign: The Decision Test: Review 9, identify the hidden assumption and the control that exposes it. Use Scenario to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field.

recarve: The Decision Test 2

For recarve: The Decision Test 2, connect the choice to seller, customer, and operating consequences. 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.

Territory Management: The Decision Test: Review 11

For Territory Management: The Decision Test: Review 11, identify the hidden assumption and the control that exposes it. 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.

disruption: The Decision Test: Review 12

For disruption: The Decision Test: Review 12, identify the hidden assumption and the control that exposes it. 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.

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.

How to Put Decision To Recarve Or Adjust Territories Into Practice

Classify the trigger before opening a scenario: departures, hires, corrected data, and routine account events are usually managed; a GTM shift, merger, persistent imbalance, changed segmentation, or broken capacity model can justify redesign. How to Put Decision To Recarve Or Adjust Territories 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. Give the the decision to recarve or adjust territories decision a source date, an owner, and a condition that would trigger revision.

Operating and Governing the Model: The Decision To Recarve Or Adjust Territories

After activation, monitor unassigned records, stale identifiers, role vacancies, rule exceptions, and differences between the approved scenario and Salesforce. Use defined maintenance triggers for ordinary change and reserve a recarve for evidence that the model itself is wrong. Before activating the decision to recarve or adjust territories, show managers the effect on Territory Management and every downstream rule that depends on it.

Define Roles and Comparable Populations

For Define Roles and Comparable Populations, 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.

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.

Define Assignment Rules and Exceptions

For Define Assignment Rules and Exceptions, produce a reviewable output before the next decision begins. Use disruption to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field.

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 Scenario to test whether the live state, future scenario, and approved Salesforce result remain consistent; record exceptions instead of hiding them in a person field.

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.

Practical Implications

An adjustment maintains an approved territory model through ordinary change, while a recarve redesigns the model's logic, boundaries, or comparable books.

Decision Worksheet

Decision	Evidence to inspect	Control
Define the population	recarve and comparable roles	Named data owner
Measure the current state	manage vs redesign and Territory Management	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

Source of Truth and Identity Controls

Create a field-level source map for the decision to recarve or adjust territories. Name the authoritative system for account identity, hierarchy, segment, owner, territory, role, opportunity, and customer obligation. Reconcile records with a stable external ID, flag unmatched accounts, and prevent a local spreadsheet or custom person field from quietly becoming another golden record. Use recarve as the account-level test for this control.

Current-to-Future Scenario Test

Preserve the live Salesforce configuration as a dated Current State Scenario before evaluating the decision to recarve or adjust territories. Build the proposed model separately, compare every changed account and role, and keep rejected alternatives available. Reviewers should see both the summary tradeoff and the exact records behind it. For manage vs redesign, record the assumption that would cause the future state to change.

Approval and Exception Review

Classify feedback on the decision to recarve or adjust territories as a data correction, policy exception, or preference. Corrections update governed evidence; exceptions require a reason, owner, and expiry or review condition; preferences remain visible without silently changing the model. Name one Approver and use Territory Management to show which evidence that person considered.

Salesforce Activation Checklist

Turn the approved the decision to recarve or adjust territories scenario into a deployment package containing territory and role changes, account identifiers, effective dates, exceptions, and rollback instructions. Sync only approved records, capture failures, and compare the activated Salesforce state with the package. Close the change only when disruption and the affected account roster reconcile.

Frequently Asked Questions

When should you recarve territories?

An adjustment maintains an approved territory model through ordinary change, while a recarve redesigns the model's logic, boundaries, or comparable books. Adjustment protects continuity and speed but can preserve structural problems; redesign can correct the model but imposes disruption, communication, quota, customer, and activation costs. Use the published definitions and complete-territory result instead of relying on one universal benchmark.

Can you fix imbalance without a full redesign?

Classify the trigger before opening a scenario: departures, hires, corrected data, and routine account events are usually managed; a GTM shift, merger, persistent imbalance, changed segmentation, or broken capacity model can justify redesign. One rep leaving should trigger temporary coverage and replacement inside the existing territory. The same region missing its viable market and capacity goals across several reviews can justify a recarve. Publish the assumptions so another reviewer can reproduce the answer.

What data is required for the decision to recarve or adjust territories?

For the decision to recarve or adjust territories, assemble governed account data, current assignments, role capacity, and decision evidence for recarve, manage vs redesign, and Territory Management. 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 decision to recarve or adjust territories be reviewed?

Review the decision to recarve or adjust territories on the formal planning cadence and whenever the inputs behind recarve, manage vs redesign, and Territory Management 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 Salesforce and the planning layer divide responsibility?

For the decision to recarve or adjust territories, keep the governed source data behind recarve, manage vs redesign, and Territory Management 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.

How should territory changes be tested before activation?

Changes to the decision to recarve or adjust territories should be tested by freezing the live Salesforce state, validating the inputs behind recarve, manage vs redesign, and Territory Management, 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.

In Summary

Manage when a rep leaves. Redesign when the model is wrong. Knowing the difference 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 the decision to recarve or adjust territories, compare scenarios, and make the account-level tradeoffs visible before activation.