Czas czytania: 8 minut
Mandatory training recertification: how to decide who needs retraining when the rules change
When a procedure changes, training that is already completed stops being evidence of anything. The record still says "completed" while the person learned something else.
In March a procedure changes on a production line. In April the training team updates the module. And then comes the question nobody had on the agenda: the 800 people who already completed it on the previous version, do they have to do it again?
It's an uncomfortable decision because both answers cost money. Retraining everyone for any change burns production hours and credibility. Training nobody leaves a record saying "completed" over content that no longer describes what people have to do.
Here we give you the criteria to decide case by case, what the law says about when there's an obligation to repeat, and how the record has to look to survive an inspection.
In occupational risk prevention the law is clear: it requires training workers at the point of hiring and also "when changes occur in the functions they perform or new technologies or changes in work equipment are introduced".¹ The same article adds that training must adapt to the evolution of risks and be repeated periodically, if necessary.
That "if necessary" is where the real discussion lives. The rule sets the trigger (a change of function, of technology or of equipment) but doesn't say how many people or at what depth. And outside prevention, in quality or compliance, frameworks like ISO 9001 or ISO 45001 don't set a deadline either: they require the organisation to determine the competence needed and retain evidence that it exists.
That's where the practical rule we use to separate cases comes from:
A change that modifies what a person has to do requires retraining. A change that only modifies how what they already did is documented, doesn't.
Applied in order, they resolve most cases without escalating the decision to the leadership team.
If the operator is going to press a different sequence, use different protective equipment or apply a different acceptance criterion, there's a change in behaviour and the training has to be updated. If what changes is the form where they log it, the document code or the name of the person responsible, it's a documentary change and a documented communication is enough.
The most expensive confusion in mandatory training is treating both as the same event and launching a full refresher campaign over a change to a document template.
Not every modification carries the same weight. If the point that changes is the one where a mistake turns into an accident, a non-conformity or a customer claim, retraining stops being optional even when the change is small.
A temperature threshold, a waiting time before intervening, or the order of two lockout steps are one-line changes that justify retraining the whole affected group.
This is the one that usually decides the case and is almost never asked. There are changes where the previous training simply falls short, and others where the previous training actively teaches people to do it wrong.
When the old version contradicts the new one, the priority isn't training, it's unlearning. And that calls for an explicit message about what has changed, not for resending the updated module and hoping someone notices the difference.
| Type of change | Who it affects | What has to be redone | Reasonable deadline |
|---|---|---|---|
| Documentary (format, codes, owner) | Nobody | Communication, no new record | Immediate |
| Addition (a step is added without altering the previous ones) | Only the group performing that step | Short specific module | Before the next affected shift |
| Replacement (the way something is done changes) | Everyone trained on the previous version | Full module and new record | Before the procedure applies |
| Contradiction (what came before is now incorrect) | Everyone, as a priority | Change notice plus module and check | Before the effective date |
| Regulatory with a deadline (new legal obligation) | The scope the rule defines | Module, record and archived evidence | Before the legal deadline |
The column most often neglected is the last one. A reasonable deadline isn't when the training team has capacity, it's when the procedure starts to apply. When those two dates don't match, a window opens in which the workforce works to one version and the record documents another.
Repeating the training without fixing the record solves half the problem. What an inspector or an auditor asks for isn't a certificate, it's being able to reconstruct what each person knew on a specific date.
In practice that means three things:
This is where the problem stops being administrative. If updating the content takes weeks of production, the temptation is to skip versioning and apply the change "at the next annual review", which is exactly the gap that later shows up in the audit. That's why the content update cycle and the record cycle have to run at the same pace, something training platforms like Vidext resolve by regenerating the module from the source instead of re-recording it. We cover the mechanics of that update in our guide on how to update video training without re-recording.
Most organisations manage mandatory training on annual logic: planned in January, delivered through the year, closed in December. But procedures don't change in January. They change when they change, and each of those moments opens a gap between what the workforce knows and what the record claims.
Deciding well isn't retraining everyone just in case, nor waiting for the annual review. It's having written criteria, applying them the day the change is approved, and leaving the record able to explain itself. In the end it's the same root that shows up in the data behind the state of AI-powered corporate training in Spain, where content arrives late to the procedure: when that distance stretches, the record ends up telling a story that is no longer true.
Yes, when the change affects the worker's functions, the technology or the work equipment. Spain's Occupational Risk Prevention Act requires it explicitly, and adds that training must adapt to the evolution of risks and be repeated periodically if necessary.
Prevention regulations don't set a general interval: they set triggers. Renewal is activated by a change of function, technology or equipment, not by the passage of time. Some collective agreements and sector-specific rules do establish set frequencies, so it's worth checking the framework that applies to each role.
Only when the change extends what came before without contradicting it. If the new version corrects something that used to be taught differently, you have to flag explicitly what has changed, because the risk isn't that the person doesn't know, it's that they apply what they learned before.
No. It's closed with its date and kept. Historical traceability is what lets you evidence what training a person had at the time of an incident that predates the change, and overwriting it leaves the company without that evidence.
Completing evidences that the person went through the content on a date. Being recertified evidences that they did it on the current version of the procedure. When the procedure changes, the first remains true and stops being enough. We cover this in our guide on how to ensure your workforce completes mandatory training.
Program wspierania zatrudnienia na czas nieokreślony wykwalifikowanych osób młodych w ramach Krajowego Systemu Gwarancji dla Młodzieży. Otrzymano od LABORA (Walencka Służba Zatrudnienia i Szkoleń) dotację z wyżej wymienionego programu na zatrudnienie na czas nieokreślony w 2024 r. wykwalifikowanych osób młodych zarejestrowanych w Krajowym Systemie Gwarancji dla Młodzieży; działanie kwalifikuje się do współfinansowania z Europejskiego Funduszu Społecznego Plus (EFS+) 2021-2027 lub innego funduszu Unii Europejskiej. Expediente ECOGJU/2024/550/46.
