What is Dynamic SCORM - and why it matters for compliance training

If you manage training content in an LMS, you've almost certainly experienced the SCORM update problem. A regulation changes. A policy is updated. An error is found in a published course. And what should be a simple correction becomes a multi-step project: open the source file, make the change, republish the SCORM package, upload the new package to the LMS, check that existing completion records haven't been disrupted, communicate the update to learners.

For a single course, this is inconvenient. For a compliance content library with dozens or hundreds of courses that require regular updates, it becomes a significant operational burden.

Dynamic SCORM addresses this. Here's what it is, how it works, and when it matters.

What SCORM is and why it exists

SCORM - Sharable Content Object Reference Model - is a technical standard for packaging e-learning content so it can be delivered through any compatible LMS. When you export a course as SCORM, you produce a ZIP file containing all the course assets (HTML, images, JavaScript, assessment logic) along with a manifest file that tells the LMS how to launch and track the content.

SCORM was developed in the late 1990s and has been the dominant e-learning interoperability standard ever since. SCORM 1.2 (released 2001) and SCORM 2004 are the two versions you'll encounter in most LMS platforms. Both work the same way at a fundamental level: the course is a self-contained package that the LMS hosts and launches.

This self-contained nature is SCORM's great strength - and its greatest weakness.

The traditional SCORM problem

Because a SCORM package is self-contained, any change to the course requires producing a new package and uploading it to replace the old one. The LMS doesn't know anything about the course content - it only knows the package it was given.

This creates several practical problems:

• Version management. Different learners may complete different versions of a course without any clear record of which version they took. For compliance purposes, this creates audit complexity.
• Update overhead. Every update - even a single corrected sentence - requires the full republish-and-upload cycle. LMS admin time, testing time, potential disruption to in-progress learner attempts.
• Multi-platform distribution. If a course is deployed across multiple LMS platforms - common in training consultancies serving multiple clients - every update requires re-uploading to every system.
• No live editing. If a course contains an error that is discovered after publication, there is no way to correct it without going through the full re-upload process. Learners who have already launched the course may still see the error.

What dynamic SCORM is

Dynamic SCORM separates the SCORM tracking wrapper from the course content. Instead of packaging all the course assets into a self-contained ZIP file, a Dynamic SCORM package contains a lightweight launcher - typically a small HTML file and the SCORM manifest - that connects to the course content hosted on an external server.

When a learner launches the course in their LMS, the launcher loads the current published version of the course from the host server in real time. The LMS handles tracking (completions, scores, time spent) exactly as it would with a standard SCORM package - but the content itself is served live.

The result: you upload the SCORM package to the LMS once. Every subsequent update to the course content is applied immediately, to every deployment, without any re-uploading required.

"Upload once. Update anywhere. Every learner who launches the course always sees the current version - without any change to the LMS configuration."

How it works technically

In CourseAgent's implementation, when you publish a course as Dynamic SCORM, the system generates a compact SCORM 1.2 or 2004 package containing:

• A standard imsmanifest.xml that the LMS uses to register the course
• A launcher HTML file that initialises the SCORM API communication with the LMS
• A reference to the course hosted on CourseAgent's servers

When a learner launches the course, the launcher establishes the SCORM session with the LMS, then loads the current published version of the course content from CourseAgent. Completion data, scores and session time are communicated back to the LMS through the standard SCORM API - the LMS has no awareness that the content is being loaded remotely rather than from its own file system.

When you update and republish the course in CourseAgent, the content on the host server is updated. The next time any learner launches the course - in any LMS it has been deployed to - they see the updated version. No re-upload required.

There is one important technical requirement: learners must have internet access when launching the course, since the content is loaded from an external server. Dynamic SCORM is not suitable for offline delivery scenarios.

Why it matters most for compliance training

Dynamic SCORM has obvious benefits for any course that might need updating. But it is particularly valuable for compliance training, for three reasons.

Regulations change on a schedule you don't control. A compliance course that was accurate when published may become inaccurate when new legislation is introduced, when guidance is updated, or when an enforcement ruling clarifies what a regulation actually requires. With traditional SCORM, every regulatory change triggers a content update cycle. With Dynamic SCORM, the course is updated and the change is live across all deployments immediately.

Audit trails require version clarity. In regulated industries, the question "which version of the course did this learner complete?" sometimes has legal significance. Dynamic SCORM with a well-managed publish history allows you to identify exactly what content was served on any given date - something that is significantly harder to establish with traditional SCORM deployments that may have multiple uploaded versions across multiple systems.

Multi-organisation deployment is common in compliance. Training consultancies building compliance content for multiple client organisations typically maintain the same core course deployed to multiple LMS platforms. Dynamic SCORM eliminates the need to re-upload to every client's LMS when the course changes - a single update in CourseAgent propagates to all deployments simultaneously.

Dynamic SCORM vs Static SCORM: at a glance

• Updates: Dynamic = immediate everywhere · Static = re-upload required
• LMS upload: Dynamic = once · Static = every version change
• Multi-LMS deployment: Dynamic = single update · Static = update each separately
• Offline delivery: Dynamic = not supported · Static = works offline
• LMS compatibility: Both = any SCORM-compatible LMS
• Learner experience: Both = identical

Limitations and when to use static SCORM

Dynamic SCORM is not universally better than static SCORM. There are specific scenarios where traditional SCORM packaging remains the right choice.

Offline delivery requirements. If learners need to complete courses without internet access - field workers, remote sites, secure environments without external network access - Dynamic SCORM cannot be used. The course content requires a live connection to the host server.

Highly restrictive network environments. Some enterprise environments with strict egress filtering may block requests to external servers during course delivery. In these cases, static SCORM - where all content is hosted within the LMS - is more reliable.

Archival and compliance record-keeping. If there is a regulatory requirement to retain a complete, self-contained copy of the exact content a learner completed, a static SCORM package provides a more straightforward archival record than a dynamically served course.

Content that genuinely doesn't change. If a course covers stable content that will never need updating - historical training, archived programmes - the overhead of Dynamic SCORM infrastructure provides no benefit.

For the majority of compliance, onboarding and skills training content - where updates are periodic, delivery is online and multi-platform distribution is common - Dynamic SCORM significantly reduces the operational burden of maintaining a live content library.

Dynamic SCORM in CourseAgent

Dynamic SCORM is available on CourseAgent's Enterprise plan. Publish once, deploy to any SCORM-compatible LMS, and update your content without ever touching the LMS configuration again.

See Enterprise plan → · Compare SCORM features →