SCORM, xAPI, and Tracking Student Progress

SCORM (Sharable Content Object Reference Model)

A set of technical standards that lets course content talk to an LMS. When a student completes a lesson, passes a quiz, or spends time on a module, SCORM is the protocol that reports that data back to the LMS.

What it does in practice:

• Tracks whether a student completed a lesson
• Records quiz scores
• Tracks time spent on content
• Lets the LMS mark a course as “complete” when all requirements are met

SCORM 1.2 vs. SCORM 2004: Two versions. SCORM 2004 is newer and supports sequencing (you can require lessons to be completed in order). SCORM 1.2 is older but more widely supported.

When you’ll hear it: When selling courses into corporate training, compliance, or any environment that uses a traditional LMS (Moodle, Canvas, Cornerstone). If a corporate buyer asks “Is your content SCORM-compliant?”, they need your course to plug into their existing LMS.

Do you need to care? Only if:

• You’re selling to businesses that have their own LMS
• You’re building compliance or certification training
• Your course needs to plug into a system like Moodle or Canvas

Most individual course creators on platforms like Teachable, Kajabi, or GoHighLevel never need SCORM. Those platforms handle progress tracking on their own.

xAPI (Experience API, formerly Tin Can API)

The successor to SCORM. It tracks a wider range of learning experiences — not just “completed a lesson” but “watched a video,” “downloaded a PDF,” “participated in a discussion,” or “completed a real-world task.”

What makes xAPI different from SCORM:

• Tracks learning outside the LMS (mobile apps, simulations, real-world activities)
• Doesn’t require a browser — works offline and across devices
• More flexible data — you define what “completed” means for any activity
• Stores data in a Learning Record Store (LRS)

When you’ll hear it: In corporate and enterprise training discussions. If someone mentions Tin Can, they mean xAPI — it was renamed after the original Tin Can API project.

Do you need to care? Same as SCORM — only if you’re in the corporate/enterprise space.

LRS (Learning Record Store)

A database that stores xAPI learning data. If xAPI is the language, the LRS is the database that collects and stores the statements.

Do you need to care? Only if you’re using xAPI, which most individual course creators aren’t.

LTI (Learning Tools Interoperability)

A standard that lets external tools integrate with an LMS. If you’ve ever used an external quiz tool, video platform, or virtual classroom that seamlessly appeared inside your LMS, LTI made that possible.

Do you need to care? Only if you’re integrating third-party tools into a traditional LMS. Most all-in-one platforms handle integrations through their own APIs, not LTI.

Progress Tracking (The Practical Version)

Most course platforms track student progress without SCORM, xAPI, or any of these standards. They use their own built-in systems:

• Lesson completion — marked done when the student clicks “Complete” or watches the video
• Quiz scores — recorded automatically
• Course progress percentage — calculated from completed lessons
• Certificate triggers — automatically issued when all lessons are marked complete

If you’re building on GoHighLevel, Teachable, Kajabi, or Thinkific, this built-in tracking covers everything you need. SCORM and xAPI only matter when your course needs to live inside someone else’s LMS.