SCORM is a packaging standard for online courses. A SCORM course is a zip of web files plus a manifest (imsmanifest.xml) that any compliant learning management system (LMS) can import, launch and use to record completion, score and time spent.

What is the difference between SCORM 1.2, SCORM 2004, xAPI and cmi5?

SCORM 1.2 tracks completion and score and runs in almost every LMS. SCORM 2004 adds richer status (completed and passed are reported separately) and sequencing, and runs in most modern LMSs. xAPI sends detailed activity statements to a Learning Record Store, including from outside an LMS. cmi5 applies xAPI rules to courses launched from an LMS. If your LMS accepts SCORM 2004, you're set.

Not if you want people to take a course, because you can share it with learners inside Skill7. You probably want an LMS if you need training records alongside HR data, compliance reporting across many courses, or you already have one.

SCORM explained

Someone has asked you for “a SCORM file”, or you’ve seen SCORM listed as a must-have in an LMS brochure, and you’d like to know what it actually means before you commit to anything. This guide explains it in plain words: what SCORM is, how it compares with the newer standards you’ll hear about, whether you need an LMS at all, and where Skill7 fits.

What is SCORM?

SCORM (short for Sharable Content Object Reference Model) is a packaging standard for online courses. A SCORM course is a single zip file. Inside it are the web files that make up the course, such as pages, images, quizzes and a little JavaScript, plus a manifest: a file called imsmanifest.xml that lists what’s in the package and tells the platform how to start it.

A learning management system (LMS) is the software many organisations use to assign training to people and keep records of it. Any SCORM-compliant LMS can import that zip, launch the course for each learner and record what happened: whether they completed it, what they scored and how much time they spent.

The easiest way to think about it: SCORM is like a PDF for e-learning — one file any compatible platform can open. You don’t need to know which tool built the course, and neither does the LMS. It only needs to speak SCORM.

Your LMS imports the SCORM package, launches it and records each learner’s completion and score.

What SCORM does, and what it doesn’t

SCORM handles the plumbing between a course and the platform that runs it:

Packaging: everything the course needs travels in one file, so you can hand it to a client or upload it to a new LMS without rebuilding anything.
Launching: the LMS knows which page to open first and how to show the course to a learner.
Tracking: the course reports progress back to the LMS, so a manager can see who has finished and who hasn’t.
Resuming: a learner can close the course halfway through and pick up where they left off.

SCORM doesn’t decide what the course looks like or how well it teaches. It’s a container and a reporting line, not a teaching method. SCORM carries your course; the teaching inside it is what people remember.

SCORM has been around since the early 2000s. Newer standards exist, but it’s still the most widely accepted format for e-learning: if an LMS imports course packages at all, it almost certainly imports SCORM. That’s why it’s the usual answer when a client or an HR team asks “what format do you need?”

SCORM 1.2, SCORM 2004, xAPI and cmi5

You’ll come across four names. They’re all ways for a course to report what a learner did, but they differ in how much they record and where they can run.

Standard	What it tracks	Where it runs	Skill7 today
SCORM 1.2	Completion and score	Almost every LMS	Available
SCORM 2004	Adds richer status (completed and passed reported separately) and sequencing	Most modern LMSs	Available
xAPI	Detailed activity statements sent to a Learning Record Store, including from outside an LMS	Needs a Learning Record Store (LRS)	Available
cmi5	xAPI rules for courses launched from an LMS	Newer LMSs	Available

In a little more detail:

SCORM 1.2 is the oldest and simplest version, and the most widely supported. It records whether someone finished and what they scored. It has only a small amount of space for remembering where a learner got to, which long courses can outgrow.
SCORM 2004 is the newer version of the same idea. Its most useful change is that “completed” and “passed” are separate: a learner can reach the end of a course but fail its quiz, and the LMS sees both facts. It also adds sequencing, meaning rules about the order learners take sections in, or which sections they can skip. It went through several editions; the 4th edition is the most recent.
xAPI (the Experience API, sometimes called Tin Can) takes a different approach. Instead of reporting a handful of fields to an LMS, the course sends detailed statements, such as “Sam answered question 3 correctly”, to a Learning Record Store (LRS), a database built to hold learning activity. Because it isn’t tied to an LMS, xAPI can track learning in apps, simulations or on the job. The trade-off is more setup: you need an LRS, and someone has to decide what to record and how to report on it.
cmi5 is a set of rules for using xAPI with courses that are launched from an LMS. It aims to combine xAPI’s detail with SCORM’s simple “upload, launch, track” routine. It’s the newest of the four, and support is mostly in newer LMSs.

