How to Write Meeting Minutes: Steps, Examples and Templates

To write meeting minutes, record what the meeting decided and who must do what by when, not what everyone said. Use the past tense, keep a neutral tone, and send a draft within 24 hours. Below is the workflow, the wording rules, and two templates: one for informal team syncs and one for formal board meetings.

What meeting minutes are, and why verbatim notes fail

Meeting minutes are the official, shortened record of a meeting: decisions, action items with owners and deadlines, and questions that remain open. They are not a transcript. Unfill's guide puts it simply: effective minutes capture what the meeting did rather than what everyone said.

Verbatim notes fail for three practical reasons:

• Nobody reads them. A reader who missed the meeting wants to know what was decided, not follow the argument line by line.
• They hide the outcome. In a four-page record, the one sentence that matters ("we will launch on the 14th") is easy to miss.
• They stop you from participating. If you are typing every sentence, you are not listening.

Minutes vs. meeting notes

Notes are your working capture. They can be messy, abbreviated and personal. Minutes are the cleaned-up version other people rely on later, for example when someone asks in March why a supplier was dropped in January. You write notes during the meeting and turn them into minutes after.

Verbatim or summarized?

Summarized, almost always. The exception is a formal motion, where the exact wording matters. We cover that in the board template below.

How to write meeting minutes: the three-phase workflow

Treat minutes as a three-phase job. Kiolo's guide describes the lifecycle as before (prepare the template), during (capture decisions and tasks) and after (finalize and circulate within 24 hours). The preparation is what makes the rest easy.

Before the meeting

1. Copy your template into a fresh document and fill in the date, time, location or call link, and meeting purpose.
2. Paste in the agenda as numbered headings, so your notes already have a structure to land in.
3. List expected attendees and verify the list. It is much faster to tick names off than to type them from memory.
4. Review the previous minutes and carry over any action items that were due, so you can ask for updates.

During the meeting

1. Mark attendance as people join, including late arrivals and early departures.
2. Write decisions as they happen. When the room reaches agreement, write one line immediately. If you are unsure, ask the chair to restate it.
3. Log each task with an owner and a date at the moment it is assigned. Do not leave this for later. People's memory of who agreed to what fades within hours.
4. Mark open questions separately so they do not get mistaken for decisions.
5. Skip the debate. Note the outcome and, only if it matters for the record, the main reason.

One structural point: Kiolo recommends that the chair and the minute-taker should not be the same person, because actively running a meeting leaves no room for real-time note-taking. If you are both, expect gaps. Ask someone else to take the minutes, or record the meeting and use the recording as a backup.

After the meeting

1. Clean up within hours, while you can still read your own shorthand.
2. Check every action item for an owner, a verb and a date.
3. Circulate a draft within 24 hours. Zoom's guide to minutes templates makes the same point: send promptly while context is fresh and recall is highest.
4. Set a short correction window, for example two working days, then mark the minutes final and file them where the team will find them.

What to include: the five essentials

Every set of minutes needs five things, whatever the meeting type. Anything beyond these is optional.

1. Basics: meeting name, date, time, attendees and apologies.
2. Decisions: what was agreed, stated as a clear outcome.
3. Action items: each with an owner, a task and a deadline.
4. Open questions: issues raised but not resolved, with who will follow up if known.
5. Next meeting: date, time and any items already parked for it.

Writing action items properly

Vague tasks are the most common failure. Audiostranscribe's template guide recommends an explicit owner-task-deadline pattern, with a verb and a result, instead of statements like "the team will look into it."

Each strong version answers three questions without a follow-up message: who, what, and by when.

Writing style: past tense, neutral, specific

Write minutes in the past tense with a neutral tone. Unfill suggests attributing outcomes to the group rather than to individuals where you can, for example "The committee approved the budget" instead of "Priya got the budget through."

Some practical examples:

Three habits keep the record clean:

• Avoid adjectives and judgment. "Heated" and "productive" do not belong in an official record.
• Use names for tasks, groups for decisions. An owner needs a name. A decision belongs to the meeting.
• Keep numbers exact. Amounts, dates and percentages are the things people dispute later.

Two templates: informal sync and formal board

Match the template to the meeting. A weekly stand-up does not need motions and signatures, and a board meeting needs more than a bullet list.

