The question is never just a count
An auditor wants to know who completed which version of a course, when, under which requirement, and whether that requirement applied to them at the time. A completion percentage does not answer any of that.
What a defensible record contains
- The learner, with continuity across identifier and role changes
- The course and the exact version completed
- The requirement that made it mandatory and the role or population it applied to
- Completion date, score and any certificate issued
- The source system and a trace back to the original record
Prepare before the request arrives
Keep records normalized and reconciled continuously so an audit pull is a query, not a project. Store lineage with the record. Agree retention periods with legal and compliance in advance.
Common failure modes
- History left in a retired platform that can no longer be queried
- Duplicated learners after a migration splitting one person's record in two
- Completions recorded against the current course version instead of the version taken
- Spreadsheets used as the system of record with no audit trail
Ready to see your learning data in one place?
Tell us which systems you run and we will show how the platform connects, normalizes and preserves their records.