cmi5

What is cmi5?

cmi5 is an e-learning standard developed by the Advanced Distributed Learning Initiative (ADL) in 2016 that defines how training content is launched from an LMS and how learning data is recorded using xAPI. In practice, it acts as an xAPI profile that adds clear rules around packaging, secure launch, and session termination, resolving the interoperability gaps that xAPI left open. Its name comes from “computer-managed instruction,” the category of specifications from which its original structure was inherited.

In the context of corporate training, cmi5 is significant because it combines the familiar structure of SCORM with the data richness of xAPI. While SCORM can only record whether a learner completed a course and their score, cmi5 can capture any learning interaction in detail, regardless of device or internet connectivity. For L&D teams looking to move from basic tracking to training decisions grounded in real data, it represents the most advanced standard available today.

How does cmi5 work?

The cmi5 architecture relies on three components that work in coordination:

• Assignable Units (AUs): the content modules that the LMS can independently launch and track. Each AU is a learning piece that can be hosted on any server without needing to be imported into the LMS itself.
• LRS (Learning Record Store): a specialized database where all learning statements are stored in xAPI format. This is the component that separates cmi5 from SCORM — data is not locked inside the LMS but held in a standard, queryable repository.
• cmi5.xml file: the course package manifest, equivalent to SCORM’s imsmanifest.xml. It describes the course structure, its assignable units, and the metadata the LMS needs to interpret it correctly.

A cmi5 session works as follows: the LMS generates a secure launch URL with token authentication and passes it to the content. The content uses that URL to communicate directly with the LRS via standard HTTP requests, without an iframe and without a permanent connection to the LMS. Data is sent asynchronously, ensuring it works even in environments with intermittent connectivity.

cmi5, SCORM, and xAPI: key differences

Confusion between these three standards is common. The table below summarizes the most relevant differences for L&D managers, beyond the technical detail:

Benefits of cmi5 for corporate training

For L&D teams, cmi5 is not simply a technical upgrade to the standard — it represents a shift in how learning tracking is understood:

• Native mobile compatibility: content runs on any device without iframe dependency or browser window constraints. Especially relevant for field teams, retail, or logistics where desktop access is not the norm.
• Offline tracking: if a learner completes a module without an internet connection, cmi5 stores the data locally and syncs it to the LRS as soon as the device reconnects. No learning data is lost.
• Detailed analytics: while SCORM only records whether the learner completed the course and their grade, cmi5 can capture which questions were failed, how many attempts were made, how long each section took, and where the learner dropped off. This data drives evidence-based instructional design decisions.
• Distributed content: modules can be hosted on CDNs, dedicated servers, or cloud solutions without needing to be physically imported into the LMS. This simplifies technical management and reduces infrastructure costs.
• Real interoperability: any cmi5-compatible LMS can launch and track the content regardless of vendor. Content created with isEazy Author in cmi5 format can be deployed on any platform supporting the standard without modification.

Limitations and considerations before adopting cmi5

Like any technical standard, cmi5 has requirements worth evaluating before a full-scale rollout:

• Requires an LRS: unlike SCORM, cmi5 does not work with the LMS alone. It needs an active LRS — either built into the LMS or connected externally. This adds an infrastructure layer that some organizations with legacy systems may not have in place.
• Adoption still growing: although modern LMS platforms such as Moodle 4.x, Docebo, TalentLMS, and Cornerstone have strengthened their cmi5 support in recent years, not all platforms implement it at the same level of maturity. Before committing to cmi5, it is recommended to verify real LMS compatibility with an integration test.
• Authoring tools: not all course creation tools support cmi5 export with equal quality. It is important to validate that the tool correctly generates the cmi5.xml file and that AUs are launched using the standard secure protocol.
• Transition curve: teams accustomed to SCORM need to become familiar with concepts such as AU, LRS, and xAPI statements. The learning curve is not steep, but it does require targeted training for content publishing teams.

The standard recommendation for organizations looking to adopt cmi5 without risk is a coexistence strategy: retain existing SCORM content and publish new strategic modules in cmi5 from the outset.

cmi5 in practice: a real-world corporate training scenario

Imagine a retail company with over 2,000 employees distributed across physical stores in multiple regions. The L&D team needs to ensure all employees complete the annual compliance module, but access devices are heterogeneous: some staff use store tablets with intermittent Wi-Fi, others access from personal mobile phones outside working hours.

With SCORM, this scenario generates familiar problems: content fails to load correctly in a mobile iframe, data is lost when a learner completes the module offline, and the LMS only shows “completed / not completed” with no insight into where the training bottlenecks are.

With cmi5, the same compliance program:

• Launches natively on any device with no iframe dependency
• Stores progress locally when offline and syncs on reconnect
• Records in the LRS which employees consistently failed the same safety regulation question, enabling the L&D team to redesign that specific section
• Delivers detailed reports by store, region, or role — without manual data exports

This level of tracking is not theoretical — it is the practical difference between a standard from 2001 (SCORM) and one designed for the reality of modern distributed training.