What is cmi5?
cmi5 is an e-learning specification that combines the structure of SCORM with the flexible tracking of xAPI. The LMS launches course units, and results flow back as xAPI statements to a Learning Record Store. You keep reliable completion and scoring, and gain far richer data about what learners actually do.
Assignable Units: how cmi5 structures a course
In cmi5, a course is made up of Assignable Units (AUs): the launchable building blocks the LMS assigns to a participant. Each AU reports a defined set of results back to the LRS, like completed, passed, failed, or a score. A course structure file tells the LMS which AUs belong together and the order in which participants should progress. Because AUs speak xAPI, they can also send any additional detail you care about, from individual answers to time spent per section.
Should your organization care about cmi5?
If your training lives entirely inside one LMS as classic courses, SCORM still does the job. cmi5 becomes interesting when you want the reliability of formal courses and deeper data: mobile or offline delivery, detailed reporting beyond completion, or content hosted outside the LMS. If you are choosing a standard for new content today, cmi5 is the more future-proof option, and it is backed by ADL, the same organization behind SCORM and xAPI.
Migrating from SCORM to cmi5
Moving to cmi5 is usually a gradual transition, not a big-bang project:
- Audit your current content and note which courses actually need richer tracking.
- Check that your LMS or platform supports cmi5 launch and has access to an LRS.
- Export new and updated courses as cmi5 from your authoring tool, most modern tools support it.
- Run SCORM and cmi5 side by side, migrating older content only when it is worth the effort.
- Use the richer data to improve your courses, that is the reason you migrated.
AICC vs SCORM vs xAPI vs cmi5
Here is how cmi5 compares with the standards that came before it:
| AICC | SCORM | xAPI | cmi5 | |
|---|---|---|---|---|
| Released | 1993 | 2000 | 2013 | 2016 |
| How it works | Course reports to the LMS over HTTP (HACP) | Course runs in the LMS via a JavaScript API | Activities send statements to an LRS | LMS launches the course, results go to an LRS |
| Tracking depth | Completion, score, and time | Completion, score, progress, and time | Any learning experience, in detail | xAPI-level detail for LMS-launched courses |
| Offline support | No | No | Yes | Yes |
| Status today | Legacy, committee dissolved in 2014 | Widely supported but aging | Modern standard for broad tracking | Emerging successor to SCORM |
In short: SCORM is the established choice, xAPI the broad tracking layer, and cmi5 the bridge that gives formal courses modern data.








