Pavilion design tips for states and associations

What makes a pavilion different

A pavilion is not a large stand. It is a group of small stands sharing an identity, an entrance and a budget, and the design problem is social as much as it is spatial. Every co-exhibitor wants to be visible, several of them have views on the design, and the organising body has to keep the whole thing looking like one thing.

That changes the design priorities. On a single-brand stand the question is how to draw a visitor in. On a pavilion the question is how to draw a visitor in and then move them past every participant without the pavilion feeling like a corridor of identical booths.

It also changes the project management. A single-brand stand has one approver. A state or association pavilion has a department, a committee, a set of participants and often a tendering process, and the design has to survive all of them with its coherence intact.

One identity, visible from the aisle

The pavilion has to be legible as a single entity before any individual participant is legible. That is achieved with a small number of elements repeated without exception: a consistent fascia band, one colour family, one typeface, one height line and a single clear entrance.

Resist the instinct to let each participant brand their own fascia in their own style. The moment that happens the pavilion stops reading as a pavilion and becomes a row of unrelated booths, and every participant loses the visibility the shared identity was supposed to buy them.

Allocating booths fairly

Booth allocation is where pavilions generate the most friction, and the way to reduce it is to make the rules public before anyone sees the plan. A small number of standard booth sizes, a stated basis for allocation and a transparent position draw take most of the heat out of the process.

Use a standard module rather than bespoke sizes. Our usual planning ratios apply to small booths as they do anywhere — storage at 10% of the area up to 18 sq.m, a meeting corner at 5% and the remainder display — and at pavilion booth sizes that leaves very little room for anything other than one clear product story.

Shared spaces earn their area

The strongest argument for a pavilion over a row of individual stands is that participants can share things none of them could afford alone. A proper reception, a meeting room, a stage, a lounge and real storage are all more achievable collectively.

They also give the pavilion a centre. A pavilion that is only booths is a corridor; a pavilion with a stage or a lounge at its heart has somewhere for visitors to stop, which is what creates the cluster that pulls in more visitors. Put the shared space where it is visible from the main aisle, not tucked away at the back.

Laying out the plan

Circulation decides whether every participant gets seen. A single straight aisle through the middle means the booths at the far end are visited by a fraction of the people who visit the first ones. Breaking the route — with the shared stage, the lounge or a turn in the aisle — distributes footfall far more evenly.

Keep sightlines open along the length of the pavilion so a visitor at the entrance can see that there is more to walk towards. Solid walls between booths at full height turn a pavilion into a series of cells; a lower divider or a partial screen keeps the volume reading as one space while still giving each participant a defined area.

Think about the pavilion's edges as well as its interior. The outer faces are prime visibility and should carry the pavilion identity and a reason to come in, not the backs of participant booths.

Running the approvals

A pavilion has more approval layers than a single stand, and they run in parallel: the organiser approves the structure and the loads, the sponsoring body approves the design and the identity, and participants confirm their own content. Treat those as three separate tracks with three separate deadlines.

The sequence that works is to freeze the shared design first and let participants work inside it, rather than collecting participant requirements and trying to reconcile them afterwards. Reconciliation after the fact is how pavilions lose their coherence and their schedule at the same time.

Build the fabrication window in properly. A pavilion is a large build by definition, which puts it in the five-week bracket from sign-off, and the organiser's drawing approval cycle sits in front of that rather than inside it. Where the pavilion includes a structural element such as a double-height entrance, add the engineer's certification cycle as well.

Freeze the shared design first and let participants work inside it. Collecting everyone's preferences and reconciling them afterwards is how a pavilion becomes a row of booths.

On the show floor

A pavilion needs running, not just building. Someone has to own the shared reception, keep the stage schedule moving, manage meeting-room bookings and walk the pavilion keeping booths tidy. Without that role the shared spaces decay by the second day and the pavilion reverts to a row of stands.

Give participants something to do together. A published demo schedule on the shared stage, with each participant taking a slot, gives every booth a moment in front of an audience and gives visitors a reason to stay inside the pavilion rather than passing through it.

Collect leads centrally as well as individually. A pavilion that can tell the sponsoring body how many visitors it handled, which sectors they came from and which participants they met has made the case for next year's pavilion, which is a large part of why pavilions exist.