Save and compare scenarios
Current, saved versions, new scenarios and the History of every change.
A feasibility rarely has one answer. You test a lower land price, a second lender, a later start. Scenarios let you keep each option as a saved, versioned record, move between them without losing work, and see exactly what changed and what it did to the returns.
How it fits together
- Current is your working copy. Every edit lands there and saves automatically; the header shows “Session saved” and how long ago. Each person has their own Current in a project.
- A scenario is a named, saved set of inputs, such as “Baseline” or “Lower land price”. A new project starts with one called Baseline.
- Each time you save Current to a scenario, it becomes that scenario’s next version: v1, v2, v3. Saved versions don’t change.
Step 1: See where Current stands
The scenario switcher in the header reads Scenario · Current with a tag. “Baseline v3” means Current matches that version. “Not saved to a scenario”, in amber, means you’ve made changes since.
Click the switcher to open the menu. Working session shows Current, with its profit and return; Saved scenarios lists each scenario with its latest version and when it was saved.
Step 2: Save a new version
In the menu, hover over the scenario and click Save as v4 (the number is the next version). A message confirms “Saved Current as Baseline v4”, and the tag goes back to matching it.
Save a version whenever you reach a point you might want to return to, such as before a lender meeting or after a board decision.
Step 3: Save Current as a new scenario
To keep an option alongside the original, click + Save current as new scenario at the bottom of the menu. The new scenario starts as v1, named after the one it came from with “(copy)”, and its name is ready to type over. Double-click a scenario’s name, or click Rename, to rename it later.
Step 4: Load a scenario into Current
Click a scenario in the menu to load its latest version into Current. If Current has changes that aren’t saved, Save Current before loading? asks first. Name them and click Save & load to keep them as a new scenario, or click Don’t save and then Discard & load to replace them.
Step 5: Review the History
Click History in the header. The drawer lists every input change across all scenarios, newest first: who made it, the field (for example “Costs › Construction Costs › Main Works Contract › Rate”), the old and new values, and whether it was in Current or a saved scenario. Saves, loads, renames and shares are listed too.
When Current takes a new BBSW rate from ASX, History shows it as Automatic.
Step 6: Compare scenarios
Three places show the comparison:
- The KPI strip under the tabs shows how Current differs from the version it was loaded from, such as “+1.2 pts vs Baseline v4” or “−$0.4m vs Baseline v4”.
- The Summary tab’s Scenarios card lists Current and every saved scenario with RoC, RoE, Equity IRR and Peak equity.
- The scenario menu shows each scenario’s profit and return.
The scenario figures follow the Report returns for selection on the Summary tab, so you can compare a single sub-phase across scenarios.
Tips
- Name scenarios for the decision they test (“Second lender”, “Six-month delay”), not the date.
- Save a version before sharing or exporting. A share always sends a scenario’s latest saved version.
- Deleting a scenario deletes all of its versions and can’t be undone. Only people who can manage the project see the delete button.
- Each person’s Current is their own, so a colleague’s unsaved changes never appear in yours until they save them.