What-if scenarios

A scenario asks the report a question it was not built to answer. What if the key witness turns hostile? What if the ITRs cannot be produced? Judicio re-evaluates the grounds the change touches and lands the answer as a linked version of the report, leaving the report you already read exactly as it was.

Nothing is overwritten and nothing is lost. A report and its scenarios are one family, and you move between them from the version strip at the top of the grounds rail.

1

The report a scenario branches from

This is the version you start with. The strip appears above the lane tabs in the grounds rail as soon as the report has a second version, and until then a report is simply itself.

The version strip

The strip sits above the lane tabs in the grounds rail, labelled Version. It appears once the report has a version family.

Control	Where	What it does
Version chips	Left	One per version, in creation order. The first reads Initial; a scenario carries its own name, or the scenario question truncated. The chip you are reading is selected.
New scenario	After the chips	Opens the Test a scenario modal.
Chevron	Right	Show the scenario cards and Hide the scenario cards. Opens the full cards inline, under the chips.

Selecting a chip opens that version. Every version has its own address, so a scenario can be linked to and reloaded on its own.

A scenario that failed, was stopped or was cancelled never became a version worth switching to, so it gets no chip. A scenario still running does get one, and its card says Still running: the report lands here when it completes.

New scenario is held back until the run it would branch from has finished, with the tooltip Available once this run finishes. When it is available, the tooltip explains what it does: it tests a scenario question against the open version, not always the baseline.

The version cards

The chevron expands one card per version.

Part	On the initial report	On a scenario
Badge	Baseline	Scenario n
Name	Initial report	The scenario's name
Line under it	The full strategy as generated. Every ground at its original strength.	The scenario question
Strength strip	One segment per ground, tinted by its strength	The same, with a ring around each ground the scenario moved
Footer	The run date and the overall confidence badge	How many grounds changed, then the confidence before and after

The card you are reading carries Viewing this version along its foot. A dashed New scenario row sits at the end of the list, with the same job as the button above: Test a scenario question against this report. It runs as a linked version and lands here.

The Test a scenario modal

New scenario opens a modal titled Test a scenario. The rail's own Test a scenario action, on an open ground, opens the same one.

Part	What it is
A new version of this report	A note explaining what will happen: the affected grounds are re-evaluated under your scenario, and strength arrows and a delta summary land on a linked version, leaving this report untouched.
Your scenario	The field. Type the change you want tested. The placeholder is What if the ITRs cannot be produced?
Example scenarios	Three starters. Selecting one fills the field.
Cancel	Closes without spending anything.
Re-evaluate	Starts the scenario. Disabled until the field has something in it.

Re-evaluate takes you straight to the new version's run view, so you watch it being written the same way you watched the first report. Going back from there returns you to the report you branched from.

Reading a scenario version

A scenario version is a full report: the same four tabs, the same grounds rail, the same authorities. What it adds is a strip pinned above the document, outside the scroll.

The strip is headed Scenario - followed by the question you asked. Under it:

• The delta summary in prose: what actually changed and why.
• One entry per ground the scenario moved, as Gn with the strength it held before, an arrow, and the strength it holds now.
• Revised outlook: with the new overall confidence badge.
• View the original report, which opens the version this scenario branched from.

Grounds the scenario did not touch keep their original strength and are not listed.

Working with versions

• Scenarios stack. A scenario run from a scenario branches from that one, not from the baseline. The strip's tooltip tells you which version New scenario will act on.
• Triage is per version. Lanes belong to the report you are reading, so keeping a ground on the baseline does not keep it on a scenario.
• Compare by switching. There is no side-by-side view. Switch chips: the grounds under the strip always belong to the chip that is filled, so there is never a question of whose grounds you are looking at.
• The header counts versions. Once a family exists, an n versions chip appears in the report header and points you back at the strip.

Credits

Case Strategy credit costs

Action	Mode	Cost	Example
Strategy report	Deep	35 credits	Any matter
Strategy report	Standard	15 credits	Any matter
What-if scenario	-	5 credits	Asking the report a question is free
Moot court session	-	10 credits	One session, however many turns it runs

What a scenario costs

A scenario is charged once, when you press Re-evaluate, at a flat rate. It does not matter how many grounds the change touches. Reading a version, switching between versions and asking the Assistant about one are all free. See Credits explained.

Next steps

• Reviewing grounds - triage the version you settle on.
• Moot court - argue it before you argue it.
• Exporting and drafting - export the version you are reading.

Open Case Strategy (opens in a new tab)