SCORM 1.2, SCORM 2004 and xAPI: What a Buyer Needs to Know

If a training provider mentions SCORM, SCORM 2004 or xAPI and you are not sure which one you actually need, you are not alone. All three exist to solve the same underlying problem, getting a course to report back to your learning management system (LMS) correctly, and providers do not always explain which one they mean or why it matters to you as a buyer, rather than to whoever built the course.

What SCORM actually is

The ADL Initiative, the organisation that created and still maintains the standard, describes SCORM as a technical framework for packaging e-learning content so it works the same way across different learning management systems. In practice, that means a course built to SCORM specification arrives as a single file your LMS can import, and reports back a small set of standard data: whether a learner started it, finished it, and what score they got.

SCORM 1.2 vs SCORM 2004: what actually changed

SCORM 1.2 was released in 2001 and, in the ADL Initiative’s own words, was “the first version of SCORM that was widely adopted.” SCORM 2004 followed from 2004, with a fourth and most recent edition in 2009, adding more detailed sequencing and navigation rules: finer control over the order learners move through content. For most buyers this distinction matters less than providers sometimes suggest. Both report completion and score reliably, and SCORM 1.2 remains, in the ADL Initiative’s own words, still “in wide use” precisely because it is old enough that every LMS built in the last two decades has had time to support it properly.

Where xAPI fits

xAPI, also called the Experience API, is a newer specification that the ADL Initiative itself now recommends for new projects. It can record a far wider range of learner activity than SCORM, not just completion and score, but individual actions inside or outside an LMS altogether. The trade-off is that xAPI needs a Learning Record Store to receive the data, which not every organisation has set up, whereas SCORM reports straight into the LMS you already run.

Why the confusion happens

Providers sometimes use “SCORM compliant” as a blanket phrase without saying which version, because from their side of the fence any of the versions technically qualifies. From a buyer’s side, the version matters because your LMS was built to support specific ones, and a package built to a version your LMS does not fully support can fail silently: it uploads, sits there, and never reports a completion back to you, so nobody notices the problem until someone asks for a completion report that does not exist.

Which one should you ask for?

For most organisations buying a course to run in an existing LMS, such as our AI training courses, SCORM 1.2 remains the safest specific request, precisely because of how long it has been supported. Asking for “SCORM” without a version number is not quite specific enough. Asking for SCORM 2004 buys you sequencing features most single courses do not need. Asking for xAPI only makes sense if you already have, or plan to set up, a Learning Record Store to receive what it sends.

Does the version matter if you have no LMS at all?

If your organisation has no LMS, none of this changes what you should ask for from the course itself, but it does change who hosts it. Some providers can host learners directly, with logins, certificates and reporting handled for you, without your organisation needing to stand up an LMS just to run one course.

A note on cost

None of the three formats is inherently more expensive to build well. If a provider quotes a higher price for “SCORM 2004” or “xAPI” specifically, ask what extra capability you are actually paying for, since for most single courses without a Learning Record Store already in place, the answer is very little.

How to check a package actually is what it claims

A label of “SCORM 1.2 compliant” is a claim, not a guarantee. Before you roll a course out to your whole organisation, ask the provider to confirm in writing that the package has been tested against a standard SCORM 1.2 compliant LMS, and, where possible, run it through a small pilot in your own system first, the same LMS question worth asking whichever of the three training formats you end up buying. A short pilot with a handful of learners is the cheapest way to catch a reporting problem before it affects everyone.

What a course reports, and what it doesn’t

Even within SCORM 1.2, providers make different choices about what a course actually tracks. At minimum, expect a start, a completion, and a score against the pass mark. Some providers add time spent on each screen or section-level detail; most single courses do not need that level of granularity. Ask what your specific course reports before you assume it matches what a previous provider gave you; see our pricing for what is included as standard in ours.

A short checklist

Before you sign anything: ask for the specification by name and version, not just “SCORM”; ask how completion and score report back to your own LMS; ask for written confirmation that the package has been tested in a standard SCORM 1.2 compliant system; ask exactly what data the course reports, beyond a bare completion and score; and, if you have no LMS, ask what hosting the provider offers instead.