What is an airwall, and why does it change how floor plans work?

Airwalls are the movable partitions that split a ballroom into sections. EventDiagram draws the space once and derives every combination, instead of storing a separate floor plan per combination.

From the course: Venues, spaces & airwalls · 1:35

An airwall is a movable partition that divides a large event space into smaller ones. A ballroom sold as Grand Ballroom A, AB, ABC or whole is one physical room with airwalls at fixed positions.

EventDiagram draws the space once and treats the sections as data, so every combination derives automatically. You never maintain a separate floor plan per combination.

Why that matters more than it sounds

The conventional approach stores each combination as its own uploaded floor plan. A four-section ballroom has ten sensible combinations, so a correction to the room — a column in the wrong place, a door that actually opens inward — has to be applied ten times. In practice it gets applied once, and nine plans quietly go stale.

Because sections here are data on one drawing, the area, the section labels and the capacity all recompute together when the walls move. Three event spaces in a typical property become a dozen usable floor plans without anything being drawn twice.

Setting sections up

  1. 1Open Venues and add the event space with its real width, depth and ceiling height.
  2. 2Add the airwall sections along the axis they divide — usually A, B, C, D.
  3. 3Give each section its real size; they do not have to be equal.
  4. 4Open My venue and every combination is already there, ready to lay out.

What counts as an event space

An event space is somewhere you actually book — a ballroom, a lawn, a rooftop. Back of house captured alongside it (a stage, a pre-function corridor, storage) is not, and is marked as such so it is never metered against your plan and never lands on a public capacity chart. Nobody books the loading dock.

Related

Try it on your own event space

Start free

Updated September 2, 2026 · 12 articles in the knowledge base