What GrandPlanner is

The planner answers “what happens this week”. GrandPlanner answers the bigger question: does the season hold? It layers three things on top of the planner — scenarios for trying out changes without risk, a feasibility engine that checks the whole season against staffing, rooms, and working time, and an approval flow for the changes that need sign-off.

The workspace

GrandPlanner in the menu opens the workspace with two parts:

• Live season — the feasibility of the actual plan, with Run feasibility check to refresh the verdict.
• Scenarios — your scenarios, each with its summary of breaches and warnings. See Scenarios.

There’s also Live mode: a list of upcoming live events where you can shift individual events directly — every move is checked immediately, and a banner tells you if it introduced a breach. The change saves regardless; the banner is information, not a block. If the change requires sign-off per the approval matrix, it becomes a request instead.

Where GrandPlanner shows up elsewhere

With the module on, the rest of runorder gains small additions:

• Event chips on the planner get a feasibility dot (red on breach, amber on warning).
• The week view gets Compare against scenario — the scenario’s changes overlay the live plan, with Apply/Reject per change.
• Productions get the Staffing tab, and events can call in whole departments. See Staffing and departments.
• The drafts list shows a branch-point badge and change counter on scenarios.

Module-controlled

Everything above switches on and off together with the GrandPlanner module under Admin → Modules. With the module off, the routes don’t exist and the planner behaves as before.