A learning record store (LRS) collects xAPI learning data from across your tools. What it captures, how it relates to your LMS, and when you need one.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
A plain-English explainer of SCORM, its versions, how it compares to xAPI and AICC, and when you actually need it.
A plain-English comparison of xAPI and SCORM, with a use-case recommendation for regulated, multi-site employers.
The learning analytics metrics that earn executive attention, and how to build dashboards on data you own instead of a SaaS reporting tier.
A learning record store (LRS) is a database purpose-built to receive, store, and return learning activity data sent as xAPI statements. In plain terms, it's the system of record for what your people learned, where they learned it, and whether they finished — including activity that happens outside your LMS.
If your LMS only knows about courses people took inside the LMS, you have a blind spot. A learning record store closes it. It collects signals from the LMS, the simulator on the plant floor, the safety walk-through app, the mentor sign-off form, and the video platform, then stores them as one queryable record per learner. This explainer covers what an LRS captures, how it relates to xAPI and your LMS, and when a mid-market training team actually needs one.
An LRS stores xAPI statements. Each statement follows a simple "actor — verb — object" structure: a person did something to a thing. The Advanced Distributed Learning Initiative, which stewards the xAPI specification, designed it exactly this way so that almost any learning experience can be expressed in one consistent format.
A few concrete examples of statements an LRS can hold:
None of those last three live in a traditional LMS course. That's the point. An LMS records course completions; a learning record store records learning experiences, wherever they happen.
The two are easy to confuse because they overlap, but they do different jobs.
A useful way to think about it: the LMS is where learning is delivered, and the LRS is where learning is recorded. Many modern LMS platforms, including Moodle, ship with a built-in LRS or can connect to an external one. So this is rarely an either/or decision — it's a question of whether you turn the capability on and route data through it.
xAPI (the Experience API, sometimes called Tin Can) is the language; the LRS is the place that speaks it. xAPI defines the statement format and the rules for sending and retrieving statements. An LRS is any system that correctly implements that specification as a store.
This is the key break from the older SCORM standard. SCORM tracks completions and scores inside an LMS and struggles with anything beyond a browser-based course window. xAPI plus an LRS tracks experiences anywhere — mobile, offline, simulators, on-the-job — and keeps the data in one place you control. If you're weighing the two standards, our explainers on what SCORM is and xAPI vs SCORM go deeper.
You don't have to abandon SCORM to adopt an LRS. Many organizations run SCORM courses in the LMS and use the LRS to capture everything SCORM can't reach.
Most single-site teams running standard compliance courses inside one LMS do not need a separate LRS on day one — the LMS reporting is enough. You need one when learning escapes the LMS. That usually shows up in a few specific situations:
If two or more of those describe you, an LRS is worth scoping. For the reporting and audit angle specifically, see how we approach compliance reporting.
Here's the part most vendor pitches skip: where your learning record lives determines who controls it.
When your LRS is bundled into a per-seat SaaS LMS, your granular learning data sits in the vendor's environment, on their export terms, often behind a premium tier. If you ever switch platforms, getting that data out cleanly is a negotiation — and statement-level history is exactly the data that's hard to reconstruct after the fact.
When you own the LRS — self-hosted or hosted in your own cloud tenant alongside a platform you own outright — the granular record is yours. You decide the retention period, the export format, the access controls, and the data residency. For regulated, multi-site firms, that ownership is not a nice-to-have; it's the difference between a record you can stand behind in an audit and one you're renting access to. The same logic drives connecting the LRS to your people data through proper HRIS integration, so completions tie back to current roles and locations automatically.
Capturing statements is only half the value. The other half is turning them into something a director can act on — completion gaps by site, overdue recertifications by role, time-to-competence for new hires. That's where the LRS feeds reporting and learning analytics dashboards that pull from every connected source rather than just the LMS.
A practical rollout usually looks like this: turn on the LRS, connect the LMS first, then add one external source at a time (the simulator, then the check-in app, then the sign-off form), validating the statements at each step. Trying to wire everything at once is how data quality problems hide.
No. An LMS delivers and manages courses; a learning record store stores learning activity data as xAPI statements from any source, including tools outside the LMS. Many LMS platforms include or connect to an LRS.
Effectively yes. An LRS is defined by the xAPI specification — it receives and returns xAPI statements. You can capture SCORM activity separately in the LMS, but the LRS itself speaks xAPI.
Yes. Moodle can send xAPI statements to an internal or external LRS, which lets you keep delivering courses in Moodle while recording broader learning activity in a store you control.
For regulated, multi-site organizations, in an environment you own or control — self-hosted or in your own cloud tenant — so you set retention, export, access, and data-residency rules rather than renting access from a SaaS vendor.
Most teams discover the LRS question while scoping HRIS and analytics work, not in isolation. If you're mapping your training data stack, talk it through with us before you commit to a platform — the right time to design data ownership is before launch, not after.