WHITEPAPER
Not sure how to choose your SCORM-compatible authoring tool?
November 17, 2026
CONTENT CREATED BY:

Table of contents
SCORM sequencing is the set of rules that determines which activity is delivered to the learner after each one, which navigation controls are available and under what conditions they can move forward, repeat or skip part of the course. It does not affect what happens inside each piece of content: it governs what happens between them.
In practical terms: without sequencing, a SCORM course is a list of modules the learner works through at will. With sequencing, the package can decide that module 3 stays locked until module 2 is passed, that anyone who passes the diagnostic test skips the theory section, or that a test allows only three attempts. That logic does not live in the content, but in the package’s manifest file, and it is the LMS that runs it.
This is the first source of confusion and it is worth clearing up right away: SCORM 1.2 has no sequencing. Not partial, not limited: it does not exist in the specification. Anything that looks like a conditional path in a SCORM 1.2 package has been programmed inside the content itself, not handled by the standard.
Sequencing arrived with SCORM 2004, in the component called Sequencing and Navigation. And it was not written from scratch: according to the standard’s documentation, it derives from the Simple Sequencing specification published by the consortium known today as 1EdTech, whose version 1.0 was released in March 2003 and which was not designed specifically for SCORM.
The dates are worth keeping in mind too, because they put the landscape in order. According to the official version history, SCORM 1.2 was published in October 2001 and SCORM 2004 had four editions, of which the fourth, from March 2009, is the latest one in existence: the standard has received no revisions since.
| Version | Does it have sequencing? | What that means in practice |
|---|---|---|
| SCORM 1.2 (October 2001) | No. | The LMS displays the course tree and the learner navigates freely. Any condition has to be programmed inside the course. |
| SCORM 2004, editions 1 to 3 (2004-2006) | Yes, Sequencing and Navigation. | Available, but unevenly implemented across platforms. The 1st edition had known issues in the sequencing specification itself. |
| SCORM 2004, 4th edition (March 2009) | Yes, the most complete version. | It is the last published edition of the standard and the one that handles sequencing best, but also the least supported by older LMSs. |
| xAPI and cmi5 | No, and that is not a shortcoming. | These standards record what happens, they do not decide the path. That logic moves to the LMS or the learning platform. |
To understand sequencing you have to see the course the way the LMS sees it. According to the SCORM content packaging documentation, the manifest describes the course in three blocks: the resources (the actual pieces, whether content objects or plain files), the organizations (hierarchical groupings of those pieces) and the items (the nodes of that hierarchy). An item with no children must point to a resource; an item with children is a container.
That hierarchy is the activity tree. Every item in the manifest is an activity, and those with children are called clusters. The full tree is the course’s entire organization. Sequencing acts on that tree, not on the files.
Each activity carries its own tracking data: whether it is completed, whether it has been passed and with what score. Leaf activities take that data from the Runtime API while the learner works; containers obtain it by aggregation —rollup— from what their children have done. That mechanism is what allows a whole folder to be marked as passed when the modules it contains are passed.
The rules are declared in XML inside the package manifest, and each activity can have its own set. These are the main groups, with an example of what each one solves:
| Type of rule | What it controls | Typical example |
|---|---|---|
| Navigation controls | Which buttons the learner sees: previous, next, exit, and whether they can move freely through the menu. | Hiding the side menu during an assessment so the learner cannot go back to the content. |
| Choice restrictions | Whether the learner can jump to a specific activity or must follow the intended order. | Locking module 3 until module 2 is completed. |
| Conditional rules | If-then decisions that determine which activity is available and which one is delivered. | If the diagnostic test is passed, skip the theory unit and move on to the case study. |
| Attempt limits | How many times an activity can be entered and how much time can be spent on it. | Allowing three attempts at the final exam before locking it. |
| Rollup of results | How a container’s status is calculated from the status of its children. | Marking the block as passed only if all five modules it contains are passed. |
| Objectives and randomization | Objectives shared between activities and selection or shuffling of children. | Presenting three case studies chosen at random out of ten. |
The sequencing engine is run by the LMS, not by the content, and it is triggered at three moments: when the course is launched, when the learner leaves an activity and on any navigation request. The standard’s documentation describes the cycle as follows:
That last point explains a behavior that puzzles many training teams: when a learner clicks “next” and nothing happens, the content is almost never broken. What usually happened is that the engine evaluated the rules and concluded there is no deliverable activity.
It is not just an impression: the standard’s own reference documentation admits that Simple Sequencing “is anything but simple” and that using it requires a thorough understanding of its concepts. There are three concrete reasons behind that reputation.
The specification was not written for SCORM. Simple Sequencing was created as a generic standard for describing the intended behavior of a learning experience, and SCORM 2004 adopted it afterwards. That explains why it feels more abstract than an ordinary course needs.
The default values are surprising. The standard’s documentation warns that the values applied when nothing is defined can produce counterintuitive behavior, to the point that they often have to be overridden explicitly to get what you would take for granted.
Objectives get used as variables. In practice, learning objectives end up overloaded and used as flags to control the flow. It works, but it turns the manifest into a small program that is hard to read for anyone who did not write it.
On top of that comes the obvious: if the target LMS does not implement sequencing properly, the rules are not enforced. And since SCORM 2004 is less widespread than version 1.2, the risk is real. Before building a conditional path it is worth checking what your platform supports, a point we cover in our comparison of SCORM-compatible LMSs.
The useful question is not whether sequencing is powerful, but whether your course needs it. In most corporate training, the honest answer is no:
| Your case | Do you need sequencing? | What to do |
|---|---|---|
| Linear course: watched from start to finish, with completion and score recorded. | No. | SCORM 1.2 covers the case and is the most compatible option. Adding SCORM 2004 only adds risk. |
| You want to stop learners from skipping the content and going straight to the test. | Sometimes. | Many authoring tools solve this inside the course itself, without touching the manifest. Check first. |
| Different paths based on a prior diagnostic test. | Yes. | This is where sequencing genuinely pays off. It requires SCORM 2004 and an LMS that supports it well. |
| Compliance training with limited attempts and lockout after failing. | Yes, or your LMS. | Before building it into the package, check whether your platform already handles it through settings: it is usually easier to maintain. |
| You want to measure learning outside the course or outside the platform. | No, and sequencing will not help. | That is the territory of xAPI and cmi5, which record the experience instead of deciding the path. |
SCORM is made up of three pieces, and sequencing is the third:
The order matters: sequencing consumes what the run-time environment records. If the course does not report its completion status or its score properly, conditional rules will have nothing to decide on, however well written they are. It is by far the most frequent cause of a path that “doesn’t work”.
If you are just getting started with the standard, the basics are in our guide on what SCORM is, and the full process in how to create SCORM step by step. To choose a version, the detailed comparison is in SCORM 1.2 vs. SCORM 2004. And if what you are considering is moving away from SCORM, the contrast is in SCORM vs. xAPI and in the entry on cmi5, the profile that lets you launch from the LMS while measuring with the detail of xAPI.
If you manage training and do not write code, four practical decisions come out of all of the above:
With isEazy Author you can create e-learning courses and export them in formats such as SCORM 1.2 and SCORM 2004, with no need to edit the manifest manually. isEazy LMS, in turn, lets you manage and distribute training, organize learning paths and track learner progress. If you need to apply advanced sequencing rules inside a SCORM 2004 package, it is important to check beforehand which features your LMS supports and how it interprets the rules defined in the content.
An example of what changes when that part stops causing trouble: Pepco, the fashion and homeware chain with more than 4,000 stores across 18 countries, took the completion rate of its Iberian subsidiary from 27% to almost 84% and cut the time spent producing tracking reports by 70%.
No. Sequencing does not exist in the SCORM 1.2 specification: it arrived with SCORM 2004, in the Sequencing and Navigation component. In a SCORM 1.2 package the LMS displays the course structure and the learner navigates freely, so any progression condition you see in a course of that version has been programmed inside the content itself, not handled by the standard. That is why, if you need real conditional paths —locking a module until another is passed, branching based on a prior test— you have to publish in SCORM 2004 and check that your LMS supports it.
From the Simple Sequencing specification published by the consortium known today as 1EdTech, whose final 1.0 version was released in March 2003. That specification defines a method for representing the intended behavior of a learning experience, including branching rules based on learner results, and it is important to know that it was not written specifically for SCORM: SCORM 2004 adopted it afterwards. That generic origin explains much of its complexity, to the point that the standard’s reference documentation admits Simple Sequencing is anything but simple.
Almost always because the sequencing engine evaluated the rules and concluded there is no deliverable activity, not because the content is broken. There are three usual causes. First, the previous module did not report its completion status or score correctly to the LMS: without that data, a conditional rule has nothing to decide on. Second, the attempts allowed for that activity have run out. And third, the LMS does not implement sequencing properly, something common on older platforms. Before reviewing the rules, check what status the player is actually recording.
In most cases, no. If the course is linear and all you need is to record who completed it and with what score, SCORM 1.2 covers the case and is the version most compatible with any platform. Sequencing genuinely pays off in two scenarios: when you want different paths based on a prior diagnostic test, and when you need limited attempts with lockout after failing, typical of compliance training. Even in that second case it is worth checking first whether your LMS already handles it through settings, because maintaining it on the platform is considerably simpler than maintaining it inside the package.
No, and it is not a shortcoming but a different division of responsibilities. xAPI and cmi5 are designed to record what happens —what each person did, where and with what result—, not to decide the path. In those standards the logic of what comes next moves to the learning platform or to the content itself, instead of being packaged in a manifest. If what you need is to measure learning that happens outside the course or outside the LMS, SCORM sequencing will be of no use to you and the route is a different one.
With visually appealing content and ready-to-use resources. Select, customize, and done!
Try it freeRequest a demo
