How to build an eLearning course and export it as SCORM

You create an eLearning course, then export it as a SCORM package. SCORM is a packaging and communication standard, not the course format itself. The export is normally a ZIP containing the course's web content and media, an imsmanifest.xml file, and code that communicates with a learning management system.

The LMS launches the course and the course reports information back, such as whether the learner completed it, whether they passed, their score and where they stopped. This is why simply uploading a video or ordinary HTML page does not provide the same tracking.

Before building, confirm which SCORM version your LMS accepts. Most platforms support SCORM 1.2, while many also support SCORM 2004. If your organisation already has a tested standard, follow it.

Decide the completion rule before writing content. Otherwise the assessment and LMS settings may contradict each other later.

• Viewed content: suitable for information-only modules.
• Reached the end: useful when the learner must follow a sequence.
• Passed an assessment: appropriate when knowledge must be demonstrated.
• Combined rule: require key content plus a passing score.

Document the pass mark, number of attempts and whether practice questions contribute to the score. Skipped graded questions should still count in the denominator; otherwise an incomplete attempt can produce an inflated score.

Start with a small number of measurable learning outcomes. Each outcome should describe what the learner will be able to do, not merely what the course will cover.

A reliable structure is: context, essential knowledge, worked example, practice, assessment and summary. Group related material into short modules and remove information that does not support an outcome or a workplace decision.

Choose the course format deliberately. Slide-based eLearning supports controlled progression and focused interactions. Scroll-based eLearning works well for readable, responsive guidance. The packaging standard does not force either design.

Use headings in a logical order, meaningful link text, sufficient colour contrast and alternative text for informative images. Do not use colour alone to communicate status or correctness.

Check keyboard navigation, visible focus indicators, zoom and mobile layouts. Captions or transcripts should accompany meaningful audio and video. Assessment instructions must explain what is expected before the learner begins.

Keep interaction purposeful. A block should help the learner understand, practise or decide something—not exist merely to make the page feel interactive.

Set the SCORM version, completion rule, pass mark and reporting behaviour in the authoring tool. If the course contains graded questions, verify the maximum score includes every graded item, including unanswered questions.

Use a clear course title and identifier. Avoid changing the identifier after learners have started unless you intentionally want the LMS to treat the upload as a different activity.

For the broadest legacy compatibility, SCORM 1.2 is often the conservative choice. SCORM 2004 offers more detailed completion and success states. Read the SCORM 1.2 vs SCORM 2004 guide before deciding.

Export the course as a SCORM ZIP package. Do not unzip it and create a new ZIP around the containing folder: the manifest normally needs to sit at the root of the package.

Keep the exported ZIP as the controlled release file. Record its version, date, owner, pass mark and source-course version so future updates can be traced.

Lumeo exports the same authored course as SCORM 1.2, SCORM 2004, standalone HTML or PDF. The HTML and PDF versions are useful for review and reference, but they do not replace LMS tracking.

Upload the package to a test area in your LMS—or a dedicated SCORM testing service—before production release. Test with an ordinary learner account, not only an administrator account.

1. Launch the course and complete it with a passing score.
2. Confirm completion, pass status and score appear correctly in the LMS.
3. Fail an attempt and verify the recorded result.
4. Exit halfway, relaunch and check resume behaviour.
5. Leave one graded question unanswered and verify scoring.
6. Test keyboard use, a mobile viewport and at least two browsers.

Take screenshots of the expected LMS results and retain them with the release record.

• The LMS cannot find the course: the manifest may be missing or nested inside another folder.
• Completion never records: the course and LMS may use different completion expectations.
• Scores are wrong: practice questions or skipped graded questions may be handled incorrectly.
• The course opens blank: a blocked script, invalid asset path or browser security rule may be involved.
• Resume returns to the wrong place: suspend data may exceed the chosen standard's practical limits or be overwritten.

When troubleshooting, separate authoring behaviour from LMS behaviour: test the same ZIP in a second conforming environment before deciding where the defect sits.