eLearningDecision guide
SCORM 2004, xAPI or both? Choosing e-learning standards that keep your courses portable
Most teams meet e-learning standards the day a course built in one tool refuses to report completion in another. SCORM and xAPI solve different problems, and the right choice depends on what you need to record, where learning happens and how easily you want to move courses later. This guide compares them in practical terms and ends with a checklist you can run on any package before it reaches learners.
What SCORM and xAPI actually record
SCORM is a packaging and runtime standard. A course is delivered as a ZIP file with an imsmanifest.xml file that describes its structure, and while the learner has it open in the browser, the content talks to the learning platform through a JavaScript API. It reports a small, well-known set of data: whether the lesson was completed, whether it was passed, the score, the time spent and a bookmark so the learner can resume.
xAPI, now published as IEEE 9274.1.1, takes a different approach. Learning activity is recorded as statements in an “actor – verb – object” form, such as “Ana completed Forklift safety module 2”, and stored in a Learning Record Store. Statements can come from a browser course, a mobile app, a simulation or an offline session that syncs later. That flexibility is the point, but it also means you must decide which verbs and activities matter, because xAPI will not decide for you.
| Question | SCORM 1.2 / 2004 | xAPI |
|---|---|---|
| Where can learning happen? | In a browser session launched by the platform | Anywhere that can send a statement, including apps and offline sessions |
| What is tracked? | Completion, pass/fail, score, time, resume point | Any activity you define as statements |
| How is content packaged? | ZIP with imsmanifest.xml | Not defined by xAPI itself; cmi5 adds packaging and launch rules |
| Typical strength | Broad support in authoring tools | Rich data and learning beyond the course player |
SCORM 1.2 versus SCORM 2004 in practice
SCORM 1.2 is old and limited, yet still the most widely exported format, because almost every platform plays it. Its main weakness is that completion and success share a single status field, so a learner who finished a course but failed the quiz can be reported ambiguously. Suspend data is also small, which can break resume in long courses with many interactions.
SCORM 2004 separates completion from success, allows much larger suspend data and adds sequencing rules that control the order of activities. If your authoring tool offers both, SCORM 2004 (4th edition) is usually the better choice for compliance training where “passed” must mean exactly that. Keep SCORM 1.2 for content you must share with older platforms you do not control.
The authoring-tool round trip
Portability problems usually start in the authoring tool rather than the platform. Agree on publishing settings once and save them as a template: the SCORM version, what counts as complete (slides viewed, quiz passed or both), the passing score and whether the course reports to an LRS as well. Different authors using different settings is the most common reason two similar courses report differently.
Keep the editable source files next to the published package and record which version is live. When a regulation or product changes, you want to update the source, republish and replace the package without losing learner history. A good platform keeps attempts from the previous version and lets you decide whether learners must retake the new one.
Preview a package before learners see it
Upload every new package to a preview area first and complete it the way a learner would. Then check what the platform recorded, not what the course showed on screen. Close the window halfway through and reopen it to confirm that resume works. Fail the quiz deliberately and verify that the record says failed, not completed.
Repeat the test on a phone and with the keyboard only. Many packages that look fine in a desktop browser trap keyboard focus inside a player or hide the “next” button on small screens. Finding this in preview costs minutes; finding it after a mandatory course has been assigned to every employee costs a week of support messages.
Export progress data you can reuse
Standards matter less than what happens to the data afterwards. Training results are useful when they reach the people who act on them: HR needs completions and certificate dates on the employee file, managers need a view of their team, and sales teams running a customer academy need course progress on the account record. Plan these destinations before choosing a format.
SCORM data stays inside the platform that launched the course, so check that it can export attempts as CSV or through an API. xAPI statements can be read from the LRS by other systems, which makes it a strong fit when results feed reports, a CRM or a mobile app. Many teams use both: SCORM for packaged courses from authoring tools and xAPI for activity that happens elsewhere.
Portability and avoiding lock-in
Ask three questions of any platform. Can you download the original packages you uploaded? Can you export full learner history, including attempts, scores and dates, in an open format? Can an external LRS receive xAPI statements, or are they locked inside the product? If the answers are yes, you can change platforms later without rebuilding courses or losing evidence of past training.
Avoid proprietary course formats for anything you expect to keep longer than a year. Native lessons built in a platform’s own editor are convenient for short updates and announcements, but your core curriculum should exist as standard packages or as source files you own.
A test-package checklist
Run these checks on every new or updated course before you assign it to learners:
- The manifest opens without errors and shows the expected title and lessons.
- Completion and pass/fail are recorded separately and match the authoring settings.
- Closing and reopening the course resumes at the right place.
- A deliberately failed quiz is recorded as failed, with the correct score.
- The course works on a phone and with the keyboard only.
- Videos have captions and the transcript is available.
- Results appear in the learner report and can be exported.
- If xAPI is enabled, statements reach the LRS with the expected verbs.
How RDCopilot eLearning handles both standards
RDCopilot eLearning imports and plays SCORM 1.2 and SCORM 2004 packages and records xAPI statements, so existing courses keep working and new activity from mobile apps or live sessions lands in the same history. Completions and certificates reach the employee file in RDCopilot HR, customer academy progress shows on the CRM account, and Reports turns training data into team and course dashboards.
We start by importing a sample of your current packages and running the checklist above with you, so any reporting issue is found before launch. Setup and course migration are a one-off fee; the monthly licence covers EU hosting, updates, backups and support, and any additional work is billed at a fixed hourly rate.
Follow the references
Sources & inspiration
EdMill
Devpost project by Alban P., Appoline B., Gabrielle Verneuil, Olivier Coué, Quentin Giraud, Sophie Manago
An online course platform whose team worked through SCORM imports and exports and xAPI learner tracking, a useful reference for the portability questions above.
This independently created project is credited as inspiration. The workflow and implementation guidance in this article are RDC’s analysis.
Put the guide to work
Start with your workflow.
Tell us what your team needs to do, which systems are involved and where the current process slows down.