SCORM 1.2 vs SCORM 2004: Which Do You Actually Need?

SCORM 2004 is newer, more capable, and — for most training — completely unnecessary. Here's how to decide.

The short answer

Use SCORM 1.2 unless you have a specific requirement that only 2004 meets. 1.2 is supported by essentially every LMS in existence; 2004 support is common but not universal, and implementations vary.

What 2004 adds

• Sequencing and navigation — rules that control the order learners move through content, and conditions that unlock sections.
• Better status granularity — completion and success are separate values rather than conflated.
• Richer data model — more interaction detail, more objectives, longer suspend data.
• Multiple attempts handling — clearer rules for what happens on a re-attempt.

What that costs you

Sequencing is powerful and notoriously fiddly. Complex sequencing rules behave differently across LMS implementations, which turns 'it works in SCORM Cloud' into 'it doesn't work in the client's Cornerstone instance'. If you don't need the rules, you're taking on the compatibility risk for nothing.

When 2004 is genuinely the right call

• Your client or LMS mandates it — some enterprise and government platforms do.
• You need enforced sequencing that your authoring tool can't achieve within a single SCO.
• You need to distinguish 'completed but failed' from 'completed and passed' as separate reportable values.
• You have long-form courses where 1.2's suspend-data limit (4096 characters) is genuinely constraining.

When 1.2 is the right call

Everything else. Single-SCO courses, most compliance training, most onboarding, most product training. If your course is one linear experience with a completion status and maybe a score, 1.2 does everything you need and will work everywhere.

What about xAPI and cmi5?

Different question. xAPI tracks learning experiences beyond a course — including things that happen outside an LMS — and needs a Learning Record Store. It's excellent for measuring behaviour over time, but it doesn't replace SCORM for the simple job of 'put this course in the LMS and track completion'. cmi5 is the bridge between the two, and support is still patchy.

The practical recommendation

Export SCORM 1.2. If a client comes back requiring 2004, deal with it then — it's a far less common request than vendors imply.