How to Run a Multilingual Get-In and Technical Rehearsal

What the multilingual get-in and technical rehearsal must prove

A multilingual get-in and technical rehearsal is the load-in and technical integration period for a production that works across two or more languages. It covers the usual get-in tasks—unloading, assembling the set, rigging, focusing, sound checks and cueing—but adds interpretation, surtitles, translated paperwork, multilingual stage-management calls and, in many cases, a separate listening system for the audience. The practical answer is to treat language as production infrastructure: map who must hear or read what, test every language path with the equipment and signal flow the performance will use, and rehearse the points where language and stagecraft collide.

In a monolingual production, the get-in is mainly a logistics and systems phase, and the technical rehearsal is mainly a cueing phase. In a multilingual production, both phases also test access. The technical rehearsal is not the first time interpreters should see the script, and it is not the first time the stage manager should test a bilingual call. The earlier the language map enters the production schedule, the less the technical rehearsal has to improvise.

Simultaneous interpretation planning begins with the languages people will speak, the languages the audience needs, and the sessions that run at the same time; it then covers preparation, interpreter handovers, workstations, the original audio feed, language paths and listening through receivers or a platform (GLMedia). For theatre, the equivalent is a map of scenes, songs, announcements, videos, curtain calls and front-of-house moments that need to be heard or read in more than one language.

Before the get-in: build a language map and assign ownership

The first deliverable is a language map. It should list the languages spoken onstage, the languages the audience needs, the languages used by crew and creative team, and any relay or pivot languages. It should also identify which parts are interpreted live, which are surtitled, and which are pre-recorded. The map is not merely a translation schedule; it is a listening and reading schedule. A production may interpret the spoken dialogue, surtitle the songs and keep technical cue sheets in two languages, and those choices need to be visible before the get-in begins.

Give each task an owner. A multilingual event fails most often because nobody owns a task, not because the technology breaks; name a host, co-host or producer, interpreter coordinator and technical lead even when one person covers two roles (SmartMeet). In theatre terms, the stage manager usually owns cue calls and show reporting, the production manager or technical director owns get-in and systems, and the interpreter coordinator owns interpreter booking, briefing, handovers and glossary changes. The person who books receivers is not automatically the person who books interpreters, and recording the programme does not automatically capture every language (GLMedia). Those distinctions belong in the production paperwork.

Script and glossary preparation belong in this phase, not the first technical rehearsal. A short preflight should confirm the exact language pairing and lock terminology before the language run; the checklist includes the audio feed, languages, terminology, attendee experience and a glossary lock (PikkaAI). For theatre, the glossary should include character names, place names, songs, recurring metaphors, technical jargon and any words that carry legal or safety weight. Translated paperwork is part of the system too: cue sheets, risk assessments, running orders, character lists and rehearsal notes should exist in the working languages of the people who need them. It is not enough to translate the play text if the crew’s safety briefing and the stage-management running order remain in one language.

Set-up and signal flow: test the get-in as an audio system

During the get-in, test every audio path with the same microphones, mixer outputs, playback devices and network that the performance will use. The rehearsal should use the same microphone and mixer output as the real event and confirm clean speech—not music-heavy, distorted or riding a compressor that pumps (PikkaAI). In a theatre, that means testing stage microphones, radio mics, playback, video sound, talkback, interpreter consoles, transmitters, receivers and, where used, the surtitle or streaming computer. A dry run should set up all equipment exactly as it will be used, check connections, power and compatibility, and test microphone sensitivity, volume and clarity (InterpretCloud).

Interpreters need more than a clean feed. Plan their workstation, sightlines to the stage and monitors, and a reliable way to signal stage management. Interpretation planning explicitly includes workstations, the original audio feed, language paths and listening through receivers or a platform (GLMedia). If interpreters cannot see the action or hear the original, they cannot make timing judgments. The technical rehearsal should therefore test not only whether there is sound, but whether the interpreter can hear the right source, see the right cue and be heard on the right channel. Hybrid or remote contributors add another layer: check that the software integrates with audio consoles and streaming platforms (InterpretCloud).

