How to get meeting notes in English, or in your own language, from a meeting held in another language

If a client meeting is held in French, Spanish or another language and the notes need to be in English, the reliable route is to transcribe the meeting in the language it was spoken, translate the transcript into English one line at a time, and only then write the notes. In that order every sentence stays attached to the person who said it and the moment they said it, so anything in the notes can be checked. This guide is for freelancers and consultants whose client calls happen on Google Meet or Microsoft Teams in a language other than English. The advice works with any notetaker; how TrackHeros does it, with automatic language detection and nothing to set — including notes written in the client's language instead of English — is at the end.

Should you translate the transcript or write the notes straight in English?

Translate the transcript first, then write the notes from the English. Writing English notes directly from a French or Spanish transcript asks one step to do two jobs, compressing and translating, and when something comes out wrong you cannot tell which job broke it.

Notes are a lossy summary by design. A decision that took ten minutes to reach becomes one line. That is fine when the summary and its source are in the same language, because anyone can open the transcript, find the discussion and check the line. When the source is in another language, checking means reading French to verify English, which most readers of the notes cannot do and which you will not do at seven in the evening.

A translated transcript removes that step. The notes and their source are in the same language, anyone can check the summary against it, and the translation itself can be checked against the recording where it matters.

There is one case for writing the notes directly: a short call, in a language you read well, where nothing was decided. For anything with commitments, dates or money in it, translate first.

Why does line-by-line translation beat translating a wall of text?

Because a wall of text has lost the two things a meeting record needs: who said each sentence, and when. Paste a whole transcript into a translation tool and you usually get back fluent paragraphs with the speaker labels merged, sentences reordered for style and the timestamps gone.

Translating each line on its own keeps three things intact:

Kept per line	Why it matters
The speaker	An action item belongs to the person who said "I'll do it", not to whoever the paragraph seems to be about
The timestamp	You can jump to that moment in the recording and hear the original
The boundary	A sentence that translates badly fails on its own, without dragging its neighbours with it

The cost is some stiffness. A line translated alone does not borrow context from the line before, so a pronoun can come out vague: "he said it would be ready" — who? That is a fair price. Stiff and traceable is worth more than smooth and unverifiable, especially for the lines that end up as action items.

What should you check in a translated transcript?

Check four things before the notes go anywhere: names, numbers, dates and technical terms. These are the words a translation is most likely to change, and the words a client is most likely to quote back to you.

1. Names. People, companies and products should come out exactly as spoken. A surname or product name that happens to be an ordinary word in its own language is the one most likely to be translated by mistake. Names that come from a language with another script, such as Arabic, Russian or Hindi, have several common spellings in Latin letters — Mohammad, Mohamed, Muhammad — so use the one the person uses in their own email signature.
2. Numbers. French writes one and a half as "1,5" and groups thousands with a space, as in "10 000". Read every figure against the recording, and write the currency next to every amount. These are the lines that end up in a quote or an invoice.
3. Dates. "05/10" is 5 October in Beirut, London or Dublin and 10 May in the United States. Relative dates are worse: "jeudi prochain" said on a Monday can mean this Thursday or the next one. Resolve every date to a day and a month in the notes.
4. Technical terms. "Staging", "deploy", "pull request" and ticket ids should stay the way the team says them. A translation that keeps "le ticket PROJ-142" as ticket PROJ-142 is right; one that turns the client's product name into a common noun is not.

Then read the lines that became decisions or action items against the recording. Negation and hedging live in small words — "on ne peut pas livrer avant jeudi" and "on peut livrer avant jeudi" differ by two of them — and a translation that drops one reverses the commitment.

How do you tell the client which language the notes are in?

Say it at the top of the notes, in one sentence: "This meeting was held in French; these notes are in English." It costs nothing, and it heads off the most awkward reply you can get, which is a client pointing out that they never said the thing in quotation marks.

Three habits make the rest easier:

• Agree it once. At the start of an engagement, ask whether English notes are acceptable or whether someone on their side needs them in French. Most clients who hold meetings in their own language and hire in English are happy with English notes; some have a manager who is not, and you want to know before the first set goes out.
• Quote carefully. Do not put translated words in quotation marks as if they were the speaker's own. Paraphrase the decision, and if the exact wording matters, play the recording at that moment and confirm it with the client in writing.
• Invite corrections. End the notes with "tell me if anything here does not match what you meant". In a second language that line is not politeness; it is how you find the one action item that was translated in the wrong direction.

How does TrackHeros turn a meeting in another language into notes?

TrackHeros detects the language of each meeting from the meeting itself, transcribes it in the language spoken, renders every line into English and writes the notes in English, or in the language you chose. Nothing has to be set: you invite the bot to a Google Meet or Microsoft Teams call, and the language is worked out afterwards. Listing the languages a client speaks is optional.

The steps, in order:

1. Captions first. The bot collects the platform's captions during the call. They give the real speaker names, but Meet and Teams captions listen for one language at a time, so they are a scaffold, not the record.
2. Detection. The language is worked out in stages, cheapest first: a recurring meeting's memory of its language, a check of whether the captions read as coherent text, a short audio sample, then a pass over the recording.
3. The audio pass. A meeting in a language other than English, or in more than one, is transcribed by a Whisper model that hears the spoken language itself; close to 100 languages are recognised.
4. Line-by-line English. Each line is translated on its own and keeps its speaker and timestamp. A line that fails to translate keeps its original text rather than disappearing.
5. The notes. The summary, decisions, action items and minutes are written in English by default, or in Arabic, French, Spanish, German, Italian, Portuguese, Ukrainian or Indonesian, by a model that is told which language the meeting was held in, so it reads the transcript as a translation rather than as the speakers' own words.

On the transcript page, one line tells the reader what happened: "Translated to English from a conversation held in French". That is the only place the transcript mentions language. The original wording is stored with each line but not shown beside the English. Speakers keep their real names from the platform, and a line that cannot be attributed is labelled "Unknown" rather than guessed.

Every language TrackHeros recognises, and the nine the notes can be written in, are on the languages page; they all go through the same steps. If a transcript cannot be read — garbled audio, a recording with nothing usable in it — the summary says "This transcript could not be read reliably" instead of inventing content.

Should the notes be in English or in the client's language?

Whichever language the people who act on them read first. English suits a mixed team, or a client whose managers work in English; the client's own language suits minutes that go to people who read it before English. TrackHeros sets this per client, so one engagement can run in French and another in English, and a single recurring meeting or call can differ from its client. "Same as the meeting" writes the notes in the language the meeting was mostly held in, when that is one of the nine.

What can you do with the notes?

Send them. The notes go into the client's minutes template — heading, colour theme, sections on or off — and come out as a PDF or through "Copy for email", with headings and dates in the notes language. The checks above still apply: read the names, numbers and dates against the recording before anything goes to the client, and when the notes are in a different language from the meeting, add the one sentence saying which language it was held in.

If a client needs French minutes, set French as that client's notes language; the minutes, their headings and their dates then come out in French, and the French page shows what they look like. For rooms where nobody shares a first language, see meeting notes when the room doesn't share a first language, and for how detection decides what each meeting needs, the guide to notetakers that detect the language. Audio for these meetings is processed under terms that exclude training; what is promised about your data is on the privacy section.