Skip to content
English
Contact Support
  • There are no suggestions because the search field is empty.

SCORM Packages

SCORM Packaging

1. EVERFI generates one or more SCORM dispatch packages personalized for your own organization and will send them to you. A separate package will be made for each distinct combination of:

  • Organization ID (ID of the org)

  • Content ID (ID of the course)

  • Package ID (ID of the package, used for mapping users to content)

  • Training Cycle Date Refresh (see the Re-Assigning Content Section)

  • Geolocation (Location of learner taking the course)

  • SCORM version: either 1.2 or 2004 3rd edition

  • Role (Role of learner taking the course, ex: Supervisor or Non-Supervisor)

2. You import the SCORM package into LMS/HRIS
3. See the section below on guidance to test your content packages

Course Configuration in LMS

  1. All course configurations are done in Foundry per course. This includes adding your organization's policies, resources, and other configuration options the course allows.
  2. Creating assignments and launching courses is all done in your LMS/HRIS which is where your learners will go to access their trainings.
  3. You do not need to upload any users into Foundry.
  4. Progress and completion data should primarily be be managed from your LMS/HRIS, but the data is also recorded in Foundry as a back-up.

User Management

Since your LMS/HRIS is managing administrative matters such as users and assignments, EVERFI does not take on this role. You do not need to upload users or learners into Foundry and you don’t need to create single sign-on. When a learner views an EVERFI course, per the SCORM protocol, the LMS/HRIS will automatically provide to Foundry the  ID of the LMS/HRIS user. Foundry will create a “lightweight” user record in Foundry to represent this user and keep track of progress and related data.

The user data stored in Foundry is LMS/HRIS employee ID, first name, last name, and organization’s address. The employee ID is the primary identifier of your LMS/HRIS user. It could be an email address, a username, or an ID, depending on your LMS/HRIS and configuration. Technically, in the SCORM data model, it’s the value of cmi.core._id in the LMS/HRIS. In Foundry, this value gets saved into the user’s SSO ID field. The learner’s email address is not saved in Foundry, unless the ID is an actual email address.

If the same user returns multiple times, then Foundry will be able to match the user based on the LMS/HRIS employee ID and let them resume the learning activity where they left off.

Learner Experience

​​​1. Learners will go to your LMS/HRIS and to launch and access their EVERFI assignments. The launch will be on your URL.
2. The course content window receives the course pages, images etc. from the EVERFI content server
3. Course progress events first are logged to EVERFI  (complete, incomplete, progress, exit)
4. Once the EVERFI content server receives course progress events, the customer-hosted LMS/HRIS is sent the event using the SCORM API. This way, the external LMS/HRIS will have the same course progress status as EVERFI LMS.
5. See the section below for details on the learner experience for re-assigned content

Re-Assigning Content

Learners using SCORM dispatch can only have 1 progress record per course per training cycle. If they try to take the same course again within the same cycle, the learner will pick up from where they left off (or it will be shown as complete if they finished it) and not from the beginning. This will occur regardless of when the assignment was made in your LMS/HRIS.

When the training cycle changes, the previous year's progress record is still stored, but moved to a historical record. The next time a learner launches the course in the new training cycle, they will begin from the start.

There are 3 options of SCORM training cycles that you can set per course package that fit the needs of your training plans. Below are each of the options and the sample training plan scenarios that work best.
 

1. Archive annually on a specific calendar date

Best used for courses that need to be taken annually by learners, whether for compliance purposes or prevention focused refreshers. This allows administrators to have a consistent training timeline. For example, if your organization assigns a course every year in October, the SCORM training cycle should refresh annually on September 1.

2. Archive [X] days after a course is completed or [X] days after a course is launched and incomplete

Whichever date comes first is when the learning record will be archived. Best used for training plans that require learners complete courses more than once. This option offers more flexibility with accommodating training plans within a year.

3. Archive 1 year or 2 years after the learner first launches the course

Best used for new hires or incoming students that come in on a rolling basis and need to take introductory courses as part of onboarding or orientation. This allows learners to have up to 1 year to complete the course regardless of when they started or matriculated. This is recommended for courses that learners only need to take once.

