The eLearning standards landscape
When an enterprise buys an LMS, the vendor demos beautiful courses, clean interfaces, and impressive dashboards. What the vendor does not demo is what happens when the buyer tries to upload their existing content library — 200-800 courses developed over the last decade by various authoring tools, designed for various LMS versions, packaged in various formats.
This is where the eLearning content standards conversation matters. Three standards dominate:
SCORM (Sharable Content Object Reference Model)
The dominant standard for the last two decades. SCORM 1.2 was the original; SCORM 2004 (often called "SCORM 2004 4th Edition") is the more capable successor. SCORM courses are packaged ZIP files containing HTML/JavaScript content and a manifest that tells the LMS how to launch the course, track completion, and report scores.
Strengths: Universal LMS support. If a course is SCORM-compliant, it will run on essentially any LMS produced in the last 20 years.
Weaknesses: Limited tracking (just completion, score, time spent), no offline support, no mobile-friendly behaviour, no rich-data analytics, browser-launched only.
In 2026, SCORM is still the largest installed base of enterprise eLearning content. Many organisations have decades of SCORM courses that work, that they have invested in, and that they cannot easily replace.
xAPI (Experience API, also known as Tin Can)
The successor standard. xAPI tracks learning experiences as statements ("actor did activity with result") and stores them in a Learning Record Store (LRS). Courses can be on any platform, mobile or web, online or offline, and the experiences flow to the LRS for analytics.
Strengths: Rich tracking (every interaction can be recorded), mobile and offline native, multi-platform, supports beyond-course learning (videos, simulations, real-world activities).
Weaknesses: More complex to implement, LMS vendor support is variable, ecosystem is fragmented.
xAPI is the future for organisations doing serious learning analytics. The transition from SCORM to xAPI is still in progress in 2026.
CMI5
A pragmatic standard that combines SCORM's structure with xAPI's tracking capabilities. CMI5 packages courses like SCORM does but uses xAPI for tracking. It is the bridge format for organisations migrating from SCORM to xAPI.
Strengths: SCORM-like packaging (familiar workflow) with xAPI tracking (rich analytics).
Weaknesses: Newer standard, fewer authoring tools, fewer LMS implementations.
What the standards conflict looks like in practice
A real example: An Indian enterprise with 12 years of compliance training content, mostly SCORM 1.2 packages built by various consultants. The L&D team buys a "modern" LMS that supports "all major standards" per the vendor RFP response.
On Day 1 of content migration:
- 220 of 280 SCORM 1.2 packages load and run correctly
- 35 packages have manifest issues from the authoring tool's idiosyncrasies; need cleanup
- 18 packages fail to launch because they use SCORM 1.2 features the new LMS implements differently
- 7 packages run but completion tracking fails (the LMS records "incomplete" even after the learner finishes)
The L&D team now faces a choice: re-author the failing courses (₹40-80k per course × 60 courses = ₹40-50 lakh), accept that 21% of the content library is unusable, or push the LMS vendor for fixes (which take months and may not resolve).
This is not an unusual scenario. It happens at most enterprise LMS implementations because content standards conformance is more theoretical than practical.
The buyer-side questions vendors do not want
When evaluating an LMS, ask these eight questions and demand demo evidence, not RFP answers:
1. What versions of SCORM do you actually support?
Some vendors claim SCORM 2004 support but only handle a subset of the SCORM 2004 specification. Edge cases break. Ask for the conformance test results from the ADL (Advanced Distributed Learning) test suite .
2. Show me a SCORM 1.2 course running with all features
Many older compliance courses use SCORM 1.2 features that newer LMSs implement loosely. Run an actual demo with one of your real courses, not the vendor's test course.
3. What is your xAPI implementation depth?
xAPI has profiles and complexity. Ask for: which xAPI statement types are supported, which verbs are accepted, what the LRS storage and retention model is, and how xAPI data flows to reporting.
4. CMI5 support and roadmap
If you are planning to migrate from SCORM to xAPI gradually, CMI5 is your friend. Ask for CMI5 support details and the vendor's roadmap.
5. Authoring tool compatibility
The major authoring tools (Articulate Storyline, Articulate Rise, Adobe Captivate, Lectora, iSpring, Easygenerator) produce slightly different package structures. Ask which tools your LMS handles cleanly.
6. Mobile rendering of SCORM courses
SCORM courses written for desktop browsers do not always render well on mobile. Ask how the LMS handles this — responsive wrapping, mobile rendering, or unchanged delivery.
7. Offline support and synchronisation
For learners with intermittent connectivity, can content be downloaded for offline consumption and synchronised when reconnected? SCORM does not natively support this; xAPI does.
8. Migration path for legacy content
The vendor's migration tools and services. Manual re-uploading of 500 courses is operationally painful; automated migration with conversion services is materially better.
Where authoring strategy meets LMS choice
The authoring tool the L&D team uses is downstream of LMS choice and content standards strategy.
If primarily SCORM and likely to stay there
Use SCORM-strong authoring tools (Storyline, Captivate, Lectora). Mature, capable, well-supported. Output is universally compatible.
If moving to xAPI
Use authoring tools with strong xAPI output (Storyline 360+, Rise 360, iSpring Suite, Articulate Review). Ensure the LMS handles xAPI well; otherwise you produce content the LMS cannot fully track.
If on a hybrid path
Use authoring tools that support both. CMI5 packages are useful here.
For microlearning
Modern microlearning tools (EdApp, Axonify, native LXP authoring) often skip the standards conversation entirely and rely on native APIs. This works inside that platform but locks the content in.
The standards conversation in 2026
Where does the industry actually sit in 2026?
- SCORM 1.2: largest installed base of legacy content, slowly declining. Still essential for any LMS in enterprise use.
- SCORM 2004 4th Edition: steady use; sweet spot for compliance training where rich navigation and sequencing matters.
- xAPI: growing rapidly for advanced learning analytics use cases. Strong adoption in tech-forward organisations.
- CMI5: niche but growing as a bridge format.
- Native (non-standard) content via APIs: dominant for new content within specific LXPs and microlearning platforms; trapped inside those platforms.
A pragmatic enterprise strategy in 2026:
- LMS for compliance: must handle SCORM 1.2 and 2004 well; xAPI support nice-to-have
- LXP for skill building: native authoring acceptable as long as you can export to xAPI for analytics consolidation
- New compliance content: author in SCORM 2004 or CMI5 for flexibility
- New skill-building content: author in xAPI native or CMI5; consider non-standard if locked into a specific LXP
The bottom line
eLearning content standards are unglamorous infrastructure that determine whether your existing content library transfers to your new LMS cleanly. Get the standards conversation right early in LMS evaluation. The cost of getting it wrong — typically ₹30-80 lakh of content re-authoring per failed implementation — is large enough to justify careful upfront work.
For organisations with significant existing content libraries, the LMS evaluation is as much about content standards as about features. Vendors who handwave on standards should be deprioritised; vendors who answer specifically and demonstrably should be advanced.
