02 · The season
The planner tells you what happens on Thursday. GrandPlanner takes a whole season — or a window, or a set of productions — and tells you where it breaks: which roles aren't covered, which rooms collide, which rules get bent. You work the answer out in a scenario, then merge the parts you want.
A · Scenarios
A scenario branches off the live schedule, scoped to one production or the whole organisation. Nothing gets copied. You edit events inside the scenario and runorder records what you changed, against the state of things at the moment you branched.
Scenario edits sit as an overlay on top of live data. The live calendar keeps moving underneath — someone else's Tuesday change lands as normal — and the scenario keeps the baseline it branched from, so the difference between the two stays meaningful.
B · The feasibility check
Pick a season, a date window, or a set of productions, and run the check. It returns findings — warnings and breaches — each attached to the event, person, production, or season it belongs to, and each named for the rule it broke.
Role coverage. Room overlap. Room turnaround. Availability collisions. Work-time compliance. Rehearsal lead time. Call notice. Productions that share people running overlapping tech weeks. Productions that share a room with too few changeover days. Department prep and breakdown buffers that collide.
C · Diff & cherry-pick
The diff compares three states — what live looked like when you branched, what live looks like now, and what the scenario says — entity by entity and field by field. Apply a change into live, reject it, or leave it sitting.
Where live has moved the same field you moved, that's a conflict, and you pick a side field by field before anything applies. Merge-all exists for when the scenario is simply right — it applies what it can, requests approval for what's gated, and skips whatever is still conflicted.
D · Approvals
An admin writes the matrix: which action, in which context, needs whose approval. Move an event. Add overtime hours. Reassign a role. Exempt a call. Eleven gated action types, each either left open or routed to named approvers.
A requirement can point at the stage manager of the production, the head of the affected person's department, HR, a named group, a named person, the affected person themselves, or any planner-editor — with a count for how many must sign. runorder resolves those to real people when the request is made and stores that list, so editing the policy next week doesn't quietly rewrite who was asked.
30-minute discovery call over Teams. Bring a season that gave you trouble and we'll walk through how GrandPlanner would have read it.
Request a conversation →Each surface gets the same depth as this page. Click around or head back to the overview.
All features →