Promote scenarios
Promotion is the org-wide tool to push a Validated scenario to one or more cohorts in a single move. Trainers can also promote scenarios to their own cohort from their surface; admin promotion is the broadcast that lets you roll a scenario out across the whole organisation.
Before you begin
- The scenario is Validated — peer validation by a field expert has signed it off.
- The scenario is Live — the field expert who authored it has run the realism preview and the scenario has crossed both gates of the scenario lifecycle.
- Your org is subscribed to the scenario’s field. See subscribe a field.
Step 1 — Open the library page
From your home, go to the library page. You’ll see every scenario in your org’s catalogue with its title, field, and status. Filter by field to narrow the list to the scenarios you want to consider.
Step 2 — Pick scenarios
Select one or more rows. The library is read-only for your role — only the authoring field expert can edit the scenario itself — but promotion is the governance action you own. The status pill on each row tells you which scenarios are eligible: only Live scenarios can be promoted.
Step 3 — Promote to cohorts
Click Promote to cohorts. Multi-select the cohorts that should
see the scenario. Confirm. The scenario appears in those cohorts
immediately. What learners see depends on cohort settings: in
trainer-driven cohorts, the trainer assigns it to specific learners;
in self-pick cohorts, the scenario appears in the available list for
every learner in the cohort.
The lifecycle in one line
A scenario moves through Draft → Pending validation → Validated → Live → Retired. You promote between Validated/Live and Retired. Substantive edits to a Live scenario fork into a new draft; cosmetic edits stay in place. See the scenario lifecycle, including the fork rule for what counts as substantive.
When something goes wrong
- A scenario is Validated but you can’t promote it. It probably isn’t Live yet — the authoring field expert hasn’t run the realism preview. Validated and Live are the two gates; both must close.
- You promoted but learners don’t see it. Refresh first; the cohort listing updates lazily. Then confirm the learners are in the cohort you promoted to and that the trainer has assigned the scenario (in trainer-driven cohorts).
- Promotion is missing the field you expected. Your org isn’t subscribed to that field, or no scenarios are Live in it for your org yet.
- The same scenario shows up twice. A fork has Live status and so does the original. Retire the older one; the audit trail keeps both.