How do you balance route efficiency with technician skill matching?

Deja, this is exactly the kind of problem that breaks dispatch teams if you don't get ahead of it. Here's how we solved it — and honestly wish we'd done this six months sooner.

First, we got ruthless about skill categories. Not just "HVAC" but "HVAC - Commercial - 10+ ton systems" and "HVAC - Residential - Diagnostics." The more granular, the better your matching.

Second, we created a tiered response system:

• Tier 1 (Same day): Proximity wins unless the job absolutely requires a specialist cert
• Tier 2 (24-48hr): We hold for the right tech even if it means a longer drive
• Emergency: Closest qualified tech, period — we follow up with a specialist if needed

We also started tracking "skill stretch" jobs — where a Tier 2 tech shadows a Tier 1 on complex work. Builds your bench and reduces the "only one person can do this" bottleneck.

Pro tip: Use FieldPulse's custom fields to flag jobs by complexity, not just type. Makes filtering way faster when you're building the board.

@gwen.albright we tried the tiered approach and it created more problems than it solved. My team couldn't keep the tiers straight and we ended up with angry customers who thought they were Tier 1 but got bumped.

We simplified: every job gets tagged skill-required or skill-preferred. Required means we wait for the right person. Preferred means closest tech gets it and we monitor completion time. If a preferred job takes 2x the estimate, it becomes required next time.

Much easier to execute. Your dispatchers need something they can apply in 10 seconds, not a decision tree.

Brandon, fair point on execution speed — but I think this depends on team size. At 17 techs you might get away with binary tags. We're at 34 and growing, and the binary approach started creating quality issues. Customers could tell when they got the "B team."

Maybe the real answer is: start simple, add complexity as you scale, and train your dispatchers like they're making high-stakes calls because they are.

Thanks so much Gwen and Brandon! This is really helpful. I think we're probably closer to Brandon's stage right now — we need something our dispatchers can actually remember and use without a cheat sheet. But I love the idea of building toward Gwen's tiered system as we grow.

Quick follow-up: how are you actually tracking the skill certifications in FieldPulse? Custom fields on the user profile? Tags? Something else?

We don't overthink this... closest tech who isn't already overbooked gets the job. If they can't handle it, they call for backup or we reschedule.

Customers care more about showing up on time than getting the world's greatest technician. Missed windows cost us way more than occasional callbacks.

That said — we do keep a "don't send" list. Like, don't send Dave to commercial refrigeration. Learned that one the hard way.

Ray's got a point about callbacks vs. late arrivals, but I'd push back on "call for backup" — that's expensive and kills your tech's day. Better to get it right the first time.

Pro tip: we use FieldPulse's job notes template to force the office to document why a specific tech was assigned. Creates accountability and patterns start to emerge. After 90 days we had solid data on which "stretch" assignments worked and which didn't.

Practical answer: we optimized for route efficiency on 80% of jobs, skill matching on 20%.

• Used FieldPulse's technician tags for base qualifications (HVAC, electrical, etc.)
• Created a "complex" checkbox on job intake that triggers manual dispatch review
• Everything else auto-assigns by zone

Key was getting sales/onboarding to actually use the complex checkbox. Took some training but now it's habit.

We also run a weekly report on drive time vs. job complexity to spot patterns. Takes 10 minutes and caught a bunch of inefficiencies we didn't see day-to-day.

In my experience the "skills" field in FieldPulse gets out of date fast. Nobody updates it when someone gets trained on new equipment.

We keep a paper binder in the dispatch office. Low tech, I know, but it's accurate and the dispatcher can flip through it in 30 seconds. Digital solution would be better but only if someone owns keeping it current.

Anyway — proximity wins unless the job explicitly requires certification for warranty or insurance. Then we eat the drive time.

we're struggling with this too. our dispatcher just left and the new person is drowning

how do you all handle when the closest tech is already at 90% capacity for the day. do you overload them or send someone farther away

we've been overloading and getting burnout

Teresa — we hit the same burnout issue last year. The team fixed it by capping daily job count regardless of drive time, and building in 15-minute buffers between jobs for the closest techs. Dispatch hated it at first (felt inefficient) but our completion rate went up and callbacks went down.

The key was getting leadership to accept that "busy" and "productive" aren't the same thing. Worth having that conversation if you can.

Also — if your new dispatcher is drowning, happy to share our training checklist. It helped us cut onboarding time in half.