On this page11 sections
Why a reorganization breaks routing
A sales reorganization changes territories, managers, and owner assignments at the same time. The routing rules that worked last month may now point to a person who has moved, a team that no longer exists, or a territory that has been split. The first symptom is usually a lead with no owner or an owner who should not have it. A short exception review during the transition catches those gaps before customers wait. It treats routing as part of the reorganization plan, not as a settings task to finish later.
List the routing rules that changed
Start by listing every rule that references a person, team, territory, or product assignment affected by the reorganization. Record the rule name, the condition, the destination, and the owner of the rule. Include round-robin lists, territory maps, and manual assignment queues. Mark which rules were edited during the transition and which were left untouched but now point at changed data. A rule that was not edited can still be broken because the value it matches has moved. The list is the scope of the review.
Find leads with no valid owner
Query the leads created since the reorganization began and identify any without a named owner or with an owner who is inactive. Record the arrival time, the source, and the routing rule that should have applied. Group the results by rule and by source. A single form that produces unowned leads is a specific fix; a broad pattern across sources suggests the fallback assignment is missing. The count of unowned leads is the most direct measure of the transition's health.
Check the fallback before the exception
Every routing setup needs a fallback for leads that match no rule. During a reorganization, the fallback is more likely to be used, so confirm that it still points at a person or queue that can act. Test a lead with an unusual territory or product value and follow it to the fallback. Record who receives it and how quickly. A fallback that points to a shared inbox with no owner is not a fallback; it is a delay with extra steps.
Review reassigned accounts for orphaned opportunities
Changing an account owner does not automatically update open opportunities, tasks, or sequences. Check a sample of reassigned accounts for open deals whose owner is still the previous person or a deactivated user. Record the account, the opportunity, the owner, and the next action. This is where a reorganization can create silent gaps, because the account looks reassigned while the work does not move. The review should produce a list of records that need an explicit owner change.
Test the notification path
A routed lead is only useful if the owner learns about it. Check the notification that fires on assignment and confirm that it reaches the new owner, not the previous one or a disabled address. Test one lead per routing path. Record the channel, the recipient, and the time. If the notification depends on a personal setting or a group that changed, fix it before the next campaign. A lead that sits in a queue without a notification is effectively unassigned from the salesperson's point of view.
Keep a temporary manual queue
During the transition, keep a small manual queue for exceptions that the rules cannot resolve. Name one person who checks it twice a day and one backup. Record the leads in the queue, their age, and the reason they could not be routed. The queue is a safety net, not a permanent process. Review it weekly and close the rules that keep sending the same exception. If the queue grows, the routing rules need attention rather than more manual work.
Check reporting before the first review
Lead routing changes can distort the first weekly report. Confirm that the report groups by the new owner structure and that unassigned leads appear as a visible category rather than being excluded. Check that the response-time calculation still uses the form submission time, not the reassignment time. Record the report version and the date it was updated. A report built on the old structure can make the transition look cleaner than it is.
Assign an owner for the transition
Name the person who owns routing during the reorganization and the person who can approve an exception. Record a deadline for the transition period and the criteria for ending it, such as no unowned leads for five working days. The owner should review the exception queue, the unowned count, and the reassigned-account list on a fixed cadence. Without a named owner, the cleanup becomes everyone's side task and no one's responsibility.
Close the transition with evidence
End the transition when the evidence supports it: unowned leads at zero for a defined period, the fallback tested, notifications delivered, and the reassigned accounts carrying a named owner. Record the evidence and the date. Keep the temporary queue for one more cycle in case a delayed lead surfaces. Then remove the manual workaround and return to the normal routing process. The review is complete when the team can explain who owns every new lead and why.
Keep the review for the next change
Add the routing exception review to the checklist for any future territory change, manager change, or CRM migration. Keep the same fields and the same tests so the next review is fast. The goal is not a perfect routing system; it is a transition that does not lose customers while the team reorganizes. A repeatable review turns a stressful change into a known sequence of checks.