How sales operations teams rebalance territories each quarter
Accounts open, close and move every month, so last year's patches drift out of balance. A quarterly routine to redraw territories fairly and show who changed.
Part of the guide Workflow automation
A sales operations team keeps territories fair by redrawing them on a fixed rhythm, usually each quarter, from the accounts and prospects that exist now rather than the ones that existed when the patches were first drawn. Pull the current account list, add the new prospects found since last quarter, drop the ones that closed, let Split by territory share them into compact patches of about the same size, and compare the result with last quarter's owners before anyone is told. Only the changes need a conversation.
This is written for sales operations, revenue operations and regional sales managers who own territory design for field or inside teams of three to twenty reps. It covers why patches drift, what a quarterly rebalance should and should not change, a made-up rebalance in Jakarta, the mistakes that make reps distrust the map, and an AI employee that prepares the draft each quarter.
Why territories drift out of balance
A territory that was fair in January is rarely fair in October. Nobody redrew it; the market moved underneath it.
- New openings cluster. A new business district or a mall fills one patch with prospects while the next one stays flat.
- Closures thin a patch. A rep whose accounts closed over the summer has fewer doors to knock on, through no fault of their own.
- Wins change the work. A rep with many live customers spends time on service and has less room for new business.
- Headcount changes. A rep leaves or joins and the old patches no longer add up.
Waiting for complaints means rebalancing under pressure, mid-quarter, with targets already set. A fixed quarterly rhythm turns it into a routine everyone expects.
What a rebalance should change, and what it should not
The goal is fairness, not a fresh map. A good rebalance moves as few accounts as possible to fix the imbalance, and leaves relationships alone where it can. Three rules help:
- Decide what fair means for your team: the same number of accounts, the same number of new prospects, or a mix. Split by territory shares out the items it gets, so feed it the items you want balanced.
- Keep named accounts out of the shuffle. Strategic customers with a long relationship stay with their rep; remove them from the items before the split and add them back after.
- Compare before you publish. Match the new owners against last quarter's and list only the accounts that moved, so managers review twenty changes, not five hundred rows.
How the split works
The block takes every item that reaches it, each with a position, and shares them between a number of reps or between people you name. It aims for compact patches of about the same size, with no rep holding more than their share: with 300 accounts and four reps, nobody gets more than 75. Each item comes out with an owner and a territory named by direction, such as North-west or Centre. Items without a position go to the rep with the fewest and are marked so you can fix their address.
Because the owner is a field on every account, the blocks after it can use it: a Route planner set to one route for each rep plans each rep's visits inside their own patch, and Make a report can write a page per territory.
A worked example (made up)
Say a payments company sells card terminals to restaurants, pharmacies and shops in Jakarta with five field reps. At the start of each quarter, sales operations exports the account list to a table, and the flow adds every target business the places database lists across the city that is not already an account. It drops accounts the database now marks as closed, keeps twelve named key accounts aside, and splits the rest into five territories.
The draft that arrives says, in invented figures: "Five territories of 118 to 121 businesses each. 34 accounts change owner, most of them in the south, where two new malls opened. North-east loses 11 accounts to Centre." The regional manager reads the 34 moves, keeps four with their old rep because of open deals, and publishes the rest. None of these numbers come from a real company.
Mistakes that make reps distrust the map
- Redrawing too often. Monthly changes break relationships and make targets meaningless. Quarterly, or twice a year, is enough for most teams.
- Balancing the wrong thing. Equal counts of accounts can hide unequal work if one patch is all large customers. Balance the items that reflect effort.
- Moving accounts mid-deal. Check open opportunities before you publish and hold those accounts back for a quarter.
- Publishing without the list of changes. A new map with no explanation looks arbitrary. A short list of who moved and why looks fair.
- Forgetting closed businesses. Patches full of accounts that no longer trade look busy on paper and empty in the car.
Doing it with an AI employee
One AI employee can prepare the quarterly draft without touching your CRM. Its blocks, in order:
- Schedule: a custom timetable for the first working day of January, April, July and October.
- My data: this quarter's account export.
- Filter: leave out accounts your export marks as closed or lost.
- Split by territory: five reps, or the reps you name.
- Match with my table: last quarter's owners, so each account carries its previous owner.
- Calculated field: a yes or no field that says whether the owner changed.
- xMap LLM: one note for the whole list that sums up each territory and the moves.
- Approval: the regional manager approves before anything is shared.
- Email or a Google Sheets app block: the approved territories to the team.
What lands in the inbox is a draft, not a decision: a short summary per territory, the list of accounts that change owner, and a map. Once approved, the full table goes to the shared sheet. The template Split my city into fair sales territories is a ready start; Fair franchise territories for a city does the same for franchise areas. For the first split, see splitting a city fairly between sales reps.
Questions
How often should territories be rebalanced?
Quarterly suits most field teams: often enough to follow the market, rarely enough to keep relationships. Teams with long sales cycles often redraw twice a year.
Will the patches change completely each time?
No. They are built from where the accounts are, so they move only as far as the accounts moved. Comparing with last quarter's owners shows exactly which accounts changed hands.
Can I keep certain accounts with their rep?
Yes. Leave named accounts out of the items before the split and add them back afterwards, so they never move.
Does it update my CRM?
Not by itself. It sends a draft for approval. Once approved, the table can go to a sheet or your own database for your CRM team to import.