SCORM Integration on Foundry

Overview

SCORM integration allows organizations to deliver ComplyEQ courses through an external learning management system (LMS) while Foundry securely hosts and maintains course content.

This article serves as a starting point for understanding how SCORM works on Foundry. It explains the overall model, key responsibilities, and learner experience, and links to other articles for detailed setup, configuration, and troubleshooting.

How SCORM Integration Works

When using SCORM integration:

• Foundry hosts course content and manages course‑level configurations
• Your LMS or HRIS is where learners access and launch training
• Progress and completion data are tracked through the SCORM standard
• Foundry records completion data as a backup reference

This approach allows your LMS to remain the primary learner interface while ensuring ComplyEQ content stays current and compliant.

SCORM Packaging on Foundry

For SCORM integrations, Foundry generates SCORM Dispatch packages that are tailored to your organization and course configurations.

Each package reflects choices such as:

• Course
• Learner role and location
• Training cycle
• SCORM version

These packages are uploaded into your LMS and launched like standard SCORM courses.

Course Configuration Responsibilities

Course configuration is handled in Foundry, while assignment and learner management occur in your LMS or HRIS.

In Foundry, administrators configure:

• Policies and acknowledgements
• Resources and supplemental content
• Course‑specific settings supported by the content

In your LMS or HRIS, administrators:

• Create assignments
• Control learner access and due dates
• Launch courses for learners

This separation ensures configuration remains centralized while delivery stays within your LMS workflows.

User Management in SCORM Integrations

When using SCORM integration, user management is handled entirely by your LMS or HRIS.

You do not need to:

• Upload users into Foundry
• Set up single sign‑on for learners

When a learner launches a course, the LMS automatically passes a student or employee identifier to Foundry using the SCORM protocol. Foundry creates a lightweight user record to track progress and completion.

This identifier is stored in Foundry as the user’s SSO ID and is used to match the learner when they return.

Learner Experience

Learners always begin in your LMS or HRIS.

From the learner’s perspective:

• Courses are launched from the LMS
• Course content is displayed in a window hosted by Foundry
• Progress and completion are tracked automatically

Progress data is shared between Foundry and the LMS so both systems reflect the same completion status.

Retraining and Course Resets

SCORM integrations support retraining through training cycles.

At a high level:

• A learner can have only one progress record per course per training cycle
• If reassigned within the same cycle, the learner resumes where they left off
• When the training cycle changes, prior progress is archived and the learner starts again

Training cycles are configured when SCORM packages are created.

Testing and Quality Assurance

Before launching training to a large learner population, we recommend testing SCORM packages in your LMS to confirm:

• Courses launch successfully
• Content displays correctly
• Progress and completion are recorded as expected

Testing helps identify LMS‑specific behavior early and reduces rollout issues.

Where to Go Next

Use the articles below for deeper SCORM guidance:

• SCORM Dispatch – How SCORM Dispatch works and how packages behave
• SCORM Dispatch for Workplace Training – Supported versions and recommendations
• Retraining Schedule (SCORM) – Training cycles and course resets
• Reporting (SCORM) – Completion and progress reporting