If you have ever tried to move a course from one learning management system to another, or wondered why completion data from a mobile app never made it into your reports, you have run headfirst into the problem of e-learning interoperability. Interoperability is the ability of different systems — authoring tools, LMSs, learning record stores, mobile apps — to exchange content, track learner activity, and report results in a way both sides understand. A handful of technical standards make this possible, and knowing how they work will save you from expensive surprises.
SCORM, or Sharable Content Object Reference Model, has been the dominant standard for packaging and tracking e-learning content for more than two decades. At its core, SCORM defines two things: a way to bundle course files into a ZIP package with a manifest that describes the structure, and a JavaScript-based communication protocol that lets the content talk to the LMS while a learner is taking a course. When a learner launches a SCORM module, the LMS opens the content in a browser window, and the content uses a set of API calls to send data back — things like completion status, score, time spent, and bookmark location. Because SCORM has been around so long, nearly every LMS and authoring tool supports it, which makes it the safest bet for basic course delivery.
But SCORM has real limitations. It requires a browser. It assumes the learner is sitting in front of an LMS. It cannot track experiences that happen outside a traditional course — think simulations on a separate platform, instructor-led sessions, on-the-job observations, or learning that happens in a mobile app while offline. The data model is also relatively rigid: you get completion, pass/fail, a score, and a handful of interaction records, but you cannot easily capture richer information like how a learner navigated a branching scenario or what choices they made in a simulation.
The Experience API, commonly called xAPI (and sometimes still referred to by its earlier project name Tin Can API), was designed to address those gaps. Instead of relying on a direct, real-time connection between content and an LMS, xAPI uses a simple data structure called a statement. Each statement follows an actor-verb-object pattern: "Jane completed Module 3," "Carlos scored 85 on the compliance quiz," "Amira watched the safety video." These statements are sent to a Learning Record Store, or LRS, which can be a standalone system or a component built into an LMS. Because statements are just data sent over standard web protocols, they can come from virtually anything — a mobile app, a VR headset, a chatbot, a point-of-sale system, even a spreadsheet upload. This makes xAPI dramatically more flexible than SCORM.
That flexibility, however, introduces its own challenges. xAPI does not define how to package or launch content. It does not specify what verbs or activity types you should use. Two organizations tracking "completed" might define it differently, which makes cross-system reporting messy unless you invest in a shared vocabulary, sometimes called a profile. Without governance, an LRS can fill up with inconsistent data that is difficult to analyze.
cmi5 exists to solve exactly this problem. It is a profile built on top of xAPI that adds back the structure SCORM users expect — a defined course package format, standardized launch mechanisms, a required set of verbs (like "completed," "passed," "failed"), and clear rules about which statements the LMS is responsible for versus which the content generates. Think of cmi5 as the best of both worlds: xAPI's flexible tracking underneath, with a SCORM-like contract between content and platform on top. Adoption is growing but still trails SCORM significantly, so check your LMS vendor's support before committing.
So what should a practical L&D leader do with all of this? Start by mapping your actual tracking needs. If you are delivering self-paced courses inside a single LMS and all you need is completion and score, SCORM 1.2 or SCORM 2004 will serve you reliably. If you need to capture learning across multiple platforms, track informal learning, or build richer analytics, xAPI is the right foundation — but plan to invest in vocabulary governance and an LRS strategy. If you want structured course delivery with modern tracking, investigate cmi5 and confirm your systems support it.
When evaluating authoring tools, ask what export formats they support and test the output in your actual LMS — not just in theory. When evaluating LMSs or LRSs, ask how they handle each standard, whether they can consume xAPI statements from external sources, and how they surface that data in reports.
Finally, remember that a standard only delivers value if it is consistently implemented. Build internal guidelines for how courses are packaged, what metadata is required, and how completion is defined. These governance decisions matter more than which acronym you choose, because the most sophisticated standard in the world will not help you if every team uses it differently.