Menu

VC use case

Prove training qualifications

This use case allows a tradesperson on a mining site to prove their training qualifications.

  • Mining
Issuer authoritative source creates the claim
Holder person or organization presents proof
Verifier service checks status and makes a decision

Overview

Tradespeople can prove safety and compliance training at the point of site access using Verifiable Credentials.

The site operator does not need to manually inspect certificates or call training providers for every worker. It needs a current proof that the person has the required training for the site and task.

Why it matters

Mining sites operate under strict safety and compliance requirements. Manual checks slow onboarding, create inconsistent evidence, and increase risk if records are outdated or training has lapsed.

Verifiable Credentials create a cleaner model:

  • training providers issue credentials when qualifications are completed
  • tradespeople store credentials in a wallet
  • site access systems verify training at induction, entry, or task assignment
  • status checks identify expired, revoked, or unsupported credentials before work begins

Ecosystem roles

  • Issuer: Training providers, regulators, or accredited safety bodies issuing certifications.
  • Holder: The tradesperson storing credentials in a wallet.
  • Verifier: Site access control, induction systems, safety compliance teams, or supervisors.
  • Trust governance: The rules that define accepted training providers, credential schemas, site requirements, expiry, and revocation.

Trust decision

The verifier decision is narrow: can this tradesperson enter the site or perform this task right now?

That decision may depend on site induction, training type, expiry, role, contractor engagement, and whether credentials are current.

Privacy and assurance

The verifier should request only the credentials needed for the site or task. A generic gate check may need induction and training status, while a specific task may need additional certification.

Assurance depends on issuer trust, credential status, expiry, and binding between the worker and the presented credential.

Implementation notes

  • Map training credentials to specific site access and task rules.
  • Keep status and expiry checks available for gate, induction, and supervisor workflows.
  • Define offline verification behavior for remote sites with limited connectivity.
  • Record verification outcomes for audit while avoiding unnecessary storage of full training records.
Objective
Enable a mining site to validate training qualifications for a tradesperson required to work on-site.
Description
A tradesperson presents training credentials so the site can verify required qualifications before access or task assignment.
Actors
Tradesperson; training provider; regulator or safety body; mining site operator.
Dependencies
The tradesperson holds training certifications in their wallet, and the site can check issuer trust and credential status.
Preconditions
The tradesperson is engaged to work on a mining site and must present training qualifications before access.
Postconditions
The tradesperson is permitted, denied, or escalated for site access or task assignment.
flowchart LR
    TRAIN@{icon: "tabler:certificate", label: "Training provider", pos: "b"} -->|Issues training VC| WAL@{icon: "tabler:wallet", label: "Wallet", pos: "b"}
    WAL -->|Presents credential| VER@{icon: "tabler:helmet", label: "Site access / verifier", pos: "b"}
    VER -->|Status check| REG@{icon: "tabler:book", label: "Credential registry", pos: "b"}
sequenceDiagram
    participant Trainer as Training provider
    participant Wallet
    participant Worker as Tradesperson
    participant Verifier as Site access / verifier
    participant Registry as Credential registry

    Trainer-->>Wallet: Issue training VC
    Worker->>Wallet: Stores credential
    Worker->>Verifier: Present training VC
    Verifier->>Registry: Check status
    Registry-->>Verifier: Valid
    Verifier-->>Worker: Site access granted

Talk to UNIFY

Explore how this use case could work in your trust ecosystem.

Share the scenario you are testing and we will help map the issuers, holders, verifiers, and policy decisions involved.
Looks good!
Please enter your name.
Looks good!
Please enter your company.
Looks good!
Please enter your e-mail address so we can contact you.
This form uses Google ReCaptcha to ensure interactions with our site are from legitimate users. Please accept the use of recommended storage before submitting the form. Find out more at the Privacy Centre.
Your message could not be sent. Try again later.