Learning record store (LRS)
Also known as: LRS
A learning record store, or LRS, is a database built to receive and store xAPI statements, the records that say who did what, such as "Anna completed Fire Safety". It can collect learning activity from anywhere: courses, apps, simulations, and on-the-job tasks. An LRS can be built into an LMS or run as a separate system.
What an LRS does
An LRS accepts xAPI statements from any tool that sends them, stores them securely, and lets other systems read them back. Because xAPI is a shared standard, one LRS can collect data from many different sources.
It is the memory of your learning data, independent of any one course or tool.
LRS vs LMS
An LMS assigns, delivers, and manages training. An LRS only stores learning records. Many modern LMS platforms include an LRS, while some organisations run a separate one to collect data from several systems in one place.
Why it matters
With an LRS, learning that happens outside formal courses can be recorded alongside them. That gives you a fuller picture for reporting and analytics, and a record you can keep even if tools change.
Read the learning analytics definition
Frequently asked questions
What is a learning record store?
A database that receives and stores xAPI statements, the records of who did what in their learning, from any tool that sends them.
What is the difference between an LRS and an LMS?
An LMS manages and delivers training. An LRS stores learning records. Many LMS platforms include an LRS, but it can also be a separate system.
Do I need an LRS to use xAPI?
Yes. xAPI statements have to be sent somewhere, and that place is an LRS, either inside your LMS or standalone.
Can an LRS collect data from outside the LMS?
Yes. Any tool that sends xAPI statements can report to the LRS, including apps, simulations, and on-the-job activities.
Does cmi5 use an LRS?
Yes. cmi5 is built on xAPI, so course results are recorded as xAPI statements in a learning record store.