Sequencing Fundamentals

This is the real reason SCORM 2004 exists.

Sequencing

SCORM 1.2 could launch content.
It could track status.

But it could not formally define how learners should move through activities.

Progression logic was often:

• Hardcoded inside content
• Configured inside LMS platforms
• Implemented inconsistently across vendors

SCORM 2004 introduced a formal sequencing model.

It standardized behavior.

🌳 The Activity Tree

The Structural Core of Sequencing

At the heart of SCORM 2004 sequencing is the activity tree.

Every SCO and content item sits inside a structured hierarchy defined in the imsmanifest.xml .

This hierarchy is not just structural.

It drives behavior.

Each node in the tree is an activity.
Activities can contain child activities.
Rules evaluate state across this hierarchy.

The tree is the execution model.

Sequencing does not operate on files.
It operates on activities.

🎛️ Control Modes

What Is the Learner Allowed to Do?

Control modes define navigation permissions.

Common modes include:

• flow
• choice
• forward only

Flow
The LMS determines the next activity automatically based on sequencing rules.

Choice
The learner may select available activities directly.

Forward Only
The learner cannot navigate backward.

These modes shape how navigation requests are interpreted.

If control modes are misunderstood, sequencing appears broken when it is actually enforcing defined constraints.

📊 Rollup Rules

How Results Move Up the Tree

Rollup rules define how child activity results affect parent activities.

For example:

• If all child activities are completed, the parent may become completed.
• If one child fails, the parent may fail.
• If progress thresholds are met, completion may trigger automatically.

This logic is not hardcoded in the LMS.

It is defined in the sequencing configuration inside the manifest.

That is the architectural shift.

SCORM 2004 moved progression logic from vendor-specific implementation into the specification itself.

The LMS executes the rules.
It does not invent them.

🔁 Navigation Requests

What Happens When a Learner Clicks Next?

When a learner clicks “Next” or selects a different activity, the LMS evaluates:

• Current activity state
• Control modes
• Pre-condition rules
• Post-condition rules
• Rollup results

Sequencing then determines:

• Whether navigation is allowed
• Which activity becomes active
• Whether progression is blocked

If completion and success values are inconsistent, sequencing may prevent movement.
If control modes restrict choice, learner expectations may conflict with defined behavior.

Sequencing is deterministic.

If something feels random, it usually indicates misalignment between data and rules.

⚠️ Why Sequencing Feels Unpredictable

When sequencing feels unstable, it is usually because:

⚠️ Control modes are misunderstood
⚠️ Rollup rules are misconfigured
⚠️ Completion and success statuses are inconsistent
⚠️ The activity tree design is flawed

Many teams attempt to handle progression inside content logic while also enabling sequencing rules.

That creates conflicting systems.

SCORM 2004 expects architectural clarity.

You either design progression inside the sequencing model, or you simplify the model intentionally.

🧠 From Complexity to System

Sequencing is powerful.

It allows:

• Structured learning paths
• Conditional remediation
• Mastery-based progression
• Modular rollup behavior

But it requires architectural thinking.

Once you understand:

• The activity tree
• Control modes
• Rollup logic
• Navigation evaluation

SCORM 2004 stops feeling complex and starts feeling systematic.

It becomes predictable.

And predictability is exactly what SCORM 2004 was designed to achieve.

🔢 6 of 12 | SCORM 2004: The Sequencing Era of Learning Standard