Run a monthly territory-data review before quota planning
A bounded review that fixes ownership, location, and segment fields before the planning lock.

Start from the planning decision
A territory review should begin with the decision it must support, such as how many accounts each seller can cover next quarter. Write that decision at the top of the review so the team does not clean fields that will never change the plan. The review is not a general data project, and it should not expand into every account attribute in the CRM. A clear decision keeps the work bounded and makes the finish line visible.
Ask the sales leader which two or three assignments are currently disputed. Disputes usually point to the records that matter most, such as a large account with two owners or a region with no named seller. Record those examples before opening the full list. The examples become test cases for the cleaned data, and they show whether the review actually resolved the problem.
Define what counts as a territory record
A territory record needs a legal account name, a physical location, a segment, and an owner. Add the source of each field and the date it was last confirmed. Without those details, two reviewers can disagree about the same account without either being careless. The definition should fit the planning model rather than an ideal data model.
Write down which records are out of scope, including prospects with no location and accounts that belong to a partner. Out of scope does not mean unimportant, but it does mean the review will not resolve them. Keep a separate list for those records so they are not lost. A clean boundary prevents the review from turning into an endless cleanup.
Check account ownership before size
Ownership errors distort territory balance more than missing revenue fields. Find accounts with no owner, multiple owners, or an owner who has left the company. Compare the CRM owner with the assignment file the sales operations team uses for planning. A record can look complete while pointing to a person who cannot act on it.
Resolve ownership conflicts with a written rule rather than a series of private messages. For example, the account owner of record may be the person who logged the most recent qualified conversation. Apply the rule consistently and record every exception. The goal is a defensible assignment, not a perfect history of every handoff.
Test the address and firmographic fields
Check country, state, city, and postal code as a set rather than as separate columns. A record with a valid city and an incompatible postal code will fail routing even though each field looks populated. Use a reference source to confirm the combination, and flag records that cannot be confirmed. Do not overwrite a customer address without a second review.
Review employee count and industry against the segment definitions the team uses in planning. A company classified as enterprise in one report and mid-market in another will unbalance the territory model. Record the rule for each segment and apply it to the whole list. If the source is stale, mark the field as uncertain instead of guessing.
Look for duplicate and orphan accounts
Search for duplicates by domain, legal name, and billing address, then review the matches by hand. Automated matching will pair unrelated companies with similar names, and a careless merge can destroy history. Merge only when the team can identify the surviving record and the reason for the merge. Keep a log of every merge so an owner can reverse a bad decision.
An orphan account has activity but no clear owner or parent. These records often sit at the edge of a region and are easy to skip. List them with the last activity date and the person who touched them. Assign a temporary owner who can confirm whether the account belongs in the plan.
Assign a correction owner and deadline
Every correction needs a named owner and a date, even when the fix is a single field. Group the work by system so one person can correct the CRM while another updates the planning file. Put the deadline before the planning lock, not after it. A correction that arrives after the plan is signed creates a second round of rework.
Keep the correction list short enough to finish in the review window. If the list is long, rank items by their effect on the planning decision. Fix the ownership and location errors first, then move to descriptive fields. A partial fix that resolves the disputes is better than a broad cleanup that misses the deadline.
Record the exception list
Keep a separate exception list for accounts that the rules cannot resolve. Each exception should name the account, the conflict, the person who decided, and the date of the decision. A short note is enough if it lets another reviewer understand the choice. The list should not become a second territory plan.
Review the exceptions at the next planning cycle and ask whether the same rule failed again. A recurring exception may mean the rule is wrong, not that the account is unusual. Update the rule and remove the exception when the pattern is clear. An exception list that only grows is a sign that the rules are not being maintained.
Set the next review date
Choose the next review date before the current one ends. A monthly review is usually enough for a stable sales team, while a quarterly planning cycle may need two checks. Put the date in the operations calendar with the owner's name. An unscheduled review tends to happen only after a seller complains.
At the close of the review, record the number of records checked, changed, and left unresolved. Compare that with the previous review and note whether the same errors returned. Repeated errors point to an intake problem, not a cleaning problem. Fix the intake rule before scheduling another large cleanup.
Sources
- Occupational Outlook Handbook: Sales managers, U.S. Bureau of Labor Statistics. Describes sales manager work and the operational context for territory coverage.
- Market research and competitive analysis, U.S. Small Business Administration. Outlines a practical market and customer analysis process for small teams.
- Business Trends and Outlook Survey, U.S. Census Bureau. Provides business survey context for segment and demand assumptions.