How to Run a Multilingual Meeting: A Practical Guide

Why multilingual meetings are harder—and how to fix them

When your team speaks different languages, meetings take more attention. People think slower in a second language, miss references they would catch at home, and feel tired faster. The good news: small changes to how you run the meeting make a big difference.

The three changes are agenda clarity, assigned roles, and turn-taking. A translator (human or AI) adds another layer, but it is not the only fix.

Before the meeting: agenda and agenda-setting

A multilingual team needs a written agenda sent 2–3 days ahead. Here is a template.

Meeting: Weekly Retro
Date, time (in two zones): Wednesday 8:00 AM PT / 12:00 AM JST
Duration: 45 minutes
Attendees: [names, who is based where]
Translator: [name or "AI bot Akume joins the call"]

1. Check-in and housekeeping (5 min)
   — Remind: camera on, use raise hand, speak clearly
2. What went well this week (10 min)
   — Austin, then Fukuoka
3. What was hard (10 min)
   — Use the shared doc: list items in the doc before the call
4. Action items from last week (5 min)
5. Next week's priorities (10 min)
6. Close: one word to sum up the week (5 min)

Notes doc: [link] (edit live during the call)
Recording: Yes / No (and who it goes to)
Language of notes: English (with summaries in Japanese if time)

Why this works:

• Written agenda with time stamps tells non-native speakers what to expect and how fast to listen.
• Assigned time per agenda item prevents one person from dominating.
• Assigned regions or people (Austin first, then Fukuoka) keeps turn-taking fair.
• A notes doc captures what is said and lets people contribute in writing.
• A stated translator and language removes guessing.

During the meeting: roles and turn-taking

Assign these four roles. Rotate them each week so no one person carries the load.

Facilitator (1 person): Time keeper, keeps the meeting on track, reminds people to unmute before speaking (if they are on mute). Raises hands for people who type in chat instead of speak.

Scribe (1 person): Writes bullet points in the shared doc as people speak. Adds links, action items, and names. Writes clearly enough that someone reading it later understands.

Translator's partner (1 person, if a human translator is present): Sits next to the translator, relays technical questions, and watches the room to make sure the translation is reaching people.

Timekeeper (same as facilitator): 2 minutes before end of each section, gives a visible signal (hand up, text in chat: "2 min left").

Turn-taking in a multilingual call

The pause rule: After someone speaks, pause for 3 seconds before the next person speaks. Non-native speakers need this to translate in their head and form a reply. If you speak English as a native speaker, this will feel slow. It is not—it is fair.

The raise-hand rule: Use the meeting platform's raise-hand feature or put a marker in the chat (👋). This lets the facilitator manage the order and keeps people from talking over each other.

The one-language rule: Speak in the meeting language (usually English). If you slip into a local language (Spanish at a LatAm meeting, Mandarin at a Taiwan retro), stop, repeat in English, and apologize. The effort signals respect.

Chat for numbers and links: If you share a figure, a URL, or an email, type it in chat. Spoken numbers are easy to mishear. Say "we shipped three releases" and type "3 releases" in the chat.

Speak clearly, not loudly: Avoid:

• Filler words (um, uh, like, you know).
• Acronyms without definition ("Our QA process uses OKRs" means nothing to someone who heard it for the first time).
• Idioms ("Let's not put all our eggs in one basket" does not translate).
• Speaking fast to fill silence.

Clear, slow speech helps both non-native speakers and people on bad internet.

Virtual meeting etiquette for multilingual calls

Camera

• Keep your camera on. Non-native speakers rely on lip-reading, facial expressions, and body language. A black square is harder to understand.
• Frame yourself shoulder-to-shoulder. Make eye contact with the camera, not the side of your own video.
• Light your face, not your screen. Sit facing a window or lamp so people can see you, not a backlit silhouette.

If you are in a loud or messy space, you can leave the camera off for one or two remarks, but come back.

Introductions

At the start of the meeting:

1. Say your name clearly (spell it if it is uncommon in the meeting's language).
2. Say where you are and what time it is for you.
3. Say one sentence about what you hope to get out of this meeting.

Example: "I'm Maya Singh (S-I-N-G-H). I'm in São Paulo, it's 11 PM here. I hope we'll agree on the release date for next quarter."

Names and pronouns

• Ask for the correct pronunciation, and use it.
• If you stumble, say the correct version and move on. Do not apologize repeatedly.
• Ask for pronouns in writing before the meeting if you do not know them. Do not ask people to announce pronouns at the start of the call (this outs transgender people and is not safe).

Humour that doesn't translate

Many jokes, puns, and funny references do not survive translation. If humour is important to your team:

• Use visual humour (a funny image, a cat video).
• Explain jokes after you make them: "That's a pun on the English word 'sprint,' which also means to run fast."
• Ask your team what makes them laugh. Local humour is often good humour.
• Skip sarcasm unless your team knows you well.

When you add a translator: human or AI bot

Introducing a translator

Before the meeting, send a note:

We will have a live translator in this call. [Translator name / "AI bot Akume"] will join as a participant and translate what is said.

What you will see:

• Live captions in the call (all languages, in the meeting platform).
• Spoken translation on a listener link (if the translator is an AI bot).

What the translator will hear:

• Everyone in the meeting. The translator hears English, Japanese, and any code-switching, and translates it all.

Your rights:

• You can ask the translator to skip a topic (e.g., "Please do not translate my comment about personal leave.").
• If you have an accent or speech difference, let the translator know before the call.
• If you are deaf or hard of hearing and rely on captions, the translator will make sure captions are on.

If you have questions, ask in chat or email me.

How a translator works in the call

Human translator (usually in the room or on a side call):

• Sits or stands near the group, listening.
• Raises their hand when they want to add context or clarify something.
• May ask someone to repeat or speak clearly.
• The facilitator manages their turn like any other speaker.

AI bot translator (Akume or similar):

• Joins as a participant, like anyone else.
• Shows live captions in the call in all the languages you selected.
• Does not speak unless you ask it to.
• If listeners open a link outside the call, they hear spoken translation in their language.
• The bot needs to know your language settings before the call starts (this is set up when you paste the meeting link into the translator app).

Accessibility in a multilingual call

Translators help, but accessibility is bigger:

• Captions: Turned on by default. Check that the meeting platform is set to show captions (Zoom, Teams, Google Meet all have this).
• Transcripts: After the call, ask the translator or your notes-taker to produce a written summary.
• Audio descriptions: If you are sharing a screen or a chart, describe it aloud for blind participants ("The chart shows our conversion rate went from 8% to 12% over three months.").
• Accessible links and docs: Shared documents should have alt text on images and clear headings.

Checklists

Before the meeting

• [ ] Agenda sent 2–3 days ahead with times and duration.
• [ ] If using a translator (human or AI), explain it in writing to attendees.
• [ ] Shared doc (Google Doc, Notion) open and shared with everyone.
• [ ] Timezones double-checked (use a tool like Timeanddate.com).
• [ ] Camera tested, lighting checked.
• [ ] Translator (if human) briefed on topic, names, and any sensitive language.
• [ ] Translator app (if AI) has the right meeting link and language pair.

During the meeting

• [ ] Facilitator says: "Camera on, raise hand to speak, we have a translator."
• [ ] Each person introduces themselves, their location, and what they hope for.
• [ ] Facilitator uses the pause rule: 3-second pause after each speaker.
• [ ] Scribe captures action items and decisions in real time.
• [ ] Numbers and links go in the chat, not just spoken.
• [ ] Translator is thanked at the end.

After the meeting

• [ ] Notes doc is cleaned up, formatted, and shared within 24 hours.
• [ ] Action items are clear: who, what, by when.
• [ ] If recording, transcript is made available (use auto-captions or a professional service).
• [ ] Thank the translator (human or AI was important).
• [ ] Reflect on what worked and what did not: plan to change one thing next meeting.

Keep reading

To choose and set up live translation for your next call, start with these guides:

• Video call translator
• Real-time voice translator
• Interpreter or AI: which to choose
• Live translation in Zoom
• Translation in Google Meet

The core rule

Multilingual meetings work when everyone knows the ground rules, feels they will be heard, and has time to think. A translator helps, but a good agenda, clear roles, and turn-taking are the foundation.

Before your next multilingual meeting, pick one thing from this guide and try it. Likely you will find it worth repeating.