Help Center

SCORM Content

Import and use SCORM packages in your courses

SCORM (Sharable Content Object Reference Model) packages let you use training content created in external authoring tools like Articulate Storyline, Adobe Captivate, or iSpring.

Supported SCORM Versions

Konstantly supports both major SCORM standards:

VersionDescription
SCORM 1.2Legacy standard, widely supported
SCORM 2004Newer standard with extended tracking capabilities

Importing a SCORM Package

  1. In the course builder, drag the SCORM element onto your course map
  2. Click the element to open the upload dialog
  3. Upload your .zip SCORM package file
  4. Wait for the package to process and validate
SCORM packages must be valid ZIP files containing an imsmanifest.xml file. Konstantly automatically parses the manifest to extract content structure.

What Gets Tracked

When learners interact with SCORM content, Konstantly tracks:

Progress Data

  • Completion status: not attempted, incomplete, completed, passed, failed
  • Progress measure: Percentage of content viewed
  • Time spent: Total time in the content

Assessment Data

  • Score: Raw, scaled, min, and max scores
  • Success status: Passed or failed
  • Mastery score: Required threshold from the package

Learner Responses

  • Individual question responses (if the package reports them)
  • Interaction data and timestamps

SCORM Player Features

When learners view SCORM content:

  • Resume capability: Learners can exit and resume where they left off
  • Fullscreen mode: Expand content to full browser window
  • Progress saving: Automatic state saving as learners progress
  • Time tracking: Accurate time-on-content measurement

Configuring SCORM Elements

Completion Criteria

Set how completion is determined:

  • By SCORM package: Use the package's internal completion logic
  • By score: Require a minimum score to mark as complete
  • By time: Require minimum time spent in content

Passing Score

If the SCORM package includes assessments:

  • Use the package's built-in mastery score, or
  • Override with a custom passing threshold

Attempt Limits

  • Allow unlimited attempts, or
  • Limit to a specific number of tries

Troubleshooting

Package Won't Upload

  • Verify the ZIP contains imsmanifest.xml at the root level
  • Check that the ZIP isn't corrupted
  • Ensure file size is within limits

Content Doesn't Display

  • Check browser console for JavaScript errors
  • Verify the package works in other LMS systems
  • Some packages require specific browser settings (popups, cookies)

Progress Not Saving

  • Ensure the package properly calls SCORM API commit functions
  • Check that learners don't close the browser before content saves
  • Verify the SCORM version matches what Konstantly detected

Best Practices

  1. Test before publishing - Always preview SCORM content as a learner
  2. Check mobile compatibility - Not all SCORM packages work on mobile devices
  3. Verify tracking - Confirm that scores and completion status report correctly
  4. Keep originals - Store the original authoring tool files for future edits
  5. Document sources - Note which authoring tool and version created each package