Approvals

Some plan changes shouldn’t happen without the right person saying yes — moving a performance, adding overtime for a technician. GrandPlanner’s approval matrix lets the organisation define exactly which changes require sign-off, without slowing everything else down: changes with no rule pass straight through.

The matrix

Administrators set the rules under GrandPlanner → Admin → Policies. Each rule couples a change type — move event time, add overtime, reassign a role — and a context (global, person in department, event in production, event type) to who must approve:

• The production’s stage manager or department head for the affected item — resolved automatically to the right people.
• HR, a specific group, or a specific person.
• The affected person themselves, or any planner editor.

Each row can require multiple signatures. The configuration also sets the request expiry (default 7 days) and which group is HR.

The queue

GrandPlanner → Approvals has three sections: Awaiting your approval — requests you can sign, with Approve and Decline and an optional note; Your requests — your own, with progress (“2 of 3 approvals”); and History — the organisation’s complete log.

When the last required signature comes in, the change is carried out automatically and the requester is notified. A single decline ends the request. Unanswered requests expire after the deadline, with a notification back.

Everything is audited

Every transition — requested, approved, applied, declined, expired — is written to a dedicated immutable approval log. The History section reads from it.