cmi5 tends to appear quietly, as one more option in a publish menu or one more line in an LMS feature list. It is easy to skip past, because the name explains nothing. Yet it addresses a real gap that anyone who has tried to launch xAPI content from an LMS will recognize. What is cmi5, and what does it add to xAPI and SCORM?
cmi5 is a set of rules, built on xAPI, that defines how an LMS launches a course, how the course authenticates, and which xAPI statements it must send to report progress. Plain xAPI describes how to record learning activity, but not how an LMS should start a course or pass it the learner's identity. cmi5 adds a defined launch process, a course structure file, a required set of statements and a "moveOn" rule for when a unit counts as done. It was designed as a successor to SCORM. LMS support is narrower than for SCORM, so confirm it first.
What Problem Does cmi5 Solve?
It solves the launch problem. xAPI lets a course send statements to a Learning Record Store (LRS), but it leaves open how the course is started, how it knows who the learner is, and where it should send its data. Each LMS that supported xAPI content had to invent its own answer, and courses built for one system often failed in another.

The specification came from two groups with long histories in e-learning standards: the Aviation Industry Computer-Based Training Committee (AICC) and the Advanced Distributed Learning (ADL) Initiative, which also maintained SCORM. That lineage shows in the design, which deliberately borrows SCORM's ideas about LMS launch and reporting.
ADL's cmi5 specification page describes cmi5 as built on xAPI, adding an xAPI Profile and defining launch, authentication and reporting from an LMS. In plain terms, it brings back the predictability of SCORM ("upload this package and it will report correctly") while keeping the flexibility of xAPI.
How Is cmi5 Different From Plain xAPI?
cmi5 narrows xAPI's choices so different systems can agree. Four pieces do most of the work.
First, a course structure. A cmi5 course includes a structure file describing the course, any blocks that group content, and its Assignable Units. An Assignable Unit, or AU, is the launchable piece of content, roughly what a SCO is in SCORM.
Second, a launch process. The LMS opens the AU with a set of URL parameters: the LRS endpoint, a one-time fetch URL, the actor, a registration ID and the activity ID. The AU calls the fetch URL to obtain a session credential, then reads launch data that the LMS has stored for it, including the launch mode and any mastery score.
The launch mode deserves a note of its own. cmi5 defines three: Normal, where the attempt counts; Browse, where the learner looks around without it counting; and Review, where they revisit finished work. In Browse and Review modes the AU sends only initialized and terminated, never completed, passed or failed, which prevents a learner who is only revisiting content from accidentally changing their record.
Third, a defined set of statements. That is what "xAPI profile" means here: an agreed vocabulary. The LMS records that it launched the AU. The AU must send initialized and terminated, and it sends completed, passed or failed when those things happen. The LMS can add statements such as satisfied, abandoned or waived.
Fourth, moveOn. Each AU carries a moveOn value that tells the LMS what counts as done: Passed, Completed, CompletedAndPassed, CompletedOrPassed or NotApplicable. When the condition is met, the LMS records the AU as satisfied and rolls that up through the course.
An AU may still send other xAPI statements for richer tracking, so you keep the detail that drew people to xAPI. The required set simply guarantees a common floor. If the underlying ideas of statements and an LRS are new to you, start with xAPI and Learning Record Store basics and come back.
How Does cmi5 Compare With SCORM?
Both give you an LMS-launched course with predictable reporting. They differ in how the data travels and what it can describe.
| Question | SCORM | cmi5 |
|---|---|---|
| How the course talks to the system | JavaScript API in the browser, via the LMS window | Web requests to an LRS |
| Where content can live | Normally inside the uploaded package | In the package or hosted elsewhere |
| What can be recorded | A fixed data model | Required statements plus any other xAPI statements |
| Saved progress | Suspend data with size limits | State storage in the LRS |
| What counts as done | Status fields set by the course | moveOn rule evaluated by the LMS |
The cmi5 vs SCORM choice is mostly practical. cmi5 suits content hosted outside the LMS or opened in its own window, and teams that want detailed xAPI data with dependable LMS reporting. SCORM remains the safer default when your LMS handles it well and the reports you need are simple.
Does Your LMS Support cmi5?
Ask directly, and ask for detail. cmi5 LMS support has grown, but it is still less common than SCORM support. Useful questions:
- Can the LMS import a cmi5 course package and read its structure file?
- Does it include an LRS, or does it need an external one?
- Does it honour each AU's moveOn value and mastery score?
- Does it report satisfied status at course level?
- Can AUs be hosted outside the LMS?
If the answers are good, publishing both ways for a pilot is a sensible step. AuthorLearn Studio publishes to cmi5 as well as SCORM 1.2, SCORM 2004 and xAPI, so the same course can be compared across standards. Each standard can still look different in your LMS reports, so run the pilot there before deciding.
How Do You Test cmi5 Content?
Use the official test tools first, then your LMS. ADL's CATAPULT project provides free, open-source tools for testing cmi5 content and systems for conformance, along with a player and good-practice guidance.
A practical test sequence:
- Run the package through the content test tool and fix any structure or statement errors.
- Launch each AU and confirm it sends initialized first and terminated last.
- Confirm completed and passed are each sent at most once per registration, and that failed never follows passed.
- Check that the LMS marks the AU satisfied according to its moveOn value.
- Repeat in your LMS with an ordinary learner account and read the report.
cmi5 Is xAPI That Finally Knows How to Start a Course
What is cmi5, in one line? It is xAPI with launch rules: a course structure, a defined launch and credential handshake, a short list of required statements, and a moveOn rule that tells the LMS when a unit is done.
That combination makes xAPI content behave predictably inside an LMS, which plain xAPI could not promise. Check your LMS support carefully, test with CATAPULT before uploading, and pilot one course before converting a library. When the support is there, cmi5 gives you much of SCORM's predictability with far fewer of its limits.
