Skip to main content
Versioning helps you preserve a known-good state inside the same model lineage. It is useful when you want a stable checkpoint before the next close, forecast update, or review cycle.

​
When to save a version

Save a version when you want to record a meaningful point in time, such as:
  • before a budget or forecast review
  • after a close update
  • before a large formula or structure change
  • before sharing a milestone with leadership

​
What versions are for

Versions help you:
  • preserve a trusted baseline
  • compare current work to an earlier checkpoint
  • roll back carefully if a recent change caused problems
Versioning works best when the model structure is still recognizable across checkpoints.

​
Recheck comparisons after major changes

If you change major model structure, linked dependencies, or core time settings, compare results carefully before you rely on an older version as a baseline. A saved version may still be useful, but it may no longer be the clean comparison point you expected. If you restore an older version, recheck the key outputs that other teams depend on before you publish the model widely again.