The training matrix every small service should have

Strip away the extra columns most templates carry. Four are doing the work.

Who. Named individual, not role. Roles move. People are who actually completed training. A matrix organised by role gives you no way to know that the new starter who replaced the previous holder is or is not trained.

What training.Specific module name, not category. "Safeguarding" is a category; "Level 3 Safeguarding Adults, e-learning module v2.1" is a specific training. The specific module matters because an inspector can verify whether the module covers what their question needs covered.

When last completed.Date, not year. A matrix that records "2025" for completion cannot tell you whether the training was in January or December. The cadence question (is this person up to date?) depends on the precise date.

When next due.Date, derived from the training's renewal cycle. Some training is annual, some triennial, some one-off with no renewal. The matrix should hold the renewal logic so that the next-due date is calculated, not typed.

Four columns. Anything beyond these (location, evidence file link, who verified the competency assessment) is useful but not load-bearing. A matrix with just these four columns, kept current, is more useful than a matrix with twelve columns most of which are blank.

An admin person in the service needs a different set of required trainings from a clinician, who needs a different set from a nurse, who needs a different set from the registered manager. The matrix should hold the required-training set per role, and then track each named individual against the set their role requires.

Without this, you end up either over-requiring everyone (the admin person has to complete BLS resuscitation training they will never use) or under-requiring some (the clinical lead is missing prescribing-safety training because the matrix only carried the cross- organisation minimum). Both shapes break the matrix as a useful tool.

The mechanics: define the roles in your service (admin, care assistant, nurse, clinician, prescriber, registered manager, and so on); attach the required training set to each role; when a new person joins, their role automatically inherits the required set; when their role changes, the required set re-derives. The individual record then tracks completion of each required training in that set.

Each role's required-training set is drawn from a broader catalogue. Sector-specific catalogues vary; the cross-sector spine of categories is roughly consistent. For a healthcare service in England, the catalogue should at minimum cover:

• Safeguarding (adults and children, at the level appropriate to each role)
• Mental Capacity Act and DoLS where applicable
• Infection prevention and control
• Resuscitation (BLS or ALS, at the level appropriate to each role)
• Information governance and data protection
• Equality, diversity and human rights
• Fire safety and evacuation procedures (site-specific)
• Manual handling (where applicable)
• Conflict resolution and lone working
• Role-specific clinical training (e.g., medicines management for prescribers, decontamination for dental nurses, end-of-life care for adult social care staff)

Plus any sector-specific or contract-specific requirements (NHS framework agreement, provider-specific clinical governance training, professional-body CPD requirements for individual registrants). Each of these attaches to the roles that need it, not to everyone.

For a service with eight staff across four roles and twelve trainings in the catalogue, the actual matrix (only required training × person) is much smaller than the full catalogue × person grid. Per-role attachment keeps it that way.

Update the matrix when training completes, not at the annual review. The annual review is for catching what got missed; the day-to-day update is for keeping the matrix current.

The pattern that works: when a staff member completes a training, the certificate or completion record gets filed AND the matrix cell gets updated in the same action. If those are two separate actions that depend on someone remembering, the matrix drifts.

The matrix should also produce a forward-looking view: what training is due in the next four weeks, what is overdue right now. Without this, the matrix is a record of the past rather than a tool for the future. With it, the matrix tells the manager what training to book this month.

Inspectors look at the matrix for three things, roughly in this order.

Is it current?A matrix six months out of date reads as "we do not track this". Currency is signalled by recent update dates against multiple cells, not by the year on the header.

Is it credible?A matrix with zero overdue rows and zero gaps reads as "this matrix is not honest". Real services have some overdue rows. The credible matrix has overdue rows with a plan against each (booked, cancelled, rescheduled, awaiting external course) rather than zero overdue rows.

Does it match the staff on duty? If the inspector walks the service and meets a clinician who is not on the matrix, the matrix is not real. If the matrix lists a clinician who left six months ago, same. The cross-check between the staff list and the matrix is one of the cheapest checks the inspector does.

A service that keeps its matrix current and honest is demonstrating, in one document, that it tracks staff competence systematically. That tracking is the foundation of Well-led. Without it, the service is relying on the manager's memory to know who can do what. With it, the service has a record that anyone covering for the manager can read.

The matrix is also the first place inspectors see whether the service treats records as live tools or as paperwork artefacts. The pattern is consistent: services with a current and honest matrix are usually well-led on the other categories too. Services with a stale or implausibly clean matrix usually have the same problem elsewhere.

Training matrix is one of the new lifecycles being added to Verivius v1. The architecture matches the shape above: required trainings are attached to roles, individuals inherit the required set from their role at onboarding (and re-derive when their role changes), and completion is tracked per person against their role's required set. Sector packs ship default role-to-training mappings (so a Verivius dental practice gets the dental nurse, hygienist, dentist, and practice manager defaults out of the box, customisable per tenant). The dashboard surfaces overdue and approaching-due trainings, scoped to the requirements that actually apply to each person. Currently in active build; dental and ASC sector packs are the first sectors getting it.