# Meeting notes when the room doesn't share a first language

> Practical advice for freelancers and consultants whose client meetings on Google Meet or Microsoft Teams bring together people with different first languages, from Montreal and Madrid to Beirut, London and Dublin: agreeing the language of the written record, keeping names and technical terms as spoken, confirming numbers and dates in writing, sending minutes the same day and flagging uncertainty. Then how TrackHeros helps.

Canonical: https://trackheros.com/blog/meetings-without-a-shared-first-language/  
Author: Sami Kanafani  
Updated: 2026-10-22

**In short:** In a meeting where people do not share a first language, agree with the client which language the written record is in, keep names and technical terms as spoken, confirm numbers and dates in writing, send the minutes the same day and flag what you were unsure of. TrackHeros helps on Google Meet and Microsoft Teams by detecting each meeting's language and writing the notes in the language agreed with the client.

| Fact | Detail |
| --- | --- |
| Language setting | None needed. The language is worked out from each meeting |
| Notes language | Set per client: English, Arabic, French, Spanish, German, Italian, Portuguese, Ukrainian or Indonesian |
| Minutes | Per-client template, exported as PDF or copied for email |

When the people in a meeting do not share a first language, the notes have to do more work than usual: they become the version everyone can check afterwards, in a language everyone has agreed on. The practical rules are short. Agree the language of the record, keep names and terms as spoken, confirm numbers and dates in writing, send the minutes the same day, and say what you were not sure of. This guide is for freelancers and consultants whose clients are spread across places like Lebanon, the Gulf, Spain, the UK and Ireland, or whose client teams mix languages, on Google Meet or Microsoft Teams. How TrackHeros handles it, with [automatic language detection](/features/automatic-language-detection/) and notes in the language you agree, is at the end.

## Which language should the written record be in?

The one you agree with the client, once, at the start. Ask on the kickoff call which language the minutes should be in and who reads them, then put the answer in your first email so nobody has to remember it.

The answer is not always the language most spoken in the meetings. A team may talk to each other in Spanish while the person who approves invoices reads English most comfortably. A client in Dublin may have engineers elsewhere who follow English more easily on the page than on a call. The person who signs off the work matters more than the person who speaks most.

Two things are worth settling at the same time:

- **One record or two.** If someone needs the minutes in a second language, agree who produces that version and which one counts if they disagree. One authoritative version saves arguing over translations later.
- **Quotations.** In a translated record, quotation marks around translated words put a sentence in someone's mouth that they never said in that form. Paraphrase decisions, and quote only when the exact wording was agreed in the record's own language.

## How should you handle names and technical terms?

Keep them exactly as spoken. Product names, system names, ticket ids and terms like "staging", "pull request" or "deploy" stay in the form the team uses, even when the rest of the sentence is in another language. A translated term is one nobody searches for, and it can make a familiar system unrecognisable to the people who run it.

People's names deserve particular care. Names that come from a language with another script, such as Arabic or Russian, have several common spellings in Latin letters — Mohammad, Mohamed, Muhammad — and the right one is the one in the person's email signature, not the one a transcript chose. Company names are the same: use the client's own spelling, capitals included.

Keep a short glossary per client: people, products, internal acronyms, the system everyone calls by a nickname. Check every set of notes against it before it goes out. It is the cheapest accuracy improvement there is, and it carries over from one meeting to the next.

## How do you make sure numbers and dates mean the same thing to everyone?

Confirm them in writing, in a form nobody can read two ways. Numbers and dates are where mixed-language meetings go wrong quietly, because each person hears them in their own conventions and nobody realises there was a difference until the invoice.

| Trap               | What was said                             | Write instead                              |
| ------------------ | ----------------------------------------- | ------------------------------------------ |
| Date order         | "05/10"                                   | 5 October 2026                             |
| Relative days      | "next Thursday", said on Monday 5 October | Thursday 8 October, or Thursday 15 October |
| The working week   | "by the end of the week"                  | A date and a day                           |
| Decimal separators | "1,5 jours" in French                     | 1.5 days                                   |
| Currency           | "the budget is four thousand"             | 4,000 USD, or whichever currency was meant |
| Time zones         | "call at ten"                             | 10:00 London, 12:00 Beirut                 |

The working week deserves its own line because it is not the same everywhere: in several Gulf countries the weekend falls on Friday and Saturday, so "end of the week" can mean Thursday. Clocks are another quiet trap. The Gulf states do not change their clocks, and the UK and Ireland do, so a standing call between Dubai and London moves by an hour for one side every March and October.

