cmi5 explained: how it brings SCORM-like structure to xAPI. Compare SCORM vs xAPI vs cmi5 and pick the right e-learning standard by use case.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
A plain-English explainer of SCORM, its versions, how it compares to xAPI and AICC, and when you actually need it.
A plain-English comparison of xAPI and SCORM, with a use-case recommendation for regulated, multi-site employers.
A plain-English explainer of what a learning record store is, how it works with xAPI and your LMS, and when a mid-market training team actually needs one.
If you're choosing an e-learning standard today, the short answer is this: cmi5 is usually the right modern default. cmi5 is an xAPI profile that brings back the structure SCORM gave you — defined courses, launch rules, pass/fail, completion — while keeping xAPI's ability to track far richer learning data. SCORM still works and is everywhere; plain xAPI is powerful but loose. cmi5 sits between them, and for most multi-site organizations it's the practical choice.
This post explains what each standard does, compares SCORM vs xAPI vs cmi5 in a table, and recommends one by use case so you're not guessing when a vendor's authoring tool asks how to publish.
A standard is the contract between the content (the course your team builds or buys) and the platform (your LMS). It defines how a course launches, how it reports progress, and what "complete" means. Without one, every course would need custom wiring to every LMS — exactly the lock-in and integration cost you're trying to avoid when you own your platform.
Three standards matter in practice. All three are tracked and maintained with reference material from ADL, the US Department of Defense initiative that originally created SCORM and later co-developed xAPI.
SCORM (Sharable Content Object Reference Model) has been the industry default since the early 2000s. Almost every authoring tool exports it, and almost every LMS imports it. It defines a fixed structure — a course launches inside the LMS in a browser, and a small set of data points flows back: score, completion status, pass/fail, time, and bookmarking.
Its limits are well known. SCORM runs in the browser window, so it can't easily track learning that happens outside the LMS — instructor-led sessions, simulations, mobile field work, on-the-job tasks. It also can't run reliably offline, which matters for deskless and multi-location workforces. The data it captures is shallow by modern standards.
xAPI (the Experience API, sometimes "Tin Can") replaced SCORM's narrow reporting with statements: "actor — verb — object," such as "Maria completed Lockout/Tagout Refresher." These statements can describe almost any learning experience, online or off, and they're stored in a Learning Record Store (an LRS) rather than trapped in the LMS.
The trade-off is structure. xAPI on its own doesn't define how a course launches, what counts as "complete," or how the LMS authorizes the content. Two teams can implement xAPI in ways that don't interoperate. That flexibility is a feature for custom analytics and a problem for portable, audit-ready compliance courses.
cmi5 is an xAPI profile — a defined set of rules layered on top of xAPI. It answers the questions plain xAPI leaves open: how content launches, how it's authorized, and which statements signal passed, failed, completed, and terminated. In effect, cmi5 gives you SCORM's predictable course structure and sequencing expectations, but the data underneath is full xAPI, stored in an LRS.
That combination is why cmi5 is the sensible modern target. You keep the things compliance teams rely on — a clear "did they pass, and when" record — while gaining offline support, tracking beyond the browser, and a data model that doesn't dead-end. For a manufacturer or utility with field crews and varied training types, cmi5 captures the in-person and on-the-job pieces SCORM never could.
Note that authoring-tool and LMS support shifts over time — confirm current cmi5 support with your authoring vendor and platform before you standardize, as feature coverage varies by product and version.
Choose SCORM when you need the widest possible compatibility right now, your courses are browser-based, and your tracking needs are limited to score and completion. It remains a safe baseline, and a good platform should still ingest it.
Choose plain xAPI when you're tracking experiences that aren't structured courses at all — simulations, performance support, on-the-job sign-offs feeding a custom analytics or competency model — and you control both ends of the integration.
Choose cmi5 for new, structured training content — especially compliance and certification courses — where you want defined pass/fail records and the freedom to track beyond the browser. It's the standard that ages best and the one we'd point most mid-market firms toward.
Importantly, this isn't strictly either/or. A platform you own can support SCORM for legacy content and cmi5 for new content side by side, with an LRS underneath. Owning the platform is what lets you make that call on your timeline instead of a SaaS vendor's roadmap. How content actually launches and reports across your sites is part of deployment, and the completion data these standards produce is what feeds defensible compliance reporting.
Is cmi5 the same as xAPI? No. xAPI is the underlying specification; cmi5 is a profile that adds rules on top of it — launch, authorization, and defined completion semantics. cmi5 content sends xAPI statements, so it's xAPI with structure.
Does cmi5 replace SCORM? For new content, it's the natural successor — it covers what SCORM did and more. But SCORM isn't going away, and you'll likely run both during a transition. Keep a platform that ingests both.
Do I need a Learning Record Store for cmi5? Yes. cmi5 (like xAPI) stores statements in an LRS. Many modern platforms include or integrate one. Confirm LRS support and where the data resides as part of your selection.
Will my existing SCORM courses still work? On a capable LMS, yes. There's no need to re-author everything at once — standardize new builds on cmi5 and migrate legacy SCORM courses as they come up for revision.
SCORM is the established, universally supported baseline with shallow data. xAPI is powerful and flexible but unstructured on its own. cmi5 is the middle path: an xAPI profile that restores SCORM-like structure and clear pass/fail records while capturing rich data beyond the browser. For most mid-market, multi-site organizations building new compliance and certification content, cmi5 is the standard to target — ideally on a platform you own, so you can run SCORM and cmi5 together and decide when to migrate.