A multilingual session can fail long before the speaker reaches the stage. The usual cause is not interpretation quality. It is a booth receiving the wrong deck, an old version, or no visual reference at all. This interpreter booth workflow guide sets out a practical handoff process for AV teams, speaker room staff, and language teams that need slides in the booth when they matter.
The objective is simple: interpreters should see the same presentation the audience sees, with enough advance notice to prepare terminology and enough operational control to handle last-minute changes. That requires a workflow built around roles, room assignments, versions, and confirmation - not a chain of USB drives, email attachments, and verbal promises.
Start with the booth's real requirement
An interpreter booth does not need every file collected for an event. It needs the correct visual reference for the session currently being interpreted, delivered to the correct language position or booth display in time to be useful.
That distinction changes the workflow. A speaker's PowerPoint file may be useful in advance for preparation, but on show day the booth also needs a reliable live view of the deck being played. If the presenter replaces slide 18 five minutes before the session, the booth needs to know whether that change reached the room operator and whether its own reference is current.
Treat these as two related but separate needs:
- Preparation materials give interpreters time to research names, acronyms, product language, and technical terminology.
- Live slide synchronization gives interpreters visual context during delivery, including slides added or changed at the last minute.
Some events need both. A policy congress with dense terminology may require decks well before the session. A fast-moving corporate meeting may have little usable material until speakers arrive. Your process should support either case without turning the booth into another uncontrolled file destination.
Define ownership before files arrive
The fastest way to create confusion is to make everyone responsible for slide delivery. Assign a clear owner at each handoff point.
The speaker room team owns intake, file checking, naming, and routing. The room operator owns playback from the approved show machine. The interpretation coordinator or booth lead owns confirmation that interpreters have the material or display they need. The production manager owns escalation when a change affects timing, routing, or session readiness.
This does not need a long procedure document. It needs a shared operational rule: a file is not considered delivered because someone sent it. It is delivered when the intended destination confirms receipt and the version is identifiable.
For multi-room programs, assign rooms in the system rather than relying on filenames alone. A deck called “Keynote Final Final 2” is not operational information. A deck assigned to Tuesday, 10:30 a.m., Main Ballroom, Session 4, with a named speaker and version timestamp is.
Use one source of truth
Speaker room staff should receive files into one controlled intake point. From there, materials are checked and distributed through the event network to the relevant operator and, where required, the interpreter booth.
Avoid parallel routes. If a speaker emails the interpreter directly, hands a USB drive to the AV technician, and uploads another copy to a shared folder, no one can confidently say which version is live. Direct communication may still be necessary for terminology questions, but presentation distribution needs one controlled path.
Purpose-built event software such as Kondukto can support this model by routing files over the local LAN according to agenda and room assignment, while keeping speaker room and technical teams on the same operational record. The key benefit is not file transfer alone. It is knowing where the file went and which session it belongs to.
Build the workflow around session status
A file name cannot tell a booth whether a deck is ready for use. Status can.
Create a small number of statuses that reflect real event decisions: received, checked, routed, booth available, live approved, and superseded. Keep the language plain enough that speaker room staff, AV operators, and interpretation coordinators read it the same way.
“Received” means the file has arrived, nothing more. “Checked” means the file opens, media has been reviewed as appropriate, and the basic session assignment is correct. “Routed” means it has reached the designated room operator or booth destination. “Live approved” means the operator has confirmed the version intended for playback.
The booth should not assume that every routed deck is live approved. A presenter may still be revising slides, or an operator may be waiting for a font, video, or embedded media check. Showing a clear status prevents interpreters from preparing against a draft that will be replaced on stage.
For high-profile sessions, add a time-based cutoff. For example, materials received more than 30 minutes before start can be checked and shared for preparation. Changes inside the final 10 minutes should trigger a direct notification to the room operator and booth lead. The exact window depends on program pace, number of rooms, and the complexity of media, but the escalation rule should be fixed before doors open.
Route by room, not by memory
In a multi-room venue, manually forwarding each deck to each booth creates avoidable risk. A busy speaker room may process dozens of files per hour. One incorrect recipient can leave a booth following the previous speaker's slides while the room plays a new deck.
Route materials by agenda item and room. The schedule becomes part of the technical workflow, not an isolated planning document. When a session moves rooms or a breakout is added, update the routing assignment first, then verify the destinations.
This approach also matters when multiple sessions have similar titles or the same speaker appears twice. A room-based workflow gives the operator and booth a shared context: the deck belongs to this session, in this room, at this time. That is more dependable than asking a technician to remember which “Leadership Update” is the one scheduled after lunch.
Give interpreter booths the right display mode
There is no single best booth display setup. It depends on the event.
For a keynote with tightly produced graphics, a direct live slide feed is usually the best option. Interpreters can follow the exact visuals presented to the audience, including animations and late changes. For a breakout with static slides and extensive terminology, advance access to the deck may be equally valuable.
If video playback is part of the session, test what the booth will actually receive. A slide preview may not provide audio, embedded video playback, or presenter notes. Do not describe a preview as a complete program feed if it is not one. The language team needs to know whether they are working from slides only, a program return, or both.
Treat last-minute changes as a controlled exception
Late changes are normal. Uncontrolled late changes are the problem.
When a revised deck arrives, the speaker room should register it as a new version rather than silently replacing the existing file. The room operator needs a visible indication that a newer file exists. The booth lead needs confirmation of whether the revised version is now the live reference.
A practical change call includes three facts: the session and room, what changed, and whether the room operator has loaded it. “New deck for Hall B” is incomplete. “Hall B, 2:15 p.m. panel: revised deck received, two slides added after slide 12, operator loading now” gives the booth a usable decision point.
Do not force every small edit through a full approval cycle if time is short. A corrected logo may not need the same response as a reordered presentation or a new compliance slide with unfamiliar legal language. The trade-off is speed versus certainty. Define which changes require booth notification, and make that rule consistent.
Test the workflow before the first session
A network connection alone is not proof that the workflow works. Run a real test from speaker room to operator to booth display using the devices, room assignments, and network that will be used on show day.
Check that the correct devices are visible on the local LAN, the assigned room receives the intended file, and the booth can identify the presentation without opening several similarly named files. Then test a revision. Replace a deck, notify the destination, and confirm that the room and booth can distinguish old from current.
Also test the failure path. If a booth device disconnects, who notices? If a room is reassigned, who changes the routing? If a speaker arrives with a video file that cannot play from the show computer, how is that issue communicated to the booth? These are not edge cases at a live conference. They are the work.
Keep a local fallback for critical sessions, but do not let the fallback become the everyday process. A printed running order, a direct contact path to the booth lead, and a verified backup display feed can protect the program. USB drives passed between departments cannot.
Keep the booth in the operating picture
Interpreter booths are often treated as a downstream recipient of presentation files. In practice, they are part of the live production chain. They notice missing context quickly, and their work depends on timely, accurate visual information.
Include the booth lead in the relevant session communications, especially for keynotes, executive presentations, technical demonstrations, and sessions with late editorial changes. They do not need every speaker room message. They need the information that affects interpretation: new terminology, significant slide changes, session order changes, and the confirmed live deck.
A good booth workflow is quiet when the program is running. No USB chase, no search through inboxes, no question about which deck is on screen. Build that quiet into rehearsals, routing, and confirmations, and interpreters can focus on the work only they can do.