Fix Broken Packages That Will Not Report Completion
Learners finish the course but the LMS still shows incomplete — or the package will not even upload. Diagnose and repair the most common SCORM packaging and completion failures in the browser.
Two tickets land in every LMS admin’s queue eventually. "The package will not upload." And the worse one: "Learners are finishing the course but it still shows incomplete." Both get reported as "the SCORM is broken," and both are usually fixable — but only once you know which failure you are actually looking at.
Upload-time failures
If the package will not even import, it is almost always a packaging problem. The classic is "imsmanifest.xml is missing" even though the file is right there inside the zip — because it was zipped one level too deep and sits in a subfolder instead of at the archive root. Close behind: a malformed manifest, a stripped byte-order mark some parsers expect, or the manifest declaring files that are not actually in the package.
Completion-time failures
A course that imports and plays but never marks complete is a different animal. The learner reaches the end, the LMS still says incomplete, and nobody can see why. Typical causes: the course never reaches the step that commits its final status to the LMS, it sets the wrong lesson status, or — in certain hosting setups — it cannot find the LMS API object to report back to at all.
These are not always one-click fixes, because the right repair depends on why the course is not reporting. The first job is diagnosis: confirm whether the package is structurally sound and whether the completion call is even being made, so you stop guessing.
How ScormEdit handles it
- The free validator checks manifest location and validity, flags declared-but-missing files, and verifies the launch entry point.
- For the classic packaging errors, one-click fixes move the manifest to the root and repackage correctly.
- Preview the package in the built-in player with a live SCORM call log, so you can see whether the course is actually sending completion and where it stops.
- Confirm the package is LMS-ready before you re-upload, instead of round-tripping through the LMS to test each attempt.
Always confirm in a real LMS
Even structural fixes should be confirmed where it counts: upload the repaired package to a test LMS or SCORM Cloud and verify it both imports and marks complete on a full run-through. ScormEdit gets you to a clean package fast; the final sign-off is a real completion in a real LMS.
Most "broken SCORM" tickets are a manifest in the wrong place or a completion call that never fires — both are findable in minutes once you can actually see what the package is doing.