Prepare the package first
Export a SCORM ZIP from your authoring tool and confirm its completion rule, pass mark and version. Test the package before uploading it to production.
Keep a release record containing the source-course version, exported file name, SCORM version and expected status values.
1. Add the SCORM package
In Docebo, add the package as training material within the target course, then upload the ZIP. Use a clear title so administrators can distinguish the activity from older releases.
If Docebo rejects the package, check that imsmanifest.xml is at the correct level inside the ZIP. Our manifest guide explains what to inspect.
2. Match completion and scoring rules
Confirm what the course reports when a learner finishes and what Docebo is expected to record. A package can launch correctly while still reporting the wrong status or score.
Make sure graded questions, pass thresholds and success rules are aligned. If scores are missing, use the SCORM score troubleshooting guide.
3. Run realistic learner tests
- Complete and pass the course.
- Fail an assessment.
- Exit part-way and relaunch.
- Check the learner transcript or course reports.
- Test on at least one typical learner browser and device.
4. Replace packages carefully
When updating SCORM content, avoid assuming a new ZIP will behave identically with existing attempts. Structural or tracking changes can affect resume data and reporting.
For important courses, test the new package in a separate course or sandbox before replacing the production version.
Put the guidance into practice
Build a real course in Lumeo, preview it in the browser, and export it to SCORM, standalone HTML or PDF. The free plan does not require a payment card.