Scenarios

A scenario starts from the stored grids and overrides chosen inputs. Up to four named, independent scenarios are returned beside the baseline. Reading scenarios saves nothing and writes no inputs.

Saved scenarios

A scenario can be saved, with its window, its Included choices for payroll rows, its Include pending setting and any input overrides. The Base case is the stored model with no saved choices and is read-only: duplicate it, or create a scenario, to model changes. Over MCP, list_scenarios and get_scenario read saved scenarios and save_scenario creates or changes one; that save is a change to data, so it needs the write permissions described in permissions and is recorded in the change log as made by the agent.

The Capacity Plan and AGI reports use a scenario's Included payroll rows and its Include pending setting. They do not use its input overrides, which change the Model Calculator only. Those reports count Pending projects only when Include pending is on.

See the Model Calculator.