How to Audit Your HubSpot Lead Routing Setup

Most HubSpot routing setups aren't built — they accumulate. A workflow gets added when the first SDR joins. Another gets added when territories are introduced. A third gets added to handle a specific edge case that came up during a board meeting. Six months later, nobody has a complete picture of what the system actually does, and the first sign that something is wrong is a rep complaint or a pipeline shortfall.

A routing audit is how you get that picture back. Not a theoretical exercise — a structured review of what your routing system is actually doing, where it's failing quietly, and what it would take to make it reliable.

This post is a practical audit framework. Work through it in order. By the end you'll have a clear inventory of your current routing architecture, a diagnosis of where it's leaking, and a prioritized list of what to fix.

Before you start: what you're auditing for

A routing audit has three goals. First, documentation — producing a written record of what your routing system does that exists independently of the workflows themselves. Second, accuracy — verifying that the system is doing what you think it's doing. Third, gap identification — finding the failure modes that are costing you leads, rep time, or conversion rate.

The audit covers six areas: workflow inventory, assignment accuracy, lead ownership health, speed-to-lead distribution, SLA compliance, and audit trail integrity. Each area has specific questions to answer and specific data to pull.

Block two to three hours for a first pass. Plan to come back to specific sections with additional data once the initial review surfaces where the real problems are.

Section 1: Workflow inventory

The first question in any routing audit is simple and often uncomfortable: what workflows are currently touching lead assignment?

Pull a complete list of active HubSpot workflows. Filter for workflows that include any of the following actions: rotate record to HubSpot owner, set contact owner, set company owner, create task assigned to a specific user, or send internal email notification. Every workflow that appears in this list is part of your routing architecture.

For each workflow, document:

• What triggers enrollment
• What conditions branch the logic
• What assignment action fires and to whom
• What notification action fires, to whom, and through what channel
• When it was last modified and by whom
• Whether it has re-enrollment enabled

What to look for:

Overlapping enrollment criteria — two workflows that can both enroll the same contact simultaneously. The contact may get assigned twice, with the second overwriting the first.

Workflows with no fallback action — if enrollment criteria match but no branch condition applies, the contact exits the workflow with no owner. Many teams discover their routing has no explicit fallback.

Stale user references — assignment actions that route to specific users who have left the company or changed roles.

Notification gaps — workflows that assign ownership but don't notify the assigned rep. Every assignment action should have a corresponding notification.

Section 2: Assignment accuracy

Knowing what your routing workflows are supposed to do is step one. Verifying that they're doing it correctly is step two.

Pull a sample of contacts created from your primary inbound sources in the last 30 days. Target at least 50 contacts.

For each contact, verify:

• Did the contact enroll in the expected routing workflow?
• Was ownership assigned within the expected timeframe?
• Is the assigned owner the correct rep for that contact based on your routing rules?
• Is the contact correctly associated to a company record, and does the contact owner match the company owner?

What to look for:

Owner mismatches — contacts assigned to a rep who doesn't cover that territory or account. If you find more than a handful in a 50-contact sample, the routing logic has a structural problem.

Missing enrollments — contacts that should have enrolled but didn't. Typically a property wasn't set or a form submission didn't populate the right field.

Delayed assignments — contacts where the gap between creation and owner assignment is longer than expected. This is routing latency.

An assignment accuracy rate below 90% warrants investigation. Below 80% is a systematic problem.

Section 3: Lead ownership health

Assignment accuracy looks at leads that do enroll. Lead ownership health looks at the broader population — including leads that fell through entirely.

Run these reports in HubSpot:

Unowned inbound contacts — contacts created from inbound sources in the last 90 days with no contact owner. Every contact in this report is a lead that exited your routing system without an assignment.

Contacts owned by inactive users — contacts whose current owner is a deactivated user. These leads have a nominal owner but nobody responsible for them.

Contacts with no logged activity — contacts from inbound sources in the last 90 days with zero activities. The overlap between unowned and zero-activity contacts tells you how much inbound volume is going completely unworked.

