Proving Compliance: What an Auditable Training Record Needs

The training was delivered. Six months later someone asks you to prove it. What you can produce at that moment is the only thing that matters — and it's determined by decisions you made before the course went live.

What auditors typically ask for

• A list of who was required to complete the training, and who did.
• Completion dates, and whether they fell within the required window.
• Evidence of what content was presented — often the actual course, or a document version of it.
• Assessment results where competence was claimed.
• Evidence of acknowledgement where an obligation was accepted.
• The version of the course each person took, if the content has changed since.

That last one catches people out repeatedly. If you updated the course in March, you need to know who took which version.

Where the record actually lives

Your LMS holds completion data. Your authoring tool holds the content. Neither, by itself, is a complete record — and if you change LMS or lose access to the authoring tool, you may lose half of it.

The practical answer is to keep three things together for each course version:

1. The deployed package (SCORM or HTML) as delivered.
2. A document version of the content, readable without any special software.
3. The completion export from the LMS for that period.

Why a document version matters

A SCORM package proves what was delivered only if someone can still run it. In five years, that's not guaranteed — the LMS may be gone, the authoring tool discontinued, the browser requirements obsolete.

A Word or PDF version of the course content is readable indefinitely and can be handed straight to an auditor. It's the cheapest insurance in compliance training, and almost nobody does it.

Versioning discipline

Adopt a simple, explicit convention and stick to it — a version number and date in the course itself, visible to learners, and in the filename of every archived artifact. When someone asks 'what did staff actually see in April?', you want to answer in seconds, not spend a day reconstructing it.

Completion vs comprehension

A completion record proves someone reached the end. If your obligation is to demonstrate competence, you need assessment data — scores, and ideally which items were answered incorrectly. Configure your course to report a score, not just a completion status, or you'll have evidence of attendance where you needed evidence of understanding.

Retention

Retention periods vary by jurisdiction and obligation — commonly several years, sometimes for the duration of employment plus a period. Establish the requirement before you design your archive, because retrospectively reconstructing records is expensive and often impossible.

A practical routine

At the point a course goes live: archive the package, export a document version, note the version number and date. When the course is retired or updated: export the completion data for that version and archive it alongside. Ten minutes of discipline at each release makes an audit boring, which is exactly what you want it to be.