Getting Started Guide step

Projects, Versions, And Scenarios

Before you get deep into the workflow, it helps to know where work is actually being stored. GridGap keeps the job, the saved option, and the modeled setup as separate layers.

The project layer

The project is the top-level container. One property, one vehicle, or one distinct backup job will usually live inside one project.

Think of it as the folder for the whole job. That is where the version history, results, and later exports are anchored.

The version layer

A version is a saved option inside the project. Versions are what you compare.

One version might hold an AC backup option. Another might hold a DC distribution option. Another could use a mixed AC/DC solar path, or test the same scenario type with different recharge assumptions.

Name versions properly once there is more than one. You will thank yourself later.

Older versions stay editable. Reopen one and calculate it again, and you update that version only.

The scenario layer

A scenario is the actual modeled setup inside a version. This is the layer where the battery, inverter, charging, solar, and usage inputs come together.

Each version has one scenario. It can be AC, DC, or mixed AC/DC, with or without solar. You can reach it through guided setup, or use Start with blank scenario settings and choose the scenario type in the blank scenario modal if you want direct control.

Versions preserve different saved options over time. The scenario is the setup carried by that version.

How you move between them

The Projects page leads you into a project. The project detail page shows the versions in that project. From there you can move into the scenario editor to work on inputs, or into results to review the saved calculation for that version.

Those two views do different jobs. The editor is for building and changing. The results page is for inspecting what is already saved.

Why Calculate behaves the way it does

This structure explains the version actions.

Calculate updates the version you are currently editing. It replaces the stored results for that version only.

Create New Version preserves the current version and opens a new one for further work. The new version is not calculated automatically. You branch first, then calculate when the new version is ready.

If you are still working on the same option, use Calculate. If the current option is worth keeping and you want a comparison branch, use Create New Version.

Keep this model in your head

The project is the job. The version is the saved option. The scenario is the setup inside that version.

One useful habit

Try to make versions represent meaningful saved options, not tiny random edits. If a change is important enough to compare later, it usually deserves its own version name.