Contacts with mismatched owners — contacts where the contact owner differs from the company owner. For account-based teams, this is the most consequential ownership health metric.

A routing fallthrough rate above 5% is worth investigating. Above 10% indicates a systematic gap.

Section 4: Speed-to-lead distribution

With ownership health established, audit how quickly owned leads are being worked. A lead can be correctly assigned and still be worked too slowly to convert.

Build the speed-to-lead report. The output you need:

• Percentage of inbound leads contacted within one hour
• Percentage contacted within four hours
• Percentage contacted within 24 hours
• Percentage not yet contacted at 48 hours or beyond
• Conversion rate to opportunity for each bucket

The shape of the distribution tells you something. Concentrated in under-one-hour suggests routing and notification are working. Concentrated in four-to-24 hours suggests reps see leads but don't prioritize quickly. A long tail at 48+ hours suggests unowned leads or notification failures.

Look for variation by lead source, by rep territory, by time of day. Business-hours-adjusted speed-to-lead is more meaningful than raw speed-to-lead.

Section 5: SLA compliance

Speed-to-lead tells you what's happening. SLA compliance tells you how that compares to what should be happening.

If your team has a defined speed-to-lead SLA, calculate the percentage of leads where first contact fell within the window. That's your compliance rate.

If you don't have a defined SLA, use the conversion rate data from Section 4 to inform the target. Let your own data drive the number rather than an external benchmark.

Two additional questions matter:

Are SLA breaches visible in real time? If a lead goes four hours without contact during business hours, does anyone know? Real-time visibility is what separates an enforced SLA from an aspirational one.

What happens when an SLA is breached? If the answer is nothing, the SLA is decorative. An operational SLA has a defined escalation path — reassignment, manager notification, or breach logging.

Section 6: Audit trail integrity

The final section evaluates whether you can reconstruct what happened to any given lead.

Take five contacts from recent inbound volume — a mix of correct and problematic routing. For each, attempt to answer:

• When did this contact enter the system and from what source?
• Which workflow enrolled them?
• Which branch applied?
• Who was assigned as owner and when?
• What notification was sent and when?
• When did the assigned rep first view the record?
• What was the first rep activity and when?
• If reassigned, why and by whom?

For each question, note whether the answer is immediately available, requires cross-referencing, or is simply unavailable.

The questions you can't answer are the gaps in your audit trail. These gaps represent the blind spots in your routing operation.

Prioritizing what to fix

After completing the six sections, prioritize by the product of frequency and per-instance revenue impact.

Unowned leads — high frequency, high impact. A lead that never gets worked has zero conversion probability. Fix this first. Establish a fallback assignment for every inbound lead.

Assignment accuracy errors — variable frequency, high impact for account-based teams. Fix second.

Routing latency — affects every lead, impact depends on conversion rate sensitivity. Fix third.

Notification failures — high per-instance impact, often concentrated in specific channels. Fix in targeted fashion.

SLA enforcement and audit trail gaps — important for ongoing operations but less immediate per-lead impact. Address after structural problems.

Running the audit on a schedule

A routing audit done once is a snapshot. Done quarterly is a maintenance program.

Schedule a lightweight version every quarter — unowned lead count, assignment accuracy sample, speed-to-lead distribution. Run the full audit annually or after significant changes to team structure, territory model, or routing logic.

The routing system degrades when the team changes faster than the workflows are updated. Quarterly monitoring catches that drift before it becomes systematic.

A note on documentation

The most durable output of a routing audit isn't the findings — it's the documentation. A written routing architecture document, updated after each audit, is what makes your routing system maintainable by someone other than the person who built it.

Document your routing architecture as if you're going to leave the company tomorrow. That document is worth more than any individual fix the audit produces.

FlowRouter gives you a visual routing canvas where your routing architecture is always documented — every flow, every condition, every assignment rule visible in a single view without opening a single workflow. Start a free account and connect your HubSpot in minutes.