The Standards Question Nobody Asks Until It’s Too Late
Most LMS buying conversations focus on the obvious things: interface design, pricing, support, integrations with HR systems. Technical standards — SCORM, xAPI, cmi5 — tend to come up late in the process, if at all.
Then organisations discover that the content library they built over five years is not compatible with the platform they just bought. Or that they cannot pull the learning data their analytics team needs because their LMS does not support the right specification. Or that their blended learning programme cannot track offline completions because the standard they are using was not built for it.
Technical standards are the invisible plumbing of a learning management system. You rarely notice them when they work. You cannot ignore them when they do not.
This guide breaks down what the major standards actually mean, why they matter, and what to look for when evaluating an LMS.
SCORM: The Standard That Built the Industry
SCORM — Sharable Content Object Reference Model — has been the dominant standard in eLearning for more than two decades. If you have ever bought or built an online course, it was almost certainly packaged in SCORM format.
SCORM defines how a piece of learning content communicates with an LMS. When a learner completes a module, the content tells the LMS: this person finished, they scored this percentage, they spent this much time. The LMS records it. That exchange — simple, standardised, reliable — is what made it possible to build a global market for interoperable eLearning content.
The two versions most commonly in use today are SCORM 1.2 and SCORM 2004. SCORM 1.2 is older but still extraordinarily widespread — the majority of existing eLearning content in the world was built to this specification. SCORM 2004 added more sophisticated sequencing and navigation, but adoption was slower, and compatibility inconsistencies between different SCORM 2004 implementations created headaches that led many organisations to stick with 1.2.
Any LMS worth considering in 2026 supports both. If a vendor cannot clearly confirm SCORM 1.2 and SCORM 2004 support, that is a red flag.
What SCORM does not do is handle learning that happens outside the LMS. It was built for a world where all learning was online, synchronous, and browser-based. That world no longer describes how most organisations actually train people.
xAPI: Learning Data Beyond the Browser
xAPI — also known as Tin Can API — was developed specifically to address SCORM’s limitations. Where SCORM was built for a single context (a learner, a browser, a course), xAPI was built to capture learning wherever and however it happens.
The core idea behind xAPI is elegantly simple: a learning statement. Every learning event generates a statement in the format “Actor did something with object” — for example, “Sarah completed the compliance module,” or “James watched the product demonstration video,” or “The team practised the sales objection simulation.” These statements are stored in a Learning Record Store (LRS), which can sit inside an LMS or as a standalone service.
What this enables is genuinely transformative for organisations with complex training needs. xAPI can capture learning from mobile apps — including completions made without an internet connection and synced later. It can capture learning that happens in simulations, games, virtual reality environments, and video platforms. It can capture informal learning and social learning. It can capture any structured activity, on any device, in any context, and store it in a standardised format that can be analysed, visualised, and reported on.
For organisations running blended learning programmes — which is most organisations with serious L&D functions — xAPI is not just useful. It is increasingly necessary. If your learners complete activities offline, in mobile environments, or in tools outside the LMS itself, SCORM cannot capture that. xAPI can.
cmi5: Bringing Structure to xAPI
If xAPI’s flexibility is its strength, it is also, occasionally, its challenge. Because xAPI makes so few assumptions about how learning statements should be structured, different organisations and content developers implementing xAPI can produce data that is difficult to compare or aggregate.
cmi5 is a profile built on top of xAPI that adds standardisation back in. It defines a specific set of rules for how eLearning content packaged for an LMS should behave using xAPI — how launch sequences work, how completion and pass/fail are reported, and how content communicates with the LRS.
Think of it as SCORM’s successor: it takes SCORM’s simplicity and reliability but runs on xAPI’s data infrastructure. For organisations building new content or refreshing existing libraries, cmi5 is increasingly the specification to build toward.
Not all LMS platforms support cmi5 yet, but the number that do is growing. If you are building a long-term content strategy, asking vendors about cmi5 support is a useful indicator of how modern their technical architecture is.
Blended Learning and Offline Access
One practical implication of this standards landscape deserves particular attention: blended learning and offline access.
A blended programme that combines face-to-face sessions, online modules, and on-the-job practice creates a data capture challenge. SCORM handles the online modules. It cannot handle the face-to-face sessions or the on-the-job activity. xAPI can handle all three — but only if the LMS and content are configured to use it.
Offline access is a related challenge. Many learning platforms offer a mobile app that allows learners to download content and complete it without an internet connection, syncing when they reconnect. That functionality requires xAPI (or a proprietary equivalent) to work reliably. SCORM content runs in a browser and requires a live connection to the LMS to record progress. If offline learning matters for your workforce — and for frontline, field-based, or logistics teams it absolutely does — you need an LMS and content standard that support it.
What to Ask When Evaluating an LMS
When assessing an LMS against technical standards, five questions cover the most important ground.
Does the platform support SCORM 1.2 and SCORM 2004, and does it handle both reliably without known compatibility issues? Does it include a built-in LRS, or does it integrate with external LRS solutions? Does it support xAPI tracking from mobile apps, including offline sync? Is cmi5 on the product roadmap, or already supported? And can you export raw xAPI data for use in external analytics tools?
These questions are not designed to catch vendors out. They are designed to surface the gap between what a platform markets as capability and what it can actually deliver at the technical level. Standards support that is incomplete, inconsistently implemented, or dependent on specific content authoring tools is standards support in name only.
The Right Foundation Matters
Technical standards are not the most exciting part of choosing a learning platform. They are, however, one of the most consequential. The standard your LMS supports determines what learning you can track, what data you can analyse, and what content you can use — now and in the future.
An LMS built on modern standards is an investment in flexibility. As your training programmes evolve, your data infrastructure can evolve with them, rather than against them.
Explore how Zillearn handles SCORM, xAPI, and blended learning in one platform at https://zillearn.com/contact-us/
Sources:
- Advanced Distributed Learning Initiative. “SCORM Overview.” https://adlnet.gov/projects/scorm/
- ADL xAPI Working Group. “Experience API (xAPI) Specification.” https://adlnet.gov/projects/xapi/
- cmi5 Project. “cmi5 Specification.” https://aicc.github.io/CMI-5_Spec_Current/