Before buying a third-party SCORM course, test its actual package in the LMS your employees will use. A successful ZIP upload is only the starting point. The course must launch for an authorized learner, send the completion and assessment results your organization needs, resume a saved attempt, and preserve trustworthy training records. A vendor's claim of "SCORM compatibility" cannot substitute for these buyer-specific acceptance results.
This guide gives procurement, L&D and LMS administrators 12 measurable SCORM acceptance checks, a vendor evidence request, repeatable test cases and a 100-point decision framework. If you are still choosing a standard, start with the SCORM vs AICC vs xAPI comparison. If a purchased course is already reporting incorrectly, use the SCORM completion troubleshooting guide. Here, the buying decision is whether a specific licensed package should be accepted before rollout and what evidence would justify that decision.
What does a passing SCORM compatibility test prove?
A pass shows that a specified version of a specified package meets written requirements in a specified LMS configuration. It does not certify an entire publisher's catalog, future versions of the course, accessibility compliance or commercial licensing rights. Start with five independent buying gates, then document the evidence required to pass each one.
| Gate | Required verification | Reason to reject |
|---|---|---|
| Package import | ZIP and manifest import using the contracted edition | Missing launch resources or incompatible edition |
| Runtime completion | Required completion, score and pass/fail statuses reach the LMS | Mandatory learner results not reliable |
| Attempt continuity | Suspend, save, resume and retake match agreed rules | Progress or historical evidence unexpectedly lost |
| Workforce delivery | Required browsers, devices, language and accessibility checks pass | Mandatory learner population cannot complete |
| Licensed use | Signed rights cover the audience, term and chosen delivery method | Working course but unauthorized distribution |
Keep the test package's name and version, test date, learner role, LMS tenant, LMS version, browser and device in the results. A certification statement for an unrelated package is not evidence for this particular buyer's configuration. The training content license agreement guide explains how to verify delivery and reuse rights separately.
What to request from a vendor before importing the ZIP
Ask for the production-intended package and permission to test it in your sandbox. The SCORM content packaging specification explained by Rustici Software describes the imsmanifest.xml at the root of the package, the listed resources and launchable SCOs. Not every dependency is guaranteed to be self-contained, so external resources and required browser settings deserve a written inventory.
| Vendor artifact | Why procurement needs it | Acceptable proof |
|---|---|---|
| Exact course ZIP and edition | Avoid testing a different package than the licensed deliverable | Version, file name and manifest |
| Launch and dependency notes | Find external services and supported browser expectations | Launch documentation and resource list |
| Tracking design | Understand completion, assessment and grading thresholds | Expected status and score outcomes |
| Attempt behavior | Confirm resume, bookmarks, retries and review mode | Documented learner workflow |
| Support and release policy | Establish how defects and updates will be handled | Named support route and version policy |
| Rights and accessibility evidence | Confirm authorized users and the specific player version | License schedule and evaluated experience |
Ask for a distinct sample of each high-risk course type rather than assuming one small package represents hundreds of titles. A single-SCO, no-assessment course cannot prove the behavior of a multi-SCO course with graded assessments. Combine this with the course sample evaluation framework and the publisher assessment guide.
Test the precise SCORM 1.2 or SCORM 2004 edition
SCORM 1.2 and SCORM 2004 do not report every status through the same fields. SCORM run-time documentation explains that SCORM 1.2 uses cmi.core.lesson_status, while SCORM 2004 separates cmi.completion_status from cmi.success_status. This distinction is particularly important when a learner finishes a course but fails the assessment.
| Behavior | SCORM 1.2 | SCORM 2004 |
|---|---|---|
| Status | cmi.core.lesson_status combines completed, passed and failed states | Separate completion and success fields |
| Score | cmi.core.score.raw and optional min/max | cmi.score.raw and potentially scaled scoring |
| Bookmark | cmi.core.lesson_location | cmi.location |
| Navigation | Course packaging and LMS behavior drive the flow | Explicit sequencing can control multi-SCO flow and rollup |
Require the supplier to identify the supported edition, not just "SCORM 2004". The LMS and package should both support the sequencing features actually used. Consult Comparing SCORM 1.2 and SCORM 2004 and the run-time field reference for the standard's field names and behavior. This technical distinction should appear in the procurement acceptance sheet, not be left to the LMS administrator to discover after purchase.
The 12-point SCORM course compatibility checklist
Use one test record per check. The following are practical acceptance criteria proposed for buyers, not an official SCORM certification checklist. Mark each result as Pass, Fail or Not Applicable. A capability specified as mandatory in the RFP cannot be excused as Not Applicable.
| Check | Action | Pass evidence |
|---|---|---|
| 1. ZIP and manifest | Import the exact package into the buyer's LMS | Expected SCORM edition; no broken resources |
| 2. First launch | Assign a normal test learner and launch | Course opens, navigates and returns to LMS |
| 3. Identity attribution | Use two separate accounts | Attempts belong to the correct people |
| 4. Completion status | Finish the assigned learning path | Status matches the business rule |
| 5. Grading outcome | Produce known pass and fail results | Expected status and score recorded |
| 6. Suspend and resume | Stop mid-course and relaunch | Progress and location restored as required |
| 7. Normal and abnormal exit | Use course Exit and permitted interruption | Saved attempt and predictable recovery |
| 8. Retakes and review | Repeat after failure and completion | Attempts remain distinguishable |
| 9. Navigation and rollup | Finish multi-SCO branches and prerequisites | Course-level result is accurate |
| 10. Device and browser | Repeat priority journey on supported platforms | Usable launch, media and controls |
| 11. Accessibility and language | Check keyboard, captions and needed translations | Specific required experience is usable |
| 12. Transcript and export | Reconcile LMS report, score and certificate | Correct IDs, dates, statuses and scores |
These tests connect package behavior to the buying decision. The SCORM Run-Time Environment explanation documents the launch and API calls; the SCORM technical overview explains content packaging, runtime and sequencing. Neither source states that SCORM conformance automatically ensures all twelve business requirements.
Checks 1 to 4: import, launch, learner identity and completion
1. Inspect the ZIP and manifest
Import the vendor's proposed production package without repacking it. Confirm that imsmanifest.xml is accessible at the ZIP root, the intended edition is identified and required launch resources are present. Record exact errors, missing dependencies and resource URLs. Test the actual artifact that will be delivered under the agreement.
2. Launch under normal permissions
Use a standard learner account rather than an administrator's privileged preview. Verify the launch in the LMS's configured window or frame, allow the learner to navigate the first activity, and confirm that closing the course returns the user to the LMS. Log browser restrictions, popup failures and authentication loops before treating the package as compatible.
3. Reconcile learner identity and access scope
Assign the same course to two separate test accounts. Confirm that one cannot see or change the other's saved attempt and that transcripts attach to the correct learner identifier. If an employer uses contractor or seasonal groups, verify the external learner rights described in the external workforce licensing guide before testing their actual access.
4. Separate completion from assessment success
Finish an unscored version of the activity and inspect the learner-facing status and an administrator report. For scored content, test finishing without passing. SCORM 2004 can communicate completed and failed as separate statuses; SCORM 1.2 expresses its lesson status differently. The important criterion is not that every field is populated, but that the delivered data satisfies the buyer's documented completion logic and report.
Validate technical fit before purchasing
Compare the specific package, SCORM edition and reporting requirements with the training content licensing scope. Request proof, not just a compatibility claim.
Checks 5 to 8: scores, progress, exits and repeat attempts
5. Check scores and pass/fail mapping
Run one attempt above and another below the supplier's declared passing threshold. Verify that score and success outcomes are consistent in the course player, LMS transcript and manager report. Raw and scaled scores need not use identical numeric scales. The SCORM run-time reference chart distinguishes those fields; compare the actual output against your approval rules.
6. Resume a partially completed learner attempt
Leave a lesson halfway through, sign out and reopen the assignment. Check that the bookmark, required progress and allowed assessment state persist. Include a longer module to expose issues that a simple two-page sample would miss. SCORM's suspend and location fields exist in both major versions, but an authoring tool or LMS might not implement the desired resume experience. Define exactly what must be remembered.
7. Test expected exits and interruption recovery
Use the course's Exit button and the LMS close control. Where the employee workflow makes interruptions likely, separately test a dropped connection or tab close and document the expected supported behavior. SCORM's runtime sequence covers initialization, value updates and termination; an abrupt exit may behave differently from normal close. Ask the provider for a runtime log rather than accepting unexplained loss of progress.
8. Preserve attempt history on retakes
After one passing or failing result, use the LMS's approved retake process. Check whether an old valid result remains auditable, how the new attempt is recorded and whether review mode unintentionally overwrites evidence. For regulated or recurring training, ask the compliance owner to define the evidence requirement; the records retention guide covers why record periods vary by program.
Checks 9 to 12: sequencing, mobile learning, accessibility and reporting
9. Test multi-SCO navigation and course-level rollup
Choose a sample with more than one SCO. Traverse prerequisites, optional branches and required modules; then verify the course-level completion result. SCORM's technical overview describes the sequencing mechanism in SCORM 2004. A successful single-SCO test does not prove the LMS will roll up multi-SCO status in the way the buyer needs.
10. Verify the actual browser and device matrix
Test the browsers, devices and screen sizes the employer supports, including phones when workers learn on site. Inspect responsive navigation, media playback, popup or iframe behavior and reconnecting after a brief interruption. Record unsupported combinations explicitly. A desktop demonstration should not be scored as a pass for a mobile-first workforce.
11. Evaluate the course and player for accessibility and language
Use keyboard-only navigation, inspect visible focus, play captioned media where required and attempt every interactive assessment control. Test each contracted language version rather than assuming translation from a marketing badge. W3C's WCAG 2.2 Recommendation provides applicable testable criteria. A SCORM package can import perfectly and still fail a buyer's accessibility or language requirements.
12. Validate transcripts and external exports
Compare an intentional pass and fail across the course display, LMS transcript, manager reporting, certificate service and a permitted export. Match learner ID, course ID, version, attempt, date, status and score where supported and required. Ask who will diagnose conflicts and supply a corrected package. For deployment questions involving hosted course access, see the LMS-first delivery guide.
Run a reproducible pilot instead of an informal demo
Set up named test accounts and known expected outcomes before asking the provider to attend. Do not use actual employee records unless a controlled and authorized test permits them. Use the same configured LMS environment for competing packages so the comparison is fair.
| Test account | Scenario | Buyer should capture |
|---|---|---|
| Learner A | Open, complete one section, exit | First assignment and saved partial progress |
| Learner A, resumed | Sign in again, finish all required sections | Expected bookmark, status and timestamps |
| Learner B, failed | Submit assessment below threshold | Failure and score in transcript |
| Learner B, retake | Pass with an authorized fresh attempt | Preserved history and new success result |
| Learner C, mobile | Start or resume using required device | Approved accessibility and supported behavior |
| Administrator | Export and reconcile all three learners | Matching learner IDs, statuses and scores |
For each step, capture observed result, runtime log or screenshot, reviewer, date and package version. Build these acceptance requirements into the training content RFP and marketplace buyer checklist. A vendor's own LMS sandbox can help diagnose a failure, but does not replace acceptance in the purchaser's intended environment.
How to classify failures and request vendor fixes
Give each issue a ticket with: expected result, exact reproduction steps, course and package version, LMS build, browser/device, learner test role, actual result, supporting evidence, severity, correction owner and retest status. Distinguish an LMS configuration issue from a missing or malformed package dependency rather than assuming one organization is always at fault.
Blocker: a required course cannot launch, a mandatory completion or score is unreliable, or the customer lacks permitted use rights. Major: an essential learner group cannot resume, navigate or operate an assessment. Minor: a noncritical display defect with an agreed workaround. These are suggested buyer severity definitions, not an industry-certified scale.
After a package update, rerun the failed case and affected regression checks. Changes to content are not merely editorial when they modify branching, reporting or assessment behavior. Use content update triggers and publisher update verification to plan subsequent acceptance.
Apply hard gates before the 100-point buyer scorecard
This is an illustrative original procurement scorecard. Agree the weighting, passing threshold and mandatory conditions before a supplier demonstration. A high score cannot compensate for a hard failure in lawful access or required training evidence.
| Dimension | Weight | Acceptance evidence |
|---|---|---|
| Import, launch and core results | 30 | Checks 1 to 5 pass |
| Saved attempts and multi-SCO progress | 20 | Checks 6 to 9 pass as applicable |
| Device, language and accessibility | 15 | Checks 10 to 11 meet required populations |
| Transcript and audit reporting | 15 | Check 12 reconciles relevant records |
| Content quality and version currency | 10 | Subject-matter reviewer accepts course version |
| License rights and support | 10 | Signed audience rights and documented remedies |
Disqualify packages where required accessibility is absent, mandatory completion data cannot be validated, or the signed license excludes the intended learner group. Evaluate other candidates by the verified evidence, not catalog claims. For a broader choice among vendors, pair test results with vendor consolidation analysis and content library renewal auditing.
Hypothetical example: two courses pass import, but neither is approved
Illustrative scenario, not actual supplier pricing or customer experience: A US employer needs a SCORM-based supervisor course for 480 authorized workers. Package A imports and launches but fails to preserve a required assessment score after Exit. Package B records grades correctly but blocks keyboard access to a mandatory quiz control. Import success does not resolve either issue. Package A fails the buyer's reporting gate and Package B fails its accessibility requirement.
Suppose Package A is quoted at $9 per learner and Package B at $12. At 480 learners the illustrative license amounts are $4,320 and $5,760, excluding testing, implementation and support. These numbers are invented examples, not TraineryXchange prices or real publisher quotes. The lowest-priced package should not win until the material defects are corrected and the intended use is contractually authorized. Model total costs using the training platform business case guide.
Also document which retests are required after any content withdrawal or replacement; the course retirement response guide covers that contract risk.
SCORM ZIP import and LTI launches are not interchangeable
Some suppliers host content remotely rather than delivering an importable package. 1EdTech's LTI specification describes a separate way to connect remote tools and platforms; applicable LTI Advantage services can support grade return. Neither SCORM import support nor LTI launch support by itself guarantees the other integration. Ask providers to name the specific format and the fields that will return to your LMS.
For an LTI option, evaluate authentication, accounts, grades, transcript mapping, data handling and exit rights as a separate acceptance plan. A buyer should not silently convert a SCORM purchase requirement into a hosted link without revising the approved business case.
Final SCORM buyer sign-off
The release package should contain the specific ZIP or hosted-delivery specification; signed rights for all intended groups; a completed 12-check acceptance record; import and runtime evidence; test learner transcripts; known exceptions; accessibility and language findings; support escalation contacts; retest obligations; and a named business approver. Assign technical sign-off to the LMS owner, instructional sign-off to L&D, commercial sign-off to procurement and any regulated-use decision to the appropriate organizational specialist.
Suggested acceptance language for a purchase order or content schedule: "The vendor will provide the named package and SCORM edition for the customer's agreed LMS acceptance tests. Both parties will document mandatory pass criteria, defects, approved exceptions, remediation ownership and retest requirements before rollout." Treat this as a buyer negotiation example, not a promise of actual TraineryXchange contract terms or legal advice. Have procurement and counsel approve the final wording.
Compare training content with documented acceptance
Share your SCORM edition, target LMS and buyer requirements. Ask for licensed samples and a version-specific test plan before purchasing.
Primary sources and editorial boundaries
The references below are standards organizations or SCORM technical documentation; the testing plan, suggested gates, severity definitions and fictional buyer examples are original editorial tools rather than a conformance certificate or a measured industry benchmark.
- Rustici Software, The SCORM Content Packaging Specification. Manifest, SCO resources and ZIP package format.
- Rustici Software, SCORM Run-Time Environment: Explanation and Examples. Launch, session calls, bookmarking and completion.
- Rustici Software, SCORM Run-Time Reference Chart for SCORM 1.2 and SCORM 2004. Tracking fields, status and data types.
- Rustici Software, Comparing SCORM 1.2 and SCORM 2004. SCORM edition behavior.
- Rustici Software, Technical Overview of the SCORM Specification. Packaging, runtime and sequencing.
- World Wide Web Consortium (2024), Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation. Web accessibility requirements and testable success criteria.
- 1EdTech Consortium, Learning Tools Interoperability (LTI). Remote tool integration specification.
Editorial note: This article provides educational US-market procurement guidance, not legal advice or a claim of regulatory compliance. SCORM support does not guarantee course availability, reporting, accessibility, privacy or distribution rights. Validate the precise licensed package and applicable employer policies. No firsthand customer results, certified test outcome or actual TraineryXchange price is asserted.





