Resolving room conflicts

The planner checks every room for overlap when you place an event. The check runs across production and project events — a project can collide with a performance and vice versa — so the room has one truth no matter who books it.

What counts as a conflict

Two events conflict when their time spans actually overlap in the same room. Back-to-back is allowed: an event ending at 14:00 doesn’t conflict with one starting at 14:00. Cancelled events and unpublished project drafts don’t count. A pending event is a tentative hold and doesn’t block others either.

Two exceptions are controlled by the room itself, under Admin → Rooms:

• Rooms with overlap allowed are never checked — useful for foyers and shared spaces.
• Rooms with a changeover buffer also flag events that come too close after the previous booking. That’s a warning, not a block.

Resolving the conflict

The conflict alert pulses in the quick-plan panel with the message Conflicts with “the title” in the room, linked to the event you’re colliding with. The fastest fixes, in order: move the new event to another room or time, move the existing one, or split the rehearsal into sub-events so the room frees up in the break.

From the New event form the conflict is blocking — adjust and save again. From the quick-plan panel you can override.

Overriding on purpose

Some overlaps are right — a get-in rehearsal borrowing into the next production’s break. Choose Place anyway in the conflict alert and the event is placed on top of the conflict.

Overrides are audited and notify

Every override is written to the production’s or project’s audit log — which event was placed, and which ones it collided with. The people called to the affected events are notified automatically.

With the GrandPlanner module on, each chip additionally gets a small feasibility dot: red on a room collision, amber on changeover-buffer issues or when a called person is busy in another event.