SCORM and xAPI are both standards that let e-learning report to a system, but they track different things. SCORM packages a course so any compatible LMS can launch it and record completion, score and pass or fail. xAPI records learning activity wherever it happens and sends it to a Learning Record Store (LRS), and cmi5 is a set of rules that makes xAPI courses launch and report from an LMS the way SCORM courses do.
For most organisations buying courses for staff, SCORM is still the safe default. xAPI earns its place when you need to track learning outside a standard course, such as an app, a simulation or on-the-job checks. This guide explains each standard for buyers rather than developers, and what to write in a tender so you get content and a platform that work together.
What is the difference between SCORM and xAPI?
SCORM is a set of technical standards for e-learning from the Advanced Distributed Learning (ADL) Initiative, part of the US Department of Defense. A SCORM course is a zip file with a manifest. You upload it to your LMS, the LMS launches it in a browser, and the course reports a fixed set of data back: whether the learner started and finished, their score, pass or fail, and where they left off.
xAPI (Experience API) takes a different approach. Instead of a fixed set of fields, the course or app sends short statements about what someone did, in the form “this person did this thing”. Those statements go to a Learning Record Store. The xAPI specification describes an LRS as a server responsible for receiving, storing and providing access to learning records, and says the learning it describes could take place in an online course, on the job or elsewhere.
In practice the difference for a buyer comes down to this:
- SCORM tracks a course inside an LMS. It is simple and almost universally supported.
- xAPI tracks activity anywhere it can be sent from, as long as something is there to receive it.
xAPI is also a formal standard. It was published as IEEE standard 9274.1.1-2023 in October 2023, which defines the data model and the web service used to exchange data between learning activities and an LRS.
SCORM 1.2 vs SCORM 2004 vs xAPI
You will often see these three listed side by side in supplier answers. Here is what each means for you.
| SCORM 1.2 | SCORM 2004 | xAPI | |
|---|---|---|---|
| Where it runs | In your LMS, in a browser | In your LMS, in a browser | Anywhere that can send data: courses, apps, simulations |
| What it records | Completion, score, pass or fail, bookmark | The same, with completion and pass or fail recorded separately | Any activity you define, as statements |
| What you need | A SCORM-compatible LMS | An LMS that supports SCORM 2004 | A Learning Record Store, standalone or built into the LMS |
| LMS support | Almost universal | Most corporate LMSs | Varies, so check |
SCORM 1.2 is the older version and still the most widely supported. SCORM 2004 is useful when someone can finish a course without passing it, because it reports the two separately. If your LMS supports both and you have no specific reason to choose, ask your LMS administrator which one gives the clearest reports on your platform.
What is cmi5, and how does it compare with SCORM?
xAPI on its own is deliberately general. It says how learning data is described and stored, but not how an LMS should launch a course or decide that a course is complete. That gap is what cmi5 fills.
The cmi5 specification describes itself as a profile for using xAPI with a traditional LMS. Work on it started in the AICC (the aviation industry’s computer-based training committee) in 2010, it passed to ADL in 2014, and the first production release came in June 2016. It sets the rules for launch, authentication, sessions, reporting and course structure, so a cmi5 course and a cmi5 LMS should work together without custom set-up.
For a buyer, the useful parts are:
- A course package. A cmi5 course is described in a file called cmi5.xml, usually inside a zip, much like a SCORM manifest.
- A defined launch. The LMS launches each unit and tells it where to send its data.
- Clear rules for completion. Each unit has a “move on” setting, such as passed, completed, or completed and passed, so everyone agrees what finished means.
- An LRS is part of the deal. The cmi5 specification text says a cmi5 LMS must implement an LRS as defined in xAPI.
So cmi5 gives you the structure of SCORM with the richer data of xAPI. The catch is support. Support for cmi5 varies between LMSs and authoring tools, so check it with each supplier before you rely on it.
Do you need a Learning Record Store?
You only need an LRS if you are using xAPI or cmi5. SCORM courses report straight into the LMS.
There are two common set-ups:
- An LMS with a built-in LRS. The LMS receives xAPI statements itself and can show them in its reports. This is the simplest option if your LMS offers it.
- A standalone LRS. A separate system receives the statements, often from several sources, and you report from it or feed it into a dashboard or data warehouse.
Before you pay for an LRS, decide who will look at the data and what decisions it will change. xAPI can record a great deal of detail. If nobody has time to analyse it, you will end up with the same completion report you would have had from SCORM, at a higher cost.
When is xAPI worth it?
xAPI makes sense when the learning you need to evidence does not sit neatly inside a browser course. Typical reasons are:
- Learning outside the LMS. A mobile app, a simulation, a virtual environment or a coaching tool that needs to report what people did.
- Detailed evidence. You want to see the choices someone made in a scenario, not only whether they passed.
- Joining up records. You want course results, practical assessments and on-the-job sign-offs in one learner record.
- Content hosted elsewhere. The course lives on a different system from the LMS but still needs to report back.
If your requirement is compliance and policy courses for staff, with completion and pass or fail reported to managers and auditors, SCORM does that job well.
What about LTI?
LTI comes up in the same tenders, but it does a different job. 1EdTech describes LTI as a technical standard used to connect learning tools with an institution’s learning environment. In simple terms, SCORM, xAPI and cmi5 are about how content reports what a learner did, and LTI is about plugging an external tool into your platform so learners can open it without a separate login. You may need both, and one does not replace the other.
What to ask for in an e-learning or LMS tender
Many problems come from a mismatch between the format a supplier delivers and what the LMS can actually play and report. A few clear lines in your specification avoid that.
If you are buying e-learning content:
- State the exact format you need, for example SCORM 1.2 or SCORM 2004, and which LMS it will run on.
- Ask the supplier to test a sample package in your LMS, or a copy of it, before full build.
- Say what must be reported: completion, score, pass or fail, time spent, and whether learners can resume where they left off.
- If you ask for xAPI, say which LRS will receive the data and what the statements must cover.
- Ask whether you receive the source files as well as the published package, so you can update or republish later.
If you are buying an LMS:
- Ask which standards it supports in full: SCORM 1.2, SCORM 2004, xAPI and cmi5. “Supports xAPI” can mean anything from a full LRS to simply launching an xAPI course.
- Ask whether it has a built-in LRS, or whether you would need a separate one.
- Ask how SCORM and xAPI results appear in reports, and whether managers can see them without exporting data.
- Ask whether your existing courses can be moved across with their completion history.
Which should you choose?
For most UK organisations buying courses for staff, the honest answer is SCORM, with xAPI added where a specific need justifies it:
- Choose SCORM 1.2 or 2004 for standard courses in an LMS, especially compliance, policy and induction training, or when content may move between platforms.
- Choose xAPI when you need to track learning outside a browser course, or capture detail SCORM cannot hold, and you have an LRS and someone to use the data.
- Consider cmi5 when you want xAPI data with SCORM-style launch and completion, and both your LMS and your authoring tools support it properly.
Whatever you choose, test a real package on your real platform before you commit. That single step catches most compatibility problems.
How Capytech handles SCORM and xAPI
We build e-learning in SCORM 1.2, SCORM 2004 and xAPI, so the package can match the platform you already have and report what you need. If you are converting existing material, our guide to turning PowerPoint and PDF training into SCORM e-learning covers that route in detail.
For bespoke programmes with scenarios, simulations or richer tracking, see our custom e-learning development service. If you need content quickly from your own documents, FastTrack builds modules typically in 4 to 5 working days and includes a branded LMS.
If you are choosing a platform, the Capytech LMS runs on your own domain with single sign-on through Microsoft or Google, courses that work in the browser on any phone, tablet or desktop, and UK hosting on AWS London with daily backups.
Frequently asked questions
Neither is better in every case. xAPI can track far more, and from far more places, but it needs a Learning Record Store and someone to use the data. SCORM is simpler and almost universally supported, which makes it the better choice for most standard courses in an LMS.
SCORM 1.2 and SCORM 2004 both package a course to run in an LMS and report completion, score and pass or fail. SCORM 2004 records completion and pass or fail separately. xAPI records any learning activity as statements sent to a Learning Record Store, inside or outside the LMS.
cmi5 was designed to do the job SCORM does using xAPI, and it has been production ready since 2016. In practice, support for cmi5 in LMSs and authoring tools still varies, so check your platform’s cmi5 support before you rely on it.
Yes. Tin Can was the earlier project name for what became the Experience API, and you will still see both names used. The current version is published by the IEEE as standard 9274.1.1-2023.
No. xAPI statements have to be sent to a Learning Record Store. Some LMSs include one, others need a separate LRS, and some can launch an xAPI course without storing much of its data, so ask exactly what your LMS records.
A branded LMS your people will actually use
The Capytech LMS and TMS gives you your own branded academy, a training calendar and reporting, hosted in the UK and run by our team.

