Learning management system (LMS)

Atlas

The platform of record for enrolment and completion reporting, which an AI training layer writes into rather than replaces.

What is a learning management system?

A learning management system is the platform of record for enrolment and for completion reporting. It holds assignments and due dates, and it is the system a compliance function reports from. An AI training layer writes into it rather than replacing it, because the reporting obligations are already attached to it.

Also called: LMS

Why replacing the platform of record is the wrong fight

Proposing to replace a learning management system is the fastest way to lose a training programme. The platform carries years of completion history alongside a reporting format the compliance function has already agreed with its regulator. None of that is interesting work, and all of it is load bearing. A training layer that generates modules and writes completions back into the existing platform avoids the migration, which is usually the difference between a deployment in weeks and a project in quarters.

  • Completion history already in the platform is the organisation's audit evidence.
  • Reporting formats have been agreed with regulators and auditors over years.
  • Directory integration determines who is enrolled, and it rarely transfers cleanly.
  • Writing into the platform of record avoids a migration nobody has budgeted for.

How a learning management system works

  • The platform is confirmed as the system of record for completion evidence.
  • Modules are published to it as launchable content against a stated standard.
  • Enrolment and cohort assignment remain under the platform's control.
  • Completion and assessment results are written back with the module revision attached.
  • Reconciliation compares what the training layer recorded against what the platform holds.

How a learning management system is evaluated

Integration is assessed on whether the platform's records remain complete and reconcilable. Test the following after each publication cycle:

  • proportion of completions written back without manual intervention
  • discrepancies between the training layer and the platform of record
  • fidelity of assessment detail surviving the transfer
  • availability of the module revision reference inside the platform
  • time from module release to enrolment of the intended cohort

Limitations, risks and common failure modes

  • Completion is written back without the module revision, which defeats the audit question.
  • Platform standards support a score and little of the evidence behind it.
  • Two systems each believe they own enrolment and produce conflicting due dates.
  • Platform upgrades break the integration at the moment a compliance deadline lands.

Related terms

Learning record store (LRS)The repository where experience statements are kept, separate from the system that delivered the learning.System of recordThe authoritative source for a given fact, which an AI layer must agree with rather than compete against.Completion recordThe record of who completed which module, on which version of the source, and when.RollbackReturning a system to its previous state after a change, which has to be planned rather than improvised.SCORMThe long-standing interchange standard that allows a course to be delivered and tracked by any compliant platform.Write-backReturning a result into the system of record, which is where an answering layer takes on real consequence.

All 315 terms