For most teams, the choice is simpler than the table makes it look. You need whichever standard your LMS accepts, and nearly all of them accept SCORM. If your LMS accepts SCORM 2004, you’re set.

Do I need an LMS?

It depends on what you want training to do for you.

No, if you want people to take a course. You don’t need an LMS to train a team. You can share a course with learners inside Skill7: invite them, they work through the lessons and quizzes in Skill7’s player, and you can see their progress. No zip files and no extra system to buy or maintain.

Yes, if training has to fit into a wider system. An LMS earns its keep when you need training records alongside HR data, when you have to report on compliance across many courses, or when your organisation already has one and people expect to find their training there.

You probably want an LMS if…

you need to show an auditor, regulator or client who completed which training, and when, across your whole organisation
you want training records to sit next to other employee data, such as start dates, roles and reviews in your HR system
you already pay for one, and adding courses to it is easier than asking people to use something new

If none of those apply, start without one. A course built in Skill7 can still be exported as a SCORM package later, if you adopt an LMS or a client asks for one.

How Skill7 fits

Skill7 is a course-authoring tool with an AI assistant. It helps you shape what your team already knows into a structured course, and SCORM is one of the ways that course leaves Skill7. Here’s the route from document to LMS:

Upload your documents. SOPs, handbooks and policies, as PDF or Word files, web pages or pasted text. Save slide decks as PDF first.
Review the draft. Skill7 maps your documents into a course plan, then its AI assistant drafts lessons, diagrams, flashcards and quizzes in a scroll or slide format. You review and edit the lessons before anything goes out, and you stay in charge of every word.
Export a SCORM zip. Choose SCORM 1.2 or 2004 (or xAPI or cmi5, if that’s what your LMS uses), and Skill7 packages the finished course as a single file, ready for your LMS.
Upload it to your LMS. Look for a screen called something like “Add SCORM package” or “Upload course”, choose the zip, and assign it to learners as usual.

Once it’s live, the package reports completion and quiz scores back to your LMS, so the course shows up in the same reports as the rest of your training. Skill7 exports standard SCORM packages.

What to check before you upload

Which versions your LMS accepts. Most LMSs list the SCORM versions they support in their help pages. Skill7 exports SCORM 1.2, SCORM 2004, xAPI and cmi5, so pick whichever your LMS accepts.
What “done” means for this course. Decide whether finishing the lessons is enough, or whether learners must also pass the quiz, and check how your LMS shows each case in its reports.
A test run. Upload the package, take the course yourself as a learner, and check that your completion and score appear in the LMS before you roll it out.

Not every course needs to go into an LMS. You can also export a course as a Word document (DOCX) for review, sign-off or printing, or share it with learners directly in Skill7’s player.

Skill7 is in early access, and we’re inviting teams in waves. Join the waitlist to share your first course, built from what your team already knows. Run an eLearning studio? Book a call instead.

Quick glossary

LMS (learning management system): software that assigns courses to people, launches them and keeps training records.
SCORM package: a zip file containing a course and its manifest, ready to upload to an LMS.
Manifest: the imsmanifest.xml file inside a SCORM package that lists its contents and tells the LMS how to launch it.
LRS (Learning Record Store): a database that receives and stores the activity statements xAPI and cmi5 courses send.
Completion status: whether a learner has finished a course, usually shown as not started, incomplete or completed.
Passing score: the minimum quiz score a learner needs to pass; SCORM 2004 reports “passed” separately from “completed”.