Turning a Thai meeting into actionable minutes

A 40-minute Thai meeting recording is only raw material. Turning it into minutes that people actually read and act on takes a few human checks: how well the meeting was recorded, whether the speakers were separated correctly, which parts of the transcript deserve another listen, and whether the decisions and action items are complete. This article walks through those steps in order, with what the machine does at each one and where you should look.

1. Recording: most of the quality is decided here

The model can only work with what it hears, and the minutes can only contain what the model heard. A few things cost almost nothing and affect every later step:

• Put the recording device in the middle of the table. Do not leave it in a bag or under a laptop. Voices from far away get smeared by the echo of the room.
• When someone joins remotely, make sure their voice goes into the same recording, at a volume close to the people in the room.
• At the start, ask everyone to say their name and role in one sentence. Later, this lets you match "Speaker A, B, C" to real people quickly.
• Try not to talk over each other. When two people speak at once, both the transcript and the speaker separation tend to go wrong.
• Thai meetings often include English product names and abbreviations such as KPI and OKR. Say the full name the first time and use the short form afterwards. It saves a lot of work during review.

When you upload, prepare the file according to the formats and the per-meeting length limit shown on the page.

2. What happens after you upload

The minutes are generated in four stages: uploading the recording, transcribing speech, separating speakers, and writing the summary and action items. The page shows the current stage and progress, so you do not need to watch it. Processing time depends on the length of the meeting; the figures are in the metrics section of the meeting notes page.

If the connection drops, your daily free limit is reached, or the recording exceeds the per-meeting duration limit, the page shows a clear explanation and a retry option.

When it finishes you get four things: a transcript with speakers and timestamps, a summary, decisions and action items. We suggest reading them in reverse: check whether the action items and decisions make sense first, and look into the transcript only where you have doubts.

3. Check the speakers first

Speakers are first shown as letters: Speaker A, B, C. Start by counting. Does the number match the people who actually attended? If four people attended and the result shows six, one attendee was split into two speaker tracks. Then listen to the first thing each person says, match it to a real person and rename the speaker. Every action item owner later uses that name.

There are two common problems:

• One person is split into two speakers. This often happens when they change seats halfway through, or their distance from the microphone changes. You can merge the two sets of segments.
• Short replies such as "ครับ" and "ค่ะ" are easily assigned to the previous speaker. This does not affect the summary, but be careful when you quote who said what.

Speaker separation is measured with DER:

DER = (missed speech
       + false alarm
       + confusion)
    / total speech time

Missed speech means someone spoke but was not marked. A false alarm means nobody spoke but a segment was marked. Confusion means a segment was marked but given to the wrong person. DER is weighted by duration, so one long turn assigned to the wrong speaker weighs far more than a few short replies.

4. Review the transcript without reading every word

Reading a 40-minute meeting word by word is not worth the time. Review in this order of priority:

1. Names of people, companies and products. These are the words most likely to be wrong, and they do the most damage to the credibility of the minutes.
2. Numbers, dates and amounts. Thailand commonly uses the Buddhist Era (พ.ศ.). The Buddhist year is the Gregorian year plus 543, so 2569 is 2026. If the minutes feed a system that uses Gregorian dates, convert them consistently.
3. Mixed-language words. English brand names keep their original letters and are not forced into Thai script. Where the spelling is inconsistent, change it to one form in the minutes.
4. Negations. In Thai, a missing "ไม่" reverses the meaning.

Wherever you have doubts, click the item and the player jumps to that position in the recording. Listen to those few seconds only, not the whole meeting from the start.

5. Summary, decisions and action items: three questions

The summary should answer: what did this meeting decide, and what did it leave open? Two or three sentences are enough.

Decisions should only list things that were agreed. Topics that were discussed without a conclusion do not count. Every decision carries its position in the recording, so when you are unsure, listen to the tone. In a Thai meeting, "ลองดูก่อน" (let's try it first) and "ตกลงตามนี้" (agreed, let's go with this) can both sound like a commitment, but they mean very different things once they are written into the minutes.

An action item must answer three questions: what is to be done, who does it, and by when.

• Task: send the load-test report to the customer this week
• Owner: Speaker B
• Due: next Wednesday
• Recording position: 00:12:40

The owner is the speaker, and shows as a name once you have renamed the speaker. The due date is recorded in the speaker's own words, for example "next Wednesday". Convert it to a specific date using the meeting date, otherwise nobody will remember which day it was a week later. For an action item that lacks an owner or a due date, listen to its position in the recording. Most of the time it was said in the meeting but not recognized as part of the action item.

6. Export and check against the recording

Export after you have reviewed. There are two formats:

• Markdown: the title, duration and number of speakers, the summary, numbered decisions, action items with checkboxes, and the full transcript with speakers and times. It suits a knowledge base or a code repository.
• Word: the same content, for colleagues who do not use those tools.

The header of an exported file contains only the title, the duration and the number of speakers. It has no meeting date. Put the date in the title, or in the body of the email you send the minutes with, so that "next Wednesday" in an action item has something to refer to.

Do one last thing before you send it: click the recording position of every decision and action item. There are not many of them and it takes a few minutes, which is much less work than being asked "who said this?" afterwards.

DA

DataArc Team