Bookitive
Seating

Venues and arrangements

Reusable places and layouts — zones without prices, the arrangement design studio, and version snapshots you can restore.

Not verified yet

Venues (sidebar footer, organization scope) are the places you run events at; each holds arrangements — named, reusable room layouts. Together they're the library your events draw from.

Venues

A venue is simple on purpose: name, address, city. Its value is what hangs off it — the arrangements, and the fact that creating an event can point at a venue instead of a typed-out place name.

Arrangements and zones

An arrangement is one complete way to set the room up. Create it with a name (and optionally the kind of event it suits), then design:

  • Zones — the arrangement's categories: a color and a label (Front, Gallery, VIP), deliberately without prices. Zones describe the room's geography; money enters later, when an event maps each zone to its own ticket type.
  • The layout — floors, sections, seats, tables, standing areas, drawn in the same design studio events use, just with zones in place of ticket types.

One venue typically accumulates a few arrangements over the years — "Ball", "Concert", "Banquet" — and new events pick from the shelf.

Snapshots and restore

Every save of an arrangement's chart is auto-saved as a snapshot with a version number — you don't do anything to capture them. Redesigned the hall and regret it? The Version history panel in the arrangement design studio lists every version; pick one and restore it. Restore sits behind a confirm, and before it applies, your current layout is itself saved as a new version — so a restore is always undoable, and you can step back and forth without losing anything.

Version history is a venue arrangement feature only. An event's own seating chart, once an arrangement has been applied to it, is an independent copy and does not carry restorable history — restore the arrangement, then re-apply it to future events if you want the earlier layout back.

Behaviour and edge cases

  • Applying copies, never links. An event that applies an arrangement gets an independent copy. Editing or even deleting the arrangement afterwards does not touch any event — past or on sale.
  • Changes don't propagate — that's a feature. If this year's layout improved mid-season, re-apply the arrangement to future events that haven't sold seats yet; live events keep the plan their buyers bought into.
  • Venues and arrangements are organization-wide — one shared library, governed by the venues permissions in Team.

On this page