Technician Dispatch Software: Assigning Jobs by Skill and Route

Dispatching is the moment a shop decides how its day goes. Every call that comes in has to land on a technician, and there are two ways to get it wrong: send the wrong person, or send the right person to the wrong place. Skill and route. Get both right and the day runs itself; get either wrong and you're paying a specialist to drive, or driving a generalist back to the shop for a tool nobody thought to check.

The two questions behind every dispatch

Strip away the software and dispatch is two questions asked in a specific order:

1. Who can do this job? Not who's free — who is actually qualified, equipped, and cleared for this machine and this repair.
2. Of those, who can get there? The nearest qualified tech, given where they already are and where they're already committed.

Most shops answer them in the wrong order. They look at the board, find a hole, and drop the job in — then discover the tech in that hole has never touched a final drive. Skill is the gate; proximity is the tiebreaker. Software that treats them as one blended score will quietly send your hydraulic specialist out to change oil.

Build the skill grid before you dispatch anything

You cannot assign by skill if the skill lives in your head. Write it down — a simple grid of technicians against the work your shop actually sells:

• Machine types — excavators, loaders, dozers, skid steers, trucks, cranes
• Systems — hydraulics, powertrain, electrical, diesel engine, undercarriage
• Certifications and tickets — manufacturer training, welding tickets, air brake, high-voltage for hybrid drives
• Shop-side authority — who can sign off a job, who can approve a repair on site, who can close for review

The grid doesn't have to be elaborate. It has to be honest. A tech marked "hydraulics" who's really only done hose replacements is a mis-dispatch waiting to happen, and the customer pays for it in a second visit.

Route is a constraint, not a suggestion

Once you know who can do the job, distance decides. Three things belong on the screen when you make that call:

• Where the tech is right now — not where they started the day
• What they're already committed to — the rest of today and tomorrow
• The actual drive between the two, not a straight line on a map

A job forty kilometres away at 2pm is a different decision than the same job at 9am. A tech with a three-day rebuild starting tomorrow should not be your emergency call today. If drive time isn't visible on the board, you're dispatching on a calendar that's lying to you — which is exactly why a calendar alone doesn't dispatch a repair shop.

Pair the specialist with the drive

The best dispatch decision is usually not "the closest tech" or "the best tech" — it's the pairing. A few patterns that hold up in real shops:

• Specialist work travels. For a reseal, a diagnostic, or a machine-down call, drive the specialist. The customer is paying for the diagnosis, and the wrong tech on a hydraulic fault costs more in callbacks than the fuel.
• Generalist work clusters. For greases, filter services, and inspections, group them into one route and hand them to whoever's already in that lane. Skill floor, then proximity wins.
• Emergency calls break the rules — deliberately. When a machine is down on a job site, proximity plus "can get it running" beats a perfect skill match two hours away. Send the closest capable tech, and let the specialist guide by phone if needed.
• Keep a shadow on the specialists. Pair a junior tech with a specialist on the complex jobs, and the skill grid grows itself instead of staying a single point of failure.

The trap: your best technician gets everything

If one person is the only name on every dispatch, the shop has a problem the software can't fix. The pattern shows up as one tech with a full board and everyone else idle, one tech on every hard job, and eventually one tech burning out.

The fix is structural: widen the grid. Cross-train deliberately, dispatch to the second-best qualified tech on jobs where the customer won't notice the difference, and keep the specialist's calendar for work that actually needs the specialist. Dispatch software should make that visible — if it can't show you who's overloaded and who's underused, it's a job list, not a dispatcher.

Dispatch is not a broadcast — it's a handoff

The job isn't dispatched when it lands on the board. It's dispatched when the technician has everything they need to run it without calling the office:

• The customer and the machine, with serial number and service history
• The complaint, in the customer's words — not a summary you typed at 7am
• The address, with a map link that works on a phone
• The scheduled time and estimated duration, so the tech can plan the day
• The job-site notes — gate codes, site contact, whether the machine is in a pit or on a pad
• The parts and tools known to be needed, and a flag if a part is still inbound

A tech who has to phone the shop three times before they can start work hasn't been dispatched — they've been notified. And it has to survive a dead zone: the handoff lands on the phone and stays readable offline, because the sites where heavy equipment breaks are the sites with no signal. That's the same offline discipline every mobile work order app needs to get right.

What to demand from dispatch software

When you evaluate a dispatch tool — or audit the one you run — these are the questions that separate a real dispatcher from a drag-and-drop board:

1. Can you assign by skill? A per-tech grid of machine types, systems, and certifications that gates the assignment, not just a free-text "notes" field.
2. Is route a first-class constraint? Current position, existing commitments, and real drive time visible before you commit.
3. Does unassigned work stay loud? A job with a date and no technician should be impossible to miss, on the board and on the dashboard.
4. Does the tech see the whole job, offline? Customer, machine, complaint, address, duration, parts — cached on the phone.
5. Can you see balance across the team? Who's overloaded, who's idle, who's working outside their grid this week.

Fail question one and you'll mis-dispatch until someone notices. Fail question four and your techs will keep running the day off a text message and a screenshot, and the board will be wrong by ten o'clock. For how the routing side of that plays out across a multi-truck shop, see scheduling field service technicians with a map.

The morning test

Take this morning. Could you name, without opening anything, which of your technicians was qualified for each job you sent out — and whether the tech who got it was the closest one who could actually do the work? If the answer is "mostly" or "I think so," the dispatch is living in your head, and it stops working the first week you're on a roof, in a pit, or on a call you can't take.

JSD ServicePro keeps the skill grid, the map, and the calendar over the same work orders — assign by who's qualified, see where that puts the truck, and hand the whole job to the technician's phone, offline. Beta is open: run a real dispatch week on it free and see whether it matches the way your shop already sends work out the door.