What SCORM is, what versions Continu supports, and the operational realities of running SCORM content in your LMS — including the limits Continu can't override.
SCORM is the bridge between eLearning authoring tools and the LMS. It's a technical standard that lets content built in tools like Articulate, Captivate, iSpring, or Lectora communicate progress and completion back to Continu. Without SCORM, your authoring tool's output would be an isolated file that Continu couldn't track.
The trade-off: SCORM is a 20+ year old standard whose last official update was in 2004. It works reliably for the cases it was designed for, but it has quirks — completion reporting can be inconsistent, browser compatibility varies, and Continu has no control over the SCORM file's internal behavior. Treat SCORM like an old engine: capable, but predictable only when you know how it behaves.
For the strategic frame on content type selection, see Content Strategy: Designing Learning Assets That Scale. For the creation flow, see Add a SCORM File.
The Basics
What is SCORM? A set of technical standards for eLearning. It defines how content built in eLearning authoring tools communicates with an LMS — tracking who started, where they are, and whether they completed.
What versions does Continu support? SCORM 1.2 and SCORM 2004 (Editions 1–4). When exporting from your authoring tool, choose SCORM 2004 if available — it's the most up-to-date version and handles edge cases better than 1.2.
Is SCORM native or third-party content? Third-party. SCORM content is built outside Continu, in a separate eLearning tool. Everything about the course — what it shows, how it tracks, when it marks complete — is decided by the SCORM file, not by Continu. Continu plays it back and reads what it reports.
SCORM vs Learning Track. A SCORM course is built in an external authoring tool and uploaded as a package. A Learning Track is built inside Continu — natively, with Continu's editor, and editable in place. Use SCORM when the content needs the rich interactivity of a dedicated authoring tool. Use Learning Tracks when you want a course experience built natively in the platform.
Operational Realities
Browser compatibility. SCORM works well in current versions of Chrome, Safari, Firefox, and Edge. Internet Explorer is no longer supported by Microsoft and can produce inconsistent SCORM behavior — don't rely on it.
VPN interactions. Corporate VPNs can interrupt SCORM playback and completion reporting. If your organization uses a VPN, test SCORM courses behind the VPN before launching to learners. If issues appear, work with IT to allowlist Continu's domains or have learners attempt completion outside the VPN.
License limits from your training provider. If your SCORM provider has sold you a limited number of seats, Continu honors that limit. The provider's warning or limit-reached message comes from the SCORM file itself — Continu just plays it. If you hit a limit unexpectedly, contact your training provider, not Continu Support.
Continu's role and limits. Continu plays SCORM courses, tracks completion as the SCORM reports it, and handles assignment, segmentation, and reporting against that completion. Continu doesn't control quiz logic, scoring rules, time tracking, or completion criteria — those are baked into the SCORM file by its author. If something inside the course isn't behaving the way you expect, the answer almost always lives in the SCORM, not in Continu.
Reporting
Quiz scores. If the SCORM course contains a quiz that's set up to report its score, that data flows into Continu's reporting. If the quiz doesn't report scores back, Continu has no way to surface them.
Status values. The status column varies based on what's in the course:
Incomplete / Completed. The course didn't contain a quiz requiring a passing score. Status tracks whether the learner reached the end.
Passed / Failed. The course contained a quiz with a required passing score. Status tracks the quiz outcome.
Time Spent — when it's unknown or inaccurate. Some SCORM files only track time at completion (so time-spent shows "unknown" for in-progress learners). Inaccurate time values usually indicate the SCORM isn't tracking learning activity in the way you'd expect — the authoring tool's settings control this.
Common Issues
The course doesn't mark completion. The most common SCORM issue. Continu can only report what the SCORM tells it. If the SCORM doesn't fire a completion event, Continu won't show the learner as complete. Options:
Test the course end-to-end as a learner — make sure you're actually triggering whatever the author defined as completion (often a specific button, the final slide, or passing a quiz).
Check whether VPN or browser issues are blocking the completion signal.
If the SCORM was built in-house, the author can re-export with explicit completion logic.
If purchased from a provider, contact the provider — they can fix the SCORM file's completion behavior.
Test before you launch. If completion tracking is critical to your program, take the course as a test user before rolling it out. SCORM behavior that looks broken to admins almost never reveals itself until a learner tries to complete it.
What You Can Do With SCORM in Continu
Assign SCORM courses. Yes — like any other content. Assign directly or through an Automation. See Creating an Automation.
Segment SCORM courses. Yes — like any other content. Use Segmentation to control who sees the course on Explore and who receives assignments. See Segmentation For Content.
Pop-out vs in-window playback. Continu lets you choose. See Add a SCORM File for the configuration.
Configuration Pitfalls
Treating SCORM Reporting Problems as Continu Bugs. Most "SCORM isn't tracking right" issues live inside the SCORM file, not in Continu. Confirm the course behaves as expected before assuming Continu is the problem.
Updating a SCORM Course Mid-Program. Updating SCORM while learners are in progress can strand them — their state may not match the new course version. Wait for cohort completion, or use a duplicate-and-replace pattern (upload as new content and assign forward).
Choosing SCORM When a Learning Track Would Work. SCORM packages take longer to author, are harder to update, and depend on the original authoring tool. For content that doesn't need rich interactivity, a Learning Track built natively in Continu is often a better tool.
Skipping VPN Testing. Org-wide VPNs interfere with SCORM more often than admins expect. If your organization uses one, test SCORM courses behind it before launching — fixing post-launch when learners can't complete is much harder than catching it early.
Forgetting Internet Explorer Doesn't Work. Some compliance-driven orgs still have IE deployed. SCORM courses behave unpredictably there. Communicate browser requirements to learners upfront.
Where This Fits
You're here because you're working with SCORM content. The mechanics of uploading a SCORM live in Add a SCORM File. For the broader content-type comparison, see Content Strategy: Designing Learning Assets That Scale.
See Also
- Content Strategy: Designing Learning Assets That Scale — the strategic anchor.
- Add a SCORM File — the upload and configuration flow.
- What is a Learning Track? — the native Continu alternative for course-like content.
- Segmentation For Content — controlling SCORM visibility.
- My Learning Track shows incomplete when each individual piece of content is complete — SCORM-related troubleshooting.
SCORM 2004 over 1.2 when possible. Test on the browsers and VPN configuration your learners actually use. Continu plays the SCORM; the SCORM controls its own behavior.