Conference planning guide

How to Plan a Multilingual Conference in Jordan

A practical checklist for teams planning interpretation, conference technology, AV and hybrid participation as one event system.

8 min read

By the Linguative editorial team · Prepared 7 October 2026 · Reviewed 10 October 2026

1. Start with the language flow, not the equipment list

Before choosing equipment, map who will speak which language and who needs to hear which language. Identify the working languages, whether interpretation is one-way or two-way, and whether every participant needs access to every language channel.

This first decision determines whether you need simultaneous interpretation, consecutive interpretation, or a mix of both.

  • Working languages
  • Speaker languages
  • Audience languages
  • One-way or two-way interpretation
  • Parallel sessions or a single room

2. Choose simultaneous or consecutive interpretation based on the meeting format

Simultaneous interpretation is generally suited to conferences, formal panels and larger multilingual events where the speaker should continue without pauses. Consecutive interpretation is usually better for smaller meetings, negotiations, trainings and site visits where a direct exchange is more important than continuous delivery.

The right format is a programme decision, not just a budget decision. Using consecutive interpretation in a dense conference agenda can substantially extend speaking time because the programme must allow for interpretation pauses; using simultaneous interpretation for a small discussion can add unnecessary infrastructure.

3. Design the interpretation system around the room

For simultaneous interpretation, the booth, interpreter position, conference microphones, language distribution and room sound need to work as one chain. The interpreter must receive a clean source signal and the audience must receive the interpreted channel reliably.

The exact equipment depends on the room and audience, but the planning conversation should cover booths, interpreter consoles, delegate microphones, participant receivers and headsets, sound reinforcement and technical monitoring.

4. Treat AV and interpretation as one technical system

Screens, cameras, playback, microphones and interpretation should not be planned by separate teams in isolation. A panel microphone affects what the interpreter hears. A remote presenter affects what the room hears. A camera feed affects what online participants see.

A single run-of-show should identify who controls microphones, presentation playback, video calls, interpretation channels, cameras and recording.

5. Plan hybrid participation before event day

If remote speakers or online participants are part of the event, define how their audio will enter the room, how they will hear the interpreted output, and whether they need to participate in Q&A.

Hybrid events work best when remote participation is treated as part of the conference design from the beginning rather than added as a separate livestream at the end.

6. Share the programme early with interpreters and technicians

Interpreters benefit from agendas, speaker lists, presentations and terminology before the event. Technicians need the programme to understand room changes, panel transitions, video playback, remote speakers and recording requirements.

Even a simple final run-of-show can prevent avoidable problems because it gives everyone one operating sequence.

7. Test the full chain, not individual devices

A microphone can work, a booth can work and a receiver can work independently while the complete interpretation path still fails. The important test is the end-to-end chain: speaker microphone → interpreter feed → interpreted channel → participant receiver or room output.

For hybrid events, add the remote participant path and recording or livestream path to that test.

8. Prepare the right information before requesting a quote

A clear brief makes the quotation more accurate and reduces unnecessary back-and-forth.

  • Event date and venue
  • Working languages
  • Expected audience size
  • Number of rooms
  • Event format: in-person, hybrid or virtual
  • Interpretation format
  • Programme or agenda
  • AV and recording requirements
  • Remote speaker requirements
  • Any existing venue equipment

An example from our work in Jordan

Expertise France assignments in November 2021 covered justice-sector sessions in Irbid and Amman, including interpretation, participant systems and hybrid Zoom camera support. This scope illustrates why language, room technology and remote participation should be planned together.

Read the assignment details ↗

Checklist

Multilingual conference planning checklist

  1. 01Languages and interpretation direction confirmed
  2. 02Simultaneous vs. consecutive format selected
  3. 03Room and booth position reviewed
  4. 04Conference microphones and sound planned
  5. 05Receivers/headsets and language distribution planned
  6. 06Remote speakers and hybrid workflow defined
  7. 07Cameras, screens and playback responsibilities assigned
  8. 08Programme shared with interpreters and technical team
  9. 09Full technical rehearsal scheduled
  10. 10One run-of-show shared across the operating team

Frequently asked questions

What is the first thing to decide for a multilingual conference?

Start with the language flow: who speaks which language, who needs to hear which language, and whether interpretation is simultaneous or consecutive.

Do interpretation and AV need to be planned together?

Yes. Microphones, room sound, interpreter feeds, remote speakers, cameras and recording are connected parts of the same live system.

When should the technical test happen?

The full signal chain should be tested before participants enter the room, with additional rehearsal time for hybrid events or complex programmes.

What information should I send when requesting a quote?

Send the event date, venue, languages, audience size, number of rooms, programme, interpretation format and any AV, recording or hybrid requirements.

Start with the brief

Plan your multilingual project with one team.

Request a quote