# Territory Realignment Announcement Script > Word-for-word talk tracks: for reps losing accounts, reps gaining accounts, the group announcement, and the follow-up email, for delivering territory changes without triggering a walkout. Free script/swipe for sales managers. Topic: [Comp, Quota, Territory & Capacity Planning](https://www.peerlab.ai/library/topic/comp-quota-territory-capacity-planning/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/territory-realignment-announcement-script/ ## How to use it Always run every affected rep's 1:1 script before the group announcement script goes out; adapt the bracketed reasoning to your actual fairness-review results so the rationale is specific, not generic. ## What's inside - Sequencing rule: every affected rep gets a 1:1 before the group announcement - Full 1:1 script for a rep losing accounts - Objection handling: "you're taking my best account" - Objection handling: "this feels arbitrary / like you're punishing me" - Full 1:1 script for a rep gaining accounts - Group announcement script - Follow-up email template with fill-in fields A word-for-word talk track for 1:1 delivery, a group announcement script, and a follow-up email, sequenced correctly so no rep learns about their own territory change in a group setting. **Sequencing rule: every affected rep gets their 1:1 before the group announcement goes out.** No exceptions, this is the single biggest driver of trust or walkout risk. --- ## 1:1 Script: Rep Losing Accounts > "I want to walk you through a territory change before it's announced to the team, because it affects you directly. > > We ran a full territory-fairness review because [reason: growth, new hire onboarding, TAM imbalance across the team, whitespace we found that wasn't covered]. As part of that, [Account names / number of accounts] are moving from your list to [new owner/team]. > > Here's the reasoning: [give the actual, specific reason, e.g., 'these accounts sit outside the geographic cluster we're building for you,' or 'this rebalances TAM across the team within 20% of parity: right now you're carrying 40% more addressable revenue than the team average, which isn't sustainable long-term for you either']. > > I know this doesn't feel good in the moment, especially with accounts you've invested in. Two things I want to be direct about: > 1. This is not a reflection of your performance: [name a specific, genuine acknowledgment, e.g., 'you built real relationships in that patch, and that work is exactly why the accounts are in good shape to hand off']. > 2. Here's what you're gaining in exchange: [new accounts, adjusted quota, adjusted comp guarantee/true-up if applicable, be specific]. > > What questions do you have?" **If the objection is "you're taking my best account":** > "I hear that, [Account Name] is a strong account and I understand why it's the one that stings most. Here's the specific data behind why it moved: [TAM parity number / geographic cluster reason / whatever the actual criterion was]. I'm not going to pretend this doesn't cost you something in the near term, so let's talk about what's on your new list that has real near-term potential." → transition to reviewing 2–3 specific high-priority accounts from their new patch. **If the objection is "this feels arbitrary / like you're punishing me":** > "That's fair to raise directly, and I want to answer it directly: this was scored against six specific fairness criteria before any names were attached to the map, [name the criteria]. I can walk you through the actual scorecard if that would help you see the reasoning, not just the outcome." --- ## 1:1 Script, Rep Gaining Accounts > "I want to give you a heads-up before the team announcement: your territory is expanding. You're gaining [Account names / number of accounts] from [prior owner/team]. > > A few things worth knowing before you dive in: [handoff notes: relationship status, open pipeline value, any sensitivities like a recent escalation or a champion who just left]. > > Your quota is adjusting to reflect this, [new quota number and effective date]. I want to be upfront that a chunk of this is new territory for you, so we'll build in [ramp adjustment / 60-day runway] before holding you fully accountable to the new number. > > What do you need from me to get up to speed on these accounts fast?" --- ## Group Announcement Script (after all 1:1s are complete) > "I want to walk the team through a territory update. [State the reason plainly: e.g., 'We ran a full whitespace and fairness review this quarter and found real imbalance in territory size across the team, plus coverage gaps in [region/segment].'] > > Here's what's changing at a high level: [summarize: number of accounts moving, which patches are affected, timeline]. > > I've already spoken 1:1 with everyone directly affected, so if this is the first you're hearing your own territory is changing, come find me right after this: that shouldn't be the case, and I want to fix that immediately. > > The new territory map is effective [date]. [Handoff logistics: CRM reassignment date, transition call requirements, who owns what during the handoff window]. > > I'm glad to take questions now, and I'm available 1:1 for anything you'd rather raise privately." --- ## Follow-Up Email Template **Subject: Territory Update: Effective [Date]** > Hi [Team/Name], > > Following our conversation on [date], here's the written summary of your territory change effective **[date]**: > > **Accounts added:** [list or count] > **Accounts removed:** [list or count] > **New quota:** $[amount], effective [date] > **Ramp/transition adjustment:** [details, if any] > **Handoff logistics:** [CRM reassignment date, overlap period, warm-handoff call requirement] > > Reasoning recap: [1–2 sentence version of the reason given in the 1:1] > > Please reach out directly with any questions, I'd rather you raise it with me than sit with it. > > [Manager Name]