SCORM Lab · reference

What each authoring check means

SCORM Lab runs these nine checks over a package while it plays, using the manifest, the API transcript and the data model together. Each one below describes what a learner or an administrator actually sees when the problem bites — which is usually how it gets noticed, long before anyone looks at a transcript.

• Will breakStatus set after the session was closedThe course reported completion after calling Terminate, so the LMS was no longer listening.status-before-terminate
• Will breaksuspend_data over the limitBookmark data is longer than the SCORM version allows, and the overflow is usually truncated in silence.oversized-suspend-data
• RiskyMissing imsss:deliveryControls in SCORM 2004An activity does not declare how completion is decided, so different systems apply different defaults.missing-delivery-controls
• Will breakA SCO that never calls InitializeThe course never opened a SCORM session, so nothing it did was ever tracked.never-initialized
• RiskyA SCO that never calls TerminateThe course never closed its session, so the LMS may discard the final state of the attempt.never-terminated
• RiskyA SCO that never calls CommitTracked data was never explicitly flushed, so an interrupted attempt can lose everything since the start.never-committed
• RiskyAn interaction written without an idA question result was recorded with no identifier, and most systems drop it.malformed-interactions
• RiskyA score reported with no statusThe course sent a score but never said whether the learner passed, so the LMS has to guess.score-without-status
• Worth a lookSlow LMS API discoveryThe course took seconds to find the LMS API, which usually means it was retrying after failures.slow-api-discovery