The front-of-house system needs the same scrutiny. Headsets, receiver distribution, surtitle screens, language-selection instructions and hearing-assistance systems should be tested in the positions where audiences will actually use them. The technical rehearsal should include the audience instruction as a cue: when the welcome is given, how the language options are explained, and who checks that a receiver is working before the performance begins. Multilingual virtual events are advised to show attendees how to choose their language in the first minute (SmartMeet); the theatre equivalent is a clear announcement and a visible, staffed point of help.

The technical rehearsal sequence

A workable sequence is: crew safety and systems briefing in the working languages; audio and interpretation line check; cue-to-cue with language channels live; selected scenes at performance speed; a full technical run with surtitles and interpretation; notes and reset. The exact order depends on the production, but the principle is to move from component tests to integrated runs. A short structured preflight can be compressed into fifteen minutes when time is tight: confirm the feed, validate the exact languages, check terminology and test the audience experience (PikkaAI).

The technical rehearsal should include the moments that only appear when language and stagecraft meet: a quick scene change under a translated announcement; a video with burned-in subtitles plus live interpretation; a curtain call in two languages; a late script change that alters a glossary term. It should also rehearse the handover between interpreters and the point at which a glossary correction is communicated to the booth, the stage manager and the surtitle operator. Interpretation planning calls for agreed preparation and interpreter handovers, not improvised swaps during the performance (GLMedia).

Interpreters should attend at least the integrated run and the notes session. A rehearsal catches wrong language pairing, missing terminology, attendee join friction and absent fallback (PikkaAI). The dry run exists so that interpreters and technical support are fully prepared and equipment is fine-tuned before the event (InterpretCloud). If the production uses a relay, rehearse the relay handover as a cue. If it uses surtitles, rehearse the operator’s cue calls and the point at which the surtitle file is locked.

Notes should be as specific about language as they are about lighting or sound. Instead of writing only that a cue was late, record which language channel was affected, whether the interpreter could see the action, whether the surtitle matched the spoken line and whether the stage-management call was understood by the crew. That record becomes the basis for the next run and for any touring or remounting of the production.

Rehearse failure and access, not only cues

Multilingual technical rehearsals should include deliberate failure tests. Common failures include bad audio, wrong language pairing, attendee join friction, missing terminology and no fallback (PikkaAI). In theatre terms, add a dead radio mic, a dropped language channel, a desynchronised surtitle, an interpreter who cannot hear a video, and a stage-management call that arrives in the wrong language. The fallback should be written down and rehearsed: who switches the channel, who repeats the call, who tells the audience, and which parts of the performance can continue without interpretation.

High-consequence communication needs particular care. The rehearsal checklist does not claim that AI replaces professional interpreters; it recommends human interpreters for high-consequence communication and rehearsal evidence before assigning any channel to AI (PikkaAI). Safety briefings, complex negotiations, sensitive audience interactions and legally significant text should not be treated as a low-stakes test case. The same caution applies to recorded material: recording the programme does not automatically capture every language (GLMedia), so archive and documentation plans need explicit language tracks.

Documentation and handover

At the end of the get-in and technical rehearsal, record the final configuration: channel assignments, cable paths, interpreter positions, receiver or platform settings, glossary version, cue numbers, surtitle file version, contact list and booking responsibilities. The planning guidance is explicit that renting receivers does not automatically include interpreters and that recording the programme does not automatically capture every language (GLMedia). Those distinctions should appear in the production paperwork, not only in conversation. A short handover note for the next performance—covering glossary changes, failed cues and workarounds—prevents the technical rehearsal from becoming a one-off experiment.

A practical checklist

• Build a language map: spoken, audience, crew, relay and recorded languages.
• Name owners for stage management, audio, interpreters, surtitles and front of house.
• Lock a glossary and distribute it before the language run.
• Test the same microphones, mixer outputs, playback and network as the performance.
• Check interpreter sightlines, monitors, talkback and cue signals.
• Run cue-to-cue with language channels live, then a full integrated run.
• Rehearse audience language instructions and headset or surtitle checks.
• Stage failure tests: dead microphone, dropped channel, lost video, late change.
• Record channel maps, glossary version, cue numbers and contacts.
• Hold a notes session with cast, crew, interpreters and the surtitle operator.

None of this removes the ordinary pressures of a get-in. It does make them legible across languages. When the language map, audio path, glossary and fallback are tested together, the technical rehearsal becomes what it should be: a shared proof that the production can be heard, understood and safely run by everyone in the room.