SCORM suspend data explained

Suspend data is a storage field a SCORM course can use to save state between sessions. Authoring tools often use it to remember completed interactions, navigation state, question progress or other information needed when the learner returns.

When a learner exits, the course writes state information to the LMS. On relaunch, the course reads it back and reconstructs where the learner was. A separate location or bookmark value may also be used.

• The course does not commit updated data before exit.
• The saved data exceeds practical limits for the chosen SCORM version or LMS.
• A package update changes how existing state is interpreted.
• The LMS overwrites or rejects part of the value.
• The course stores the wrong state at the wrong time.

1. Complete part of the course.
2. Exit using the intended course control.
3. Close the launch window.
4. Relaunch as the same learner.
5. Check page position, interactions, assessment progress and completion state.
6. Repeat after a package update.

Course authors rarely control the raw storage format, but they can avoid unnecessary complexity. Excessive branching, huge interaction histories and fragile state logic can make resume behaviour harder to maintain.