August 20, 2026
CONTENT CREATED BY:

Table of contents
In the context of corporate e-learning, Sequencing Logic —also known as sequencing rules— is the technical mechanism that governs how activities are ordered and presented within a SCORM course on a SCORM-compliant LMS. It was formally introduced in SCORM 2004 as part of its Sequencing and Navigation (S&N) module, marking a significant leap forward from SCORM 1.2, which only supported basic linear navigation.
Unlike a fixed table of contents where learners can freely access any module, Sequencing Logic allows instructional designers to set conditions: a learner can only access module 3 after passing module 2, or is automatically redirected to a review module if their assessment score falls below 70%. This ability to adapt the learning path based on actual performance makes Sequencing Logic a cornerstone of modern learning pathways.
Sequencing Logic operates through a set of declarative rules written in XML inside the imsmanifest.xml file, the SCORM package manifest. When the SCORM player within the LMS loads a course, it reads this manifest and applies the sequencing rules in real time every time a learner completes an activity, navigates back, or requests to move forward.
The process follows this pattern:
This cycle repeats at every transition, creating a controlled and reproducible learning flow on any e-learning standards-compliant platform.
The IMS Simple Sequencing specification —adopted by SCORM 2004— defines three main types of rules that instructional designers can combine:
One of the main reasons many L&D teams choose SCORM 2004 over SCORM 1.2 is precisely the sequencing capability. The difference is substantial:
| Feature | SCORM 1.2 | SCORM 2004 |
|---|---|---|
| Sequencing rules | Not available | Yes (native IMS SS) |
| Conditional pathways | Limited (manual JS) | Native in XML |
| Status rollup | No | Yes |
| Navigation controls | Basic | Full |
In a corporate training environment, Sequencing Logic solves very specific challenges that linear learning cannot address:
For these scenarios to work correctly, the LMS must implement the standard fully. This is a relevant criterion when evaluating SCORM-compliant LMS platforms.
SCORM 2004 Sequencing Logic is powerful, but it comes with complexity and limitations worth understanding before designing courses that rely on it:
For instructional design teams publishing with SCORM-compatible authoring tools, understanding these limitations enables more informed decisions about when to apply complex sequencing and when a simpler structure is sufficient.
SCORM 2004 sequencing logic was pioneering, but the concept has evolved. Modern LMS platforms have integrated their own sequencing mechanisms that go beyond what SCORM allows: rules based on dates, other users’ activity, external assessments, or the employee’s competency profile.
In this sense, SCORM 2004 Sequencing Logic can be understood as the technical precursor to what is now known as intelligent learning paths or adaptive learning journeys. The difference lies in scale and context: while SCORM 2004 defines logic within the course package, modern LMS platforms apply that logic at the level of an entire training program, integrating multiple courses, assessments, and resources.
Understanding Sequencing Logic is therefore understanding the technical foundation on which today’s learning pathways are built in any organization.
Yes, within the SCORM standard, full sequencing logic is only available in SCORM 2004, through the Sequencing and Navigation (S&N) module based on the IMS Simple Sequencing specification. SCORM 1.2 does not include this mechanism natively; creating conditional pathways in SCORM 1.2 required custom JavaScript embedded directly in the content, which created maintenance and cross-platform compatibility issues.
Not necessarily in full. The IMS Simple Sequencing specification is extensive and technically demanding to implement completely. Many LMS platforms support the most common sequencing rules (pre-condition, post-condition, and basic rollup), but may behave unexpectedly with complex or less common sequencing logic. Before designing a course with advanced sequencing, it is recommended to verify the LMS’s level of support and run tests with representative use cases.
Sequencing Logic is defined in the imsmanifest.xml file of the SCORM package, using specific XML elements such as <imsss:sequencing>, <imsss:sequencingRules>, and <imsss:rollupRules>. In practice, instructional designers rarely write this XML manually: SCORM 2004-compatible authoring tools provide visual interfaces to configure sequencing rules without writing code. The result is automatically exported to the package manifest.
They are two components of the same S&N (Sequencing and Navigation) module but with different functions. Sequencing Logic determines which activity should be delivered next based on the learner’s progress and status. Navigation, on the other hand, controls the interface elements the LMS presents to the learner: whether they can move forward freely, go back, or jump to a specific module from the table of contents. Both work together: sequencing decides the logical flow, and navigation controls how the learner can interact with that flow.
Automate processes, access 600+ ready-to-use courses, or create your own content with the help of AI.
Request a demoContact us
