missing-delivery-controlsAn activity does not declare how completion is decided, so different systems apply different defaults.
The same package completes correctly on one LMS and refuses to complete on another, with no change to the content. Commonly it works in the vendor's test system and fails in the customer's.
A deliverable activity in the manifest whose sequencing block has no imsss:deliveryControls element.
deliveryControls carries completionSetByContent and objectiveSetByContent — whether the content reports its own completion and objective, or the LMS infers them. Omitted, the defaults apply, and systems differ in how they read the interaction between the defaults and what the content actually reports. This is a portability risk rather than a definite break, which is exactly what makes it expensive: it surfaces at someone else's deployment.
Declare it explicitly on each deliverable activity. If your course sets its own completion and objectives, say so with completionSetByContent="true" and objectiveSetByContent="true" rather than leaving it to be inferred.
Open a package in SCORM Lab to see whether this applies to yours. It runs in your browser, and nothing is uploaded unless you choose to share it.
Stuck on this one, or seeing it only in a particular LMS? That is usually a short conversation — scormspecialist.co.uk.