Matching the Right Tech to the Right Job

Why this matters

Sending the nearest available tech instead of the right tech is how a simple maintenance call turns into a two-visit job, or how your best diagnostic person spends the morning on a filter change while a genuinely tricky fault sits on the board waiting for someone with less experience to fumble it. Good dispatch is not just filling time slots, it is a daily allocation decision that determines whether the day's jobs get done once, correctly, or twice, expensively. The dispatcher who matches well is worth more to the bottom line than the one who just moves fastest through the queue.

The factors that actually matter, in order

When assigning a job, work through these in roughly this priority order. Later factors should not override an earlier one that clearly rules a tech out.

1. Required skill or certification. If the job legitimately needs a license, certification, or specialized skill (working on certain equipment types, a permit-requiring task, an advanced diagnostic), that is a hard gate, not a preference. Do not send someone unqualified because they happen to be closest.
2. Job complexity versus tech experience. A straightforward, well-understood job is a good fit for a newer tech building confidence. An unclear-scope job, a repeat callback, or a customer who has already been burned once needs your most capable person, even if that means a longer drive.
3. Physical proximity and route efficiency. Once skill and complexity are satisfied by more than one tech, distance and the existing route become the tiebreaker. Do not let proximity override qualification.
4. Customer history with a specific tech. A customer who explicitly asks for the same tech, or who has a strained relationship with a specific one, is a real scheduling input, not a nice-to-have.
5. Load balancing across the crew. Do not run one tech ragged while another coasts. Skewed workload creates burnout, resentment, and eventually turnover, all of which cost more than the minor efficiency loss of spreading jobs more evenly.

Reading complexity before you assign, not after

You cannot match well if you have not sized the job first. A few fast signals that a job is more complex than it looks on the surface:

• The customer describes an intermittent problem ("it only does it sometimes") rather than a clean, consistent symptom.
• This is a second or third visit for the same underlying complaint.
• The equipment or system involved is unusually old, has been modified, or was installed by someone other than your shop.
• The customer sounds frustrated or has already mentioned wanting to escalate.

Any of these is a signal to route to a more experienced tech even if the initial call sounded routine, and to build in extra time on the schedule rather than assuming a standard duration.

Growing newer techs without gambling on hard jobs

The instinct to always send your best tech to anything tricky is understandable but shortsighted, it never lets anyone else develop. The fix is not avoiding this tradeoff, it is managing it deliberately:

• Pair a newer tech with a straightforward version of a skill you want them to grow into, not the hardest version.
• Keep an easy channel open for a newer tech to call a senior tech mid-job for a quick consult rather than getting stuck silently or guessing.
• Debrief afterward on jobs that stretched a newer tech, win or not, so the experience actually builds skill instead of just relief that it is over.

Over time this is how you build a bench deep enough that "who can handle a hard job" stops being a one-person answer.

When the "right" tech is not the available tech

Sometimes the best-matched tech is booked and only a lesser-matched one is free. Your options, roughly in order of preference:

• Delay the job to a slot when the right tech is free, if the job is not time-critical and the customer can wait.
• Send the available tech with a plan, meaning a phone consult mid-job with the more experienced tech, or a heads-up that a second trip may be needed for anything beyond the basics.
• Send the available tech and accept the risk, only when the job genuinely cannot wait and no better option exists. Flag it clearly on the job record so a callback is not a surprise.

What you should not do is silently send a mismatched tech and hope, without any of the above safeguards, simply because the schedule looked open.

The mental model to keep

Every assignment is a small bet: this tech, this job, this customer, today. A dispatcher who only optimizes for "is someone free right now" is playing every bet the same way regardless of the odds. A dispatcher who reads skill, complexity, and history before assigning is stacking the odds in the shop's favor, one job at a time.

References

• Trade-standard practice for field-service technician skill-matching and dispatch
• See related: Building Buffer Time Into a Daily Schedule
• See related: Squeeze In a Same-Day Emergency (decision tree)