What is SCORM?

SCORM (Sharable Content Object Reference Model) is a set of technical standards that lets e-learning content run inside any compatible learning management system (LMS) and report learner progress back to it. A course packaged as SCORM can be uploaded to a SCORM-compliant LMS without a custom integration.

Reviewed by Clark Quinn, Chief Learning Strategist Updated October 28, 2026

Example

A compliance team builds a ten-minute data privacy course with a short quiz at the end. They export it as a SCORM package and upload the .zip file to their LMS, the same way they upload every other course.

Every employee who takes the course shows up in the LMS report with a status (completed, passed or failed), a quiz score and the time spent. When the auditor asks for proof that staff completed the training, the team pulls the report straight from the LMS. Nobody had to build an integration or export a spreadsheet by hand.

How it works

SCORM is a reference model, which means it bundles several technical rules into one standard. It was created by Advanced Distributed Learning (ADL), a US Department of Defense initiative, so that training content could be built once and used in any compliant system. Two parts do most of the work.

The package

A SCORM course ships as a .zip file. Inside are the course files, such as HTML pages, JavaScript and media, and a manifest file called imsmanifest.xml. The manifest lists every resource, tells the LMS which file to open first, and declares the SCORM version. When you upload the .zip, the LMS reads the manifest and knows how to launch the course without any setup.

The runtime

When a learner opens the course, the LMS launches it in a browser window and exposes a JavaScript API. The course finds that API and calls it to start a session, send data and end the session. Every piece of information the course reports, such as status or score, is written to a named data field that the LMS stores against that learner.

What SCORM tracks

The most common data a SCORM course reports:

• Completion status: whether the learner finished the course.
• Success status: whether the learner passed or failed, usually against a pass mark.
• Score: the quiz result, often as a percentage.
• Time: how long the learner spent in each session.
• Bookmark and suspend data: where the learner stopped, so the course can resume there next time.

SCORM versions

Two versions are still in use.

• SCORM 1.2 is the most widely supported. It reports one combined lesson status (such as passed, completed, failed or incomplete) and has a small limit on how much resume data a course can store.
• SCORM 2004 reports completion and success separately, so a learner can be “completed and failed”. It adds sequencing rules that control the order of activities in a multi-part course and allows more resume data. Its 4th edition is the most recent.

Most authoring tools let you choose the version at export. Pick the one your LMS supports best. If your LMS supports both, SCORM 2004 gives you cleaner pass and fail reporting.

SCORM vs xAPI and cmi5

SCORM only tracks what happens inside a course launched by an LMS. xAPI (also called Tin Can) records learning statements like “Ana completed the forklift simulation” from any source, including mobile apps, simulations and in-person events. Those statements go to a learning record store rather than the LMS.

cmi5 sits between the two. It uses xAPI for data but keeps the LMS launch-and-track model that SCORM made standard. Many teams still use SCORM for most courses because every LMS supports it, and add xAPI or cmi5 where they need richer data.

Limits of SCORM

SCORM was designed for courses that run in a browser while connected to the LMS. That brings some limits:

• It does not track learning outside the LMS, such as on-the-job practice or offline events.
• Reporting is limited to the data fields the standard defines.
• Courses that open in a new window or lose their connection can fail to save progress.
• Large media files make packages slow to upload, so many tools stream video from a server instead of putting it inside the .zip.

Why it matters for L&D teams

• No custom integration. A SCORM course works in the LMS you already have, whether you built it in-house or bought it.
• Proof of completion. Completion, pass or fail, and score data land in the LMS, where compliance and audit reports already live.
• Portability. If you switch LMS, your SCORM courses move with you instead of being rebuilt.
• Vendor choice. Because the standard is shared, you can mix courses from different authoring tools and content vendors in one catalog.