Start here as an org admin

You are an Org admin. Your role is org-level oversight: you subscribe your organisation to professional fields, you invite trainers and field experts and learners, you promote validated scenarios across cohorts, you watch the escalation queues that catch stalled work, and you own the approval log that any regulator might ask for.

Your home shows

When you sign in, your home opens on the org overview and surfaces the work that needs you:

• Fields — the professional fields your organisation has subscribed to, with the count of validated and live scenarios per field.
• Cohorts — every cohort in your org, with assigned trainer, active learners, and current scenario load.
• Promotion queue — validated scenarios across all subscribed fields, with per-cohort promotion controls.
• Escalations — evidence pending a trainer verdict for more than seven days; stalled validation sign-offs; disagreement spikes on a particular trainer or scenario.
• Audit trail — the full log of Draft → Pending validation → Validated → Live → Retired transitions, with timestamps and actors. Exportable.

How the work flows

Subscription is the entry move: without subscribing to a field, you can’t onboard field experts in it, and you can’t promote scenarios in it. Once two field experts in a subscribed field exist, peer validation can produce Validated scenarios. Once a scenario is Validated AND Live, you can promote it to one or more cohorts at once. Trainers can still manage promotion for their own cohorts; admin promotion is the broadcast.

Substantive edits to a Live scenario fork into a new draft and re-enter validation; cosmetic edits stay in place and are logged. Both events land in the audit trail with the actor and the timestamp, alongside every status transition and trainer verdict.

Regulator-ready by design

The status machine produces a regulator-ready approval log. Every Draft → Pending → Validated → Live → Retired transition is logged with the actor and the timestamp; the same log captures cosmetic edits, substantive forks, and trainer verdicts. Export from the audit page to CSV or JSON.

Where to next

Subscribe a field Open a professional field so its scenarios become promotable.

Invite members Bring trainers, field experts, and learners into the org.

Promote scenarios Push a validated scenario to one or more cohorts at once.

Handle escalations Work the three queues that catch stalled or divergent work.

Export the audit trail Pull the regulator-ready log of every state transition.

You can also read the four roles, the scenario lifecycle, and evidence and verdicts for the concepts that the admin surface sits on top of.