Before you start
- Use a test course, not a live one, and a test student account (or an incognito window logged in as that student).
- Publish SCORM 1.2 for Moodle. Moodle's documentation states that SCORM 2004 is not supported: parts of the API work, so some packages run, but 2004 bugs are not fixed.
- Know what the course reports: completed, passed/failed, or both, and whether it sends a score. Check the reporting options you chose when publishing.
Step 1: add the SCORM package activity
- Open the test course and turn editing on.
- Choose Add an activity or resource → SCORM package.
- Give it a name, then drag the zip into Package file.
- Under Appearance → Display package, choose Current window or New window. If the course has its own full-screen player, New window usually looks better; Current window avoids pop-up blockers.
- Save and display. If Moodle rejects the file, see common SCORM upload errors.
Step 2: set grading, attempts and completion
- Grading method: Learning objects, Highest grade, Average grade or Sum grade. For a single-SCO course with one quiz, Highest grade is the usual choice.
- Attempts management: number of attempts, and whether a new attempt starts when the previous one is completed.
- Activity completion: pick the conditions that match the course. Require status "Passed" only if the course reports pass/fail; require "Completed" if it reports completion. A mismatch here is the most common reason a finished course never shows as complete.
- Require minimum score only if the course actually sends a score.
Step 3: run the test as a student
What to test in Moodle and what a pass looks like| Test | How | Expected result |
|---|
| Launch | Open the activity as the student | Course loads without errors or blank screens |
|---|
| Completion | Finish the course and exit with its own exit or close button | Activity shows complete; the status in the report matches |
|---|
| Score | Pass, then in a second attempt fail, the quiz | Score recorded and grade appears in the gradebook |
|---|
| Resume | Close half-way, reopen | Course offers to resume where you left off |
|---|
| New attempt | Reopen after completion | Matches your attempts settings |
|---|
| Mobile | Open in the Moodle app or a phone browser | Content is usable; check whether downloads are allowed |
|---|
For multilingual packages, also check that the language launcher appears, that each language opens, and that completing one language marks the activity the way you configured it; see one multilingual SCORM package.
Step 4: read the reports
Open the SCORM activity as a teacher and go to Reports. Each attempt has a track details view listing the raw values the course sent, such as cmi.core.lesson_status, the score fields, session time and suspend data. When completion or grades look wrong, this tells you whether the problem is the course (it never sent "passed") or the Moodle settings (it did, but the completion rule expects something else).
For deeper debugging, a site administrator can turn on "Activate API debug and tracing" under Site administration → Plugins → Activity modules → SCORM package. Set the API debug capture mask (for example admin.*) so only your account sees the log of calls between the course and Moodle.
Step 5: test accessibility and content, not just tracking
A course can track perfectly and still fail learners who use a keyboard or a screen reader. Tab through a few screens, check that videos have captions and that images have meaningful alt text. The SCORM accessibility checker scans the zip for those issues before you upload it, and opening the package in a browser preview is a faster way to proof-read content than reloading Moodle.