SCORM 1.2 vs SCORM 2004 – Which Version Should You Publish?
Every authoring tool has the same small dropdown in its publish window, offering SCORM 1.2, SCORM 2004 and sometimes several editions of 2004 for good measure. Most people select whatever was chosen last time and hope for the best. That approach works until a course reports "incomplete" for someone who passed, and suddenly the choice matters a great deal. When you weigh SCORM 1.2 vs 2004, which version should you actually publish?
Publish SCORM 1.2 unless you have a specific reason to choose SCORM 2004. SCORM 1.2 has the broadest LMS support and handles completion, pass or fail and a single score reliably, which covers most compliance, onboarding and product courses. Choose SCORM 2004, ideally the 3rd or 4th edition, when you need completion and pass/fail reported as separate values, more room for saved progress than SCORM 1.2's 4,096 characters, or sequencing rules that control the order of lessons. Confirm your LMS handles 2004 well first, since support varies more than it does for 1.2. If you're still unsure, publish both, test both, and keep the one that reports correctly.
What Actually Changed Between SCORM 1.2 and SCORM 2004?
SCORM 2004 kept the same basic idea as 1.2 (a zip package plus a JavaScript conversation with the LMS) but cleaned up the data model and added a sequencing system. Here are the differences that affect real projects.
| Feature | SCORM 1.2 | SCORM 2004 (3rd/4th edition) |
|---|---|---|
| Status reporting | One field: lesson_status | Two fields: completion_status and success_status |
| Saved progress (suspend data) | 4,096 characters | 64,000 characters |
| Score | Raw score with min and max | Raw plus a scaled score from -1 to 1 |
| Sequencing between lessons | None (LMS decides) | Detailed rules defined in the package |
| Session time format | HHHH:MM:SS | ISO 8601 duration, such as PT1H5M |
| API function names | LMSInitialize, LMSSetValue... | Initialize, SetValue... |
| LMS support | Nearly universal | Common, but quality varies |
The status row is the one people notice most. In SCORM 1.2, a course can send "passed" or "completed," but it only gets one value. If the learner passes, the course usually sends "passed," and the LMS has to decide whether that also means finished. Most platforms treat it that way, but some don't, and that inconsistency generates a large share of confused help-desk tickets.
Rustici Software keeps a clear history of each release on its SCORM versions page if you want the full timeline.
Why Does SCORM 1.2 Still Win Most of the Time?
SCORM 1.2 wins because it's predictable in the best sense. It has been available since 2001, every mainstream LMS supports it, and nearly every edge case has already been discovered and resolved by someone else. When I'm handed a course with no other information, I publish 1.2 first.
Consider what a typical compliance course needs to report: whether the learner finished, whether they passed and what the score was. SCORM 1.2 does exactly that, and the extra precision of 2004 doesn't help if your LMS report only displays a green checkmark anyway.
There's a support consideration as well. When a 1.2 course misbehaves, your LMS vendor's support team has seen the problem before, but with 2004, especially with sequencing, you're more likely to be the first customer to encounter a particular quirk.
When Is SCORM 2004 the Better Choice?
SCORM 2004 is the better choice when one of its specific features solves a real problem you have, and these are the four situations I see most often.
You need "completed" and "passed" as separate facts
Say a course requires learners to view every section and also pass a quiz. With 2004, the course can report completion_status as "completed" and success_status as "failed" at the same time, which is accurate data. A learner who read everything but failed the test then appears differently in reports from one who skipped straight to the quiz.
Your course saves a lot of progress data
Long courses, branching scenarios and courses with many interactions can exceed 4,096 characters of suspend data. When that happens in 1.2, resume breaks without any warning, so learners relaunch and land back at the start, or their answers disappear. SCORM 2004's larger limit usually resolves it.
You want the package to control lesson order
Sequencing and navigation rules let a multi-SCO package say "lesson 3 opens after the lesson 2 quiz is passed" or "skip the pretest content the learner already mastered." The feature is powerful, but it's also the least consistently supported part of SCORM, so test it carefully.
You need richer quiz interaction data
Both versions record interactions, but 2004 adds a description field and clearer response formats, which makes question-level reports easier to read.
Which SCORM 2004 Edition Should You Pick?
Pick the 3rd or 4th edition. The 3rd edition (2006) resolved a long list of ambiguities from the early releases and raised the suspend data limit, while the 4th edition (2009) refined sequencing further. Most authoring tools default to one of these two, and most LMS platforms that support 2004 handle both.
The 2nd edition still appears in some older tools and LMS settings, but avoid it for new work unless your LMS specifically requires it. Its smaller suspend data limit removes one of the main reasons to choose 2004 in the first place.
Not sure which way your project leans? Try the picker below, which asks three questions about tracking, LMS support and sequencing and then suggests a format with a short explanation.
If the picker points you past SCORM entirely, that usually means you need to track learning that happens outside a browser-launched course. In that case, the better question is what is xAPI and whether your LMS can store its data.
How Should You Test SCORM 1.2 vs 2004 in Your LMS?
Test with your real LMS, your real course and a fictional learner account. Specifications tell you what should happen, but only a test tells you what does happen.
- Publish the same course twice, once as SCORM 1.2 and once as SCORM 2004 (3rd or 4th edition).
- Upload both to a sandbox or hidden test course.
- Launch each as a test learner. Go halfway, close the window and relaunch. Confirm you land where you left off.
- Finish the course and fail the quiz once. Check the LMS record.
- Retake and pass. Check the record again, including the score and completion date.
- Run the LMS report your managers actually use. Confirm it shows what they expect.
Whichever version passes every step is your answer. If both pass, choose 1.2 for its wider support, unless you specifically want the separate pass and complete statuses.
How Do Authoring Tools Handle Each Version?
Authoring tools hide most of the version differences, but they still ask you to make one decision that matters: how the course reports status. For SCORM 1.2, that usually means selecting a pair of values, such as passed/incomplete, passed/failed, completed/incomplete or completed/failed. The first word is what the course sends on success, and the second is what it sends otherwise.
That pairing has to match your LMS. If your LMS counts only "completed" toward a compliance requirement, a course publishing passed/failed may never show as done. If your LMS treats "failed" as final and locks the learner out, a passed/failed pairing can block retakes. Ask your LMS administrator which status the reports and rules actually look for, then choose the pair that sends it.
For SCORM 2004 the tool usually sets completion and success separately, so the pairing question mostly disappears. You'll still choose what triggers completion (slides viewed, quiz passed, or both), and that choice deserves the same care.
What If Your LMS Only Supports SCORM 1.2?
Many LMS platforms support SCORM 2004 only partially, and some older or lightweight ones support only 1.2. You can still build solid courses, as long as you design around those limits.
- Watch the suspend data budget. Fewer tracked interactions, shorter variable names and fewer slides set to "resume saved state" all shrink what the course stores. Some authoring tools also offer a compression option for resume data.
- Split very long courses into shorter modules. Each module gets its own 4,096 characters, and learners get natural stopping points.
- Track pass or complete, not both. Decide which one your reporting really needs and publish for that.
- Let the LMS handle lesson order. Most platforms can require one course before the next, which replaces 2004 sequencing for many programs.
What Goes Wrong When Teams Switch Versions?
Switching versions mid-rollout causes more trouble than either version does alone, but a few habits keep the transition painless.
- Don't replace a live package while learners are partway through. Many LMS platforms start a fresh attempt, and in-progress learners lose their place.
- Check your completion rules after switching. A rule written for "passed" in 1.2 may need to look at success_status in 2004.
- Re-run reports. Some LMS reports display 1.2 and 2004 statuses differently, so a dashboard filter might miss the new version.
- Keep one version per course in your library. Mixed versions of the same course make audit reports confusing.
SCORM 1.2 vs 2004: Start Simple, Upgrade for a Reason
The SCORM 1.2 vs 2004 decision is easier than it looks. SCORM 1.2 is the safe default because almost every LMS supports it fluently. SCORM 2004 earns its place when you need separate completion and pass status, more saved progress, or lesson sequencing, and only after your LMS proves it handles 2004 well.
Before your next publish, run the six-step test above on that course and document the result. That single page becomes your team's publishing standard, and the dropdown stops being a guess.