The one-sentence difference
LMS vs LRS comes down to this: a learning management system (LMS) runs training — learners, enrolments, catalogues, launches and reports — while a learning record store (LRS) only stores xAPI statements, records of what someone did. An LMS can include an LRS, but an LRS is not an LMS, and SCORM courses do not use one.
The two are often mentioned together because modern platforms bundle them, and because xAPI made the LRS a familiar term. But they answer different questions. The LMS answers "who should take what, and did they finish it?" The LRS answers "what learning activity happened, wherever it happened?" Keeping that distinction clear avoids buying the wrong thing, or expecting reports from a system that was never collecting the data.
What an LMS does
An LMS is the system administrators and learners log into. Typical responsibilities:
- People: user accounts, groups, roles and permissions.
- Catalogue: the courses available, how they are organised, and who can see them.
- Assignment: enrolments, due dates, mandatory training and reminders.
- Launch: opening a course for a learner and providing the runtime it needs.
- Tracking and reports: who completed what, with what score, and when.
For SCORM content, the LMS does the tracking itself. When a SCORM course launches, the LMS provides a JavaScript API object in the browser. The course calls it to report status, score, time and its bookmark, and the LMS saves those values in its own database. No separate record store is involved.
What an LRS does
An LRS is a database with a defined web interface, specified by xAPI, that accepts and returns statements. Each statement is a small JSON record in an actor–verb–object shape: this person, did this, to this thing, with this result. Content, apps, simulations and other systems send statements over HTTP; reporting tools read them back.
What an LRS does not do is just as important:
- It does not manage users, enrolments or a course catalogue.
- It does not launch content.
- It does not decide what a course completion means; it stores whatever statements it is sent.
That narrow scope is the point. Because an LRS only stores statements, many systems can report to the same one, including activity that happens nowhere near an LMS. The full picture of what an LRS stores, and how it is queried, is in what is a learning record store.
| LMS | LRS | |
|---|---|---|
| Main job | Deliver and manage training | Store and return xAPI statements |
| Users and enrolments | Yes | No |
| Launches courses | Yes | No |
| Tracks SCORM | Yes, through its runtime API | No |
| Stores xAPI statements | Only if it includes an LRS | Yes |
| Who uses it | Learners and administrators | Other systems, and reporting tools |
Does SCORM need an LRS?
No. This is the most common misunderstanding in the area. SCORM 1.2 and SCORM 2004 report through the LMS's runtime API and store their data in the LMS. A "SCORM LRS" is not a thing the specification defines, and adding an LRS does nothing for a SCORM course unless something translates its data into statements.
The confusion has understandable roots. Some platforms convert SCORM results into xAPI statements so all reporting lives in one place, and some products sell SCORM hosting and an LRS together. Both are platform features, not part of SCORM.
A quick way to check what a course needs is to open its package. A zip with an imsmanifest.xml that declares SCORM 1.2 or 2004 reports to the LMS. A tincan.xml file points to xAPI content, and a cmi5.xml course structure file points to cmi5; both of those expect an LRS somewhere behind the launch. If you are unsure what your platform provides, ask your vendor directly whether SCORM results are stored in the LMS, converted to statements, or both.
The standards that do use an LRS are xAPI and cmi5. xAPI content sends statements straight to an LRS. cmi5 adds rules for how an LMS launches and tracks a course, while the results still travel as xAPI statements into an LRS. How the three standards relate is laid out in SCORM vs cmi5 vs xAPI.
When do you need both?
You need an LMS and an LRS together when:
- You deliver cmi5 courses, which an LMS launches and an LRS records.
- You track learning that happens outside courses — simulations, mobile apps, on-the-job checklists, events — alongside assigned training.
- Several systems need to report into one place, so the LRS becomes the shared record.
- You want raw activity data for analysis that the LMS's built-in reports cannot provide.
In many cases the LMS already includes an LRS, so "both" means one product with two roles. In others, organisations run an external LRS alongside the LMS to keep data portable. Either way, decide what data you need first, then check whether one system or two will hold it. If you are mixing standards, what is cmi5 explains where each piece sits.
Where SCORM Central fits
SCORM Central converts files you already have — PDF, PowerPoint, Word, or video — into SCORM 1.2, SCORM 2004, cmi5, or xAPI, and shows you the manifest, the full runtime log, and a conformance report on every build, so you can see exactly what a package will report before an LMS does. See how it works, or start with one file.