Conference Guide

Conference Production
Checklist.

By OnePass · Published October 2, 2026

Conference production is four systems running at once: AVL, the stage and set, registration and accreditation, and attendee flow. Each has its own failure mode, and the three that actually ruin conferences are an unrehearsed cue, a registration queue that outgrows its desks, and a room change nobody sequenced. This checklist covers all four plus the rehearsal day, in the order they have to be decided.

What conference production covers

A conference is not a smaller version of a gala. Its content is the product, which means everything in the room exists to make a person on a stage audible, visible and understood — and to move several hundred people between rooms on schedule, repeatedly, without anyone noticing it was organised.

  • AVL. Audio, screens, lighting, show control, comms, recording and streaming.
  • Stage and set. Structure, scenic, lectern and furniture, backdrop and sightlines.
  • Speaker management. Content collection, technical requirements, rehearsal, and on-the-day handling.
  • Registration and accreditation. Pre-registration, on-site desks, badges, access tiers.
  • Attendee flow. Arrival, plenary seating, breakout transitions, catering, prayer timing, exits.
  • Documentation. Run of show, cue sheet, floor plans, contact sheet.

Exhibitions and conferences sets out how OnePass scopes this as a service; this guide is the planning checklist that sits underneath it.

AVL specification

How do you decide AVL requirements for a conference?

Work from the back row, not from the equipment list. The furthest seat sets screen size and pixel pitch; the room's shape and surfaces set speaker coverage; the number of live sources sets how many control paths you need; and the cost of a visible failure sets how much redundancy you buy. A specification built this way is defensible. One built from a kit list is a guess with a price on it.

  • Screens sized from the furthest seat. Check legibility of the smallest text a speaker will actually use — a dense slide, not the title card.
  • Pixel pitch matched to the closest seat, so the front row does not see the grid.
  • Audio coverage mapped, including under balconies and at the back corners, with delay speakers if the room is long.
  • Microphone plan by role. Lectern, lapel for presenters who move, handhelds for panels, and roaming mics for audience questions — with a spare of each and fresh batteries per session.
  • Lighting that makes faces work on camera, not just a lit stage. If you are recording or streaming, the camera's needs outrank the room's.
  • Translation and language channels decided early: booths, receivers, distribution and who collects them back.
  • Recording and streaming specified with its own feed, its own operator and its own confidence monitor.
  • Redundancy named. Backup show computer, second screen processor, spare console, UPS on control, and a standby generator where the venue supply is the single point.
  • Comms. Radio or intercom channels, who is on each, and a tested backup.
  • Power calculated in kilowatts against the real load, with distribution positions fixed on the plan.

AVL systems covers the specification and operation side in detail.

Stage, set and sightlines

  • Stage height set against the seating, so the back rows see the speaker's full body and the front rows are not looking up at a ceiling.
  • Sightlines checked by sitting down, in the worst seat in the room, before the set is approved.
  • Lectern position and confidence monitor placed so a speaker can read without turning away from the audience.
  • Panel furniture tested for how people actually sit — microphones reachable, no sliding chairs, no low sofas for people in formal dress.
  • Backdrop designed for the camera crop as well as the room, with the logo positioned where a photograph will frame it.
  • Entrances and exits for speakers that do not cross the audience, with steps and a handrail where the stage is high.
  • Bilingual graphics designed in both directions, since Arabic and English change where the eye enters a screen and where the name and title should sit.

Speaker management

Speakers are the one part of a conference you cannot rehearse into reliability by yourself. Treat them as a workstream with deadlines rather than guests who will arrive prepared.

  • Confirmation in writing, with the session, the time and the duration.
  • Content deadline that precedes the rehearsal, not the event — a deck that arrives on the morning has not been tested on the screen it will appear on.
  • Technical requirements collected: own laptop or house machine, video with audio, presenter notes, clicker, demo needs, aspect ratio.
  • Names, titles and spellings verified in both languages, by the speaker, in writing. This is the most common visible error at conferences.
  • Rehearsal slot accepted by each speaker, with a stage walk and a microphone check.
  • Green room and a handler who knows who is on next and where they are.
  • A plan for the speaker who does not arrive, decided in advance: extend the panel, move a session, or run the break early.

