Meta Pixel Saltar al contenido
Logo Geedle

What is SCORM?

SCORM (Sharable Content Object Reference Model) is the standard that lets an e-learning course run on any compatible LMS platform, tracking progress, time, and scores. A SCORM course is produced once and reused in Moodle or nearly any commercial LMS.

All of our courses are delivered in SCORM: learn about our online course production.

01

How does SCORM work?

A SCORM course is a ZIP package containing the content and a manifest file (imsmanifest.xml) that describes its structure. When you upload it, the LMS reads that manifest and knows how to display it. While the learner studies, the course talks to the platform through a standard JavaScript API, reporting status (completed, passed), score, time spent, and the exact point where the person left off so they can resume later. There are two main versions: SCORM 1.2 (2001), the most compatible and widespread, and SCORM 2004, which adds sequencing and navigation rules between units.

02

What does SCORM do for a company?

It keeps you from being locked into any platform or vendor. A course packaged in SCORM is produced once and runs on Moodle and virtually any compatible commercial LMS; if the company switches platforms tomorrow, its course library migrates with no rework. It also standardizes tracking: no matter who produced the course, the LMS records progress and scores the same way. That is why, when hiring online course production, you should always require delivery in SCORM format. For newer scenarios —learning outside the LMS or in mobile apps— there is a successor, xAPI, though SCORM remains the most widely used standard.

03

Which SCORM version should you use?

For most corporate projects, SCORM 1.2: it is the version that virtually every LMS on the market supports without surprises, and it records what a company usually needs — status, score, time, and resume point. SCORM 2004 adds advanced sequencing (for example, requiring one unit to be passed before the next unlocks, from within the package itself), but its support varies more across platforms. The practical rule: use 1.2 unless you need that navigation logic inside the package, and always test the package on the destination platform before a large-scale launch.

04

An everyday example

A manufacturing company commissions an industrial safety course and receives it as a SCORM package. Today it publishes the course on its Moodle and the system records who passes. Three years later it decides to migrate to another LMS: it uploads exactly the same ZIP to the new platform and the course works the same, with nothing to pay for rebuilding. That same package can also be delivered to a client or a corporate group using a different compatible platform.

Related terms

Round out the picture with these other glossary entries: