<!-- Generated by scripts/export-user-manual.mjs from the rendered manual. Do not edit. -->

# Track learner progress and replay requirements

Open Behavior analytics, identify the journey version, then inspect stages and learners. Establish which version you are reading before deciding whom to follow up with.

<a id="creator-journey-roster-before"></a>

## Before you begin

The journey is published and you have analytics access. Enter through Behavior analytics, not a roster panel in the journey editor.

**Worked example**

Version 2 is live. Some learners retain qualification earned in version 1; others must complete a replay requirement. A new-version score alone cannot distinguish these groups.

1. <a id="creator-journey-roster-step1"></a>

   01

   <a id="creator-journey-roster-step1-title"></a>

   

   ## Start with the journey version

   

   1. In Behavior analytics find Journey progress and identify the journey by name and version. Review assignments and completions, then the replay requirement where applicable.

   

   **Why this matters**Version 1 completion is not version 2 completion.

   

   **Check the result**You can name the version and explain what the counts measure.

   

   Not the expected result?

   

   If data is absent, check publication, workspace and access. No data does not mean zero scores or universal failure.
2. <a id="creator-journey-roster-step2"></a>

   02

   <a id="creator-journey-roster-step2-title"></a>

   

   ## Open one stage before reading its learners

   

   1. Select the journey cover for that version, then check the stage name and content version. Open only one stage at a time, and then read that stage's learner names, emails, states, progress and available scores. Distinguish not started, in progress, cleared and locked behind prerequisites.

   

   **Why this matters**Locked is not failed, and not started does not establish poor ability. Check access and available time before drawing conclusions.

   

   **Check the result**Follow-up decisions have a specific version, stage and state behind them.

   

   Not the expected result?

   

   The current page has no journey overdue-roster or one-click roster-copy entry. Do not infer overdue status from incomplete progress or treat an example table as an available feature.
3. <a id="creator-journey-roster-step3"></a>

   03

   <a id="creator-journey-roster-step3-title"></a>

   

   ## Separate qualification, scores and replay obligations

   

   1. Compare applicable qualification with replay requirements. When someone is qualified without a new-version score, check whether prior qualification was retained. Follow the actual assigned requirement rather than demanding an unassigned replay.

   

   **Why this matters**Prior achievements may remain applicable without generating new-version play data.

   

   **Check the result**Each follow-up can distinguish no attempt, unmet passing criteria and an outstanding replay requirement.

   

   Not the expected result?

   

   For a discrepancy, record the version, stage, account and time for investigation. Do not begin by deleting history or recreating the account.

<a id="creator-journey-roster-complete"></a>

## What completion looks like

You can find a learner’s stage state in the intended version and distinguish actual new-version completion from applicable qualification.