Registration and accreditation

  • Desks and staff sized against the arrival peak, not total attendance.
  • Accreditation tiers defined — delegate, speaker, media, sponsor, organiser, crew — with what each can enter.
  • Badge production decided: pre-printed for confirmed delegates, on-demand for walk-ins, with stock and ribbons for both.
  • Offline fallback tested, because venue connectivity fails at exactly the moment four hundred people are standing in front of you.
  • Queue layout drawn on the plan, including where the overflow goes and how it stays out of the entrance.
  • A desk for problems, separate from the main line, so one complicated case does not stop a queue.
  • Lanyard and badge collection at the exit if you are reusing hardware.

Desk arithmetic and arrival curves are covered properly in event registration and attendee management, and the service scope is on event registration and accreditation.

Attendee flow

How do you plan attendee flow at a conference?

Map every movement the day requires, then find the narrowest point in each one. Arrival, entry to the plenary, plenary to breakouts, breakouts to catering, catering back to session, and the exit. The constraint is almost never floor area — it is a door, a corridor, a lift, or a single escalator that everyone reaches within the same two minutes. Widen it, duplicate it, or stagger the movement.

  • Arrival to seat walked end to end by a person, before the day, timing each segment.
  • Plenary-to-breakout transitions staggered, with signage and staff at every decision point, not just at the doors.
  • Catering positioned to pull people away from the session doors, with enough service points that the queue does not become the corridor.
  • Prayer timings built into the agenda, with a room identified and signposted — this is a schedule input in Saudi Arabia, not an accommodation.
  • Accessible routes confirmed, including stage access for a speaker who uses a wheelchair.
  • Signage in both languages at every junction, readable at walking pace.
  • Exit plan for the end of the day, which is the one movement nobody rehearses and everybody experiences.

Crowd and site operations is where the flow planning and the on-the-day stewarding sit.

The rehearsal day

The rehearsal is the cheapest risk reduction available, and it is the first thing cut when the build runs late. Protect it.

  • Every cue run, not described. A cue that has only been discussed is an intention.
  • Every deck opened on the show machine, in the room, at full screen — fonts, embedded video, aspect ratio, transitions.
  • Every microphone tested in position, with the room's doors in the state they will be in.
  • Every speaker who can attend, walking the stage, finding their mark and their monitor.
  • The opening sequence run twice. It is the only moment with no recovery time.
  • A failure drilled: switch to the backup machine, lose the main screen, lose a microphone mid-sentence.
  • Run of show reissued after rehearsal, version-dated, with the changes rehearsal produced.

Show-day control

One person calls the show. Everyone else executes. That single rule resolves most of what goes wrong in a conference room, because the alternative is three people with partial information each making a reasonable decision.

  • A named show caller on comms, with the authority to hold, extend or cut.
  • Printed run of show and contact sheet, because the day you need them the network is saturated.
  • A stage manager with the next three speakers in sight.
  • A decision rule for overruns agreed before the first session: whose time gets absorbed, and who tells them.
  • A quiet position for the client to watch from, briefed not to give instructions to crew directly.
  • End-of-day reset checked if there is a second day — stage, batteries, badge stock, consumables.

OnePass delivers conference production in Saudi Arabia across AVL, staging, registration and site operations as one scope, and states on each service page what it covers and what remains with the client.

FAQ

Conference questions,
answered directly.

What does conference production include?

AVL — audio, screens, lighting, show control, comms, recording and streaming — plus the stage and set, speaker management, registration and accreditation, attendee flow, and the documentation that runs the day. Content, speaker selection and permits remain with the organiser.

How do you choose AVL requirements for a conference?

Size screens from the furthest seat and pixel pitch from the closest, map audio coverage against the room's shape rather than its area, count the live sources to size the control paths, and then decide how much redundancy the cost of a visible failure justifies. The equipment list is the output of that, not the input.

How long before a conference should speaker content be due?

Before the rehearsal, not before the event. A deck that arrives on the morning has never been opened on the machine it will run from, at the resolution it will be shown at — which is where embedded video, fonts and aspect ratio problems appear.

What goes wrong most often at conferences?

Three things: a cue that was never rehearsed, a registration queue sized against total attendance instead of the arrival peak, and a room-to-room transition that nobody sequenced. All three are planning failures rather than equipment failures.

Do you need a rehearsal day for a one-day conference?

Yes, and it is the first thing a late build tries to take. Everything in a conference happens once and in front of everyone, so the rehearsal is where the failures are allowed to happen. Where a full day is not possible, protect a rehearsal window on the build's final evening instead.

Running a conference in Saudi Arabia? Send the venue, the dates and the agenda.

Plan an Event