A completed course does not necessarily have a score
First confirm that the course is designed to report a score. A completion-only course may legitimately send no assessment score. If a quiz exists, confirm it is marked as the tracked assessment and contributes to the published result.
Inspect the score sent to the LMS
SCORM runtime communication includes score fields. Check debug logs to see whether the course sends a raw/scaled score and whether that value is committed. If the course sends the expected score but the LMS report is blank, the problem has moved from course logic to LMS interpretation or reporting.
Watch for scale and mastery mismatches
A course might think in percentages while an LMS expects a different representation for a particular SCORM field. SCORM 2004 also supports a scaled score. Test values near the pass threshold, not only 100%, so rounding or mastery-rule problems become visible.
Test attempts deliberately
Use a fresh learner attempt and record the answers, expected score, displayed score and LMS score. Then test a fail and a pass. Retake rules can preserve, replace or aggregate results depending on the LMS, so do not diagnose from an old attempt with unknown history.
Check commit and exit timing
If the score appears in the course but disappears after closing, verify that the final score is sent and committed before the window closes. Test the intended exit button as well as browser-close behaviour.
Use a two-environment test
Run the same package in a standards-focused SCORM test environment. If the score is correct there, inspect the target LMS settings and report mapping. If both environments miss the score, return to the course publish configuration.
Also verify status separately with our completion troubleshooting 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.