What is SCORM? A plain-English guide

SCORM is a set of technical rules that lets eLearning content be packaged, launched and tracked consistently by compatible learning management systems.

The important distinction is that SCORM is not an LMS and it is not an instructional design method. An authoring tool creates the course and exports a SCORM package; the LMS hosts or launches that package and records the information the course sends back.

Without a shared standard, every authoring tool and LMS could require a different integration. SCORM created a common contract for packaging learning content and communicating runtime information.

That portability is why organisations can often build a course in one tool and upload the resulting ZIP to different SCORM-compatible LMSs without rebuilding the course for each platform.

A SCORM export is normally a ZIP containing HTML, JavaScript, styles, images and other course assets plus an imsmanifest.xml file. The manifest describes the package to the LMS, including the resources and launch information.

Do not treat the ZIP like an ordinary folder of documents. Its structure matters. Re-zipping it with an extra parent folder can leave the manifest in the wrong place and cause an LMS import to fail.

The LMS opens the course in a player or browser context and exposes a SCORM runtime interface. The course finds that interface and uses it to exchange defined values with the LMS.

Depending on the SCORM version and course configuration, that can include completion, success or pass status, score, session time, location and resume information. The authoring tool handles most of this communication so course authors rarely need to write the runtime code themselves.

SCORM is useful for operational learning records: whether someone launched or completed a course, their score, pass/fail state and some resume information. Exact reporting depends on the standard, authoring implementation and LMS.

It does not automatically tell you whether behaviour changed at work, whether performance improved or why someone chose an answer. Those questions need stronger evaluation methods and sometimes different learning-data technologies.

SCORM 1.2 remains widely supported and is often the conservative compatibility choice. SCORM 2004 separates completion and success more clearly and introduced more sophisticated sequencing capabilities.

Choose based on what your LMS has been tested with rather than assuming the newer standard is always better. Our SCORM 1.2 vs 2004 guide compares the practical differences.

• Use it when your organisation needs an LMS to record course completion or scores.
• Use it when content needs to move between compatible LMS environments.
• You may not need it for a public information page, downloadable reference or content that does not require learner tracking.

Before choosing a format, ask what data the organisation actually needs and what the target LMS supports.

1. Design and build the course in an authoring tool.
2. Choose the supported SCORM version and completion rules.
3. Export the SCORM ZIP.
4. Upload it to a test area in the LMS.
5. Complete, fail, exit and resume test attempts.
6. Confirm the LMS records the expected status and score.
7. Release the tested package to learners.

For the full process, see how to build and export a SCORM course.