Training matrix: who is trained on what, at a glance

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.

Building one

1. List tasks, not topics. Process a refund, close the month, operate the machine — things somebody either can or cannot do. Fire safety awareness is a topic and tells you nothing about capability.
2. Keep it to the tasks that matter: regulated, risky, or single-person. A matrix with eighty rows gets abandoned; one with twenty gets used.
3. Use a status scale with meaning. Not trained, trained, competent, can train others. The last level is what tells you whether knowledge can spread.
4. Record the date and the evidence. Trained is a claim; trained on this date, signed off by this person, is a record.
5. Add expiry where certification requires it, with a review date attached rather than filed.
6. Read the columns, not just the rows. The single-mark columns are the finding.

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.

What it is for, beyond compliance

• Cover planning: who can step in when somebody is away, decided before the absence rather than during it.
• Recruitment: gaps that persist across the whole matrix are a hiring specification.
• Onboarding: a new person's column is their induction plan, covered in induction training.
• Audits: in regulated work, evidence of who was trained on what and when is frequently a requirement rather than a nicety.
• Fairness: the matrix makes visible who has been developed and who has quietly been left where they started.

Keeping it alive

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.

Where it lives

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.

The matrix says who has been trained. A competency matrix says who can actually do the work, which is a different question and usually a shorter list — it is what tells you when one person is the only one able to run a process.