cmi5 is a profile built on top of xAPI that adds the LMS-launch workflow and mandatory reporting rules that raw xAPI intentionally leaves unspecified. Where xAPI says "send statements," cmi5 says exactly when, in what sequence, and with which verbs those statements must be sent, so that any compliant LMS can reliably receive and interpret them. A cmi5 course is still packaged as a ZIP with a manifest (cmi5.xml), making it familiar territory for teams coming from SCORM. The run-time communication, however, uses xAPI statements sent to an LRS rather than the JavaScript API window model of SCORM. This gives cmi5 the portability and richer vocabulary of xAPI — including the ability to track video play events — while preserving the single-source-of-truth reporting that enterprises expect from an LMS. The key gotcha is adoption: as of 2025 cmi5 support in major LMS platforms has grown but is still narrower than SCORM 1.2, so teams shipping to a broad set of corporate LMS environments sometimes choose SCORM as a fallback even when cmi5 would be technically superior. For new-build platforms where you control both the LMS and the content, cmi5 is the recommended path.
