Completion record

Atlas

The record of who completed which module, on which version of the source, and when.

What is a completion record?

A completion record is the record of who completed which module and when. It names the revision of the source material the module was generated from, so the record states what the person was actually trained on. This is the artefact an auditor asks for, and it has to stand without the system that produced it.

Also called: Training record

Why the version matters more than the date

An inspector does not ask whether training was delivered. They name a procedure and a date, then ask for the list of people trained on the revision in force at that moment. Completion against a module is easy to produce, where completion against a document revision requires the link to have been captured at the time. Organisations discover the difference during an inspection, when the module has been revised repeatedly since and the record holds only the latest version.

  • The record is the organisation's only evidence that an obligation was met.
  • Naming the source revision is what makes the record answer an inspector's question.
  • Records outlive the platform, so they have to be exportable in a readable form.
  • A completion with no linked assessment evidences attendance rather than competence.

How a completion record works

  • Each module is stamped with the identifier and revision of the source it came from.
  • Enrolment is written at assignment with the cohort and the due date attached.
  • Progress and the assessment attempt are recorded against the learner identity.
  • Completion is written with a timestamp and the module revision in force.
  • The record is made immutable and retained for the applicable retention period.

How a completion record is evaluated

A completion record is assessed on whether it answers a version specific question years later. Test the following on closed cycles:

  • proportion of completions naming the source revision trained on
  • time to produce the list of people trained on a given revision
  • completeness of assessment evidence attached to each completion
  • integrity of records exported out of the delivery platform
  • retention period against the applicable regulatory requirement

Limitations, risks and common failure modes

  • Modules are revised in place, so earlier completions point at content that no longer exists.
  • Completion is written on the final page view rather than on an assessment result.
  • Exports lose the version reference and arrive as a list of names and dates.
  • Retention follows the platform default rather than the regulatory period.

Related terms

Policy version pinningRecording which revision of a source document a module was generated from, so the two cannot quietly diverge.DefensibilityWhether a decision can be explained and substantiated when it is challenged, which is the only standard that matters at the point of appeal.Learning management system (LMS)The platform of record for enrolment and completion reporting, which an AI training layer writes into rather than replaces.Training attestationA formal confirmation that a named person has been trained on a named policy, which an auditor can ask for.AI audit trailThe complete record of what a system did, on what evidence, and who authorised it, retained for the period the decision can be questioned.Append-only logA record that can be added to and never amended, which is what makes a history worth presenting.

All 315 terms