Training Management
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Assign training by role or rule, verify understanding rather than attendance, and keep per-learner evidence an auditor can read. Completion alone is not competence, and the difference is what gets audited.
Competence you can evidence
Regulated work requires that the people doing it are trained for it, and that you can prove it. Training Management assigns the training, records what happened, and checks that the material was understood rather than merely opened.
Assignments that keep themselves current
Training is assigned three ways: by hand, by rule against roles and competencies, or sourced from something that happened elsewhere in the system. A controlled procedure being revised, or a cause type recorded in risk management, can generate the retraining itself.
- Courses, modules and curricula, organised into learning paths
- Skills and competency matrices mapped to roles
- Rule-generated assignments, so a new person in a role inherits the right training
- Retraining generated from a document revision or a recorded cause, rather than remembered
Understanding, not attendance
A completion tick proves someone opened a page. The module is built around the harder question of whether they understood it, because that is the one an auditor asks.
- Quizzes with answer keys and a configurable policy for attempts, pass marks and retakes
- Video delivery with progress tracking rather than a play button and an honour system
- Document acknowledgement tied to a content snapshot, so the record shows WHICH text was acknowledged
- AI comprehension checks: the learner is interviewed about the material against a rubric, and graded server-side rather than in the browser
When the numbers look too good
Training records are only as trustworthy as the behaviour behind them, and completion data is easy to game. The module watches for the patterns that suggest it: finishing far faster than the material allows, dwelling too briefly, skimming video, repeating a quiz until it passes, or leaving the window repeatedly.
A flag is not an accusation. It is raised with a severity, and a manager either acknowledges it as a real integrity concern or dismisses it as a false positive, giving a reason either way. Visibility is scoped: a line manager sees their own direct reports, and reaching across the organisation requires an explicit permission.
Competence demonstrated in person
Some competence cannot be shown on screen. Practical sign-offs record that a named assessor watched the work done against defined criteria, so the hands-on half of a competence claim is evidenced the same way as the rest.
Tied to the rest of the system
Training is not a silo here. Approval of a controlled document can be gated on the approver having completed the training that qualifies them to approve it, which turns a competence requirement into something the system enforces rather than something a procedure asks for.
Per-learner evidence records export as PDFs for auditors, and learners who only need training can be licensed as a separate, cheaper class.
What it looks like

Placeholder - a training matrix by role. Upload the real screenshot in the admin.
Use cases
Onboarding into a regulated role
A new hire inherits the training their role requires through a rule rather than a checklist, works through it, and is signed off - with the record attached to them from day one.
Re-training on a changed procedure
A controlled procedure is revised. The affected people are assigned the change automatically, and their acknowledgement is recorded against the exact text they saw, not against the document in general.
Proving competence at audit
An auditor asks how you know a named person was competent for a task. The answer is one export: the training, the comprehension result, the practical sign-off and the dates.
Catching records that flatter you
A cohort completes a mandatory course suspiciously quickly. The pattern is flagged with a severity, a manager reviews it, and the decision - genuine concern or false positive - is recorded with a reason.
See it on your own processes
Learning paths and competencies
Courses, modules and curricula organised into paths, with skills and competency matrices mapped to the roles that need them.
Assignments that generate themselves
Manual, rule-based, or sourced from a document revision or a recorded cause, so retraining is triggered by the event rather than by somebody remembering.
Acknowledgement against a snapshot
A document acknowledgement is tied to the content as it was, so the record proves which version of the text a person actually accepted.
Comprehension checked against a rubric
Quizzes with configurable attempts and pass marks, plus AI comprehension interviews graded server-side rather than in the learner's browser.
Engagement anomaly detection
Fast completion, short dwell, video skimming, retake gaming and repeated focus loss are flagged with a severity for a manager to acknowledge or dismiss, with a reason.
Practical sign-offs and evidence
Hands-on competence signed off by a named assessor against criteria, with per-learner evidence exportable as a PDF for auditors.
