The first talk ends and an attendee approaches reception. They could hear the speaker but could not follow the presentation. The programme promised translation; nobody explained which link to open, which language their room offered or that they needed headphones. The service was ready, yet it never reached that person.

Planning live translation for a congress means matching every programme block to a source language, target language, audience and operator. Then test the full route from the speaker’s microphone to the attendee’s phone or receiver. Choose technology and budget after defining those requirements.

This guide covers an in-person congress with presentations and questions. It includes a planning matrix and a MoriahTech IA capacity example. If you need professional interpreting, the same preparation helps you request a specific proposal.

Each language uses minutes: one hour in two languages uses 120 minutes. All channels share the service audience limit. Event, Conference and Congress include 2, 3, 4 languages respectively and one active source. Extra language slots cost €19 per month on monthly plans only, up to four languages in total, and add no minutes or listeners. A pending request does not activate capacity.

Define what translation will cover

List speakers’ languages and ask registrants what they need to follow the content. Do not infer language preferences from nationality. Some attendees may understand a talk and still need help asking a question.

Specify coverage: main-stage presentations, panel discussions, workshops or some combination. A listening service for a presentation does not automatically handle a conversation among several speakers.

Decide what attendees will receive: human interpretation through receivers, translated voice on phones, subtitles or a prepared combination. See event translation for the MoriahTech IA route: the organiser manages the session and attendees open a QR code or link for voice and subtitles in a browser.

For remote attendees, validate a separate route with the hybrid events guide. A successful room test does not prove online coverage.

Build an agenda matrix before requesting a quote

The following is a production template. Its schedule and figures are hypothetical, not customer data.

Scroll the table to see every column.

Build an agenda matrix before requesting a quote
Block Source → target Expected listeners Duration Responsible team
Opening, main room English → Spanish 180 45 min Main production
Presentation, main room English → Spanish 180 60 min Main production
Panel, main room Spanish → English 35 45 min Operator and moderator
Workshop, room B, parallel to the panel English → Spanish 40 60 min Room B operator

In your actual document, add start times, listening links, microphones and support for questions. Make language changes and overlapping blocks visible.

This example adds up to 210 planned translation minutes: 45 + 60 + 45 + 60. The panel and workshop overlap, so you need two concurrent sessions during that period. Available minutes alone are insufficient.

The table does not automatically determine session count. If you group blocks, verify configuration and combined duration. If you create separate access sessions, count each one. Rehearse language changes rather than assuming the system will detect and reorganise them automatically.

Decide where AI fits and where interpreters are needed

A talk with one main voice, a defined language direction and reviewed content offers a starting point for an AI trial. A panel with interruptions, local jokes and frequent language changes needs different preparation.

Consider the importance of each nuance and the consequences of a misunderstood phrase. Where errors could have significant consequences, arrange professional interpreting and agree its scope with the provider. Cost per minute should not be your only criterion.

Different blocks can use different services if attendees know how to join each one. One room might have professional interpretation while another uses previously tested AI translation. This needs production coordination; it does not imply automatic integration between systems.

The human, remote and AI interpretation comparison covers selection criteria. Use the multiple-room translation guide for the technical arrangement of overlapping rooms.

Prepare speakers and moderators

Request a representative rehearsal sample with names, acronyms and a figure from the presentation. Record what a bilingual reviewer should check. Do not assume the platform offers glossary uploads or slide imports.

The European Commission’s speaker guidance recommends a reasonable pace and clear delivery of names and numbers when working with interpreters. It concerns human interpreting rather than certifying AI; clarity also informs our proposed rehearsal.

Rehearse questions with the moderator. Audience speech must reach the input: a question audible in the front row may be absent from the translation feed. Let translation finish before moving to the next turn.

If someone asks in Spanish during an English → Spanish session, an English-speaking presenter needs another way to understand the question. Arrange bilingual help or a validated return route. A listener’s QR code does not guarantee automatic two-way conversation.

Budget against five separate limits

Bring the matrix and check each limit:

  1. Total minutes. Add planned audio across all sessions, including overlapping ones, and allow for rehearsal and overruns.
  2. Session count. Count separate sessions according to the actual setup; one day can need several.
  3. Duration per session. Check the longest continuous block or combined grouped blocks.
  4. Listeners per session. Count people needing that target in that room, including changes between blocks.
  5. Concurrency. Check how many translations must operate at the same time across rooms and language requirements.

The current Conferencia pack costs €149, with 1200 minutes, up to three sessions, 250 listeners per session, up to four hours per session and one concurrent session. The example’s 210 minutes fit its balance, but the parallel block requires two concurrent sessions. The pack does not cover that requirement.

The Congress pack costs €399, with 3600 minutes, up to six services, four included language channels, 400 shared listeners per service and up to four hours per service. It admits one active source. It does not cover the example’s two parallel rooms: change the timetable or discuss a specific operation. Remaining minutes do not enable another source.

Both packs are available for three months after activation. Creating an account does not activate a pack: request, payment and validation are required. Confirm the current event conditions against the full programme before purchasing. Validate technical and commercial configuration with the team for simultaneous language targets.

Test the attendee’s route as well as the microphone

Bring production, a speaker or stand-in and two listeners, including a bilingual reviewer. Use the venue’s audio and network where possible.

  • Open public access on a phone without the organiser’s account and start audio with headphones.
  • Listen from different seats and check a figure and the main idea.
  • Move between presenter, moderator and audience microphones.
  • Rehearse changing rooms: identify the target language and the correct link.
  • Agree incident support and what to announce if translation must stop.

Two phones can validate the route, but do not certify the network at full attendance. Coordinate capacity with the venue and use the translation WiFi test.

Explain access before the doors open

Tell registrants the available language and whether they need a phone, connectivity and headphones. In the room, show the public QR code or link with the programme block and target language. Announce access changes before the next talk.

Adapt and review this instruction in the audience’s language:

In the main room, you can follow the listed English presentations in Spanish on your phone. Bring headphones and a charged battery. Open the block’s listening link and start audio before the talk. For questions, wait for the microphone and moderator. When changing rooms, check the new link and language. Reception will help you join.

Keep private operating links within the team. Reception should be able to explain public access without using the organiser’s credentials.

Validate one presentation before choosing coverage for the congress

MoriahTech IA’s 14-day trial without a card includes 180 total minutes, three sessions, up to 120 minutes per session, 25 listeners per session and one concurrent session. Its technical check of up to five minutes uses minutes without counting as a session. It lets you assess a sample; it does not cover the example’s audience or parallel sessions.

Start with a presentation with a defined language direction. Check joining, comprehension and one question. Then take the results and your matrix to the capacity selector. A tested attendee route gives you a clearer basis for deciding.

Create my account and rehearse a congress presentation.