The training record an inspector actually asks for.
Train
The certificates folder
Training evidence usually lives as PDF certificates in a shared folder, with a spreadsheet tracking who has done what. It survives until someone leaves, a course is updated, or an inspector asks who took which edition of the material.
The hard part is not delivering training. It is showing, on a given date, who had completed what, and which version of the content they saw.
What Train does
Assign courses to people or to roles, with a due date and an annual recurrence. Recurring assignments roll forward when they fall due, and each person receives one reminder per cycle rather than one per course.
Course editions are frozen on publish. A completion records the edition the person actually took, their score, the attempt number and the date — so a later change to the material cannot rewrite what someone was taught.
The register only accepts new rows. A late completion is recorded as late; a retake is added beside the earlier attempt rather than replacing it.
Synthetic data
What the record keeps
New completions are added to the register; earlier evidence is never overwritten.
- A training register an inspector can read
Who was assigned what, when it was due, when they completed it, and what they scored. Every completion is added as a new record, and a late completion stays recorded as late.
- Periodic training that chases itself
Recurring assignments roll forward when they fall due, and each person gets one reminder per cycle — not one per course. A reminder that arrives three times is one people learn to ignore.
- Decision history that cannot be overwritten
Earlier audit entries, STR packs, screening decisions and training records cannot be edited or removed. A correction creates a new record beside the original, so both stay readable.
See the register on your own courses.
Bring your current material and we will show you what the record looks like.
Guided setup · Arabic and English · no card required