AICC and SCORM are two technical standards that allow e-learning courses to communicate with a learning management system (LMS). If you build online training, buy courseware from a vendor, or manage a corporate LMS, these standards determine how completion status, quiz scores, and learner progress travel between the course and the platform that records it. Both solve the same fundamental problem, but they do it in different ways, and understanding those differences matters when you’re choosing how to package and deliver training content.
What AICC Does
AICC stands for Aviation Industry Computer-Based Training Committee. The name reflects its origins in aviation training during the 1980s and 1990s, but the standard spread well beyond that industry. AICC defines a way for course content hosted on an external server to communicate with an LMS using HTTP protocols, the same basic communication method that web browsers use to request and receive web pages.
The practical upside of this approach is cross-domain hosting. Because AICC sends data between servers over HTTP, the course files don’t need to live on the same server as the LMS. A third-party training vendor can host a course on their own infrastructure, and when a learner launches it from your LMS, the two systems pass data back and forth. The LMS still records whether the learner completed the course, how they scored, and how much time they spent. This made AICC especially popular with organizations that purchased off-the-shelf courses from external content libraries.
What SCORM Does
SCORM stands for Sharable Content Object Reference Model. It was developed by the Advanced Distributed Learning Initiative, a U.S. Department of Defense program, and it became the dominant e-learning standard for most of the 2000s and 2010s. SCORM packages course content into a standardized ZIP file (often called a “SCORM package”) that you upload directly into an LMS. Once a learner launches the course, the LMS tracks their activity and progress using predefined data models.
There are two major versions you’ll encounter. SCORM 1.2 is simpler and still widely used. SCORM 2004 added sequencing rules that let course designers control the order in which learners move through content, along with a richer set of data fields. Most modern LMS platforms support both versions.
Unlike AICC’s server-to-server communication, SCORM relies on a JavaScript API running in the learner’s browser. The course and the LMS need to be in the same browser window context, which historically created limitations when course content was hosted on a different domain than the LMS. Cross-domain SCORM delivery has become more manageable with modern web technologies, but it remains less straightforward than AICC’s built-in support for external hosting.
What Each Standard Tracks
Both AICC and SCORM can send a core set of learner data to the LMS:
- Completion status: whether the learner finished the course
- Score: results from quizzes or assessments
- Time spent: how long the learner was in the course
- Bookmarking: where the learner left off, so they can resume later
- Pass/fail status: whether the learner met a minimum score threshold
SCORM 2004 expanded the data model to include more granular interaction data, like individual question responses and objectives within a course. AICC’s data model is narrower, but it covers the essentials that most compliance and corporate training programs need.
How They Differ in Practice
The biggest practical difference comes down to where the course content lives. With SCORM, you upload a packaged ZIP file to your LMS. The LMS hosts the files, serves them to learners, and handles all the tracking. This is clean and self-contained, which is why most authoring tools (Articulate Storyline, Adobe Captivate, iSpring, and others) export SCORM packages by default.
With AICC, the course can sit on a completely separate server. The LMS launches the course by sending the learner to an external URL, and the two systems exchange tracking data over HTTP. This is useful when a training vendor doesn’t want to hand over their course files, or when an organization wants to centralize content hosting separately from the LMS. On the other hand, this architecture introduces more points of failure: if the external server goes down or the HTTP communication breaks, tracking data can be lost.
From a setup standpoint, SCORM is generally simpler. You export a ZIP file from your authoring tool, upload it to the LMS, and it works. AICC requires configuring the communication between two systems, which involves more technical setup and occasionally more troubleshooting.
Which Standard LMS Platforms Support
Nearly every modern LMS supports SCORM 1.2 and SCORM 2004. AICC support is also still common, particularly among enterprise-grade platforms used in industries like aviation, defense, and pharmaceuticals where legacy AICC content remains in production. If you’re evaluating an LMS, SCORM compliance is essentially table stakes. AICC compliance is worth checking if you have existing AICC courses you need to keep running or if you rely on vendors who deliver content from their own servers.
The original AICC committee disbanded years ago and is no longer developing the standard. AICC content still works on platforms that support it, but no new versions of the specification are being released. SCORM, while also not actively evolving, has a much larger installed base of content and broader tooling support.
Newer Standards: xAPI and cmi5
Both AICC and SCORM were designed for a specific scenario: a learner sitting at a computer, launching a course inside an LMS, and completing it in one or more sessions. That model doesn’t capture everything organizations want to measure today. Learning now happens in simulations, mobile apps, coaching sessions, on-the-job activities, and other contexts that don’t fit neatly inside a traditional LMS window.
xAPI (also called the Experience API or Tin Can API) was developed to address these gaps. Instead of requiring content to run inside an LMS, xAPI lets any system send “activity statements” to a central data store called a Learning Record Store (LRS). These statements follow a simple structure: “Learner X did Y on Z.” This makes it possible to track things like watching a video on a phone, completing a task in a work application, or attending an in-person workshop.
cmi5 builds on xAPI by adding back the structured relationship between an LMS and a course that SCORM provided. Think of it as xAPI with guardrails: the LMS still assigns and launches courses, but the tracking data flows through xAPI’s richer format. cmi5 gives organizations the flexibility of xAPI without losing the familiar LMS-driven workflow.
If your tracking needs go beyond “completed” and “scored 85%,” these newer standards offer significantly more capability. That said, SCORM remains the most widely supported format across LMS platforms and authoring tools. For straightforward compliance training and course completions, SCORM still gets the job done. Many organizations run SCORM for their standard courseware while adopting xAPI selectively for more complex learning programs where richer data justifies the additional setup.
Choosing the Right Standard
If you’re building or buying e-learning content today, SCORM (particularly SCORM 1.2 for maximum compatibility or SCORM 2004 for sequencing control) is the safest default. Every major authoring tool exports it, every LMS imports it, and the workflow is straightforward.
AICC makes sense in a narrower set of situations: when you need content hosted on a separate server from your LMS, when you’re working with a vendor that delivers training from their own platform, or when you have a library of legacy AICC courses that still serve their purpose. Converting AICC content to SCORM is possible but requires reworking the communication layer, so many organizations simply keep running their AICC courses on platforms that support both.
If you’re planning a learning ecosystem that goes beyond traditional click-through courses, look at xAPI and cmi5. They handle mobile learning, simulations, and blended programs in ways that SCORM and AICC were never designed to support.