Skip to main content
Versioning and snapshots are useful when a team needs a stable reference point before the next round of scenario work begins. In the scenarios section, they matter most as supporting lifecycle tools, not as the main current-scope workflow.

​
When to preserve a state

Preserve a reference state when you reach a milestone such as:
  • budget submission
  • executive review
  • forecast sign-off
  • a scenario that should remain stable for later comparison
That reference point helps keep future comparisons honest.

​
Why snapshots are useful

Snapshots and versioning help teams answer:
  • which state are we treating as approved
  • what changed after that point
  • which branch should act as the comparison baseline
Without a preserved reference, teams often end up debating the baseline instead of the decision.

​
Snapshot versus active scenario

An active scenario is for ongoing what-if work. A preserved state is for:
  • keeping an approved baseline stable
  • supporting later comparison
  • making handoffs easier during review cycles
That is why this topic belongs in scenarios, but as a lighter supporting concept rather than the center of the feature.

​
What may come next

Near-term lifecycle improvements may eventually make this area more explicit through ideas like scenario status or approval flow. For now, the safer docs story is to treat snapshots and versioning as ways to preserve trusted reference points while the rest of the scenario workflow continues elsewhere.