The territory map you are working from was probably drawn at the last planning cycle. It still records who owned what on that day. When field activity is logged late, inconsistently, or not at all, leaders end up managing from information that is incomplete or out of date. The territory map is one of the first places the problem shows.
The map starts drifting from the field the day after a redraw. Four inputs keep changing while the map stays put: new accounts, departing reps, shifting account priorities, and visits that never get logged back to the map.
Why territory maps go stale
Between one redraw and the next, the field does not stand still. Accounts get created, reps leave, priorities move, and reps visit customers every working day. Each of those changes is made somewhere other than the map: in a CRM record, an order history, a rep’s notebook. None of them reaches the map unless someone carries it there by hand.
New accounts land outside the plan
New accounts come in from several directions. Inside sales opens one, ops imports a list, a rep adds a prospect they met on the road. The record exists in the CRM, but it can arrive without a tier, without an owner, or with an address too incomplete to plot.
An account like that sits on no one’s route. It is whitespace your team already found and then left unworked, because the map never put it in front of the rep whose territory it sits in.
The fix is a rule at creation. Every new account gets an owner and a tier the day it is entered, and it shows up on the map that same day.
Rep turnover leaves accounts without a history
When a rep leaves, their accounts can be reassigned on the map. What the rep knew is harder to move: the contacts, the last conversation, the open opportunities. The knowledge tends to live in a notebook or a personal spreadsheet, and it leaves with the rep.
The Royal Brass & Hose customer story describes a team in that position. Before the industrial distributor changed its approach, “Account information existed in notebooks, spreadsheets, Post-it notes, or nowhere at all.” Joe Anderson, VP of Sales at Royal Brass & Hose, oversees 29 representatives, and before the change each of them held their own customer data, none of it shared.
The new rep inherits accounts that look covered on the map and starts each relationship from zero. Map My Customers’ Field Sales Playbook makes the point in Play #5, Build a Stronger Sales Organization: when territories change or reps leave, customer history and open opportunities should stay intact, so the next rep is not starting from scratch. In practice, that means keeping the history on the account record. Then a reassignment moves it along with the account.
Account priorities shift after the tiers are set
Tiers get set at planning, from revenue and potential as they stood that week. Over the following months, one account’s orders climb, another’s fall off, a renewal date comes into view, a key contact changes jobs. The map still paints the first account Tier 3 and the second Tier 1.
Reps plan their days from those colors, so cadence follows the old tier. The account that grew gets the quarterly visit it outgrew months ago, and the one that faded keeps its weekly stop.
With account segmentation in Map My Customers, you can build segments from CRM fields such as revenue or renewal date and give each segment a visit cadence: weekly for Tier 1, monthly for Tier 2, quarterly for Tier 3, for example. Cadence rules then alert reps when an account is overdue, so a missed visit shows up before the next planning cycle instead of at it.
Visit data never makes it back to the map
Visit data is the hardest of the four to see, because the map was never built to hold it. A territory map shows assignment. It does not show coverage. On the map, an account visited last Tuesday looks identical to one nobody has seen since spring: same color, same owner, same pin.
When visits are logged late or not at all, the difference stays invisible until it turns up somewhere else, such as a drop in revenue from an account everyone assumed was being worked.
For the map to know about a visit, the visit has to land on it when it happens. A location check-in does that with one tap at the account. GPS verifies the position, the visit is timestamped and linked to the account record, and managers see it in real time.
A more careful redraw still starts the drift over
A more careful or more frequent redraw produces a clean map. It captures accounts, owners and tiers as they stand on the day it is finished.
What a redraw does not change is how updates reach the map. New accounts still arrive without an owner, departing reps still take their notes with them, tiers still sit where planning left them, and visits still go unlogged. All four inputs start drifting again the next morning.
None of this means boundaries never need to change. A redraw is the right tool for a structural problem: a new region, a new hire, or a territory that cannot be covered. The guide to balancing territories against rep capacity covers that job. Whether you need one is a question of structure and capacity, separate from whether the map is current.
How to feed the map from field activity
A map stays current when it is drawn from the same system where reps check in, log visits and take over accounts. Each of those actions then updates the map, with no separate step. Map My Customers is that kind of system of execution: the place where reps plan, visit and log their work. The map is drawn from the same records.
In Map My Customers, a rep checks in at an account, and that account’s last-visit date updates. The territory heatmap can be layered by last-visit date, activity frequency, revenue or tier, so accounts nobody has visited recently show up as cold zones. From a cold zone, a manager can see which accounts need a visit, build a route straight from the heatmap, or reassign accounts to a nearby rep. Cadence rules flag the Tier 1 accounts that have fallen behind.
Logged activity then syncs to the connected CRM automatically, with native two-way sync for Salesforce, HubSpot, Microsoft Dynamics and Zoho. The CRM stays the system of record and keeps the data. Map My Customers is where reps turn that data into today’s visits. When a rep leaves or a territory changes, the history stays on the account.
Royal Brass & Hose now runs with zero spreadsheets in the sales workflow, and new reps start with territories, customers and pipeline stages ready on day one. Anderson says: “We run all our funnel audits right through Map My Customers. It’s live data and that has saved us so much time.”
To see a map fed by check-ins on your own accounts, book a demo and bring the map you are working from now.
How to test your own map for staleness
You can measure the drift on your own map before the next planning cycle. Pull three counts:
- Accounts created since the last redraw that still have no owner or no tier.
- Accounts inherited from reps who have left, with no notes, contacts or visit history.
- Tier 1 accounts whose last visit falls outside their cadence.
The first count shows how far assignment has drifted, the second how much history was lost in reassignments, and the third whether coverage is keeping up. If you cannot produce the third number at all, visits are not being logged against the accounts on your map, and visit data is the input to fix first. Once you have the counts, the guide to territory management metrics covers what to track from there.
Fix how the map gets updated, then decide on a redraw
Feeding the map from field activity puts new accounts, reassignments and visits on it as they happen. Nobody waits for the next planning cycle. Planning itself stays with a leader: boundaries, rep capacity and structural redraws are decisions no feed makes for you. Fix the feed first, because a redraw built on accounts, owners, tiers and visits that still reach the map by hand will drift again. Once the feed is in place, judge any redraw on structure and capacity, not on staleness.
Start this week with three counts. How many new accounts have no owner or tier? How many accounts inherited from departed reps have no history? How many Tier 1 accounts are past their visit cadence? If the visit count is the one you cannot produce, start there. Visits are the one input a map cannot show until check-ins feed it.
FAQs
What are the most common challenges in sales territory mapping?
They come down to four inputs that change after the map is drawn. New accounts arrive without an owner or tier. Reps leave with account history in their own notes. Account priorities shift while the tiers stay fixed. And visits never get logged back to the map. In each case, the map is updated by hand while the field changes every day.
What happens to a sales territory when a rep leaves?
The accounts get reassigned. The harder part is the history: contacts, recent conversations and open opportunities that lived in the departing rep’s notebook or spreadsheet. Keep notes, contacts and opportunities on the account record, so a reassignment moves them with the account. Play #5 of the Map My Customers Field Sales Playbook makes the same point: the next rep should not have to start the relationship from scratch.
Can a CRM keep a territory map up to date on its own?
Only as far as what gets logged into it. The CRM holds the account record, so a map built on it reflects whatever ownership and fields someone has entered. Activity is often logged late or not at all, and a visit nobody entered cannot appear on the map. The more reliable setup pairs the CRM with a field sales execution platform where reps check in as they visit, and activity syncs back to the CRM, which stays the system of record.