SCORM on Rise Up — Compatibility & Progress Tracking

Prerequisite You need rights to edit a training (Admin or Designer / Author rights with the permission to edit courses).
Key message: There are no SCORM “settings” to configure in Rise Up. You simply add a SCORM step, and tracking relies on the SCORM file sending standard runtime values.

What this article helps you do

Validate a SCORM package before import (avoid blank screens & broken tracking).
Understand how Rise Up interprets progress, completion and score.
Share the right expectations with training designers and learners (what’s supported vs not).

Who can add a SCORM step and who can see results

Who can add SCORM: platform admins and training designers/authors (when they have rights to edit the training content).
Who can view results: admins and group managers can review learner progress/results through reporting dashboards (depending on their permissions scope).

I — Check your SCORM before uploading

Before uploading a SCORM into Rise Up, perform a quick technical verification. This prevents most launch issues, incorrect progress values, or missing completion signals.

Test the package in SCORM Cloud
Upload your file and confirm that the SCORM launches correctly and reaches a final completion state.
SCORM Cloud
Inspect runtime behaviour with a SCORM debugger
Check which values are sent during the session (completion status, score, suspend data).
SCORM Debugger
Verify the ZIP structure
- The archive must open directly on imsmanifest.xml.
- No intermediate folder at the root level.
- File names should not contain accents or special characters.
Validate completion logic
- SCORM 1.2 → final status sent via cmi.core.lesson_status.
- SCORM 2004 → use completion_status or success_status.
- Send the final completion only at the end of the module.
Apply basic technical checks
- Avoid popups or opening the module in a new window.
- Flash content is not supported.
- If multiple quizzes exist, send one consolidated final score.
- No specific SCORM settings are required in Rise Up.

II — Compatibility checklist before import

Technical requirements

Requirement	Expected
Package format	ZIP file
Archive structure	Archived directly at root level (no intermediate folders)
Max size	1 GB
File name	No accents or special characters
Supported versions	SCORM 1.2 and SCORM 2004 (2nd / 3rd / 4th edition)
Not supported	Multi-SCO

How to identify the SCORM version

Unzip the SCORM package
Open imsmanifest.xml
Check the schemaversion tag:
- Empty or missing → SCORM 1.2
- Otherwise → SCORM 2004 (edition specified)

Recommended validation checks

Avoid Flash, popups, and “open in a new window” behavior
Use a “Passed / Incomplete” reporting mode where possible
Use responsive design if learners access content on mobile

Note: Rise Up does not support setting a minimum duration for a SCORM step.

III — How Rise Up interprets progress & completion

Progress interpretation

Progress	Meaning
0%	Not started
50%	Started (learner clicked Start)
100%	Completed

Important: intermediate percentages are not supported.

Mandatory runtime elements (completion)

SCORM	Element	Initial value	Final values
SCORM 1.2	`cmi.core.lesson_status`	`not_attempted`	`completed`, `passed`, `failed`
SCORM 2004	`cmi.completion_status` `cmi.success_status`	`unknown`	completion: `completed` success: `passed` / `failed`

SCORM 2004 rule: completion is reached if completion_status = completed OR success_status = passed/failed.

Critical behavior: if the SCORM sends a final mandatory completion element too early, Rise Up stops updating score and success/failure afterwards.
Best practice: send the final completion element (and final score) only at the end.

IV — Understanding SCORM scores

Score rules

Topic	Rule
General	Score is optional. If used: numeric, preferably as a percentage. Avoid “minimum score to pass” logic inside the SCORM if you expect multiple attempts (only one visible attempt, previous attempts may be lost). If multiple quizzes exist, keep one consolidated final score (sent at completion).
SCORM 1.2	Mandatory: `cmi.core.score.raw` \| Optional: `cmi.core.score.min`, `cmi.core.score.max` Displayed score = `round(100 * (raw - min) / (max - min))`
SCORM 2004	Preferred: `cmi.score.scaled` (0–1) \| Supported: `cmi.score.raw`

Resume behavior (progress persistence)

Rise Up stores cmi.suspend_data (as-is, not interpreted).
That value is sent back to the SCORM file on relaunch to support resume (depending on content design).

V — Updating / replacing a SCORM module

Replacement rules

Scenario	Behavior
Impact	Immediate for all learners
Learners not completed	Progress preserved + `cmi.suspend_data` reused
Critical constraint	New SCORM must keep the same structure, otherwise progress may be corrupted (reset)
If the update is breaking	Safe option: create a new training

Issue: SCORM is blank / doesn’t load.
Fix: Check ZIP root structure (no intermediate folder), file name, and avoid new windows/popups/Flash. Test in SCORM Cloud or a debugger first.

Issue: Progress stays at 50% after finishing.
Fix: Ensure a final completion element is sent at the end (1.2: lesson_status; 2004: completion_status or success_status).

Issue: Score looks lower than expected.
Fix: Final completion/score may be sent too early. Send final values only at the end.
Do I need to configure SCORM settings in Rise Up?
- No. SCORM is used as a step inside a training. Tracking relies on what the SCORM file sends.

How can I test a SCORM package before importing?
SCORM Cloud
SCORM Debugger

Can training designers import SCORM?
- Yes, if they have permissions to edit the training content (Author/Designer rights depending on your platform setup).

Can group managers view learner results?
- Yes, if their permissions include reporting access for their scope.
Need help? Submit a request:
Rise Up Support Request

Knowledge base Rise Up