Account Assignment Rules Template
Send your account export and ownership field, get every overlap and coverage gap named before you write a single rule.
Free download · No account needed
Overlap Report
Corrigan Systems, a fictional B2B SaaS company. 600 named accounts, 34 with two or more active owners before anyone wrote a policy.
| Cause | Accounts | Share of overlaps |
|---|---|---|
| Duplicate CRM record merged, both retained | 14 | 41.2% |
| Parent-child hierarchy split across two rules | 11 | 32.4% |
| Reorg leftover: old owner never removed | 9 | 26.5% |
| Total overlaps | 34 | 5.7% of all 600 accounts |
19 of the 34 are live conflicts (every owner holds an open opportunity right now), $890,000 combined open pipeline. The other 15 are stale: $530,000 in historic value with no current deal at risk.
Coverage Gaps
The flip side of the same join: 18 accounts with zero active owners, found by the same query that found the overlaps.
| Account | Months unowned | Historic annual spend |
|---|---|---|
| Greymouth Shipping | 3 | $61,000 |
| Corrance Freight | 4 | $52,000 |
| Ashdown Financial | 5 | $38,000 |
| All 18 accounts | - | $756,000 |
Average $42,000 in historic spend per unowned account, $756,000 combined. None of these shows up as a problem in a standard pipeline report, since there is no owner to report against.
Assignment Register
The full join, before any overlap gets diagnosed or any gap gets closed.
| State | Accounts | Share |
|---|---|---|
| Exactly one active owner | 548 | 91.3% |
| Two or more active owners | 34 | 5.7% |
| Zero active owners | 18 | 3.0% |
| Total | 600 | 100% |
Every number above came from one join of the account export against its own owner field, run before a single policy rule was written.
An account assignment policy usually gets written the same way: precedence rules on a whiteboard, distributed, done. Nobody checks the CRM for what is already true, which is that missing parent-child links, duplicate records, and weak data governance are the most cited root cause of account conflicts, not a policy gap. This pack starts from the other direction. It joins your account export against its own owner field first, so the overlaps and gaps in your own book become a count instead of a rumor two reps argue about.
Every account lands in one of three states, and the counts have to sum to the total or the join gets rerun. One owner is correct, and two or more is an overlap. Each overlap gets a named cause: a duplicate record merged with both owners kept, a subsidiary and parent assigned by two rules that never checked each other, or a reorg that never removed the old owner. Zero owners is a coverage gap, which carries real revenue risk even though nobody is fighting over it.
On a worked run for Corrigan Systems, a B2B software company, 600 named accounts turned up 34 overlaps and 18 unowned accounts before any policy existed. Nineteen of the overlaps were live conflicts, both owners holding an open opportunity, worth $890,000 in pipeline that a by-owner forecast roll-up was double-counting the whole time. The routing rules that assign a lead before it becomes an account and a speed-to-lead audit both feed the same register this pack builds.
What's in the pack
Assignment Register
Every account joined against its own owner field, sorted into one owner, overlap, or zero owners, with the three counts stated.
Overlap Report
Every two-or-more-owner account with its specific cause named, plus which ones are live conflicts versus stale records.
Coverage Gaps
Every zero-owner account with its historic spend, so an unowned account reads as revenue risk, not a neutral finding.
Change Log
Every resolution logged as it happens, with the specific reason stated next to the account, owner, and date.
Assignment Policy
The precedence order a contested account resolves against, built from what your own register actually found.
Conflict Resolution
The process for a live conflict specifically: who gets looped in, what evidence counts, and the decision timeline.
Mid-quarter Change Note
The short write-up template for any account that changes owners outside the normal assignment cycle.
How to use it
- 1
Send the account export
The account list with its current-owner field, plus whatever hierarchy data links parent and subsidiary accounts.
- 2
Build the register and find overlaps
The export joined against itself, sorted into one owner, two or more, or zero, with every overlap's specific cause named.
- 3
Separate live from stale
Every overlap checked for an open opportunity on each side, since a live conflict and a stale record need different handling.
- 4
Resolve and write the policy
Each overlap and gap resolved and logged, then the Assignment Policy and Conflict Resolution process written from what was found.
Frequently asked questions
How is this different from just writing a territory or precedence policy?
A precedence policy states what should happen going forward. This starts by finding what has already happened: on the worked example, 34 accounts already had duplicate active owners before any policy existed. The policy this pack produces is built from those specific causes, not drafted in the abstract.
What if we don't have parent-child hierarchy data at all?
Send whatever informal knowledge exists, even a short list of which accounts are subsidiaries of which. It won't catch every hierarchy overlap, but it catches the largest ones, and the register can be rerun once cleaner hierarchy data exists.
Why does it matter whether an overlap is live or stale?
A live conflict, where both owners hold an open opportunity, risks killing a real deal if resolved carelessly, and its pipeline is often double-counted in a by-owner forecast roll-up. A stale overlap is just an uncleaned record and resolves directly against the policy with no conversation needed.
Does this replace our lead routing rules or scoring model?
No. Lead routing decides which rep a new lead reaches first, and lead scoring decides which leads deserve the fastest response. This pack governs the account once it exists, including the accounts routing never touches because they were created directly or inherited through a merger.
We just did a data cleanup project. Won't this find nothing?
Rerun it anyway, on a shorter cycle than you'd expect. New duplicates and reorgs keep producing new overlaps even after a cleanup clears the backlog, which is why the Assignment Policy sets a recalibration cadence rather than treating the register as a one-time project.
Our reps are still slow to respond even after ownership is fixed.
That's a separate, sequential problem. A speed-to-lead audit traces a slow response to the specific routing rule or capacity gap behind it, once every account already has exactly one clear owner to measure the response time against.
Find out how many of your accounts already have two owners
Send your account export and ownership field. The first thing back is three counts that sum to your account total.
Find my overlaps