Mining operations invest significant resources into safety training annually yet still witness serious injuries and fatalities occur to employees who have been deemed to have completed all necessary training. The reason for this gap is that completion records tell us that someone attended a training session, not that they have the ability to, for example, identify a hazard or demonstrate a lockout procedure the following day whilst under duress. Real time data is what closes that gap, it transforms safety training from an administrative exercise, and into a live system that can determine who is competent today when performing a high risk task.
Completion Isn’t Competence
A worker can pass a written test, sign an attendance sheet, and still freeze or make the wrong call when a real hazard shows up. Training completion is a lagging administrative record. It confirms a person was in the room. It says nothing about whether the skill stuck, whether it transferred to the field, or whether it’s degraded since.
This matters more than most training programs acknowledge. Research on the Ebbinghaus forgetting curve shows people lose roughly 70% of newly learned information within 24 hours if it isn’t reinforced or applied. An annual refresher on confined space entry or hazard identification is nearly useless as a safety control by month four or five. The worker is still “current” on paper. In practice, they’ve forgotten most of what they were taught, and nobody knows it until something goes wrong.
Safety skills assurance is the practice of verifying demonstrated competence instead of just tracking hours. It asks a different question than compliance tracking: not “did this person attend,” but “can this person do the task safely, today.” That distinction is the whole argument for real-time data in mining safety.
Leading Indicators Beat Lagging Ones Every Time
Most mine safety programs are still built around lagging indicators, lost-time injury frequency rate, fatality counts, days since last incident. These numbers are useful for regulatory reporting and board slides. They’re almost worthless for prevention because they only move after harm has already occurred.
Leading indicators move first. Assessment pass rates, first-attempt scores broken down by specific competency, near-miss reporting frequency, and the time gap between a worker’s last verified skills check and their current task assignment, these shift weeks before injury rates do. A crew showing declining first-attempt scores on hazard identification is telling you something long before an incident report does.
MSHA compliance requirements set the floor for training obligations, but meeting that floor doesn’t mean your workforce is actually skilled. Operations that want to get ahead of incidents, rather than explain them after the fact, need to track leading indicators as seriously as they track LTIFR. That means building dashboards around competency data, not just injury data, and reviewing them with the same discipline.
Assess Where the Work Happens, Not in a Classroom
Removing operators from their shifts and placing them in a classroom environment to evaluate them on tasks they carry out routinely on the job delivers inaccurate results. People behave differently in a test environment than they do in their actual work environment, using actual equipment, under the pressures of an actual shift, with the actual sounds of production around them.
Field-based, mobile assessment solves this. Someone with a supervisor or training role can, using something as simple as a tablet, check an operator on a task specific checklist right at the job site, while they are undertaking the task. This does not interrupt production for hours, and captures truer, more real-time data because the person is in fact doing the job they are tasked with, as assessments are happening.
The training should be no different. If they can’t constantly recall the need to apply a specific technique in the classroom, they’re not using the technique on the job, determine why and correct that. If they simply forgot it during the refresher, they’ll likely also forget it on shift, and next shift is in 12 hours. Fix it.
Build a Skills Matrix That Supervisors Can Actually Trust
Over the years, mine sites have maintained some form of a skills matrix, but it has generally been a static document, often a spreadsheet, that serves as a record of who has completed training, rather than who has been assessed as competent in a task. The difference may seem small, but in practice, if the only way you know someone is competent to enter a confined space, isolate and lock out energy sources, or work with explosives is because they completed a course last year, then you don’t really have a living, real-time skills matrix.
You do, however, have too many possibilities for an incident. Too many chances that, when a skills matrix finally is called upon to assist with an incident investigation or near-miss analysis, you will find the box marked against the name of an injured person indicates they were not yet assessed as competent for the task in question. That’s why some of the biggest shifts in mining culture in recent years have come from movements toward ‘living’ skills matrices, the Access Mining case study shows how one operator built a system where competency data updates continuously and supervisors must use it to prevent unsafe task assignments.
Put the Data in Front of the Crew, Not Just the Safety Office
Assessment data in real-time comes with less use if it’s only available in a safety report every three months that management reviews. It needs to be in shift briefs and daily meetings so you can act on it before it gets outdated.
If Tuesday’s assessments indicate that three workers on one crew had trouble with one step of a lockout process, then Wednesday’s shift brief should pull that specific gap, specific step, and specific crew right together. Generic retraining that’s applied blanket to everyone whether they need it or not wastes time and dilutes the message for people who are already competent. Targeted coaching, based on data that’s days old rather than months old, gets a much better return on the time invested.
And once you’ve started using data that’s days old in this way, refresher training isn’t about an automatically recurring fixed interval based on a calendar. It’s about looking at that task verification history, the clock, and task risk. Is the worker not quite perfect but well on their way with few gaps, gaps that don’t indicate neglect but just a weak spot? Then you can space checks further apart. Were there a couple of key gaps identified the last time you had a verification chat? Better check in more often.
Blast activities are high-risk tasks. It stands to reason that verification should happen on shorter cycles than lower-risk tasks, and a worker who had one great assessment shouldn’t just be assumed to be above board until the next round of scheduled checks rolls around.
One Source of Truth, Not Five Contradictory Ones
Many mining sites have training records stored in one system, incident reports in another, and observation checklists are done manually and kept in a supervisor’s truck. As a result, stakeholders cannot obtain an accurate picture as the sources of information are not aligned with each other.
When you integrate training data, incident records, and observation checklists into one system you create what I think of as “triangulation”. Near-miss reports can be compared to most recent scores of the relevant workers. When root cause analysis is conducted after an incident, it is far more precise if investigators can access exactly when the worker was last checked and confirmed as competent on the task instead of “this is how I remembered it” or a trail of paper that has gotten lost.
Root cause analysis performed with real training data is a different beast to root cause analysis performed with guesses about what training someone “probably” had. But you don’t get real training data until you pull it out of the silo and let it connect to all the other systems.
Start Small, Prove it, Then Scale
Trying to digitize skills assurance across an entire site in one go is a good way to ensure your supervisors work against you and resistance is rife. The immediate benefit has to be to the person who is charged with enforcing it, and that’s the supervisor. If you can’t make his life easier fast enough, you’re going to struggle.
You’re better off taking the full pipeline for a single identified high-risk competency. One crew evaluation, live skills matrix, integrated briefing schedule, predictive reschedule of refresher, do all of that for one crew and one competency first. Go and show that the system reduces the number of failed checks and doesn’t just automate them onto others. Then you’ll have people voluntarily asking you to expand it to other competencies.
Don’t Let it Become a Surveillance Tool
This is the linchpin that separates a functioning system from one that falls apart. If employees believe that an unsuccessful competency check will be wielded as a weapon in a disciplinary action, they will game the process. They will hurry through checks, prep their peers on the “right” responses to related or other assessments, or elect not to report the near misses that would bring a spotlight onto themselves.
Real-time data is possible only within a safety culture where reporting gaps and near misses are viewed as a valuable input, not as an opportunity to document poor performance. Every competency check needs to be treated as a coaching input. When someone fails, it’s a message to the supervisor to close the gap, not something to put in an employee’s file. Sites that handle this dynamic correctly find that the honest data comes flooding in the door. Those that don’t see the honest data immediately disappear out the window when the next high potential incident walks in the door.
Where This Leaves Safety Leaders
Mines that reduce serious incidents are not the ones that have the most training hours recorded, they are the ones that have real-time visibility of who can do what, safely, and take action on that information before the shift, not after an incident. Completion records will keep the auditors happy, live competency data keeps people safe.
