SCORM 1.2 vs 2004: which format should you choose?

Use SCORM 1.2 if your destination requires it or your existing package passes the checks you need. Consider a supported SCORM 2004 edition for separate completion and success statuses; choose 3rd or 4th Edition if you need more resume-data space. Test the exported package in the destination LMS.

The choice appears as a small setting in your authoring tool. Its consequences show up later: a client returns to the wrong screen, a finished quiz does not validate a lesson, or a report cannot distinguish finishing from passing. The useful question is which format preserves the behavior your course needs in its new home.

This guide compares those decisions. If you already know your format and need the upload steps, follow the SchoolMaker SCORM import guide.

SCORM 1.2 vs 2004 at a glance

Choose the destination format first, then test the behavior your course needs.

The status distinction comes from the SCORM runtime model described by Rustici Software. The edition-specific resume limits are documented in Articulate’s suspend-data reference. Those are standards and authoring considerations, not a promise that every LMS exposes the same reports or enforces the same storage limits.

Start with the platform that will receive the ZIP

Ask the destination provider which SCORM versions it accepts and which edition it recommends for your authoring tool. If a client will host your training in its own LMS, get that answer before publishing the final files. A format that suits your school may not suit the client’s environment.

Request a concrete requirement rather than a general “SCORM-compatible” answer. Is the course a single interactive module? Does it contain several separately launched learning objects? Must the client’s report show both completion and passing? A supported ZIP import does not answer all three questions.

For example, imagine that you sell an introductory negotiation course and also license it to a training company. Your own school and that company’s LMS may need different exports from the same authoring project. Keep a short export record for each destination: tool version, SCORM version and edition, tracking rule, and the date you checked the result. That makes the next update much easier to reproduce.

Decide what finishing and passing mean

A learner can read every screen and fail the assessment. You need to decide whether that should count as a completed learning activity, a passed activity, or an activity that still blocks the next lesson.

SCORM 1.2 uses cmi.core.lesson_status for values such as completed, incomplete, passed or failed. SCORM 2004 separates cmi.completion_status from cmi.success_status. This allows the package to describe a completed activity with a failed assessment. Whether that distinction is visible and useful depends on the receiving LMS and its reporting interface.

Write your rule in plain language before selecting an export option. For example: “Clients must pass the discovery-call quiz before moving to the practice assignment.” That instruction gives you something to test. “Track the course” does not tell you what should happen when someone reaches the end with an unsuccessful score.

The reporting and tracking choices in your authoring tool matter alongside the SCORM version. Articulate’s Rise 360 export documentation treats the LMS standard and tracking option as separate choices. Changing the standard while leaving the wrong completion rule in place may leave you with the same problem.

Check how much the module needs to remember

Returning to a module may involve much more than reopening a page. The content might need to remember a branching choice, a saved answer, a visited activity and the current position. The package and platform exchange that state so the authoring tool’s player can reconstruct the attempt.

The standard’s suspend-data allowance is one reason to consider SCORM 2004 3rd or 4th Edition for a complex module. Do not group every edition under a single larger limit: 2004 2nd Edition has a smaller allowance than 1.2. Also avoid treating the character allowance as a file-size limit. It concerns saved runtime state, not the size of your ZIP, images or videos.

A useful check is to stop late in the most complicated part of the course, then return. Testing only the second screen of a long scenario may miss a problem that appears after many answers have accumulated. If the module remembers simple screens but loses later choices, investigate the saved state and the authoring tool’s resume settings before rebuilding the course.

Articulate’s LMS troubleshooting guidance recommends checking the supported standard, tracking configuration and resume behavior together. A different export can help with a specific limitation, but it is not a general cure for every interrupted session.

Do not confuse a rich module with multi-SCO sequencing

A SCORM package can contain learning objects called SCOs. A single SCO may already include many screens, questions, videos and branches. A long interactive activity is therefore not automatically a multi-SCO course.

SCORM 2004 also includes sequencing and navigation rules between learning objects, as described in Rustici’s technical guide. Those rules require corresponding support from the LMS. If your package depends on them, ask the provider about that structure explicitly and demonstrate the expected route through it.

SchoolMaker plays the first launchable SCO in a package and does not implement full SCORM 2004 sequencing. A single authored module can fit that scope; a multi-SCO program whose behavior depends on those sequencing rules needs a different package structure or a platform that implements them. Splitting it into independent modules is a teaching and testing decision, not a guarantee of an equivalent course.

Use the format inside the course experience you want to build

SchoolMaker is an e-learning platform that accepts SCORM 1.2 and 2004 ZIP imports as dedicated lessons. You can use those modules alongside other course materials, then support clients with practical lesson steps, community discussions and coaching. The authored activity keeps its place inside a broader training offer.

A real local SchoolMaker lesson editor with fictional demonstration content. The upload control accepts both SCORM formats; the module still needs a representative playback test.

The relevant SchoolMaker check is whether the imported module produces the course progression you intended. A local development test used fictional packages in both formats to check reopening a saved position and automatically validating the lesson step after a successful quiz. That confirms those particular test paths; it does not certify every export from every authoring tool.

For a new package, use an account that has not already completed the lesson. Check an interrupted attempt, an unsuccessful assessment and a successful assessment. In SchoolMaker, the editor preview does not save member progress. A required passing score affects automatic validation, and an already completed step is not revoked by a later unsuccessful attempt. These details can change how you interpret a retest.

See the SchoolMaker SCORM compatibility page for the supported scope. Check SchoolMaker’s current plans separately when planning your school; a standards comparison does not establish feature entitlement or a particular storage allowance.

Make one export decision, then record the evidence

Keep SCORM 1.2 when the receiving platform needs it and the module passes your acceptance checks. Consider a supported 2004 edition when separate completion and success information or a larger resume-state allowance solves a real course requirement. If your existing 1.2 course works, the version number alone is not a reason to interrupt active learners.

Before changing a live module, keep the original package and test the new export in a separate lesson. In SchoolMaker, replacing a package resets saved positions for that module while preserving completed steps. A conversion made to improve future attempts may therefore interrupt people who are halfway through the old version.

1. Write the intended completion and passing rule.
2. Confirm the destination’s format and edition requirements.
3. Export one representative module from the authoring project.
4. Check late-course resume, unsuccessful and successful results in that destination.
5. Save the tested ZIP and export settings before repeating the process for the remaining modules.

Your finish line is a package whose behavior you can explain and reproduce: the client returns to the expected place, the assessment records the intended outcome, and the next course step opens when it should.