Verification of Competency (VOC) in Mining: What It Is and Why It Matters

A training certificate tells you someone attended a course and passed an assessment, usually at a point in time that may have been months or years ago. For a lot of mining qualifications, that’s a reasonable basis for approval. For a meaningful subset — operating specific mobile plant, certain high-risk tasks, equipment that varies significantly between sites — a certificate alone doesn’t answer the question that actually matters: can this person do this task, safely, on this equipment, today. That’s what Verification of Competency exists to answer.

What VOC actually involves

Verification of Competency is typically a practical, hands-on assessment carried out by a qualified assessor, distinct from (and additional to) the classroom or online component that produces a certificate. Rather than testing knowledge, it tests demonstrated ability — operating the actual equipment, following the actual procedure, under observation, with the assessor making a real-time judgment about whether the person is competent to do the task unsupervised.

The result is evidence that has to exist alongside the certificate, not instead of it. A worker can hold a valid certificate and still not have a current VOC — and on many sites, that combination isn’t enough to be approved for the task.

Why a certificate by itself isn’t sufficient

Certificates are portable in a way that competency isn’t always. A worker might have completed a certification course years ago, on different equipment, at a different site, under different conditions. That certificate remains technically valid. Whether the person can still competently and safely operate the specific plant on your specific site is a separate question — one that generic HR competency tools, built around tracking certificates and expiry dates, generally aren’t built to answer.

This is the reason VOC is treated as a distinct, mining-specific requirement rather than folded into general qualification tracking. It’s not extra paperwork for its own sake — it’s addressing a real gap between “certified” and “currently competent.”

Making VOC an attributable record, not a side process

The practical risk with VOC is that it often ends up handled as a separate paper process — a form filled out on-site, filed somewhere, disconnected from the worker’s actual training record. When that happens, the same problems that affect any paper-based process show up: it’s hard to prove VOC was actually done, hard to know when it needs repeating, and hard to produce evidence quickly if an auditor or an incident review asks for it.

Good competency management treats VOC as part of the same digital record as the certificate itself — a verification file uploaded alongside the certification, both needing approval before the qualification counts, with the assessor’s sign-off captured as part of that record rather than as a separate piece of paper. That structure means:

• The assessor who verified competency is identified and dated, not just implied
• The qualification doesn’t count as complete until both the certificate and the verification are approved
• A lapsed or missing VOC shows up in the same place as any other compliance gap — not buried in a filing cabinet

Competency levels, not just pass or fail

Some skills aren’t a simple competent/not-competent assessment — they’re assessed against a defined standard or level. Where that applies, the record should carry the assessed level itself, not just a binary outcome. That distinction matters for roles where the specific standard achieved is relevant to what tasks someone can safely be assigned.

What this looks like in a skills matrix

For a compliance team managing a workforce across one or more sites, the practical value of treating VOC this way shows up in a skills matrix — a single view of every worker’s qualification status, including whether VOC is current, approaching expiry, or lapsed, alongside the certificates themselves. That view is only as reliable as the underlying records, which is exactly why VOC needs to live in the same system as everything else, attributed and dated, rather than as the one part of the process still running on paper.

Escalated qualifications — the ones that carry the highest consequence if someone is wrongly approved — often warrant an additional layer: sign-off restricted to administrators with a specific escalated-approval permission, keeping the highest-stakes credentials out of general approval queues altogether.