01
Students decide
They select information within a limited budget, keep more than one plausible explanation alive, and record the condition that would justify changing the decision.
VORTEX UNIVERSITY LAB
A lecturer-led digital decision lab. Students work with evolving information, compare competing hypotheses, commit to decisions, and reconstruct their reasoning during a structured debrief.
A guided demonstrator is available now. The pilot scope is agreed with the academic unit and lecturer.
TEAM TRACE
RUN 04 / 05
New information
Conflicting institutional statement
Leading hypothesis
A system failure remains more plausible than deliberate action
Decision
Secure the area, commission an independent reading, avoid premature attribution
1
complete scenario example on the site
2
roles: participant and facilitator
1
decision trace for debrief
Local-first
save and result export
METHOD
One shared method connects information selection, a leading hypothesis, a credible alternative, a course of action, its rationale, and the condition that would change the decision.
01
New information
02
Source assessment
03
Hypotheses
04
Decision
05
Replay
06
Debrief
01
They select information within a limited budget, keep more than one plausible explanation alive, and record the condition that would justify changing the decision.
02
They define learning outcomes, facilitate each round, compare team traces, and turn the exercise into structured debrief material.
03
The system structures sources, hypotheses, actions, and revisions. The lecturer approves feedback and final assessment.
FEATURED SCENARIO
We show one complete example on the site. The actual exercise runs in the Vortex application. Open the detail page to see the challenge, roles, four rounds, decisions, and outcome.
01
Scenario Pack
Flooding, infrastructure, evacuation decisions
Diverging forecasts, a power disruption, and false alarms. Teams allocate limited resources and make protection and evacuation decisions in a fictional region.
During a meeting, we open the pack, show participant and facilitator views, and walk through the decision trace used in the debrief. We can also agree a scenario adapted to a specific course or academic unit.
MATURITY
We keep the demonstrator, pilot, and product direction distinct. The university knows what is available now and what requires a separate implementation.
NOW
The working High Water 48H pack, four controlled rounds, participant and facilitator views, and local result export. No user accounts or dynamic branching.
PILOT
One Scenario Pack adapted to the syllabus, learning outcomes, cohort, and session format. The lecturer controls facilitation, feedback, and assessment.
DIRECTION
Hosted multi-team sessions, server-side roles, dynamic scenario responses, and integrations require a separately agreed implementation scope.
PILOT PROCESS
The recommended planning window for one agreed Case Pack is up to 8 weeks after scope approval. Timing is confirmed following qualification.
01
Course, cohort, learning outcomes, format, data, and organisational constraints.
02
Student role, decision question, final outputs, and assessment criteria.
03
Rounds, materials, hypotheses, action options, facilitator guide, and debrief plan.
04
Room, devices, result export, and the complete delivery path with the lecturer.
05
Team traces, lecturer feedback, an individual transfer task, and the decision on the next step.
ENGAGEMENT MODELS
We do not publish a universal price because the scope depends on the scenario, session count, cohort, data, and level of adaptation.
01
Individual quote
One course, unit, or cohort
Qualification, adaptation of one scenario, facilitator preparation, technical rehearsal, delivery support, and a pilot summary.
02
Individual quote
Recurring courses or a university training centre
Repeat delivery, Scenario Pack versioning, preparation of additional facilitators, and an agreed update model.
03
Individual quote
A discipline-specific university case
Design workshop, materials, source and licence register, expert review, acceptance criteria, and facilitator package.
ACADEMIC CONTROL
Base scenarios use synthetic data. Public, archival, geospatial, or satellite materials are added only when their use is lawful, their source is explicit, and they answer a defined learning question. The system does not issue an automated student grade.
01
Synthetic data as a safe baseline
02
Explicit sources and material limitations
03
Assessment approved by the lecturer
QUALIFICATION
Answer a few questions. We will use them to suggest the right scenario, pilot scope, and information required for a commercial proposal.