Assigning the Right Technician: Skills Matrices Without the Bureaucracy

Certifications are the easy half and they decide almost nothing. What predicts a good assignment is 3 things a certificate does not carry: which manufacturers somebody knows, which equipment they have actually attended, and what they are slow at, which is scheduling information rather than a judgment.

The short version

Every service company that builds a skills matrix builds the same one: a grid of technicians against certifications, filled in once, and consulted rarely.

It is not wrong and it answers a narrow question: who is legally allowed to do this work. That matters for refrigerant handling and manufacturer accreditations and it is the smaller part of the decision.

The larger part is competence and familiarity, which no certificate records and every dispatcher knows informally. Making that usable without building a bureaucracy is the actual problem.

The 4 layers of a useful matrix

Layer	What it answers	How it stays current
Certifications with expiry dates	Who may legally do this	A reminder before each expires
Manufacturer accreditations	Who may do warranty work for whom	The same, plus when a new one is gained
Equipment categories	Who is competent on fryers, refrigeration, warewashing	Reviewed twice a year, ten minutes
Equipment actually attended	Who has seen this specific unit	Automatically, from the job history

The fourth layer is the one that requires no maintenance at all and is the most useful of the four. If jobs attach to equipment, the system already knows who has been to each one.

Layer 4 costs nothing and answers the best question

Who has been to this equipment before is a query rather than a matrix.

Roopairs holds equipment records with service history that jobs attach to, which means the assignment question "has anyone here seen this unit" is answerable from the record rather than from somebody's memory.

That is worth more than the certification grid on most jobs, because familiarity with a specific piece of equipment is what shortens a diagnosis, and the person who fixed it eighteen months ago knows things nobody wrote down.

It also degrades gracefully. Where nobody has attended that unit, the next question is who has attended that model, which is the same query at a wider scope.

Layer 3 is the one that needs judgment

And it is where matrices become bureaucratic if you let them.

Rating people on equipment categories is useful and it invites over-engineering. A five point scale across thirty categories produces a document nobody updates and everybody distrusts.

What works instead: three levels, across six or seven categories.

• Can work unsupervised, which is the only level that matters for dispatch
• Can work with support available, which is the training state
• Not yet, which is a plan rather than a judgment

That is a grid of maybe fifty cells for an eight technician service company. It takes twenty minutes to fill in and ten minutes twice a year to review, and it answers the dispatch question adequately.

What a matrix should never be used for

Two uses that end its usefulness, and one is tempting.

Ranking people. A matrix describes coverage, not quality. Somebody strong across four categories and unrated in three is not worse than somebody adequate across seven, and comparing them on the grid says nothing about either.

Pay decisions, silently. If skills are going to influence pay, that is a separate conversation held openly. Introduced as a dispatch tool and used for pay, the ratings become negotiated and stop being accurate.

The moment either happens, the matrix reflects what people want recorded rather than what is true, and its dispatch value is gone.

Record what people are slow at, not just what they can do

The half nobody writes down and the half that improves scheduling.

Somebody excellent at refrigeration diagnosis who is slow on paperwork needs a different slot length, not a different job. Somebody quick on routine work who struggles with unfamiliar controls should get the volume and not the unknowns.

That is not a criticism recorded about a person. It is scheduling information, and treating it as such makes it sayable.

The practical version: alongside the category ratings, one line per technician about where their time goes differently. Reviewed with them rather than about them, which also surfaces the training they would actually find useful.

The trap: the specialist nobody else can replace

A matrix makes this visible and it does not fix it.

Most service companies have one person who is the only one competent on a piece of equipment category or a manufacturer. Dispatch naturally routes that work to them, which keeps everyone else unrated, which reinforces the routing.

The cost appears when they are on vacation, and again when they resign. It is also invisible until then, because the schedule works.

The fix is deliberate and slightly inefficient: send somebody else with time allowed, on a job that can absorb it. A service company that never does this is accumulating a risk that the matrix is quietly documenting.

How to build one in an afternoon

Four steps, and none of them is a project.

1. List certifications with expiry dates, which you probably already hold somewhere, and set reminders
2. Name six or seven equipment categories that match how your work actually arrives
3. Rate each technician three ways per category, with the technicians in the room rather than about them
4. Check what the job history already tells you about who has attended which equipment, because that layer exists whether or not you built it

Then review it twice a year and whenever somebody gains an accreditation. That is the whole maintenance burden, and it is why this version survives while a thirty-category one does not.

Where this changes the dispatch decision

Two moments, and both are daily.

On an unknown fault, where familiarity with the model is worth more than proximity and the matrix plus the job history answers who has it.

And on warranty work, where a manufacturer accreditation is a hard requirement and an expired one discovered afterwards is an unpaid claim.

Everything else is a tiebreak. The pain starts around your third or fourth technician, which is also the point at which a dispatcher stops knowing all of this without looking.

Roopairs runs a product tour where you can see equipment records and service history behind the dispatch board.

What service companies in the trade say

“From an accounts receivable point of view, I couldn't be happier. This platform has transformed the way we process jobs and get invoices out to our customers. And, the integration process with QuickBooks was extremely simple.” — Sarah Bendele

Also worth reading

• Field Operations Software
• How to Dispatch: Skills, Location and Parts
• Why field service technician productivity starts on the job site

Frequently asked questions

What should a skills matrix record?

Certifications with expiry dates, manufacturer accreditations, competence across six or seven equipment categories, and which equipment each person has actually attended. The last layer needs no maintenance if jobs attach to equipment.

How detailed should the ratings be?

Three levels across six or seven categories: can work unsupervised, can work with support available, or not yet. A five point scale across thirty categories produces a document nobody updates.

What is the most useful layer?

Who has attended this specific equipment before, because it is a query rather than a matrix and familiarity with a unit is what shortens a diagnosis. Where nobody has, the next question is who has seen that model.

What should a matrix never be used for?

Ranking people or influencing pay silently. Either use turns the ratings into something negotiated rather than accurate, and the dispatch value disappears immediately.

Should you record what people are slow at?

Yes, as scheduling information rather than as criticism. Somebody excellent at diagnosis and slow on paperwork needs a longer slot rather than a different job, and treating it that way makes it sayable.

What risk does a matrix reveal?

The specialist nobody can replace. Dispatch routes work to the only competent person, which keeps everyone else unrated and reinforces the routing. The cost appears when somebody takes vacation and again at a resignation.