A new machine is installed. A digital system replaces a manual process. An AI-powered tool starts assisting with daily operations.
The change may look straightforward from the management side: introduce the technology, provide training, update the procedure, and get back to work.
But there is another question worth asking:
“Can the people doing the job still perform it safely and effectively with the new system?”
This is where the discussion around K3 competency gaps becomes important.
A worker may have years of experience, understand the previous process inside out, and have completed all required training. Yet, when the task changes, the skills that were once sufficient may no longer cover what the job now requires.
The issue is not necessarily that workers are becoming less capable. The job itself has changed.
Technology does not always create completely new jobs. More often, it changes what people need to do within existing roles.
Consider a machine operator.
Previously, the role may have focused on operating equipment manually, monitoring physical conditions, and responding directly to the machine.
After automation is introduced, the same operator may need to:
The job title has not changed, but the task profile has. That distinction matters for K3 because different tasks can involve different hazards, decision-making requirements, and controls.
If competency requirements remain based on the old task, a gap can develop without immediately appearing on the organizational chart.
A competency gap is the difference between what a worker currently knows or can do and what is actually required to perform a task safely and effectively.
It can involve knowledge, technical skills, practical ability, decision-making, or behavioral competencies.
In a changing workplace, competency gaps can appear when:
Importantly, a competency gap does not automatically mean that a worker is unqualified. Sometimes, the worker is highly competent for the previous version of the job. The problem is that the job has moved forward.
This is one area that companies often need to look at more carefully.
A worker may have attended a training session, signed an attendance sheet, and passed a knowledge test. Those are useful indicators, but they do not necessarily prove that the worker is competent to perform a changed task.
Training answers:
“Has the worker been taught?”
Competency asks:
“Can the worker apply what they have learned correctly in the actual job?”
The distinction becomes particularly important when technology changes the way work is performed.
For example, introducing an automated system may require more than explaining which buttons to press. Workers may need to understand system limitations, recognize abnormal conditions, respond to alarms, and know when not to rely on an automated recommendation.
That capability needs to be assessed in the context of the actual task.
Competency should not be separated from risk assessment.
When a task changes, the company should also consider whether the associated hazards and risk controls have changed.
A useful way to look at the relationship is:
New Technology → New Task → New Competency Requirement → New Risk Considerations
For example, a company introduces a digital monitoring system to reduce manual inspection. The technology may reduce one type of physical exposure. But it can also introduce new challenges:
The technology itself is not necessarily the problem. The gap between what the technology requires and what the worker is prepared to handle can become a K3 concern.
One practical step companies can take is to review competency requirements whenever there is a significant change in work.
Instead of starting with the question, “What training should we provide?”, start with:
“What has changed in the task?”
From there, companies can identify the competencies that are now required.
For example:
This approach helps prevent training from becoming a routine activity disconnected from actual work.
The goal is not to provide more training simply because technology has changed, the goal is to provide the right competency development for the new task and its risks.
Another common challenge is assessing competency based solely on job titles or existing training matrices, a more useful approach is to look at the actual work.
✓ What does the worker do?
✓ What decisions do they make?
✓ What equipment or technology do they interact with?
✓ What can go wrong?
✓ What level of response is expected when something goes outside normal conditions?
These questions help connect competency assessment with the realities of the workplace.
For K3, this is particularly relevant for tasks involving:
A competency matrix should therefore be treated as something that can evolve, not simply a document prepared once and reviewed annually.
A competency gap does not automatically lead to an incident, but when an employee encounters a situation they were not prepared to handle, the margin for error becomes smaller. The risk can become more significant when several factors occur at the same time.
For instance: New equipment + unfamiliar task + unclear procedure + insufficient training = greater potential for error.
This is why competency should be considered as part of the broader risk control process. Engineering controls, procedures, PPE, and other safeguards remain important. But people still interact with those controls.
If workers do not understand how a control works, when it should be used, or what to do when it fails, the effectiveness of the control can be compromised.
Closing a competency gap does not always mean sending everyone to another classroom training. Depending on the risk and the nature of the task, companies may need a combination of approaches:
This last point is increasingly important as technology continues to evolve.
The question is no longer simply whether workers are “trained”.
A more relevant question is whether they remain competent for the work they are actually doing today.
Technology may change equipment, processes, information flows, and decision-making. Each of those changes can affect the skills required to perform a job safely.
For companies, this means K3 management and competency management cannot operate in separate lanes. When a new technology or process is introduced, competency should be part of the discussion from the beginning, not something addressed after the system is already running.
Because a technically successful implementation is not necessarily a safe one. The technology may be new. The job may be new. And the competency requirement may be new too.
That is why keeping worker competency aligned with changing tasks is an important part of managing K3 risks.
Technology will continue to change how work is performed. The challenge for companies is making sure worker capability keeps pace with that change.
A useful starting point is to review three things together:
✓ What has changed?
✓ What new risks does it create?
✓ What competencies are now required?
From there, training and competency assessment can be designed around the actual needs of the workplace.
Foresta Consulting can support companies in reviewing K3 risks, competency requirements, and training needs so that worker capability stays aligned with changing work processes.
If your company is introducing new technology, equipment, or work methods, let’s assess whether your current competencies are still fit for the job.
