Polyvalence table vs competency matrix: what is the difference?

Manufacturing calls it a polyvalence table, quality calls it a competency matrix. Most of the time they mean the same thing — but there are three places where they differ, and those three surface in an audit.

Two different tables circulate in the same plant. On the production manager's wall there is a table of lines and operators with colored squares at the intersections: a polyvalence table. In the quality department's file there is a table of competencies and people with scores at the intersections: a competency matrix.

Most of the time both answer the same question: who can do which job? But they diverge in three places, and the divergence is usually noticed on audit day.

Short answer

Polyvalence looks at how many different jobs a person can do — it measures flexibility. A competency matrix looks at at what level and on what evidence a person can do a job — it measures proficiency. The first is a planning tool, the second an evidence tool. A well-built system derives both from the same data.

Difference 1 — Polyvalence measures breadth, the matrix measures depth

The polyvalence table asks: "how many people can run this line?" The goal is flexibility. If an operator can work three stations, polyvalence is high, and that helps when planning shifts, approving leave or covering a breakdown.

The matrix asks something else: "how well does this person do this job?" Under supervision, independently, or well enough to teach? The same person may work three stations but only under supervision at all three. The polyvalence table shows three green squares; the matrix shows three "2"s. They are not the same fact.

Difference 2 — The matrix expects evidence; polyvalence usually does not

In a polyvalence table a square gets colored. Who colored it, on what basis and when is often not recorded, because the table exists to plan, not to prove.

In a competency matrix every score is expected to rest on something: a training record, an exam result, a certificate, a field observation. The auditor's question is not "do you have a table" but "how do you know this person is competent" — and a colored square does not answer that.

Difference 3 — Time: polyvalence freezes, competence expires

This is the most overlooked difference. A polyvalence table is usually undated: colored once and left. Competence, however, has a shelf life — certificates expire, refresher intervals come due, people go months without doing the task.

In a competency matrix every record needs a validity period, and when it lapses the record must drop by itself. Otherwise the table keeps presenting an expired competency as valid. This is where audits produce the most findings: the record is not wrong, it is merely stale and nobody noticed.

So which one should you build?

Wrong question. Both come from the same data:

• Build the job-to-competency mapping: what does working this station require?
• Score people on levels (not competent / supervised / independent / can teach) and attach evidence.
• Give every competency a validity period.

With those three, a polyvalence view can be derived: the number of stations where a person is at "independent" level is their polyvalence. The reverse does not work — you cannot recover levels and evidence from colored squares.

Three more things that get conflated

• Authorization is not competence. Authorization is being permitted to do the work; competence is being able to. Someone competent may lack authorization — and someone authorized may lack competence, which is the risk.
• Training is not competence. Attending training is not evidence; an assessment and a decision must follow.
• A certificate is not competence. It is evidence of it. An expired certificate stops being evidence, though the person's knowledge has not vanished — which is why refresher training is shorter than initial training.

Summary

Polyvalence answers "how many jobs", competence answers "at what level and on what basis". You need the first to plan shifts and the second to face an audit. Build the matrix with levels and evidence and you can derive the polyvalence view from it; the reverse does not work.

Frequently asked questions

How is a polyvalence rate calculated?

The common method divides the number of stations where a person works independently by the total number of stations. With a levelled matrix this is derived automatically: "independent" and above count, supervised does not.

Is a polyvalence table accepted in an audit?

On its own, usually not. An auditor looks for the competency criterion, evidence that the person meets it, and proof the record is current. A colored square shows none of these.

Do the two tables need to be kept separately?

No, and it is not advisable. Two tables produce two versions of the truth and soon nobody knows which is right. Keep the levelled matrix as the single source and derive the polyvalence view.

Is a skill matrix the same thing?

In practice yes — "skill matrix" and "competency matrix" describe the same structure. Terminology varies by industry; the structure and the needs do not.