The simplest habit is to read the numbers back at the end of the call in the record's language: "So that is one and a half days, four thousand dollars, Thursday the fifteenth." It takes twenty seconds and catches most misunderstandings before they are written down.

## Why send the minutes the same day?

Because the people following in their second language rely on the written record most, and a same-day email lets them correct it while they still remember the meeting. A week later, a wrong number in the minutes has become the agreed number.

Same-day minutes also set the pace of the work. The client reads them while the decisions are fresh, action items have owners before anyone starts forgetting, and the next meeting starts from one shared page rather than from two memories in two languages. Use the same headings every time — summary, decisions, action items with owners and dates — so a reader in their second language knows where to look without reading every line. The [client meeting minutes template](/blog/client-meeting-minutes-template/) works whatever tool you write them in.

## How do you flag what you were not sure of?

Say so in the minutes, next to the line, and ask. "Delivery is Thursday 15 October (to confirm: I heard 'next Thursday')" costs the reader five seconds and saves an argument. Smoothing over a line you half heard is how a misunderstanding becomes a commitment.

Three kinds of line deserve a flag: a number or date you could not hear clearly, an action item where you are not sure who took it on, and a sentence that changed language at the point that mattered. If your notes come from a transcript, a line attributed to an unknown speaker is one to check against the recording, not one to guess. End the email with a short "please correct anything I have got wrong". It invites the corrections you want, in writing, from the people who know.

## How does TrackHeros help in a mixed-language meeting?

TrackHeros works out the language of each meeting on its own and writes the notes in the language you agreed with the client. Nothing has to be set: you invite the bot to a Google Meet or Microsoft Teams call, and the rest happens afterwards.

- **Detection per meeting.** The platform captions give the real speaker names. A meeting in a language other than English, or in more than one, gets a second pass over the recording by a Whisper model that hears the language spoken, and each line is rendered into English keeping its speaker and timestamp.
- **Notes in the record's language.** The summary, decisions and action items are written in English, or in Arabic, French, Spanish, German, Italian, Portuguese, Ukrainian or Indonesian, set once per client so the record's language is the one agreed at kickoff. The transcript stays in English and carries one line saying where it came from: "Translated to English from a conversation held in French".
- **No guessed speakers.** A line that cannot be attributed is labelled "Unknown". Action items carry the owner's name as heard and a due date kept verbatim ("end of next week") alongside the date it resolves to.
- **Minutes you can send.** The notes go into the client's [minutes template](/features/meeting-minutes/) and come out as a PDF or through "Copy for email", with headings and dates in the notes language, ready for the same-day send.

Close to 100 spoken languages are recognised, and [the languages page](/languages/) lists them. The checks above still apply: read names, numbers and dates against the recording before the minutes go to the client. For a meeting held entirely in another language, see [how to get notes in English, or in your own language, from a meeting in another language](/blog/english-notes-from-a-meeting-in-another-language/).

## Not yet available

- A transcript kept in the language spoken, rather than rendered into English — not yet available

## Frequently asked

**Which language should meeting notes be in when the team speaks several?**

The one the client agrees to, decided once at the start of the engagement and written down. Usually that is the language the decision-makers read most comfortably, which is often but not always English. Ask rather than assume, because the person who signs off the work may not be the person who talks most in meetings.

**Should technical terms be translated in meeting notes?**

No. Keep product names, system names, ticket ids and terms like staging or pull request exactly as the team says them. A translated term is one nobody will search for, and it can make a familiar system unrecognisable to the people who run it.

**How soon should minutes go out after a multilingual meeting?**

The same day. People following a meeting in their second language rely on the written record more than anyone, and a same-day email lets them correct a misunderstanding while the conversation is still fresh.

**Can TrackHeros write the notes in French or Spanish?**

Yes. The notes can be written in English, Arabic, French, Spanish, German, Italian, Portuguese, Ukrainian or Indonesian, and the choice is set per client, which is where the language of the record belongs. A recurring meeting or a single call can differ from its client.

**Does TrackHeros need to be told which languages the team speaks?**

No. Nothing has to be set. Each meeting's language is worked out from the meeting itself on Google Meet and Microsoft Teams, and a meeting in a language other than English, or in more than one, gets a second pass over the recording. Listing the languages a client speaks is optional; if you list them, list all of them.

---

TrackHeros is in early access: https://trackheros.com/#early-access