Skip to content
Alder

How to see which settings a published SCORM package was built with

Updated 26 October 2026

Quick answer

The publish settings are written into the published files, so you can read them back without the project file. The quickest way: drop the zip into Alder (free, nothing is uploaded), open “Course details” and click “See all publish settings”.

  • Storyline, Rise or Captivate: Alder lists the pass mark, the status it reports, what counts as complete and resume, in the tool's own words. How to see them.
  • Prefer to look yourself: each tool keeps them in one file. Which file, and what to search for.
  • Any other tool: you still get the course title and the SCORM version from the manifest.

Each value comes with the file Alder read it from, so you can check it.

This comes up when you inherit a course, get a zip from a vendor, or can't find the project file, and the LMS records something you didn't expect. Before you change anything, find out what the package was actually published with.

See the settings in Alder (free)

  1. Drop the zip

    Open Alder and drop the published zip, exactly as you would upload it to the LMS. Alder reads it in your browser.

  2. Open “Course details”

    Under the course name, “Course details” shows the authoring tool and its version, and a “Published with:” line with the main settings.

    Published with: Passing Score 80%, Report status to LMS as Passed/Failed, On restart Always resume. Below it, a See all publish settings link.
    The summary line, on Alder's sample course.

  3. Click “See all publish settings”

    This opens “Publish settings we found”: each setting with its value, where to find it in the authoring tool, and “Where Alder read this” (the file; hover over it for the detail). A setting that isn't in the package says “Not found in this package” instead of a guess.

    The Passing Score row: 80%, Where Alder read this: course/course.json, with a Change… button and the label Checked by Alder, not yet confirmed in an LMS.
    One row of the card. On a Storyline course the file is html5/data/js/data.js; the sample course keeps its settings in its own file.

What Alder reads for each tool

  • Storyline 360: the Tracking Options that are ticked (“When the learner has viewed” with its slide count, “When the learner completes a quiz”, “Using triggers”), the Passing Score, “Report status to LMS as”, “On restart”, what happens when the learner exits, and “Report to an LMS” (the standard).
  • Rise 360: the Tracking choice (course completion, quiz result or a Storyline block), the course completion percentage, the quiz's passing score when the course is tracked by it, “Report completion status as”, and whether the Exit Course Link is on.
  • Captivate (best effort): the Success/Completion Criteria, slide views, the passing score, the Status Representation and the exit behaviour.
  • Every package: the course title the LMS will show and the standard (SCORM 1.2, SCORM 2004, xAPI or cmi5), from the manifest.

Some settings only exist for some exports, and the card says so rather than inventing a value: Storyline offers “Report status to LMS as” only for SCORM and AICC, and a Rise xAPI export has no reporting setting at all.

Look in the files yourself

Unzip the package and open the file in a plain text editor. The settings sit in long lines of data, so use the editor's search.

Where each tool keeps its publish settingsStoryline keeps the Passing Score, Report status to LMS as, the tracking options and On restart in html5/data/js/data.js, and what happens on exit in lms/scormdriver.js. Rise keeps the course completion percentage, Report completion status as and the tracking choice in scormcontent/index.html. Captivate keeps its reporting criteria, status and passing score in assets/js/project.js, or assets/js/CPM.js in older versions. Every SCORM zip has imsmanifest.xml, with the course title, the SCORM version and any LMS pass mark.STORYLINE 360html5/data/js/data.jsPassing Score, Report status to LMS as,tracking options, On restartlms/scormdriver.jswhat happens when the learner exitsRISE 360scormcontent/index.htmlcompletion percentage, tracking,Report completion status asCAPTIVATEassets/js/project.js(assets/js/CPM.js in older versions)criteria, status, pass markEVERY SCORM ZIPimsmanifest.xmlcourse title, SCORM version,the LMS pass mark, if there is one
The file to open for each tool. Paths are from the top of the zip.

Storyline 360: html5/data/js/data.js

  • Search for "scorings". Each entry has a type: view is “When the learner has viewed” (the slide count is viewThreshold), quiz is “When the learner completes a quiz”, and action is “Using triggers”. Several entries mean several options are ticked.
  • passStatus and failStatus are “Report status to LMS as”: "pass" and "fail" mean Passed/Failed, "complete" and "incomplete" mean Completed/Incomplete, and so on.
  • The Passing Score is passPercent in the quizzes list. Careful: a slides-viewed entry also carries a passPercent, which the player ignores.
  • “On restart” is the resume part: "prompt":true is Prompt to resume, "prompt":false is Always resume, and no resume part at all is Never resume.
  • What happens on exit is EXIT_BEHAVIOR in lms/scormdriver.js.

Rise 360: scormcontent/index.html

  • var completionPercentage is the course completion percentage.
  • var reporting is “Report completion status as”, written like 'passed-incomplete'.
  • var quizId or var storylineId set to something other than null means the course is tracked by that quiz or Storyline block; then the percentage doesn't count.

In a Rise xAPI export the same file is at the top of the zip, without the reporting line.

Captivate: assets/js/project.js

Older Captivate versions use assets/js/CPM.js. The reporting settings are in quizReportingData, but as number codes that only the player's own code explains, so this one is much easier to read in Alder.

Any SCORM package: imsmanifest.xml

The manifest (the file that tells the LMS how to launch the course) holds the title the LMS shows, the SCORM version, and sometimes a pass mark of its own: in SCORM 1.2, <adlcp:masteryscore>. If that number differs from the quiz's Passing Score, see mastery score vs passing score.

If a setting is wrong

The safe fix is to change it in the authoring tool and publish again. If you only have the zip, Alder's card has a “Change…” button on the rows it can change (the Storyline Passing Score, “Report status to LMS as”, “When the learner has viewed” and “On restart”; the Rise completion percentage and “Report completion status as”; and the course title). Changing and checking it is free: Alder re-runs its checks on the changed course before you confirm. Downloading the changed zip needs Pro. Rows Alder doesn't change say why, and say to change them in the tool.

Not sure which value you want? Start with which “Report status to LMS as” option to pick, then test the course without an LMS to see what an LMS would record with the settings you have.

Why the settings are in the zip at all

A published course runs without its project file, but its player still needs the settings: which result to send, when to call the course complete, whether to offer to resume. So each tool writes them into the course's own files, which is why they can be read back. They are only what the course sends. What your LMS does with it can still differ, for example when it has its own pass mark.