First identify who thinks the course is complete
A learner seeing a final screen does not prove that the LMS received completion. Separate the visual course state from the SCORM runtime state and the LMS record.
Reproduce the issue in a clean test attempt and note the SCORM version, completion rule, assessment rule and exact LMS status after exit.
Check the authoring completion rule
Confirm what actually triggers completion: visiting a percentage of content, reaching a final screen, passing a quiz, completing an interaction or a combination. A course configured for 100% viewed can remain incomplete if branching makes one page unreachable.
Also check whether a pass is required. Completion and success are related but not identical concepts, especially in SCORM 2004.
Check what the course sends
Use the LMS debug log, SCORM test platform or browser console to inspect runtime calls. For SCORM 1.2, completion commonly maps through lesson status. SCORM 2004 separates completion and success more explicitly.
If the course never sends the intended state, fix the authoring/export configuration before blaming the LMS.
Test the final action and exit
Some problems occur because the learner closes the browser before the course commits its final state, or because a custom button bypasses the normal completion/exit logic. Complete the course, wait for confirmation, exit through the intended control and compare the LMS record.
Check manifest and sequencing settings
SCORM 2004 packages can include sequencing and delivery controls that affect how activity completion rolls up. If the content is meant to set completion, make sure the package and LMS are not applying contradictory rules.
Avoid copying manifest fixes from unrelated courses. The correct settings depend on the package structure and intended behaviour.
Isolate course vs LMS
- Test the same package in a known SCORM test environment.
- If it completes there but not in your LMS, compare LMS player and tracking settings.
- If it fails in both, return to the authoring/export configuration.
- If only one browser or launch mode fails, inspect browser errors and blocked requests.
Fast completion checklist
- Correct SCORM version for the LMS
- Reachable completion condition
- Runtime completion value actually sent
- Final data committed before exit
- No contradictory LMS completion override
- SCORM 2004 rollup/manifest behaviour checked where relevant
- Retested from a fresh attempt
For a broader release process, use the SCORM pre-launch testing guide.
Put the guidance into practice
Build a real course in Lumeo, preview it in the browser, and export it to SCORM, standalone HTML or PDF. The free plan does not require a payment card.