Versioned documents
Training material is stored with versions. An assignment pins the version the team member actually read, so revising a document later does not silently rewrite anyone's training record.
Training & competency
Team training and competency management that produces usable evidence
Most training systems end at a completion tick. This one continues: a completed training document is only the first piece of evidence towards a competency, and a competency is only useful because it opens a qualification gate on real operational work.
Evidence types
A competency declares what proves it: a scored assessment, an observed practical sign-off, or both together. The requirement is defined once, in the catalogue.
Forced retraining
When a document version is superseded or evidence is retired, affected team members are returned to a retraining state and the qualification it supported stops counting.
Status model
Every team member is in exactly one understandable state
Training status is shown with an icon, a word and a colour — never colour alone.
AssignedReviewingAssessment requiredPractical sign-off requiredQualifiedRetraining required
Where the evidence goes
A qualification record is not an attribute someone types onto a profile. It is derived from the evidence that exists at the time work is considered. That is what makes competency-based work allocation trustworthy, and why a missing document or an expired sign-off holds the work instead of letting it through.
Run the platform against your own operational tasks
Create your organisation and work the full loop yourself: a training document, the competency it proves, the qualification gate it opens, and the work that gets allocated because of it.
Start free
Staff sign-in12 months free · No credit card needed