Accept completion and passing as different learning records

Specify the two questions the record must answer

Articulate’s Storyline 360 reporting guidance, checked on 7 November 2026, distinguishes finishing from success and notes that SCORM 1.2 reports one status while SCORM 2004 reports two. It also warns that the authoring reporting option and LMS interpretation affect the displayed result. This lesson uses a SCORM 2004 4th Edition acceptance case; other exports need their own mapping.

Write two plain questions before inspecting a dashboard: has the learner completed the defined activity, and has the learner satisfied its assessment requirement? Ask the course owner what evidence answers each question. Reaching a final slide might fulfill the first condition in one design, but it cannot be assumed to fulfill the second. Keep those definitions attached to the exact package revision.

Create cases that can reveal a collapsed distinction

Prepare synthetic cases for an untouched enrollment, an interrupted activity, a completed unsuccessful attempt and a completed successful attempt. Include an unassessed activity if the package contains one, with an explicitly agreed treatment of success rather than inventing a pass. State the expected outcome before running the package.

For each case, record the course’s visible message, the status information the technical owner confirms it reported, and the LMS’s learner-facing and administrative labels. These are three observations, not interchangeable proof. A congratulations screen can be authored independently of tracking, and an administrative label can summarize several underlying values. If the LMS presents only one badge, document exactly what that badge means and where the separate evidence can be inspected.

Locate the mismatch before changing the learning rule

When a case differs from expectation, first determine whether the package sent the intended status. If it did not, review the selected tracking and reporting configuration with the authoring owner. If it did, ask the LMS owner how the destination interprets and displays that evidence. Keep sanitized diagnostics tied to the synthetic case rather than exporting real learner histories.

Do not repair a completed-but-unsuccessful case by calling it incomplete solely to make a report look familiar. That change may hide that the learner reached the assessment and needs a different next step. Likewise, do not mark success simply because the final page loaded. If the delivery standard cannot express the required distinction directly, agree and document the supported interpretation before launch rather than claiming the missing evidence exists.

Accept the meaning shown to learners and administrators

Read the resulting record as a learner would. Does it explain whether work remains, whether an assessment requirement was not met and which approved next step is available? Avoid a generic finished label if administrators will later interpret it as passed. Keep course completion evidence separate from any certificate, authorization or workplace competency claim that needs additional review.

Retain the status truth table with the export standard and edition, reporting option, LMS version and package revision. Recheck it after a tracking change or platform migration. Do not expand this table into score arithmetic or multi-attempt selection; those require separate tests. Acceptance is a verified mapping between the intended outcome and the recorded status, including the unsuccessful path, not a count of positive badges or a guarantee that finishing the course produces professional mastery.

Make the reasoning concrete.

A fictional campaign-compliance course requires all sections and a scored assessment. A test learner reaches the end but does not meet the assessment requirement. The course says finished while the administrator reads that label as passed.

The team documents the two outcomes and corrects the interpretation without awarding a pass or changing any real learner’s record.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Meaning

   What separately establishes completion and assessment success?

2. Fixture

   Which synthetic case proves the two can differ?

3. Report

   What status evidence did the package actually send?

4. Display

   How does each LMS label map to that evidence?

5. Scope

   Which package, standard edition and destination configuration were accepted?

Watch for the wrong conclusion.

• Using a congratulations screen as tracking evidence.
• Treating completed as automatically passed.
• Changing the learning rule to hide a reporting mismatch.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not supplier implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Supplier controls, contracts and local requirements can change; verify the actual placement and current provider guidance before implementation.

• Articulate: Storyline completion and success reporting →Primary platform documentation · Supports: Supports status distinctions, SCORM1.2 versus2004 representation and authoring/LMS interpretation limits; the acceptance table is editorial.