Most organisations start their competency matrix from the wrong end: the people. The right starting point is the job. A working matrix in six steps.
A competency matrix is a table that shows, at a glance, who is competent to do what. Competencies run down the rows, people across the columns, and each intersection holds that person's level for that competency. It looks simple — yet in practice most matrices are abandoned within six months.
The reason is almost always the same: the matrix was built starting from the people.
If you begin with "what can Ahmet do?", you end up adding new rows for every new employee. The matrix grows, repeats itself, and soon becomes a file nobody opens.
The right question is: "what must someone doing this job know?"
There are far fewer jobs than people, and they change far more slowly. Start from the job and the matrix stays bounded by itself.
"Engineer" is a title, not a job. A job is the work itself: "Boiler maintenance technician", "Forklift operator", "Shift supervisor".
The distinguishing test: if two people do the same work, they hold the same job — even if their titles differ.
Most mid-sized operations end up with 15-40 real jobs. If you have far more than that, you are probably listing titles.
For each job, answer "what must someone doing this be able to do?". Draw the competencies from three sources:
The output of this step is a job-to-competency mapping. Once a person is assigned to a job, what is expected of them is determined automatically.
The most common mistake is picking a 1-5 scale and never defining it. On an undefined scale, "3" means something different to every assessor, and the matrix stops being a measurement.
Four levels are enough for most operations:
Write behavioural definitions for each level: not "can do it", but "can do what, under which conditions". An assessor should be able to read the definition and decide.
Add two status codes as well: Exempt (the competency does not apply to that person) and Suspended (medical leave, change of duty, and so on). Without these two, the matrix miscalculates — exempt cells must not count towards the denominator of the proficiency rate.
What sits behind a score? Decide this before you populate the matrix:
The question asked in an audit is not "do you have a matrix". It is "on what basis did you award this 3". A matrix without an evidence rule is useless in an audit.
Competency is not permanent. Certificates expire, refresher training comes due, and skills not practised for a long time are forgotten.
Set a renewal period for each competency (for example, working at height every 24 months, first aid every 36). An expired score must automatically be treated as invalid.
Skip this step and the matrix will gradually look better than reality — the most dangerous failure mode. 90% proficiency on paper, expired certificates in practice.
A matrix is not a report; it is a work list. Set an organisation-level proficiency target (say 85% on mandatory competencies) and turn the gap cells into a training plan.
Three numbers are enough to review monthly:
There is nothing wrong with building your first matrix in Excel — in fact the six steps above are easy to think through in a spreadsheet. The limit usually arrives here:
At that point the matrix needs to move into a system. Skill Monitoring was designed to implement exactly these six steps: job-competency profiles, a defined scale, evidence attachments, automatic validity tracking, and an audit trail of every change.
You can explore the product's screens without signing in, via the product tour on the landing page.