Routing does not break loudly
When a CRM goes down, everyone knows immediately. When a routing system degrades, it happens silently. A rule that used to match 95% of leads now matches 88% because the enrichment provider changed a field format. An overflow queue that was supposed to be temporary has been catching 12% of leads for six months. A territory change from last quarter never got reflected in the routing logic, so three reps are getting leads for accounts they no longer own.
These problems do not announce themselves. They show up as slightly slower response times, slightly lower conversion rates, and slightly more "I never got that lead" complaints in Slack. Each one is small enough to dismiss individually. Together, they represent significant revenue leakage.
Forrester research on revenue operations maturity has shown that companies with disciplined operational review cadences see 10-20% higher revenue productivity. Routing is one of the highest-leverage areas to review quarterly because it sits between demand generation and sales execution. If routing breaks, nothing downstream works correctly, no matter how good your reps or how strong your pipeline.
This checklist is designed for the quarterly routing review. Run through it before your next QBR. The questions are grouped into five categories: data foundation, routing accuracy, speed and performance, workload distribution, and measurement. If you cannot answer more than half of these with data (not gut feel), your routing system needs more than a review. It needs an audit.
Data foundation
1. What percentage of inbound leads have complete routing data at the point of assignment?
Routing rules are only as good as the data they evaluate. If your routing depends on company size, industry, and geography, but only 70% of leads have all three fields populated when routing fires, 30% of your leads are being routed on incomplete information.
Pull a report on field completion rates for every field your routing rules use. The target is 90% or higher. If you are below that, the problem is not routing logic. It is data enrichment timing. Enrichment must complete before routing fires, not after.
2. What is your lead-to-account match rate, and how many false positives are you generating?
Lead-to-account matching is the foundation of territory-based and named-account routing. If your match rate is below 85%, leads from existing accounts are being treated as new leads and routed to the wrong rep.
Equally important: false positive rate. If your matching is too aggressive (matching on company name alone without domain or firmographic validation), leads from "National Bank of Commerce" might match to "National Bank" and route to the wrong account owner.
Pull the match rate and manually review a sample of 50 matched leads. How many were matched correctly? How many were false positives?
3. Are your CRM records clean enough to support your routing logic?
Routing that depends on picklist values (industry, segment, region) breaks when those values are inconsistent. If "Healthcare" and "Health Care" and "HC" all exist in your industry field, a routing rule targeting "Healthcare" misses two-thirds of healthcare leads.
Run a field audit on every picklist your routing evaluates. Check for duplicates, variants, blanks, and deprecated values. CRM data hygiene is not a one-time project. It is the ongoing prerequisite that makes routing possible.
Routing accuracy
4. What percentage of leads are routed correctly on the first attempt?
This is the single most important routing metric and the one most teams do not track. Pull a sample of 100 recently routed leads. For each one, check: did the lead reach the correct rep based on your documented routing rules?
"Correct" means the right rep by territory, segment, capacity, and any other criteria your rules evaluate. If accuracy is below 90%, identify the failure patterns. Are leads being misrouted by territory? By segment? By account ownership? The pattern tells you which rule is broken.
5. How many leads end up in fallback or unassigned queues, and how long do they stay there?
Every routing system has a fallback: a queue where leads go when no rule matches. This queue should be nearly empty. If it is catching more than 5% of leads, your routing rules have coverage gaps.
More importantly: what is the average time a lead sits in the fallback queue before a human assigns it? If the answer is more than 4 hours, you have a speed-to-lead problem hiding inside a routing problem. Fallback queues are where leads go to die.
6. Do your routing rules reflect your current territory structure?
Territory changes happen. Reps leave, reps are hired, territories are split, territories are merged, accounts are reassigned during quarterly rebalancing. Every one of these changes should trigger a routing rule update. Many do not.
Compare your current territory assignments in the CRM against the territory definitions in your routing logic. If your territory model was last updated in Q3 and it is now Q1, there is almost certainly drift. Territory-based routing only works when routing and territory are synchronized.
7. Are routing rules documented, and does the documentation match what is actually configured?
This is the question that reveals the most about operational health. Ask the person who manages routing to explain, without looking at the configuration, the exact rule order and logic. Then compare their explanation to what is actually configured.
In most organizations, these do not match. Rules have been added, modified, and patched over time without updating documentation. The result is routing logic that only one person fully understands, and when that person leaves, the organization discovers how much was undocumented.
Speed and performance
8. What is your median time from lead creation to rep notification?
Not lead creation to assignment. Lead creation to the moment the rep knows they have a new lead. Assignment can happen in seconds, but if the notification is buried in a Salesforce task queue that nobody checks, the effective response time is hours.
Measure this end to end. The benchmark from research on response time is clear: responding within 5 minutes produces a 21x higher qualification rate than responding at 30 minutes. Every unnecessary step between lead creation and rep notification is destroying conversion.
9. What is the average number of hops before a lead reaches its final owner?
A "hop" is any reassignment. Lead comes in, gets auto-assigned to Rep A (hop 1), Rep A realizes it is not their territory and manually transfers to Rep B (hop 2), Rep B sees it is a named account and reassigns to the account owner Rep C (hop 3). Three hops, 48 hours, and the prospect has already booked a demo with your competitor.
Track reassignment rates. If more than 10% of leads require manual reassignment after initial routing, your routing rules are not accurately reflecting your assignment logic. Each hop is a delay, and each delay costs conversion.
10. Are SLA timers actively tracked, and what happens when they expire?
Most teams define a response SLA. Few actively enforce it. An SLA without an enforcement mechanism is a suggestion.
Check three things: (1) Is the SLA timer actually running in your system? (2) What percentage of leads are being contacted within SLA? (3) What happens when the SLA expires? If expired-SLA leads sit untouched until someone manually notices, the SLA is not working. Expired leads should automatically escalate: reassigned to the manager, moved to a rapid-response queue, or flagged with a visible alert.
Workload distribution
11. What is the variance in lead volume per rep, and does it match territory potential?
Pull lead assignment counts by rep for the trailing 30, 60, and 90 days. Calculate the coefficient of variation (standard deviation divided by mean). If variance exceeds 25%, leads are not being distributed equitably.
But equal distribution is not always the goal. If territories have different potential, lead volume should reflect that. A rep covering 300 mid-market accounts should receive more leads than a rep covering 50 enterprise accounts. The question is whether the distribution matches the design, not whether it is perfectly even.
12. Are any reps consistently at capacity while others are underutilized?
Capacity-based routing prevents overload by factoring in each rep's current workload. But capacity thresholds need regular calibration.
Pull the current open opportunity count, active lead count, and activity volume per rep. Are some reps consistently near their ceiling while others have bandwidth? If so, either the capacity thresholds are miscalibrated, the territory balance is off, or demand is concentrated in specific segments that map to specific territories.
13. Is routing creating or reinforcing performance inequality?
This is the fairness question. If your routing includes any performance-based signals (routing more leads to higher-converting reps), check whether the feedback loop is creating an unfair advantage.
A rep who gets 40% more leads because they have a 40% higher close rate will continue outperforming, not because they are better, but because they get more at-bats. This is a legitimate design choice, but it should be deliberate, not accidental. If you are routing on performance, audit whether the performance gap is driven by skill or by lead quality and volume advantages that routing itself created.
Measurement and monitoring
14. Do you have a routing dashboard, and when was the last time someone looked at it?
A dashboard that exists but is not reviewed is functionally the same as no dashboard. Routing metrics should be reviewed weekly at minimum, not quarterly.
The core routing dashboard should show: leads routed per day (trend), routing accuracy rate, fallback queue volume, median assignment-to-contact time, SLA compliance rate, and lead volume distribution by rep. If you do not have these six metrics accessible in one view, your monitoring infrastructure is insufficient. Build it before your next QBR so that the QBR conversation is data-driven, not anecdotal.
15. Can you answer "why did this specific lead go to this specific rep" for any lead in the system?
This is the audit trail question. Pick any lead assigned in the last 30 days. Can you trace the routing decision? Which rules fired, in what order, what data was evaluated, and why the system chose the rep it chose?
If the answer is "I would have to ask the person who built the rules," your routing lacks observability. Every routing decision should be logged with enough detail to reconstruct the logic after the fact. This is not just an operational best practice. It is a requirement for troubleshooting misroutes, resolving rep disputes over account ownership, and demonstrating to leadership that the system is working as designed.
Advanced routing systems log every decision point. If yours does not, the first project after this audit should be building that audit trail.
Scoring the audit
Count how many of these 15 questions you can answer with actual data, not estimates or gut feel.
12-15 questions answered with data: Your routing operations are mature. Focus on optimization: tuning thresholds, testing new routing models, and measuring incremental improvements.
8-11 questions answered with data: You have a solid foundation with gaps. Prioritize the unanswered questions as projects for next quarter. The gaps likely cluster in one area (measurement is the most common weakness).
4-7 questions answered with data: Your routing is running but not managed. The system is probably producing results through a combination of working rules and manual intervention. Invest in instrumentation and monitoring before making rule changes.
0-3 questions answered with data: Your routing needs a full diagnostic. Do not try to optimize what you cannot measure. Start with the data foundation (questions 1-3) and build up.
Making the audit a habit
This checklist should not be a one-time exercise. Build it into your quarterly operating cadence. The best routing systems are not the ones that launch perfectly. They are the ones with a disciplined review cadence that catches degradation before it becomes visible in pipeline metrics.
Run the checklist. Score it. Identify the gaps. Fix the highest-impact gap before the next quarter. Repeat. Routing health, like data quality, is a continuous discipline, not a project with an end date.
At RevenueTools, we are building routing with observability as a core feature. Every routing decision logged, every rule traceable, every metric visible. Because routing you cannot audit is routing you cannot trust. See what launches April 14th.