← Home

Deliver your courses
without handing over your content

Your client has their own LMS and asks for your SCORM package. Send them a dispatch package instead: a package that does not contain your course, but opens it. Your content stays with you, and their tracking stays with them.

Try for free Watch the demo

The request you know well

“Send us the SCORM file,
we'll load it on our side”

It is a legitimate request: the company has a platform, tracking obligations, and does not want to send its employees elsewhere. Until now, you had only two answers, and neither is a good one.

You deliver the package

What you send is a complete copy of your course.

  • It never comes back. You have no withdrawal, no expiry, no control over its use.
  • It no longer updates. The 2024 version is still running in 2027.
  • It outlives the contract. Nothing technically prevents it from being replayed, or passed on.
  • You no longer see anything: not who is taking it, not what is blocking, not what needs fixing.

You deliver a dispatch package

What you send is an address, wrapped in the SCORM format.

  • The content never leaves your platform.
  • A fix goes live for everyone, immediately.
  • Access stops when the session stops.
  • Your client keeps their tracking: progress, score and success arrive in their LMS.

A SCORM package is a file, and a file can be kept. It is an obvious fact that gets forgotten at delivery time, and rediscovered the day a client does not renew. Dispatch does not change the SCORM standard: it changes what goes inside the package.

The mechanism

Four steps,
and the tracking that comes back

Nothing exotic on the client's side: they import a SCORM package like any other, into the platform they already use.

The journey of a SCORM dispatch package, from your platform to your client's LMS Step 1: from the session page in Geduk, you download a SCORM dispatch package. Step 2: your client imports this package into their own LMS like an ordinary module. Step 3: the learner opens it; they are recognized and signed in automatically, and your course displays on their screen without leaving their employer's platform. Step 4: progress, score, success status and time spent go back to the client's LMS. The content itself stays on your platform. On your side Your Geduk platform 1 You generate the package From the session page, in SCORM 1.2 or 2004, for the whole learning path or for a single module. 🔒 The course stays here. The package holds none of it. the zip At your client's Their LMS, the one they already use 2 They import the package Like any other SCORM module. No integration, no development. They add it to their catalogue, assign it to their employees and track it like the others. they open it The learner An employee of your client 3 They are recognized Their identity comes from their LMS. No account, no password, no second site to visit. Your course displays inside their LMS screen. 4 Tracking goes back to your client's LMS Progress Score Success Completion Time spent Their dashboards and reminders keep working, as with any other module.

Drag the diagram to explore it →

The solid line follows the package, the dotted green line follows the tracking coming back. What never travels is the content itself.

In real conditions

Forty-five seconds,
from generation to tracking

The dispatch package is generated from a Geduk session, imported into SCORM Cloud — the platform the industry uses to put a SCORM package to the test — then opened the way a learner would open it. Nothing is staged: what you see at the end is SCORM Cloud's own report.

No voice-over: everything can be read on screen. The last frame is the client's registration report, with completion, score and time spent received from the dispatch package.

The main objection, settled

“And my reporting —
do I lose it?”

It is the first question from the training manager sitting across from you, and it is what sinks solutions that send employees to an outside platform. The dispatch package writes into your client's LMS exactly what an ordinary module writes there.

ProgressThe percentage of the learning path completed, updated during the training.
ScoreThe result scaled to 100, with its minimum and maximum.
SuccessPassed or failed, according to the pass mark you set on the assessment.
CompletionCompleted or in progress, as soon as the learning path is finished.
Time spentThe length of the working session, in the format the standard expects.
SCORM 1.2 SCORM 2004 One package per learning path Or per module of the path

You keep seeing too. On the Geduk side, you keep the full detail: who opened what, on which date, how many attempts, which answers. Enough to produce a proof file (in French) for your own audit, which a package delivered to a third party no longer allows.

On the user side

Three clicks, once per client

  1. 1

    Open the session and generate the package

    From the session page, choose SCORM 1.2 or 2004 depending on what your client's platform accepts, then generate the dispatch package for the whole learning path, or for just one of its modules if you only want to deliver part of it.

  2. 2

    Send the zip to your client

    They import it into their LMS like any SCORM module, with no integration or development. Nothing distinguishes the operation from an ordinary import, and nothing more is asked of them.

  3. 3

    Check with a test account

    Ask them to assign the module to a single user first, and to open it. You will see the enrolment appear on your side, and they will see the tracking come back on theirs. It is the check that avoids bad surprises on the real launch day.

To decide with your eyes open

When dispatch fits,
and when it does not

The right case

  • You sell your courses to companies that have an LMS
  • Your content is your business asset, not a throwaway deliverable
  • Your courses change: regulations, products, internal procedures
  • You want to know what your learners actually do
  • You bill by usage, by session or by subscription
  • You work with several clients on the same content

The wrong case

  • The client's network blocks outgoing connections, or their platform runs offline
  • The client contractually requires ownership of the delivered file
  • You sell a course once, with no follow-up and no updates
  • You are looking for copy protection: dispatch stops anyone from keeping the file, not from filming the screen

Put it in the contract, do not let them find out. At the end of the session, the package stays with your client but no longer opens anything. That is precisely what you want, and it is exactly what an unhappy client will hold against you if they did not read it before signing. One sentence is enough: access to the content is granted for the duration of the session, and the module uploaded to your platform is only the gateway to it.

FAQ

SCORM dispatch, plainly

It is an ordinary SCORM package, importable into any compatible platform, with one difference: it does not contain the course, it contains the address of your session in Geduk. The industry calls this mechanism a dispatch, or an LMS dispatcher: if you have come across the term, this is exactly it. When a learner opens it, they are connected to your platform and see your course, which has never left your servers.

Yes, and that is the key point. The dispatch package sends back progress, score, success status, completion and time spent, like any SCORM module. Their dashboards and automated reminders keep working: they lose nothing in exchange for what you keep.

No. The dispatch package reads the learner's ID and name from the LMS running it, creates the matching account on your side if it does not exist yet, and enrols them in the session. The learner sees no form, no password and no second platform: they stay within their employer's interface.

The fix is visible immediately at all your clients, including for learners in the middle of the course, because there is only one copy of the content: yours. With a classic package, you would have to send a file to each client and hope they re-import it.

SCORM 1.2 and SCORM 2004. You choose the version when generating the package, depending on what your client's platform accepts. You can generate a package for a whole learning path, or for a single module of that path.

The package stays in your client's LMS, but it no longer opens anything: access depends on the session that stayed with you. That is the very purpose of the mechanism, and it is a clause to write into the contract rather than leave to be discovered. Conversely, a classic package delivered once stays usable forever.

Yes. The course is loaded from your platform when the learner opens it. A client whose network blocks outgoing connections, or whose platform runs offline, will not be able to use dispatch: in that specific case, only a standalone SCORM package will do, and Geduk can export one too.

Yes, as SaaS and as a dedicated instance, with no paid add-on. Generating dispatch packages is governed by a dedicated permission: you decide who in your organization can produce them.

Your content deserves better
than a file sent by email.

Create a free space, upload a course, open a session and generate your first dispatch package.
No installation, no credit card, no commitment.

Try for free Request a demo

Included in every plan · Hosted in France · Real human support