Hosted sessions vs SCORM: how to deliver your training

When people ask whether they should export SCORM or run a hosted session, they are usually asking the wrong question. Both come out of the same brief on Intle — one prompt, the same generated content — and the choice between them is not really about quality. It is about where the learning needs to live, who needs the completion records, and how fast you need to get it in front of people. Here is how I make that call in practice, and the technical detail underneath each option that tends to decide it.

The same content, two front doors

SCORM export produces a downloadable zip for testing in a learning management system. What the LMS launches, records and displays varies by platform version and configuration. Packages target SCORM 2004 4th Edition and SCORM 1.2, with dated local resume evidence published separately from named-platform testing. Use the LMS delivery guide, then verify import, completion, score and resume in your exact environment.

A hosted session is a link. Intle publishes the same generated content at /s/ followed by a short, random slug, and anyone with that link opens it in a browser — no account, no install, no LMS in sight. You can collect names (and, on paid plans, email), cap the number of participants, and run it either self-paced or facilitator-led, where you drive everyone through the sections together and watch responses land live. It is the quickest way to get something in front of a room or a cohort, which is why workshop and seminar formats lean on it. You can spin one up straight from the AI workshop generator.

Reach for SCORM when…

• Your organisation already runs an LMS and expects completion to land in the gradebook.
• You need a durable, auditable training record — compliance, CPD, induction, anything a regulator or line manager might ask to see later.
• Learners should resume where they left off across sessions and devices.
• The content is a solo, self-paced module rather than a shared, live event.
• You want the material to persist indefinitely inside your systems rather than expire on a timer.

Reach for a hosted session when…

• You don't run an LMS, or getting a package approved into it would take weeks you don't have.
• You're running a live workshop, seminar, icebreaker or all-hands and want participant responses in the room.
• You need it live today, shared with nothing more than a link or a join code.
• Participants are external or one-off — contractors, students, event attendees — and shouldn't need to create accounts.
• You want live polls, word clouds and paired discussion, not a static record filed away in a gradebook.

What 'hosted' really means for privacy

This is the part people get wrong, so it is worth being precise. A hosted session is unlisted, not public. The slug is eight characters drawn at random from an unambiguous alphabet — roughly 1.4 trillion combinations — so links are never sequential and cannot be guessed by counting up from someone else's. Every session page also carries a noindex, nofollow directive, which means it never surfaces in a search engine even if a link leaks. In other words, a session is reachable by people you send the link to and effectively invisible to everyone else.

• Unguessable slugs — random and collision-checked, not incremental database IDs.
• Search-invisible — noindex / nofollow on every session page.
• Optional password on paid plans, stored only as a hash and never sent to the browser.
• Participant caps plus pause and end controls, so you can close a session the moment you need to.
• Automatic expiry, after which the link stops accepting responses and shows a friendly 'session ended' page.

Records and tracking: the honest difference

Both modes give you data, but different data for different audiences. SCORM writes completion status and score back into the LMS, which is exactly what an auditor, a regulator or a manager wants: a system-of-record entry against a named learner. A hosted session gives you live and post-session analytics inside Intle instead — response distributions, item-level breakdowns, completion and average score, and an emailed summary when the session ends. That is far richer for a facilitator debrief, but it is not a gradebook entry. If the training has to evidence who completed what for something like mandatory safeguarding or anti-money-laundering record-keeping, the LMS route is the safer default; browse the compliance training examples to see the kind of material that usually belongs there.

A worked example

Take the academic integrity seminar example. It is a hosted-first interactive session for first-year undergraduates — a results-live poll, a word cloud, a timed think-pair-share, a branching AI-rewrite decision with consequence panels — the kind of judgement-first material that only works when a room responds together before anyone names the rule. But the same generated content also exports as SCORM, so the department can drop a self-paced version into the VLE for anyone who missed the live seminar and still needs it on their record. One brief, both front doors, no re-authoring.

You usually don't have to choose

That is the honest answer to 'SCORM or hosted': the same generated content can support both delivery routes. Run the live version to teach, or export the SCORM version for LMS testing and records. Start from a compliance or course brief, generate once, and decide how it ships when you know who needs to be in the room and who needs to be in the gradebook. The delivery decision is reversible; the content work only happens once.