A training matrix is a grid of people against tasks. Its value is not the record — it is that gaps and single points of failure become visible the moment you look at a column.
A training matrix is a grid: people down one side, tasks or competencies across the top, and a status in each cell. It answers two questions that are otherwise answered by asking around — who can do this, and what can this person do — and it exposes a third that nobody asked: which tasks only one person can perform.
That third answer is usually why the exercise pays for itself. Every small business has two or three columns with a single mark in them, and every one of those is a holiday, a resignation or an illness away from being a problem.
The can train others level is the most useful column in the whole grid and the one usually omitted. It distinguishes a person who can do the task from a person through whom the capability can spread, and it turns the matrix from a compliance record into a plan — because the fix for a single-point-of-failure column is naming who will teach the second person, and by when.
Matrices die by going stale, and they go stale because updating them is nobody's job. Two things prevent it: tying updates to events that already happen — somebody joins, somebody is trained, a certificate expires — and reviewing it in a meeting that already exists rather than a new one. A quarterly five-minute look at the single-mark columns is enough to keep it honest, and it is the only agenda item the matrix genuinely requires.
Ettex Records holds the matrix with the evidence, dates and expiries as fields you can filter — which matters, because the useful query is show me everything expiring in ninety days rather than a static grid. The gap analysis that decides which columns belong there is training needs analysis, and the neighbouring people-capability view in competency matrix.
The boundary: no course delivery, no automated reminders for expiring certificates, no learning content. The matrix is a register you maintain; the value is in reading it, which no software does for you.
A grid of people against tasks or competencies, with a status in each cell showing who is trained on what, with dates and evidence.
Not trained, trained, competent, and can train others. The last is the most useful and most often omitted, because it shows whether capability can spread.
A training matrix records completed training against specific tasks. A competency matrix describes the level of capability required and held, usually more broadly.
Tie updates to events that already happen — joining, being trained, a certificate expiring — and review it inside a meeting that already exists.
An SLA is a commitment with consequences attached. Most small businesses copy numbers from a competitor and discover later that nobody measures them and nobody could have met them anyway.
A naming convention is worth about ten minutes to write and saves an hour a month forever. The three rules that matter are dates first, no spaces, and no words that mean nothing in six months.
Supplier onboarding is boring paperwork that prevents specific, expensive problems — paying the wrong bank account, discovering an expired certificate mid-project, or having no contract when something goes wrong.