SCORM vs xAPI: What Actually Gets Tracked

If you run training, two acronyms come up fast: SCORM and xAPI. Both are ways of getting a course to report what a learner did back to a system that tracks it — but they were built for different jobs, and picking the wrong one usually shows up later, when someone asks for a report the data can't produce.

SCORM: completion, score, pass/fail — inside the LMS

SCORM (Sharable Content Object Reference Model), in its 1.2 and 2004 revisions, is the long-standing packaging and tracking standard for eLearning. A SCORM package runs inside an LMS and, through a defined JavaScript API, reports back a fixed, relatively small set of facts: whether the learner completed the course, what score they got, and whether they passed or failed. For most "did they finish it and pass?" compliance and certification needs, that's genuinely enough, and every major authoring tool — Articulate Storyline, Rise 360, iSpring — exports it without extra configuration, which is a large part of why it has stayed the default for so long.

xAPI: statements, not just a completion flag

xAPI (originally called Tin Can API) takes a different approach. Instead of one summary result per course, it records individual statements in an "actor–verb–object" shape — "Priya answered scenario 3", "James watched module 2 to 80%", "Amara attempted the branching exercise and chose path B". Those statements go to a Learning Record Store (LRS) rather than only to the LMS, which means xAPI can capture learning that happens outside a traditional course package entirely — a workshop attendance, a simulation, a mobile app interaction — anything that can emit a statement.

What actually decides which one you need

• Completion and a pass/fail score is enough — SCORM. It's simpler to implement, cheaper to maintain, and every LMS supports it natively.
• You need to prove specific behaviour, not just an outcome — xAPI plus an LRS. Useful for compliance audits that ask "show me exactly what they did", not just "show me they passed".
• Training happens partly outside the LMS — a blended programme with in-person sessions, simulations or a companion app — xAPI is the only one of the two that can stitch that activity into one record.
• Genuinely not sure yet — author the course in a tool that can export both, and decide the reporting question later rather than committing to a tracking model before you know what you'll be asked to prove.

In practice most compliance training we build still ships as SCORM, and most projects that need granular or cross-platform evidence move to xAPI once that requirement is explicit — see it applied in our compliance course showcase. We implement both — see our SCORM / xAPI / Articulate work and the deeper SCORM vs xAPI guide, or book a free LMS consultation if you're not sure which your reporting actually needs.