Completion vs Success vs Progress
Completion is not success. Success is not progress. If your LMS reporting looks inconsistent, the issue is often not the LMS. It is a misunderstanding of how SCORM 2004 separates these three concepts.
Discover more
The SCORM 2004 Data Model
Tracking a score is simple. Tracking learning state correctly is not. SCORM 2004 introduced a data model that separates completion, success, and progress. If you misunderstand that separation, your LMS behavior will never be predictable.
The SCORM 2004 Run-Time Environment
Most SCORM bugs are not sequencing problems. They are session lifecycle problems. If learner data disappears, completion is inconsistent, or LMS states look unpredictable, the Run-Time Environment is usually where the mistake begins.
SCORM 2004 Architecture Explained
SCORM 2004 is not just “SCORM 1.2 but newer.” It is a layered architecture with clearly separated responsibilities.
Why SCORM 2004 Exists
If you have ever struggled with inconsistent LMS progression, unclear completion rules, or vendor specific behavior, you have already felt why SCORM 2004 became necessary.
LMS Behavior: What SCORM Controls and What It Does Not
What the spec enforces, what it does not define, and where LMS vendors improvise.
The JavaScript API: SCORM’s Communication Core
How content finds the API, how it communicates, and how the lifecycle works.
Tracking Learner Data: The AICC Data Model
From status to score, AICC’s CMI data model defined how learning progress was tracked. Let’s explore the data fields that still influence SCORM and xAPI today.
Anatomy of an AICC Course
Ever wondered how early e-learning courses were structured? Let’s unpack the AICC file set — .crs, .au, .des, .cst — and see how they defined a course before XML and JSON existed.