These training cycles are created based on best practice and usage data from EVERFI customers. If you have learners who need to take a course again within the same training cycle, please contact EVERFI support.

Re-Assigning Examples

To better explain how this retraining cycle works, below are some common scenarios and what the learner experiences.

Method 1 - Archive annually on a specific calendar date

Assignment #1 begins on July 1, 2023. Jump forward a year and Assignment #2 for the same course begins on June 15, 2024.

Learner Andy launches, begins, and completes Assignment #1 on July 30, 2023 while learner April launches and begins Assignment #1 on September 15, 2023, but does not complete it.

When Andy and April receive Assignment #2, they will both be able to launch and begin Assignment #2 from the beginning. This is because all training progress is archived annually on June 1.
 

Method 2 - Archive [X] days after a course is completed or [X] days after a course is launched and incomplete

An assignment is made for a course to begin on March 1, 2024. The retraining is set to Archive 30 days after it is completed and 180 days after it is launched and incomplete.

Donna begins the assignment on March 15, 2024 and completes it on March 20, 2024. Since she completed the course, Donna's activity record will be archived 30 days later on April 20, 2024 allowing her to start the course again from the beginning if assigned again.

Tom also begins the assignment on March 15, 2024, but does not finish the course. In this case, his activity record will archive 180 days later on September 15, 2024. This means Tom can log into his company's LMS to continue where he left off in that course until September 14, 2024. If he attempts to open the course on September 15, 2024 or later, Tom will need to start from the beginning.
 

Method 3 - Archive 1 year or 2 years after the learner first launches the course

Assignment #1 for Preventing Harassment & Discrimination in the Workplace  is sent to all new employees in the month when they are hired. An administrator creates Assignment #2 for this same course to be completed annually.

New hire Leslie begin Assignment #1 on October 1, 2023 when she launches, begins, and completes this assignment on that day. To complete her annual training, Leslie will have access to Assignment #2 a year after she initially started Assignment #1, which is October 1, 2024.

New hire Ron starts the same day, but does not launch and begin the assignment until November 15, 2023 and does not complete it. For him, he will not be able to start Assignment #2 from the beginning until November 15, 2024. If Ron logs in before then, he will be taken to the Assignment #1 progress point where he left off.


 

Course Package QA Testing

Before rolling out trainings to a large population, we recommend testing a course package through your LMS/HRIS to ensure it launches smoothly and all data is appearing as expected. Below are instructions and things to note to properly test the course packages:

  1. Course Launches

    • When you launch the course, a pop-up should appear with the training in it

    • You may have to allow pop-ups, so simply click Allow if this prompt comes up

  2. Fits Window Size

    • The window should be adjustable allow you to see the full course

  3. Profiles Services

    • If the course is a profile services course, there will be different content based on location and role (supervisor/non-supervisor)

  4. Customizations display

    • If the course has customizations, such as a policy or resources page, they should display in the course

    • You will be notified if this is something you need to check for while taking the course

  5. Policy acknowledgment functions as expected

    • Learners cannot progress without signing the policy

  6. Content displays properly

    • Content is not outside the readable area

    • Content doesn’t overlap with itself of images

  7. Activities work as expected

    • Interactive pages, such as pages with selecting paths, flip cards, should function properly

  8. Completion passing to Foundry

    • This can be checked by the person who sent you the package once you have exited the course

  9. Progress saved when you exit and re-enter

    • Once complete, go back into the course and ensure you land on the completion page, and that you’re also able to go back and review previous pages

  10. Completion data saves in your LMS (most important)

 

If you do find an issue, submit a case to support and include this template:

  • A short sentence summary of the issue

  • Environment Details

    • Browser version (such as Chrome 80)

    • Operating system (such as MacOS Mojave)

  • Description

    • Please write a short paragraph describing what you observed. Also indicate if it was consistent (can make it happen 100% of the time) or intermittent (occurred a few times, but not always).

  • Reproduction steps

    • As a learner taking course X via SCORM dispatch on cloud.scorm 

    • Start at _________ (page title) e.g. _________ (paste URL)

    • Do X

    • Do Y

    • Do Z

  • Observed results: This part worked as expected, but this part seems wrong. 

  • Expected results: This is what I think should happen.