For governance meetings, Unfill notes that the minutes must record specific procedural details: whether a quorum was present, precise motions, vote counts, approval of the previous minutes, and signatures. If your organization is registered in Myanmar, our Myanmar meeting minutes guide covers the legal rules and a bilingual template.

Template 1: informal sync

Meeting: [Name]
Date / time: [Date, time]
Attendees: [Names]   Apologies: [Names]

DECISIONS
1. [What was agreed.]
2. [What was agreed.]

ACTION ITEMS
- [Owner] to [verb + result] by [date].
- [Owner] to [verb + result] by [date].

OPEN QUESTIONS
- [Question]. Follow-up: [Name], by [date].

NEXT MEETING
[Date, time]. Parked for next time: [Items].

Template 2: formal board meeting

[Organization name]
Minutes of the [Board / Committee] meeting
Date / time / location: [Details]

1. ATTENDANCE AND QUORUM
Present: [Names and roles]
Apologies: [Names]
Quorum: [Present / not present]. Chair: [Name]. Minute-taker: [Name].

2. APPROVAL OF PREVIOUS MINUTES
Minutes of [date] were [approved / approved with amendments].
Moved: [Name]. Seconded: [Name].

3. AGENDA ITEMS
3.1 [Topic]
  Summary: [Two or three neutral sentences.]
  Motion: [Exact wording.]
  Moved: [Name]. Seconded: [Name].
  Vote: For [n], Against [n], Abstain [n]. Result: [Carried / Not carried].

4. ACTION ITEMS
- [Owner] to [verb + result] by [date].

5. ANY OTHER BUSINESS
[Items raised.]

6. NEXT MEETING AND CLOSE
Next meeting: [Date]. Meeting closed at [time].

Signed: ____________ (Chair)   Date: ________

Handling multilingual meetings and using AI tools accurately

If your team switches between languages mid-meeting, decide in advance which language the minutes are written in, and keep names, numbers and decisions unambiguous. Most guides assume one language, but many teams in Myanmar, Thailand, Nigeria and elsewhere do not work that way.

Pick a minutes language and stick to it

A meeting that runs partly in Burmese and partly in English still needs one record. Agree on the language of the minutes before you start. Some teams write in the language most attendees will read. Others write a short bilingual version when a regulator or partner needs it. Keep product names, amounts and dates in the same form throughout so nothing is lost in translation.

Check the transcript before you trust it

AI transcription is useful as a backup to your notes, but it needs checking. Mixed-language speech is the hardest case. We explain why in Why Burmese-English code-switching breaks transcription tools. Before you circulate anything produced with AI help:

1. Check every name and number against the recording.
2. Check speaker attribution. Tools can assign a sentence to the wrong person, which matters when that sentence becomes someone's action item.
3. Check each decision against what the room actually agreed. A summary can read confidently and still be wrong.
4. Confirm owners and dates with the people named, especially if the discussion was in two languages.

Handle recording and privacy deliberately

Tell attendees before you record, and get agreement, particularly for sensitive discussions such as HR, legal or finance. Decide where recordings are stored and when they are deleted. If you are choosing a tool, it is worth reading how it handles data. Our post on meeting transcription without a bot lists what to check, and How to transcribe Google Meet covers a common setup.

How Loka Note fits

Loka Note records a meeting in your browser, with no bot joining the call, or takes an uploaded audio or video file. It then produces a transcript and a structured summary with a TL;DR, decisions, action items and open questions, which is close to the shape of the templates above. You still review and edit before you send, but the first draft is not a blank page.

It is built Burmese-first and handles mixed Burmese-English speech, and it also supports English, Thai, Vietnamese, Chinese, Yoruba and Hausa. Summaries come out in the meeting's language. You can export notes as PDF or send them by email, and use Ask Loka to search past meetings, for example "What did we decide about the venue last month?"

On data, customer audio and transcripts are processed for transcription and summarization only and are never used to train AI models. You can delete any meeting at any time. Details are on the security page.

There are no plan tiers. Minute top-ups start at $1.99 for 60 minutes, and an optional Unlimited plan is $19.99 a month. For a wider view of the options, see our post on AI meeting notes without a subscription.

Try it on your next meeting: start free at Loka Note