This is a subpage of SCORM

Dispatch Package

With dispatch packages, EVERFI hosts course content on our platform and your LMS can seamlessly render that content when learners launch the course from your LMS. Since courseware often has external or internal tracking and completion requirements, EVERFI hosts the course content to ensure continuity and compliance. Moreover, EVERFI continually updates content to comply with the latest regulatory landscape — no need for you to worry about getting the latest version of each course, for each state. Further, it ensures compliance data integrity by creating a data record as a backup to the partner LMS.

What is a SCORM Dispatch Package?

A SCORM Dispatch Package is a package shell that references EVERFI content via a URL, but does not contain the actual media files. The format is a ZIP file with folders and files within that adhere to the standard SCORM definition. Most LMS allow you to import a SCORM dispatch package into your LMS and administer it like a normal course. The file size of a SCORM dispatch package is around 80 KB when compressed; for comparison, a medium resolution image file is around the same size. When extracted, the package is around 400 KB.

Course Objectives / Scoring

Some LMS products may require course tracking configurations for score based course objectives, for example passing/failing grades. By default, the partner LMS may require a minimum score to pass a course. EVERFI courses, given their compliance implications, do not track scores and are designed to force 100% accurate completion.

SCORM Implementation Overview

Below is an overview of how the process works.

SCORM Packaging

  1. EVERFI generates one or more SCORM dispatch packages personalized for your own organization. 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. New packages must be created to redeploy the same course, location, and role)
    • 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. EVERFI will send you the packages

Importing SCORM Dispatch Package into LMS

  1. You import the SCORM package into your LMS/HRIS

Course Configuration in LMS

  1. You configure the course in your LMS as needed, including making assignments to users, to prepare for course launch.

Learner Experience

  1. Learners launch the course via your LMS. The launch will be on your URL
  2. The course content window receives 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


  1. If a course needs to be reassigned, a new SCORM dispatch package will need to be provided to you by EVERFI
  2. Each SCORM dispatch package contains a package ID, which is unique to the package and is used for linking the assignment from your LMS to the EVER LMS

User Management

Since your LMS is managing administrative matters such as users and assignments, EVERFI does not take on this role. You do not need to upload user/learners into EVERFI’s Foundry and you don’t need to create single sign-on. When a learner views an EVERFI course, per the SCORM protocol, the LMS will automatically provide to Foundry the student ID of the LMS 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 student ID, first name, last name and organization location’s address. The LMS student ID is the primary identifier of your LMS user. It could be an email address, a user-name, or an ID, depending on your LMS and configuration. Technically, in the SCORM data model, it’s the value of cmi.core.student_id in the LMS. 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 student 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 student ID and let them resume the learning activity where they left off.