SCORM Content

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:

Importing a SCORM Package

1. In the course builder, add an Import element to your course map
2. Choose your .zip SCORM package in the file dialog that opens
3. Wait for the package to upload and convert

There is no separate "SCORM" element in the palette. Import is the single door

for outside content – the same one that takes PowerPoint and PDF – and what it

produces depends on what you gave it. A .zip with a SCORM manifest becomes a

SCORM page; slides and PDFs become ordinary pages you can then edit.

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

What you can and cannot configure

A SCORM package carries its own rules. Completion criteria, passing score and

attempt limits are decided by the authoring tool that built the package and

declared in its manifest – Konstantly reads them and reports what the package

says, but does not override them. If a course needs a different passing score,

change it in Storyline, Captivate or iSpring and re-import.

What you control on the Konstantly side is where the SCORM page sits in the

course, and what happens around it: whether a test follows it, whether a

certificate comes after, and who the course is assigned to.

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