SCORM

SCORM is an embed block in the Disco content editor that lets admins bring externally-authored learning modules into a lesson and optionally require members to finish them before progressing.

​

Overview

SCORM is not a separate admin page or a standalone content template. It lives inside Disco’s rich text editor, which means you can drop a SCORM activity into any surface that uses the editor, including lessons, posts, curriculum items, collection items, and content apps. When the package is built correctly, Disco tracks completion and score data, surfaces that data in reporting, and can gate member progression on SCORM completion.

​

Add SCORM Content Type

Use the SCORM Content type whenever you have packaged learning content from an authoring tool (such as Articulate, Rise, iSpring, or Storyline) that you want to deliver inside Disco without rebuilding it as a native lesson.

1. From within any curriculum select Add Content
2. Select the SCORM content type
3. In the setup modal, drop or select your .zip file under Upload your SCORM zip file.

​

Add SCORM Block to a Lesson

If you have an existing Lesson, but would like to add a SCORM embed within the lesson, you can do that through the editor by adding a SCORM block.

1. Open the editor where you want the SCORM activity to appear.
2. Place your cursor in the editor.
3. Type /scorm.
4. Select SCORM from the block menu.
5. In the setup modal, drop or select your .zip file under Upload your SCORM zip file.

The helper text reads: Your SCORM file will need to be proccessed before it can be used. This may take a few minutes. The upload only accepts a zipped SCORM package. If the file is not recognized as a real .zip, you will see the validation error: Are you sure you uploaded a zipped SCORM file?

​

What Happens After Upload

Uploading the file does not make it playable right away. Disco creates a SCORM file record in a processing state and sends the package through a background job. Processing can take a few minutes. While the package is being processed, the editor shows a waiting state with the title Processing File… and the message Your SCORM file is currently being processed. Check back in a few minutes! If processing fails, the editor shows an error state with the title Something went wrong, either a specific processing error or a generic retry message, and an Upload File action so you can re-upload the package. One common failure is a missing manifest. If the package does not contain imsmanifest.xml, Disco returns the explicit error: The SCORM file is missing an imsmanifest.xml file. Packages that contain a manifest but do not resolve to a usable entry file will also fail. Once processing succeeds, the SCORM activity renders inside an iframe in the editor. At that point you can confirm the package loads, preview the embedded content, and use fullscreen when supported.

​

How SCORM Completion Works

SCORM completion tracking starts when a member opens the activity from a specific placement, such as a curriculum item or a collection item. Disco tracks completion for that specific placement rather than as one shared record for the source content everywhere it is used. The same SCORM source content can be reused in multiple places, and each placement has its own member activity and reporting. Disco reads the completion state from the SCORM package and maps it into one of six statuses that appear in admin reporting:

• Not Attempted
• Incomplete
• Completed
• Passed
• Failed
• Browsed

These statuses come from the values the package sends back. Disco checks the standard SCORM completion fields for SCORM 2004 and SCORM 1.2, and falls back to Not Attempted when no usable status is found. If the package sends a raw score, Disco surfaces it in reporting alongside the status.

​

Require SCORM Completion to Progress

Require SCORM Completion to Progress is an instance-level setting. You configure it on each placement of the content, not on the reusable source content itself. The checkbox only appears when both of these are true:

• the content is being used in curriculum
• the content actually contains SCORM

If the same SCORM source content is used outside curriculum, or if the content no longer contains a SCORM embed, the setting will not appear. The tooltip on the setting explains the real dependency: members must complete the SCORM file before they can progress, and the SCORM package must be configured to send completion status correctly or members may be unable to proceed.

​

What Members See

When this setting is turned on, the member cannot use the normal progression button until the SCORM activity reports a successful completion state. If the member has not satisfied the requirement yet, the disabled tooltip reads: You’ll need to complete the learning activity before continuing. Please finish the embedded content first. The backend also enforces this rule, so even if the frontend is stale, the content cannot be marked complete until the SCORM requirement is actually satisfied.

​

Review SCORM Completions

Admins with content management access can review SCORM progress from inside a curriculum item.

1. Open the curriculum item containing the SCORM content.
2. In the sidebar, find the SCORM completions surface.
3. Click Completions Report to open the detailed SCORM Completions view.

The completions table shows member name, status, score, start date, and last interaction. If no one has started the activity yet, the report shows an empty state instead of a blank grid.

​

Filter, Sort, and Export

The report supports text search, status filtering, sorting, and CSV export. You can filter by status using any of All, Not Attempted, Incomplete, Completed, Passed, Failed, or Browsed. You can sort by Status, Score, Start Date, or Last Interaction. The Export CSV action exports the current report view, including your active search, status filter, and sort order. This is useful when you want to hand completion data to operations, instructors, or program stakeholders.

​

Settings and Configuration That Affect Behavior

Several things outside the SCORM block itself affect how the feature behaves.

• SCORM entitlement. If your Academy does not have the SCORM entitlement enabled, you cannot complete the setup flow. The setup modal shows the SCORM paid-feature gate and disables the final Embed action. If SCORM is not appearing in your block menu, or the Embed button is disabled, reach out to your Disco contact to confirm that the entitlement is on your plan.
• Curriculum placement. The progression-gating setting only matters in curriculum contexts. If the SCORM item is not being used as a curriculum item, the Require SCORM Completion to Progress behavior is not exposed the same way.
• Package quality. The package must be structurally valid enough to process, and it must report meaningful SCORM completion values if you want reliable progression gating and reporting. A package that uploads and processes successfully can still behave poorly at runtime if it does not emit a recognized completion status.

​

Edge Cases

• A valid upload can still fail later. A file can upload as a valid zip and still fail during SCORM processing if the package structure is wrong or required files are missing.
• Missing manifest breaks processing. If imsmanifest.xml is missing, the package will not become ready.
• Removing SCORM from the content later changes behavior. If SCORM content is removed from the source description after it was previously being used with SCORM progression requirements, Disco automatically clears Require SCORM Completion to Progress on instances that had it enabled. This prevents a broken state where the lesson still requires SCORM completion even though the SCORM activity no longer exists in the content.
• Reused source content does not mean shared reporting. Admins sometimes assume one SCORM source item produces one global completion log. That is not how the platform works. Reporting is tied to the instance of the content. If you reuse the same SCORM source in two curriculum items, you get two independent completion records per member.
• Members can get stuck on silent packages. If a package never sends a recognizable completion status, members cannot progress when Require SCORM Completion to Progress is enabled. Test the package before you turn the setting on.

​

FAQ