Defensible vs. Non-Defensible Credentials
The specific differences an auditor looks for between two identical-looking certificates.
Read article: Defensible vs. Non-Defensible CredentialsTraining records that hold up under audit
A completion row proves your system recorded something. A defensible record proves who was trained, when, and how you know. Asgard produces the second kind.
Most training records document an outcome, not the evidence
A completion date and a user ID record what the platform was told, not what occurred.
The question has shifted
Auditors and regulators now ask whether the certified individual actually did the training, not just whether training was delivered.
Records document outcomes
Most systems answer with a completion date and a user ID rather than evidence of participation.
Exposed at the worst moment
The gap becomes visible during an incident investigation, regulatory review or litigation, when it is treated like no record at all.
Evidence captured as the training happens
Asgard captures evidence while the learner is training, so records do not depend on reconstruction after the fact.
- Capture as it happensDigital affidavits cover identity verification, session access history, participation metrics and anomalies collected during training.
- Tamper-proof by designAffidavits are tamper-proof and blockchain-enabled, so they can be verified rather than taken on trust.
- Follows the learnerWhere identity is verified across successive courses, the record follows the learner through the full credential lifecycle.
What changes with Asgard
Without Asgard
- Record is a completion date and a user ID
- Evidence must be reconstructed after the fact
- Records disconnected across separate courses
- Authenticity taken on trust rather than verified
With Asgard
- Record includes identity, access history and participation
- Evidence captured while the learner is training
- Record follows the learner across the credential lifecycle
- Affidavits are tamper-proof and blockchain-enabled
What sits behind each record
Tamper-proof affidavits
Blockchain-enabled digital affidavits covering verification, access history and participation, verifiable by regulators.
Audit-ready reporting
Dashboards and exportable reports packaging verification details, access history, participation metrics and completion status.
Linked verification events
Every verification is bound back to the enrollment identity, so a certificate can be traced to the human who earned it.
Learner authentication
Facial recognition and ID verification, on device, to confirm the right person is taking the training.
Identity continuity across courses
Once a learner is verified, Asgard recognises them across future courses, refreshers and renewals — no repeat ID uploads.
Global coverage
Available to learners across regions and languages, with the same verification standard applied everywhere.
From session to audit file
- 011
Capture during training
Identity verification, access history, participation metrics and anomalies are recorded as the session runs.
- 022
Seal the affidavit
Evidence is written into a tamper-proof, blockchain-enabled digital affidavit tied to the verified learner.
- 033
Export on demand
Dashboards and exportable reports package the affidavits for regulators, auditors or legal review.
Related insights
The Verified Credentials Gap
Why verifying the document is not the same as verifying the training.
Read article: The Verified Credentials GapRegulators Started Voiding Training Certificates
Enforcement action that turns record-keeping quality into an operating risk.
Read article: Regulators Started Voiding Training CertificatesSee it on your own training
Start the free trial and run learner authentication against your existing courses. Setup takes minutes and uses the training modules you already have.