Dispatching the Right Tech to the Right Job: Decision Tree

Why this matters

Sending the wrong tech to a job is a quiet profit killer. The junior who cannot finish the repair burns a truck roll and a return trip. The senior sent to a basic call is wasted on work anyone could handle, while the complex job that actually needed them sits unstaffed. Good dispatch is matching the job's real demands to the tech's real strengths, and doing it fast enough to keep the day moving. Get this right and the same crew gets more done with fewer callbacks.

Start here: what does this job actually require?

Before you assign anyone, read the job for four things the booking notes should already carry:

• Skill level: routine maintenance, standard repair, or a diagnostic that has stumped people before.
• Specialty: does it need a particular certification, license, or hands-on experience with this kind of system?
• Location: where is it relative to techs already in that part of town?
• Urgency and timing: does it have a hard window, an emergency flag, or a flexible day?

If the booking notes do not tell you these, that is the first failure. Fix the booking script so dispatch is not guessing.

Branch one: does it need a specific skill or certification?

If yes, the pool is only techs who hold that skill, full stop. Do not send someone "close enough" on a job that legally or technically requires a qualified person. A permit-bound or safety-critical task goes to the qualified tech even if a closer truck is free. Narrow to the qualified set first, then optimize within it.

If no, any competent tech can take it, so move to the next branch and optimize for efficiency rather than capability.

Branch two: how hard is the diagnosis?

If it is a clear, common fault (the customer described a textbook symptom, the fix is routine), a mid-level or junior tech handles it well and you save your best people for harder work. Sending a senior here is overkill.

If it is vague, intermittent, or already failed once, send experience. A "nobody can figure out why" call that goes to a junior usually comes back as a second truck roll. The expensive tech is cheaper than two trips. When the symptom is fuzzy, lean toward the person who has seen the most.

Branch three: who is already nearby?

Once you have the right capability tier, location breaks the tie. A qualified tech ten minutes away beats an equally qualified tech across town. Drive time is unpaid, unbillable, and burns fuel, so routing within the qualified pool by proximity is where you claw back hours.

If two suitable techs are equally close, look at their existing load. The one with the lighter remaining day or the better-fitting window gets it. Do not pile a fifth job on someone already running behind while a peer sits with room.

Branch four: pairing, training, and stretch jobs

If a junior is ready to grow, a moderate-difficulty job is a deliberate training assignment, sometimes paired with or backed by a senior on call. You are building capacity for next year. Just do it on purpose, not by accident, and not on a job where a failure damages the customer relationship.

If the job is high-stakes (a key account, a difficult customer, a do-not-mess-this-up situation), send your most reliable tech regardless of the optimization above. Some jobs are about protecting the relationship, and that outranks route efficiency.

When the ideal tech is not available

You will not always have the perfect match free. Work the fallbacks in order:

1. Reschedule into the qualified tech's next window if the job can wait and truly needs that person.
2. Pair a junior with phone support from a senior for a job slightly above the junior's level.
3. Reshuffle the day to free the right person if the job is urgent and skill-critical.

The wrong fallback is sending someone who cannot do the work just to fill the slot. An unfinished job is worse than a rescheduled one, because now you owe a return trip and an apology.

Quick reference

References

• Trade-standard dispatch and workforce-routing practice for field-service operations.
• See related: The Double-Booked Schedule Decision Tree.
• See related: The Warm Handoff: Office to Tech.