SCORM, xAPI and cmi5 Explained for Instructional Designers

SCORM, xAPI, cmi5 — three acronyms that get used interchangeably in meetings and confused constantly in practice. If you build or maintain e-learning, you need a working mental model of each: not the spec-level detail, but enough to choose correctly and call out bad assumptions. Here it is, in plain language.

The one-sentence version of each

• SCORM — the long-standing standard for packaging a course and tracking it inside an LMS, in a web browser. The default for most corporate e-learning.
• xAPI (Experience API, "Tin Can") — a flexible way to record learning experiences as statements ("Anna passed the fire-safety quiz"), anywhere, not just inside an LMS browser session.
• cmi5 — a profile/ruleset that uses xAPI but adds the structure SCORM had (launch, completion, pass/fail), so you get xAPI’s flexibility with LMS-style governance.

SCORM: the incumbent

SCORM packages your course as files (HTML, JS, media) plus a manifest, and defines how that course talks to the LMS: initialize, report status, send a score, save resume data, finish. It runs in the browser and assumes the learner is inside the LMS. It comes in two live versions — 1.2 (older, ubiquitous) and 2004 (more capable, unevenly supported).

Its limits are exactly its assumptions: it tracks a fairly fixed set of things (completion, score, time, a single resume blob), it lives in the browser, and it struggles with anything outside a hosted course — mobile apps, simulations, classroom events, "watched a video on YouTube." But it is everywhere, it is well understood, and an enormous body of content depends on it.

xAPI: track anything, anywhere

xAPI throws out the assumption that learning only happens in a browser inside an LMS. Instead, any system can send statements shaped like "actor — verb — object" ("Maria completed the forklift simulation") to a Learning Record Store (LRS). That statement can come from a mobile app, a VR headset, a piece of equipment, a website, or a traditional course.

The power is breadth: you can capture learning experiences SCORM never could, and analyze them across sources. The cost is structure: xAPI by itself does not dictate what a "course" is, when something counts as "complete," or how an LMS should launch it. That freedom means two xAPI implementations can be valid and still not agree on the basics — which is the problem cmi5 solves.

cmi5: xAPI with rules

cmi5 is best understood as "xAPI, but with the discipline SCORM had." It is a defined profile that uses xAPI statements under the hood but adds the missing structure: how the LMS launches the content, how a session is bounded, and standardized verbs for the things every LMS cares about — launched, initialized, completed, passed, failed, terminated.

The result is the combination people actually want: the flexibility and reach of xAPI, plus the predictable completion/pass-fail governance of SCORM. If you are choosing a modern standard for new content and your platform supports it, cmi5 is often the sweet spot.

How they relate

• SCORM and xAPI are different families — SCORM is browser-and-LMS-bound; xAPI is open-ended and LRS-based.
• cmi5 is built on xAPI — it is a ruleset layered on top, not a separate technology.
• They coexist — most organizations run SCORM content today and adopt xAPI/cmi5 for new or non-traditional experiences, rather than ripping everything out.

Which should you use?

1. Standard course, hosted in a standard LMS, just need completion and score → SCORM (1.2 unless you have a reason for 2004).
2. You need to track learning beyond the browser — apps, simulations, on-the-job, blended → xAPI, with an LRS.
3. You want xAPI’s reach but still need clean launch/completion/pass-fail governance and broad LMS interoperability → cmi5, if your platform supports it.
4. You are maintaining an existing library → it is almost certainly SCORM, and keeping it healthy matters more than chasing a new standard.

Pick the standard your platform fully supports and that matches what you actually need to measure. The newest standard is not the right one if your LMS only half-implements it.

The practical takeaway

For the foreseeable future, most instructional designers will keep working with SCORM packages every day, while xAPI and cmi5 grow alongside it for experiences SCORM cannot reach. Knowing which is which lets you choose deliberately and push back when someone insists you "must" migrate everything to xAPI for a course that only needs completion tracking.

Working with the SCORM you already have

Whatever the future holds, your existing SCORM library still has to work today. ScormEdit helps you keep it healthy — validate packages, fix upload errors, edit text and images, and split or merge courses — all in the browser, from the published .zip, without the original source file. The standard your content uses today is the one worth maintaining well.