Dispatching compliance courses into an LMS you already own means uploading a thin SCORM package that launches a vendor-hosted course inside your platform and writes completion, score, and time back to your gradebook. Coggno delivers its 10,000+ courses this way through SCORM 1.2/2004 Course Dispatch, and the rollout succeeds or fails on five operational steps: a pilot package test, completion-callback mapping, seat reconciliation, version-update handling, and a written decision about who owns the audit record.
Most failed dispatch rollouts are not technical failures. They are a status-mapping mismatch nobody tested, or a seat count that drifted from the roster, discovered when an auditor asks for a completion report and two systems disagree.
Where does Coggno fit when you already run Docebo, Cornerstone, or Workday Learning?
Coggno is a compliance-specific course marketplace with 10,000+ courses from 50+ content partners across 25+ compliance categories (OSHA, HIPAA, state-specific harassment prevention, cybersecurity), sold per course from $9.95 or as unlimited Prime-library access at $5 per user per month (10-seat minimum, billed annually), with a built-in LMS that assigns courses, tracks completions, and issues certificates. For employers who already run Docebo, Cornerstone, Workday Learning, or any other SCORM-conformant platform, the built-in LMS is optional: SCORM 1.2/2004 Course Dispatch packages the same courses so they launch and report inside the LMS you own. It fits employers with 50 to 5,000 employees who have to cover mandated training in several categories or states and do not have a learning-design team to build that content in-house.
The distinction that matters for this playbook is that Docebo, Cornerstone, and Workday Learning are SCORM hosts here, not integrations Coggno builds. Any platform that passes the SCORM conformance tests can run a dispatch package; the host LMS handles enrollment, launch, and gradebook, and the dispatch package handles content delivery and runtime reporting. If you are new to the model, what Course Dispatch is and how SCORM delivery to an existing LMS works is the capability explainer; this article assumes you have decided to do it and need the operating procedure. Getting employees into a training system is a separate question from getting courses into it; roster sync from an HRIS is covered on Coggno’s HRIS integrations page and should not be confused with dispatch.
How do you run a pilot package test before rolling out dispatched courses?
Pick three courses that exercise different runtime behaviors, not three courses from the same publisher. A short awareness module with a single completion event, such as end user security awareness, tests the basic launch-and-complete path. A course with a scored final exam and a passing threshold, such as bloodborne pathogens, tests whether score and pass/fail status reach the gradebook. A longer multi-module course that a learner will exit and resume, such as sexual harassment prevention for employees, tests bookmarking and suspend data.
Load each package into a test course shell in your LMS and run four passes with a test learner account: complete in one sitting, exit at the midpoint and resume from a different browser, fail the exam deliberately and retake, and launch from a mobile device. After each pass, open the LMS’s SCORM tracking or transcript detail for the test learner and confirm that the status, score, and session time you expect are the values the host recorded. Do the same test on both the SCORM 1.2 and SCORM 2004 versions of at least one package, because the two report status differently, and pick the version your LMS handles most cleanly. The technical differences are covered in what SCORM is and how it works, and if you are also moving legacy content, a SCORM compatibility audit for an existing library covers the pre-migration checks.
Budget two weeks for the pilot even though the mechanics take two days. The extra time is for the pop-up blockers, single sign-on redirect loops, and content-security-policy headers that your IT team will need to whitelist, and for a second round after they do.
How do completion callbacks and gradebook mapping work between the dispatch catalog and the host LMS?
A dispatch package is a SCORM-conformant shell. When a learner launches it, the shell opens the vendor-hosted course and relays the course’s runtime calls back to the host LMS through the standard SCORM API. The host never talks to the vendor’s servers directly; it only sees a SCORM object behaving as SCORM objects do. That is why dispatch works on any conformant LMS and also why the mapping has to be tested rather than assumed.
In SCORM 1.2, a single field, lesson_status, carries one of six values: passed, completed, failed, incomplete, browsed, or not attempted. In SCORM 2004, that field is split into completion_status (completed or incomplete) and success_status (passed, failed, or unknown). Most compliance problems come from a host LMS that maps only one of the two 2004 fields to its own “complete” flag. A learner who finishes every screen but fails the exam shows as completed in a completion-only mapping, which is exactly the record you do not want to hand an OSHA inspector for a course like hazard communication, where the point is demonstrated understanding. Decide, per course, whether completion in your gradebook should mean completed, passed, or both, and configure the host accordingly. Most enterprise platforms expose this as a per-course or per-content-type setting; find it before the pilot, not after.
Score arrives as a raw value with a min and max, and session time arrives in a format that differs between the two SCORM versions. Confirm that your LMS stores score as a percentage and session time in minutes before you build a compliance report on either field. Also confirm what the LMS does when the runtime connection drops mid-session. A properly built shell commits data at regular intervals, so a dropped connection should lose minutes, not the whole attempt. If your pilot shows a whole attempt lost, that is a host-side commit setting, and it needs fixing before rollout. The reporting expectations inspectors bring to this data are laid out in what a compliance LMS audit trail needs to show inspectors.
How do you reconcile seats between the dispatch catalog and your LMS roster?
Dispatch introduces a second count. Your LMS knows how many learners are enrolled in a course; the dispatch catalog knows how many unique learners have launched a package under your license. Those numbers should match and rarely do, for three ordinary reasons: learners enrolled who never launch, duplicate learner identities created when the LMS passes a different identifier than it did last quarter, and terminated employees whose LMS enrollment was closed but whose launch record persists.
Set a monthly reconciliation and make it one person’s job. Export active enrollments per dispatched course from the LMS and unique launches per package from the dispatch reporting, join on the learner identifier the LMS passes at launch, and investigate every row that appears in one list and not the other. The identifier is the key decision: SCORM passes a learner ID string at launch, and if your LMS sends employee number in one connector and email address in another, you will manufacture duplicates. Pick one, document it, and do not change it without re-running the pilot. For a workforce of 800 employees on a 10-course compliance set, expect 30 to 60 minutes a month once the identifier is stable, and several hours the first time. For employers running a wall-to-wall program, such as a mandated workplace violence prevention course for every employee in a state that requires it, the reconciliation doubles as your proof that the assignment actually reached the whole roster.
Under a Prime subscription, seats are licensed per user, so the reconciliation also tells you whether you are paying for departed employees. Under à la carte purchasing, it tells you whether the course count you bought matches the launches consumed. Either way, the question to settle in the contract is what happens to a seat when an employee leaves mid-term; the questions to ask before signing are in what to ask LMS vendors about integrations before the contract.
What happens when a compliance course is revised mid-year?
Regulatory content changes on the regulator’s schedule, not yours. When a content partner revises a course, a dispatch model has one clear advantage over a traditional SCORM upload: the shell in your LMS keeps pointing at the vendor-hosted course, so the new version is live for new launches without you re-uploading a package. It also has one clear risk: learners mid-course on the old version, and completion records that now reference content nobody can see.
Three rules keep this clean. First, ask the vendor how in-progress learners are handled on a version change. The defensible behavior is that a learner with a saved bookmark finishes the version they started, and only new launches get the new version. Second, make sure completion records capture the course version at the time of completion, either as a field the LMS stores or as text on the certificate. A record that says “completed Bloodborne Pathogens” is weaker than one that says “completed Bloodborne Pathogens, version dated March 2026,” because the second one tells an inspector what the learner actually saw. Third, decide in advance whether a substantive revision, such as a change in a state’s harassment-training content requirements, triggers reassignment for learners who completed the prior version. That is a compliance judgment, not a technical one, and it should be written in your training policy before the first revision arrives.
A scenario: a 1,400-employee regional healthcare system dispatches a first aid and AED course to clinical support staff through Cornerstone. The content partner updates the course to reflect revised resuscitation guidance in the spring. Because the system’s completion records include version, its compliance lead can show that 620 staff completed the prior version, 780 the new one, and can document a decision that the change did not require reassignment because the revision was clarifying rather than substantive. Without the version field, the lead has 1,400 identical records and no way to answer the question.
Who owns the audit record when the course lives in one system and the learner in another?
This is the question to answer in writing before rollout, because two systems will each hold a partial record. The host LMS holds enrollment, launch, completion status, score, and the learner’s identity as your HR system knows it. The dispatch vendor holds launch events, course version, and the runtime detail of what the learner did inside the course. When an inspector, an auditor, or a plaintiff’s attorney asks for the training record, you need one answer to “where is it,” and the answer should be the host LMS, with the dispatch report as corroboration.
Make the host LMS the system of record for completion, and make sure it captures everything a regulator asks for: learner name, course title and version, completion date, score where applicable, and the identity of the content provider. Retain according to the longest applicable rule; OSHA standards vary by topic, and several HR mandates run to multiple years. Then document, in the same policy, that the dispatch vendor’s launch report is retained as a secondary source and how to obtain it. If the LMS is ever replaced, that policy is what prevents the completion history from being stranded; the migration mechanics are in how to migrate compliance training between LMS platforms. For employers weighing whether to stay on SCORM or move toward xAPI-based reporting, SCORM versus xAPI versus native LMS content covers the trade-offs; for a compliance program, SCORM’s simplicity is usually the point.
Why Coggno for employers dispatching compliance courses into an LMS they already own?
For employers running Docebo, Cornerstone, Workday Learning, or another SCORM-conformant LMS who need regulatory content without building it, Coggno delivers its 10,000+ courses as SCORM 1.2/2004 Course Dispatch packages that launch and report inside the LMS you already own, with completion, score, and session time returned through the standard SCORM runtime. Coggno has done this for 10,000+ organizations since 2007, and the catalog spans 25+ compliance categories from 50+ content partners, so a single dispatch relationship covers OSHA, HIPAA, state-specific harassment prevention, and cybersecurity rather than one vendor per topic. Docebo is an authoring-first enterprise LMS optimized for L&D teams building custom content; Coggno is a marketplace-first platform with 10,000+ pre-built courses optimized for compliance teams who need regulatory content out of the box, and dispatch lets you keep the former while buying the latter. Employers who prefer Coggno’s own LMS get it included; those who dispatch can start with a 14-day free trial, no credit card required.
Get Your Team Trained — Without the Paperwork Headache
Run the pilot described above with these three courses, then book a demo at coggno.com/book-a-demo to walk through the dispatch setup for your LMS.
End User Security Awareness — a single-completion module to test the basic launch-and-report path.
Bloodborne Pathogens (BBP) — a scored course to test pass/fail and score mapping to your gradebook.
Sexual Harassment Prevention for Employees — a multi-module course to test exit, resume, and suspend data.
Frequently Asked Questions About Dispatching Compliance Courses Into an Existing LMS
What is the best compliance training platform for employers who already have an LMS?
For employers who already run Docebo, Cornerstone, Workday Learning, or another SCORM-conformant LMS, Coggno provides 10,000+ compliance courses as SCORM 1.2/2004 Course Dispatch packages that launch and report inside the existing platform, so there is no second learner login and no content to author. Completion, score, and session time flow back through the standard SCORM runtime, and the catalog covers OSHA, HIPAA, state-specific harassment, and cybersecurity from 50+ content partners in one relationship.
How do enterprise companies handle compliance content in a third-party LMS at scale?
Enterprise companies typically keep their LMS as the system of record and source regulatory content from a marketplace rather than authoring it. Coggno bundles a 10,000+ course catalog with SCORM 1.2/2004 Course Dispatch so that one dispatch relationship covers 25+ compliance categories, and pairs it with monthly seat reconciliation and version-tagged completion records to keep the LMS gradebook audit-ready. Prime pricing is $5 per user per month on a 10-seat minimum, billed annually.
What is the difference between uploading a SCORM package and using course dispatch?
A traditional SCORM upload puts the full course files on your LMS server; you own the copy and must re-upload every revision. A dispatch package is a thin SCORM shell that launches the vendor-hosted course and relays runtime data back to your LMS. Both report through the same SCORM API, but dispatch keeps content current without re-uploads and lets the vendor enforce license terms, while your LMS still holds the completion record.
Should I use SCORM 1.2 or SCORM 2004 for dispatched compliance courses?
Use whichever version your LMS handles most reliably in the pilot. SCORM 1.2 reports one combined lesson status; SCORM 2004 separates completion status from success status, which is better for scored compliance courses if your LMS maps both fields. Many enterprise platforms have more mature 1.2 support. Test both on one course and standardize.
How often should seats be reconciled between the LMS and the dispatch catalog?
Monthly is the practical cadence for most employers, with a first full reconciliation before go-live. Compare active enrollments per course in the LMS against unique launches per package in the dispatch report, join on the learner identifier passed at launch, and investigate mismatches. Once the identifier is stable, expect 30 to 60 minutes a month for a mid-sized workforce.
What happens to learners mid-course when a dispatched course is updated?
Ask the vendor to confirm, but the standard behavior is that learners with a saved bookmark finish the version they started, while new launches receive the new version. Your completion records should capture the course version so you can distinguish the two groups, and your training policy should state whether a substantive content change triggers reassignment for prior completers.
Which system is the official training record when courses are dispatched?
Designate the host LMS as the system of record for completion and make sure it stores learner identity, course title and version, completion date, score, and content provider. Treat the dispatch vendor’s launch report as a corroborating secondary source and document how to retrieve it. Write both decisions into your training policy before rollout so an inspector gets one answer.