Objectives and Progress
Below the attempt sit two more levels of detail: objectives, and progress through the parts of a package.
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
Objectives
Where content declares them, each objective is recorded with its own identifier, description, scores, success status, completion status and progress. So a course covering five topics can report per topic rather than as one number.
Why that matters
A learner scoring seventy per cent might have understood everything except one topic completely — which is a different situation from being weak across the board, and needs a different response.
Across a population, objective-level results say which topic your organisation is weakest on. That is a training plan.
SCO progress
A SCORM package can contain several parts, and progress through each is recorded — status, scores, time, lesson location and suspend data per part.
This is where you see that learners complete the first three sections and stop at the fourth.
Find where people stop
The most valuable use of it. A part where a large proportion of learners abandon has a problem — it is too long, it does not work on their device, or it fails.
The completion report shows people not finishing; this shows you where.
Both depend on the content
Objectives are recorded only if the package declares them, and SCO progress only if the package has multiple parts. Simple packages produce neither, and that is not a fault.
If topic-level reporting matters, ask for content built with objectives — it is a specification decision, not something you can add later.
Use aggregates, not individuals
Objective-level data about one person is of limited use and quite intrusive. Across a cohort it is genuinely valuable, and much less sensitive.
Match objectives to how you think
Content objectives are named by whoever built the package. If your own framework uses different topics, map them once so the reporting speaks in your language rather than the supplier’s.
Check them on a test attempt
Complete a course yourself and look at whether objectives and part-level progress appeared. That is the only way to know what a package actually reports, and it takes one attempt.
Worked example
Objective results across a cohort showed one topic scoring far below the others in an otherwise well-performing course. Part-level progress showed the same section was where most learners paused for several days. The section was split into two shorter parts and both figures improved.
Recommendations
- Report objectives across a cohort, not per person.
- Use part-level progress to find where people stop.
- Specify objectives when commissioning content.
- Confirm on a test attempt what actually gets recorded.