Per-learner SCORM course outcomes — completion status, completion date, and SCORM-reported metadata. The report only reflects what the SCORM file itself sends back.
The SCORM Status Report shows per-learner outcomes for SCORM courses — completion status (Complete/Incomplete or Passed/Failed depending on the course design), completion dates, and any quiz data the SCORM reports. Reach for it for compliance evidence on SCORM-delivered training and for identifying learners stuck in SCORM courses.
Continu surfaces what the SCORM file reports. If the SCORM doesn't report quiz scores or time-spent data, Continu can't show what isn't there. See A Guide to SCORM in Continu for the underlying behavior.
When to Use This Report
SCORM-based compliance audits. Per-learner completion record with timestamps — the audit trail compliance teams typically need.
Identifying stuck learners. A learner showing Incomplete on a SCORM course they should have finished is the trigger for troubleshooting (SCORM completion logic, browser issues, VPN interference).
Confirming SCORM courses are firing completion signals. If many learners show Incomplete on a course they say they finished, the SCORM itself probably isn't firing the completion event correctly.
Column Reference
SCORM ID — Unique ID for the SCORM course. Useful for API workflows.
SCORM Title — Title of the SCORM course as configured in Continu.
SCORM Status — Outcome value. Format depends on what the SCORM reports: Incomplete/Complete for courses without a graded quiz, Passed/Failed for courses with a graded quiz.
SCORM Completed Date — Timestamp the course was completed. Empty for incomplete courses.
Plus standard learner profile columns.
How to Use This Report Effectively
Filter to one SCORM at a time for analysis. Different SCORMs report different ways. Comparing across SCORMs is rarely apples-to-apples.
Look at Incomplete trends. If a single learner shows incomplete, it's environmental. If many learners show incomplete on the same SCORM, the SCORM file's completion logic is suspect.
Cross-reference with Assignment Summary for coverage. Like other Status reports, learners who never opened the SCORM don't appear. Pair with Assignment Summary to see assignment-vs-engagement gaps.
Configuration Pitfalls
Blaming Continu for SCORM Reporting Issues. Continu reports what the SCORM file sends. If completion isn't firing correctly, the issue is the SCORM file's logic, not Continu. See My Learning Track shows incomplete... for the SCORM-side troubleshooting.
Comparing Pass Rates Across SCORMs With Different Pass Marks. Each SCORM defines its own passing logic. Pass rates aren't directly comparable across courses.
Forgetting VPN/Browser Issues. VPNs and certain browsers can block SCORM completion signals. Learners showing Incomplete may have completed the content but had the signal blocked. Confirm environment before re-assigning.
Drawing Conclusions From Small Samples. A SCORM with 10 learners completing won't yield reliable patterns. Wait for enough volume before treating the data as signal.
Where This Fits
You're here because you need SCORM completion data. For SCORM behavior overall, see A Guide to SCORM in Continu. For the SCORM upload flow, see Add a SCORM File.
See Also
- Reporting: Which Report Should I Use? — the strategic anchor.
- A Guide to SCORM in Continu — SCORM behavior reference.
- Add a SCORM File — SCORM creation flow.
- Learning Track shows incomplete after all content is complete — SCORM troubleshooting.
- Admin Reports in Continu — running and filtering reports.
Filter to one SCORM for analysis. Continu reports what the SCORM sends — completion issues live in the SCORM. Cross-reference with Assignment Summary for never-opened coverage.