Adding a Package

A package is uploaded content. The platform reads its manifest and registers what it finds.

Where to find it

Architect Panel → eLearning:

Courses & Assignments — the course console — courses, units, assignments
Learner Records — a learner’s registration against a package
Course Attempts — each attempt at a package
Course Sessions — individual launches
Learning Objectives — objective-level results

What is read from the package

The standard and version it declares.
The launch point — the file that starts it.
Its identifier, and for xAPI and cmi5 the activity identifier.
Mastery score, scaled passing score and completion threshold where declared.
Maximum time allowed and the move-on rule.
The structure — the parts inside it.

Those values come from the content, not from you. If the pass mark is wrong, it is wrong in the package.

Check the pass mark before assigning

The single most valuable check. A package with no mastery score, or one set to zero, passes everybody — and you will not find out from the completion report, because everybody completed.

Test it as a learner

Properly, on a real device:

Launch it and confirm it starts.
Get part way and leave. Come back and confirm it resumed.
Complete it correctly and confirm the pass is recorded.
Complete it incorrectly and confirm the failure is recorded.

The third and fourth are where problems appear. A package that records completion but never records a score is common, and it means your pass rate is meaningless.

Test resuming specifically

Learners do not finish in one sitting. A package that does not save its position produces learners who restart repeatedly and eventually stop trying.

Check it on a phone

Much e-learning content is built and tested on desktops and used on phones. Confirm it is usable on a small screen before assigning it to a workforce.

Keep the source

The original package file, from the supplier, somewhere you can find it. You will need it to re-upload, to test an upgrade, or to prove what was delivered.

Record what you tested

Which package, which version, what you checked and when. For compliance training this is part of the evidence that the training was fit for purpose.

Worked example

An organisation tests every package by completing it correctly and incorrectly on a phone, with a deliberate mid-course exit to confirm it resumes. One supplier’s package recorded completion but no score; it was returned rather than assigned to eight hundred people.

Recommendations

Check the pass mark before assigning anything.
Test a fail, not only a pass.
Test resuming and test on a phone.
Keep the source file and a note of what you tested.