The assignment that fails before the truck rolls

A dispatcher under pressure assigns by one question: who's open? The job goes to whoever's name has a gap on the board, the truck rolls, and then the visit fails — not because the tech was lazy or the part was missing, but because the tech simply couldn't do that work. The job needed a refrigeration cert, or a panel upgrade the tech had never touched, or a diagnostic specialty they didn't have. The customer waited, the tech drove out, and now you're rolling a second truck with the right person on it. The assignment was wrong before anyone turned a key.

Skill mismatch is one of the quietest causes of a failed first visit, because it doesn't look like a mistake on the board. The slot was open, the tech was qualified on paper to be a tech, the job got assigned. The gap only shows up at the customer's door, which is the most expensive place to discover it. Matching the right tech to the right job — by capability, not just availability — is what keeps that gap off the board in the first place.

Why "who's free" isn't enough

Availability is necessary but not sufficient. A good assignment satisfies several constraints at once, and skill is the one most likely to get dropped under pressure:

  • Capability. Can this tech actually complete this job — the cert, the license, the hands-on experience? Get this wrong and nothing else matters.
  • Location. The closest qualified tech, not the closest tech, so you're not driving a specialist across town when a nearer one could do it.
  • Slack. Enough room in their day to take the work without blowing the next window.
  • Right-sizing. A senior specialist on a routine filter swap is wasted capacity; a junior on a job over their head is a callback. Match the difficulty to the person.

When a dispatcher juggles all four in their head at 8 a.m. with the phone ringing, skill is the one that slips — because availability is visible on the board and capability is buried in the dispatcher's memory of who's good at what. The fix is to make capability as visible as availability.

Put skills on the board, not in someone's head

The reason skill-matching fails isn't that dispatchers don't care who's qualified — it's that the qualification data lives in their head, and heads forget, take vacations, and quit. The skills have to be on the tech, on the board, visible at the moment of assignment.

In Hosting Field, the technician roster carries skill tags on each tech, and the dispatch board shows the day per technician with an unassigned queue — so when a job needs a capability, the dispatcher is assigning against visible skills, not a mental model of who can do what. The same board warns before you double-book, so the qualified tech you pick still has the room to take the work. Capability and availability sit in the same view, which is exactly where the assignment decision happens. The senior tech's specialties aren't tribal knowledge anymore; they're data on the board that survives the dispatcher's day off.

Skill data pays off past dispatch

Tagging skills isn't only an assignment aid — it surfaces problems you can't otherwise see:

  • Coverage gaps. When one tech is the only person tagged for a critical skill, you've found a single point of failure. The day they're out, that work can't ship. Skill tags make the gap visible before it strands a customer, so you can cross-train ahead of it.
  • A training roadmap. The skills your job volume demands, mapped against the skills your roster has, is a cross-training plan written in your own demand data — and a career path is one of the things that keeps good techs.
  • Honest right-sizing. Seeing skills on the board lets you stop wasting a specialist on routine work and stop overfacing a junior, which protects both your margin and your first-time fix rate.

Don't over-tag it into uselessness

A caution: a skill system with eighty granular tags is as useless as none, because nobody maintains it and the dispatcher can't reason about it under pressure. The point is a short, honest list of the capabilities that actually gate an assignment — the certs and specialties where sending the wrong person means a failed visit. Tag the distinctions that change who can do the job, skip the ones that don't, and keep the list current. A handful of meaningful tags a dispatcher trusts beats an exhaustive taxonomy nobody updates.

This is also where skill-based dispatch meets the emergency lane: when a same-day call lands, the right tech is the closest qualified one with slack — and you can only make that call fast if the skills are already on the board.

What to measure

  • First-time fix rate by job type — a low FTFR concentrated in specific job types often means those jobs are going to under-skilled techs. The pattern points straight at the mismatch.
  • Reassignment rate — how often a job gets bounced from one tech to another after the first assignment. High reassignment means the first pick was wrong, and skill is a common reason.
  • Skill coverage depth — how many techs can perform each critical job type. A "1" anywhere is a single point of failure and a cross-training priority.

The board's open slots tell you who can take a job. They don't tell you who can do it — and the difference is a failed visit, an angry customer, and a second truck roll. Put the skills where the assignment decision happens, match capability before availability, and the wrong-tech visit stops being a thing you discover at the customer's door.