Courses Arrive on TEX: SCORM Delivery, Bundles, and Per-School Allocation

Until now, a content provider working with schools on TEX faced an awkward split: relationships and opportunities lived on TEX, but the actual courses lived on a separate LMS — another platform to pay for, another login for students, another progress report nobody reconciles.

That split is gone. TEX now delivers courses natively: SCORM import and playback, course bundles, and — the piece providers have been asking for — per-school content allocation.

Upload once, deliver everywhere

Content providers upload standard SCORM 2004 packages — the format every serious authoring tool exports — and TEX takes it from there:

• Courses play in the browser, inside TEX, with no external hosting
• Progress, scores, and time spent are tracked automatically
• Students can leave and resume exactly where they stopped
• Certificates are issued natively on completion

For students, that means one login and one place where their whole career-readiness journey lives. For providers, it means retiring the separate LMS bill.

SCORM courses play natively inside TEX, with progress and resume tracked automatically.

Bundles: package courses the way you sell them

Providers rarely offer one course at a time — they offer programs. Bundles let you group courses into named packages ("Career Foundations," "Year 12 Employability") and manage them as a unit, straight from the course management screen.

Allocation: the right content for the right school

Here's the part that changes the business model. Previously, every published course from a connected provider was visible to every connected school — all or nothing. Now, providers explicitly allocate courses and bundles to specific schools.

• Running a pilot with two schools? Allocate to those two.
• Offering a premium tier? Allocate the premium bundle to schools that subscribe to it.
• A school's students see only what's been allocated to their school — a curated catalog, not a content dump.

Providers choose exactly which connected schools receive each course or bundle.

The details that matter

Allocation isn't a cosmetic filter — it's enforced end to end. The same permission check gates course discovery, content playback, progress saving, assessments, and certificate issuance. If a course isn't allocated to a school, its students can't reach any part of it.

And when a provider retires a course, student history is preserved: completed work and issued certificates remain on the record even after the course leaves the catalog.

Key takeaways:

• SCORM 2004 courses upload, play, and track natively inside TEX
• Bundles group courses into sellable, manageable packages
• Per-school allocation gives providers precise control over who sees what
• Access rules are enforced everywhere — discovery, playback, assessments, certificates

Ready to deliver your courses where your schools already are? Request a demo and bring one of your SCORM packages — we'll import it live.