Why a reassignment can break routing
Reassigning an account owner or deactivating a user changes the data that routing rules depend on. A rule that used to send a lead to a named person may now send it to a deactivated user, a team with no members, or a fallback that no one checks. The rule itself may not have been edited, which makes the failure easy to miss. This test checks whether routing still resolves to a valid owner after a controlled reassignment. It is a test of the rule's behavior, not of the reorganization decision.
Define the reassignment under test
Record the account, the old owner, the new owner, and the time of the change. Note whether the old owner was deactivated, moved to another team, or simply removed from the account. Include any territory or team membership change that happened at the same time. If several changes were made together, split them where possible so the result is attributable. A test that bundles an owner change, a territory change, and a rule edit cannot tell the team which action caused the failure.
Capture the routing baseline
Before the reassignment, submit a test lead that matches the rule and record the assigned owner, the assignment time, and the notification. Repeat for each routing path in scope, such as a form submission, an imported lead, and a manual assignment. Save the evidence with the test lead identifier. The baseline shows what a correct routing decision looks like. Without it, a later fallback assignment can look like a deliberate choice rather than a failure.
Apply the reassignment and retest
After the change, submit the same test leads with the same field values. Record the assigned owner, the delay, and whether the notification reached the new owner. A lead assigned to an inactive user, a shared queue, or no owner at all is a failure. A lead assigned to a different active user may be correct if the territory mapping changed; record the reason. The comparison should use the same test values so the routing decision is comparable.
Test the fallback explicitly
A reassignment often exposes the fallback rule. Submit a lead with a territory or product value that no rule matches and record where it lands. Confirm that the fallback owner is active, that the notification reaches them, and that the lead appears in the queue they check. A fallback that points to a shared inbox with no assigned reviewer is a failure even if the record has an owner field filled. Record the fallback path separately from the normal rule paths.
Check the historical records
A reassignment can leave old leads pointing at a departed owner even when new leads route correctly. Query the open leads and opportunities associated with the reassigned account and record their owners. A lead that is still owned by an inactive user will not appear in the new owner's queue. Record the count and the age of those records. This check is separate from the new-lead test, but it matters for the same reason: the work must reach a person who can act.
Test the notification and permissions
An assignment is only useful if the owner can see the record and is told about it. Check that the new owner has access to the lead, the account, and any related record. Confirm that the notification uses the new owner's address and that a deactivated user's address is not still in the path. Record the channel and the recipient. If the notification depends on a personal subscription, test it under the new owner's account rather than the administrator's.
Classify the outcomes
Group the results into routed correctly, routed to a valid but different owner, routed to an inactive owner, routed to a shared queue only, unowned, and notification failed. Add a category for a rule that produced an error. The classification separates a design decision from a defect and gives each finding a repair owner. A test that only records pass or fail hides the cases that need a product or process change rather than a rule edit.
Measure the survival rate
Report the number of routing paths tested, the number that still resolve to a valid owner, and the number that failed. Report counts alongside percentages and show the failed paths. Do not describe the result as an industry benchmark or a target. It describes this reassignment at this time. A single failed path that affects a high-volume form deserves more attention than several low-volume paths that already have a manual workaround.
Choose one repair and retest
Pick the highest-impact failure and fix it at the source. That might mean updating the rule, reassigning the historical records, correcting the fallback, or restoring access for the new owner. Retest the same paths with the same test leads. Compare the result with the baseline and report what changed. A repair that restores routing without breaking the new territory structure is the goal, even if a few low-volume paths remain.
Document limits and data handling
The test depends on controlled test leads and on the ability to inspect the routing rules. It cannot prove that the new owner will work the lead, and it does not cover changes made directly in the database. State those limits in the method note. Test leads should use clearly marked test data, and any exported records should be restricted and deleted when the review is complete. A repeatable routing test is one that another administrator can run before the next reassignment, not a one-time check after a lost lead.
Sources
- https://knowledge.hubspot.com/records/understand-original-source-properties
- https://www.w3.org/TR/NOTE-datetime
- https://www.nist.gov/cyberframework
- https://www.census.gov/data/developers/guidance/api-user-guide.html
- https://www.ftc.gov/business-guidance/privacy-security