A skills matrix is a grid. People down the side, capabilities across the top, a mark in each cell showing whether that person can do that thing and how well.
It is one of the oldest tools in workforce management and one of the most consistently disappointing, for a reason that has nothing to do with the format: the grid is easy and keeping it true is not.
What actually goes in one
Rows: people. Everyone whose capability matters for the work you have to deliver. On a contracting company site that includes labour hire and subcontractors, not only direct employees — a capability you are relying on is a capability you need to see, whoever employs it.
Columns: capabilities. This is where most matrices go wrong, in one of two directions.
Too broad — "Excavator", "Welding", "Confined space" — and the matrix cannot answer any real question. Two people marked competent at "Excavator" may be competent on entirely different classes of machine doing entirely different work.
Too granular — a column per make and model — and you get a grid nobody can read and nobody maintains.
The usable middle is the task as the site actually assigns it. "Excavator, 30–50t, trenching near services." "Confined space entry, standby person." "Isolation, electrical, LV." If the column matches how work is allocated, the matrix becomes a rostering tool. If it does not, it becomes a wall chart.
Cells: a proficiency level, not a tick. Four levels usually works:
- Not competent — cannot perform the task.
- Competent with supervision — can perform under direct supervision.
- Competent independently — can perform unsupervised to the required standard.
- Can train and assess — competent, and able to develop and verify others.
Three levels loses the distinction between 3 and 4, which is the one that tells you whether the capability can be reproduced. Five or more produces endless argument about the middle bands.
Define each level in observable terms. Without definitions you will get five supervisors rating the same person differently, and the matrix will quietly become a record of who each supervisor likes.
Skills, training and competency matrices
These three terms circulate as if interchangeable. Two of them nearly are; one is genuinely different.
| Answers | Source of truth | |
|---|---|---|
| Training matrix | What training has each person completed, and when is it due again? | Course records, statements of attainment |
| Skills matrix | What can each person actually do, and to what level? | Assessment, observation, supervisor rating |
| Competency matrix | Same as skills, with assessment against a defined standard implied | Formal assessment records |
"Skills matrix" and "competency matrix" are used interchangeably in practice and nobody will misunderstand you. Where people draw a line, competency implies assessment against a defined standard; skills can include self-rating.
The training matrix is genuinely different, and the distinction matters more than it sounds. Training completion is an input. Capability is the outcome. A person can have completed the training and not be capable — which is the entire reason verification of competency exists as a separate exercise. A business that treats its training matrix as its skills matrix is asserting that everyone who did the course can do the job.
What the matrix is actually for
Not compliance. Compliance evidence lives in the underlying records — the statements of attainment, the VOC forms, the licences. Nobody is prosecuted for having a bad grid.
The matrix is for seeing things you cannot see from a list of records:
Single points of failure. A column with one name in it is the thing that stops your operation when that person resigns, gets injured, or takes the leave they are owed. This is the single most valuable output of a skills matrix and the reason to build one even if nobody has asked.
Coverage against demand. You need four people who can do X on a shutdown. You have six who can, two of whom are on the same crew rostered elsewhere. The matrix makes that visible before the roster does.
Where to spend training money. Not on whoever asks, but on the columns that are thin.
Succession and progression. Who is one step from level 3, and what is the step.
Bid capability. Whether you can honestly say yes to a scope of work before you commit to it.
Why most of them stop being true
Every manually maintained skills matrix is accurate on the day it is built and decaying from the next morning. The decay has specific causes and they are all mundane:
- Someone's ticket expires and nothing in the spreadsheet knows about dates.
- Someone leaves and the row stays.
- A new starter is added to payroll and not to the matrix.
- A client changes a requirement and the columns no longer match what is being asked for.
- A new machine arrives and there is no column for it.
- The person who maintained it changed roles and the file was never handed over properly.
The pattern underneath all of these is the same: the matrix is a derived view being maintained as if it were a source of truth.
Capability is not really a grid. It is a consequence of a set of facts — this person holds this ticket which expires on this date, was verified on this machine on this date, has this medical current until this date. The grid is a way of looking at those facts. When it is typed by hand it becomes a second copy of the truth that immediately begins to disagree with the first.
The fix is not a better spreadsheet. It is holding the underlying credentials as dated records and generating the matrix from them, so that a ticket expiring changes the grid without anyone remembering to change the grid.
Making one that is actually useful
If you are building from scratch:
- Start from the work, not the people. List what the operation has to be able to do, in the terms work is allocated in. That gives you the columns.
- Set the required level per column — how many people at level 3, how many at level 4. A matrix without a target tells you the state and not whether it is good enough.
- Populate from evidence, not from memory. Every cell above "not competent" should trace to something: a statement of attainment, a VOC, an assessment record.
- Put dates on everything. A capability with no currency date will be wrong within a year and you will not know when.
- Show the gaps as the headline. The most useful version of this document is not the grid — it is the short list underneath it: the columns below required level, and the columns with one name.
- Decide who owns it, and how it gets updated when a person or a requirement changes. If the answer is "someone will remember", you have built a wall chart.
For contracting companies specifically
There is a version of this that matters more than the internal one: the matrix per client site.
A worker who is fully capable for one client's site may not meet another's requirements with the same qualifications, because sites differ in what they demand — different inductions, different medical requirements, different VOC currency periods, different plant standards.
A single global matrix will tell you someone is competent. It will not tell you they can go through that gate on that day. That is a different grid, and it is the one your operations team actually needs at five thirty in the morning when somebody calls in sick.
