What it means
A prospect's deal is routed to the wrong territory after an account changes headquarters. Revenue operations sales territory assignment exception rate shows how often an opportunity needs a documented departure from the normal territory rule.
A territory can be based on geography, named accounts, segment, partner relationship or product, so define the rule before calling a record an exception. CRM workflows can assign record owners automatically, but assignment logic reflects configured data and eligibility, and a successful workflow run does not prove the territory is commercially right.
State which opportunity types are in scope, such as new business, expansion, renewal, partner-sourced or internal transfers. Use a clear hierarchy when rules overlap, such as named account before general region.
If a customer has several locations, specify whether routing follows billing headquarters, buying entity or service site, and do not let a remote buyer's travel location change the account territory. For a multinational group, avoid treating the parent company and a local subsidiary as one buyer without an account rule.
If a partner originated the deal, review partner protection or registration rules before manual rerouting. Define numerator events as opportunities whose applied territory differs from the rule in force at the assignment checkpoint.
Count a deal once for the period even if several workflow jobs reassign it repeatedly, and show approved and unapproved exceptions separately, because a high approved rate may still indicate a poorly designed rule. If a rule changes retroactively, preserve the version used when the opportunity was assigned, and use historical snapshots to explain past forecasts.
Maintain an authorised exception path with reason, owner, approval and review date. If a customer asks to work with a specific seller, document whether that request may override standard routing.
A staffing reassignment after a seller leaves is not the same as a territory-rule exception, and primary ownership should be identified separately from deal-split credit. The measure is not a contest to eliminate every exception, and a low rate could coexist with a slow manual queue, so pair it with routing delay and dispute volume.
An account merge can create apparent exceptions, so map duplicate IDs before measuring, and test automation on boundary cases such as ambiguous countries or postal codes. A temporary exception should name who acts on the buyer's next request and who updates the CRM, and an incorrect assignment that affected compensation should be corrected through the approved process.
In practice
Real-world examples.
Example
A large retailer is a named account and stays with its designated seller despite a general geographic rule that would route it elsewhere. The approved exception is recorded with its reason and review date.
Example
A stale headquarters field routes a new deal for a logistics customer to the wrong region. Revenue operations corrects the assignment and logs the data cause. The deal counts as an unapproved exception.
Example
A seller at a medical software company moves teams mid-deal, but policy preserves the current owner until signature to avoid confusing the buyer. The case is logged as an approved exception with an end date.
Formula
Calculation
Exception rate = distinct eligible opportunities assigned outside the effective standard rule / all eligible opportunities assigned x 100; split approved and unapproved.
Worked example: a company assigns 800 eligible opportunities in a quarter. Of these, 56 were assigned outside the standard rule: 40 have a documented approval and 16 do not (40 + 16 = 56).
Exception rate = 56 / 800 x 100 = 7%. The unapproved rate is 16 / 800 x 100 = 2%, which is the figure that points at routing errors or ignored process, while the 5% approved share (40 / 800) tells you whether the rule itself needs redesign.Case study
Seen in the real world.
This fictional case follows Harborline Data, an invented analytics company. Its automated territory rule relied on an outdated headquarters field and moved several active opportunities to different sellers in the middle of negotiations. Revenue operations fixed the account data, documented temporary ownership exceptions and reviewed any resulting compensation disputes through the approved process. It then began testing the routing rule on boundary cases before each change, and reviewing recurring exceptions by region to find master-data problems. The case is invented for illustration.
Watch out
Common mistakes.
- Calling every staffing transfer a territory exception, when only departures from the territory rule belong in the measure.
- Comparing an old assignment against today's revised rule instead of the rule in force at the assignment checkpoint.
- Hiding approved exceptions when testing whether the design works, which conceals a poorly fitting rule.
Questions
People also ask.
Are exceptions always errors?
No. Some are valid departures under the published policy, such as a named account.
Should repeat workflow moves count repeatedly?
Normally no. Define the distinct opportunity and the assignment checkpoint.
Can a customer preference affect ownership?
Only within the organisation's applicable assignment rules, and it should be documented.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related