Projects, Versions, And Scenarios Explained

GridGap stores work in a layered structure. Understanding that structure is the key to understanding why results, warnings, and recalculations behave the way they do.

Projects

A project is the top-level container. It groups the versions and scenarios for one overall planning job, such as a house, RV, boat, office, or shop.

Think of the project as the folder for one real planning job. If you want to compare different technical paths for the same property or vehicle, those comparisons usually belong inside one project as separate versions rather than as separate unrelated projects.

Versions

A version is a saved state of that project. Older versions remain editable. If you open Version #1 later, you can still change it and recalculate results for that same version.

This is what makes side-by-side thinking possible. One version might represent a battery-only approach. Another might represent a solar hybrid. Another might keep the same scenario idea but change battery size, inverter size, or recharge assumptions.

Version names matter once there is more than one. Renaming a version to something clear makes later comparison much easier than relying only on version numbers.

If a version is deleted, remaining versions are renumbered sequentially with no gaps.

Scenarios

A scenario is one modeled setup inside a version. In normal use, one version carries one working scenario, either battery + inverter only or solar + battery + inverter.

New users may reach that scenario through a guided setup path. That route creates the load groups first, lets the user enter usage, and then prepares seeded starting inputs. Users who already know what they want can skip that process with Start with blank scenario settings.

That means scenarios are not separate long-term branches in the way versions are. Versions are the main comparison layer. Scenarios are the modeled setups that live inside one version.

How to move between them

On the Projects page, open a project with the eye icon. That takes you to the project detail page where you can review the version list.

From there, each version can lead to two different working views. The scenario view is where you enter and edit appliance and scenario data. The results view is where you review the calculated outputs for that version.

This distinction is important. The scenario editor is the place where you build and adjust inputs. The results page is the place where you inspect what the current saved calculation produced for that version.

Calculate behavior

Calculate recalculates the version you are currently editing and replaces only that version's stored results.

Create New Version preserves the current version and opens a new version for further work. It does not calculate the new version automatically.

This is the practical rule to remember. Use Calculate when you are still working on the same version. Use Create New Version when the current version is worth keeping and you want to branch into a fresh comparison.

Older versions do not become read-only just because they are older. If you reopen an earlier version and click Calculate, that earlier version is updated in place. Other versions are not touched.