Venue coordination: rooms, capacity, and the AV problem

Every event has a moment where someone realises the room change from Tuesday didn't make it into the AV brief. The venue team is setting up for a panel discussion. The schedule says it's a keynote with slides. The floor plan still shows the old room assignment. Three documents, three versions of reality, zero alignment.

This is the venue coordination problem, and it's not a people problem. It's a tools problem.

Three sources of truth is zero sources of truth

Here's how venue logistics typically work. The venue sends a PDF with room specs. Someone puts that into a spreadsheet. The schedule lives in a different tool (or a different spreadsheet). AV requirements get captured in emails, or a shared doc, or sometimes just verbal conversations during a site visit.

When a room changes — and rooms always change — three things need updating. The schedule needs the new room. The floor plan needs the new layout. The AV brief needs the new tech spec. In practice, one or two of those get updated. The third gets missed. You find out during bump-in.

The fix isn't "be more careful." The fix is linking these things together so a change in one place propagates everywhere.

Rooms connected to schedules, connected to floor plans

In ema, rooms aren't just labels on a schedule. They're objects with properties — capacity, AV equipment, layout configuration — that connect to the floor plan and the session schedule.

When you assign a session to a room, the schedule knows the room's capacity. When you move a session to a different room, the floor plan updates. When the venue confirms a room change, you update it once and everything downstream reflects it.

This sounds obvious, and it is. The reason most teams don't have it is that their schedule tool, floor plan tool, and venue communication tool are three separate products. Connecting them would require custom integrations that nobody has time to build.

Capacity tracking that prevents problems, not just reports them

Overbooking a room is one of those mistakes that's easy to make and painful to fix. You've got a 300-person room and three concurrent sessions. Two have 80 registrants. One has 250. If nobody's tracking capacity against registrations, you won't know until people are standing in the corridor.

ema tracks registered attendees against room capacity at the session level. When a session is approaching capacity, you can see it before the event — not when the fire marshal gets involved.

With QR check-in at the room level, you also get real-time capacity data during the event. That's useful for more than compliance. It tells you which sessions are drawing, which rooms are underutilised, and whether your post-event attendance reports are based on actual scans rather than registration numbers that don't account for no-shows.

AV requirements per session, accessible to the venue team

AV is where things fall apart most often. The speaker needs a lapel mic and screen share. The panel needs four handhelds and a confidence monitor. The workshop needs breakout audio. These requirements vary per session, and they need to reach the venue's AV team in a format they can actually use.

In ema, AV requirements are captured per session — not per room, per session. A room might host a keynote in the morning and a workshop in the afternoon. Different AV needs, same room. When session details change, the AV requirements stay attached to the session and update accordingly.

The venue team gets access to this information directly. No intermediary spreadsheet. No "I'll send you the updated AV brief by Friday" email that arrives on Monday.

Task management for venue operations

Venue logistics involve dozens of tasks that are specific to physical spaces. Signage needs printing and placing. Catering needs room-by-room headcounts. Setup crews need room configurations and timing.

Generic project management tools handle tasks fine. They don't handle tasks that are linked to rooms, sessions, and timelines in a way that makes sense for event production. In ema, tasks can be tied to specific rooms or venue areas, assigned to team members, and tracked alongside the rest of the event operations — not in a separate tool that nobody checks after the first week.

The pattern

Venue coordination breaks down when information is spread across disconnected tools. The schedule says one thing, the floor plan says another, and the AV brief says a third. The solution isn't a better spreadsheet or a more disciplined team. It's having venue data, schedule data, and operational data in the same system, connected at the data level.

That's what ema does. Not because venue logistics are glamorous, but because they're where events go wrong when the tools don't talk to each other.