SCORM · xAPI
Sharable Content Object Reference Model / Experience API (Tin Can API)
What is SCORM?
- The international standard for exchanging learning records between content and the LMS
- SCORM = inside the LMS; xAPI = records offline and mobile too
- The buyer should specify the standard and completion criteria in the contract
What SCORM and xAPI really change is how long your content lasts. A course built to the standard can move to a new LMS as a single zip file and open as is. A course built only for the vendor's own player won't even play once your contract with that company ends. The standard is what keeps content a company asset, and it also decides who holds the learning records. Whether content can be migrated is decided when production starts, and once delivery is complete there is practically no way to undo it.
In practice, look at the version, not just the standard's name. Almost every LMS can read SCORM 1.2, but its suspend_data limit, which holds resume information, is only 4,096 characters, so in courses with lots of branching and simulation the stopping point is lost entirely. SCORM 2004 (3rd/4th edition) raises the storage limit to roughly 60,000 characters and supports per-attempt records and sequencing, but support across LMSs is narrow, so testing beforehand is a must. Many Korean LMSs fully support only 1.2, so building in 2004 without checking before you order means rework starts on delivery day.
xAPI starts from a different premise: it stores records in an LRS (learning record store), not in the LMS. If you accept xAPI content without an LRS, the records are kept nowhere. To keep completion decisions and certificate of completion issuance running in your existing LMS, you must also require the cmi5 specification. xAPI is not a superset of SCORM but a separate lineage, so mixing the two in one order splits progress for the same course across two places and the totals won’t reconcile.
The most common mistake is trusting a single line in the proposal that says 'SCORM compatible'. If the version and completion criteria aren't written into the contract, the vendor builds to its own standard, and at acceptance testing problems like 'progress won't go past 90%' and 'pop-ups are blocked on mobile, so no record is saved' all surface at once. A standard only aligns how records are kept; it does not guarantee content quality or video resolution. Also, if you receive only the SCORM package and don't secure the original video and caption files, you end up paying the vendor again even when a law change means you need to fix a single scene.
Eun-a ChoExpert in communication, stress management, career development, and Gen Z/Millennial training
John KimCEO of Nanum Consulting and author of B2B Marketing DesignSCORM was created around 2000 by the ADL (Advanced Distributed Learning) Initiative of the U.S. Department of Defense, which consolidated scattered e-learning specifications into one. As its inability to cover mobile and offline learning became clear, ADL released xAPI in 2013.
Consider a hypothetical case. Company A, an auto parts manufacturer with 1,240 employees, decided to replace an LMS it had used for 8 years. It had to move its statutory mandatory training and 40 job-skill courses. At a vendor meeting it was told that “migrating existing content is quoted separately.” Rebuilding costs came to an estimated KRW 84 (≈ US$1) million, and the project stalled.
- Mr. Kim, a senior manager on the HRD team, unzipped the 40 existing content files himself and checked for imsmanifest.xml. 28 were SCORM 1.2 packages, and 12 ran on the producer’s proprietary player, so they could not be migrated.
- They asked the new LMS vendor’s contact to verify with a sample that the system reads both 1.2 and 2004. Before signing, they test-uploaded 3 courses and received screenshots of the progress and score logs.
- For the RFP covering the 12 courses that needed rebuilding, we fixed the standard at SCORM 1.2 and set the completion criteria in hard numbers: '90%+ progress and a score of 70+ on the assessment.' We also made delivery of the original video and caption source files a contract condition.
- During acceptance testing, we ran a two-week pilot with 30 frontline staff to check resume-after-interruption, Android Chrome, and iPad playback. When resume broke in one branch-heavy safety course, we asked the vendor to shrink suspend_data and they fixed it free of charge.
- In the end, all 28 were migrated as is: rebuild costs fell from KRW 84 million (≈ US$62,800) to KRW 26 million (≈ US$19,500), the migration timeline shrank from an estimated 3 months to 6 weeks, and post-launch “progress isn't recorded” tickets dropped from about 40 a month to 3.