How to write meeting minutes: format, template, example — and who writes them now (2026)

Meeting minutes are the official written record of a meeting: who was there, what was discussed, what was decided, and who is responsible for what by when. Unlike a transcript, minutes don't record every word — they record outcomes. Unlike a casual summary, they follow a recognizable format, and in boards, councils and associations they are usually the one document the organization is required to keep.

This guide is the manual craft first — the format, a template you can copy, a filled-in example, what changes for a board meeting — and then the part the format itself never addresses: who writes the minutes in 2026, and in whose language they arrive when the people in the room don't share one.

What meeting minutes are — and what they aren't

Three documents get produced after meetings, and they answer different questions:

Minutes sit in the middle: fuller than a recap, far shorter than a transcript, and — in formal settings — the version with legal weight. If your meeting is a working call and nobody will ever audit it, the recap format is lighter and gets read more; we keep a separate guide for it. If your meeting has a chair, an agenda and anything resembling a vote, you want minutes.

One thing they are not: a record of time. The word comes from the Latin minuta — "small" — as in minuta scriptura, notes taken in small writing, later transcribed formally. Minutes were always about compact notes, not about the clock.

What to include: the standard format

A usable set of meeting minutes carries eight elements. This is the skeleton behind nearly every template you'll find, from a project sync to a board book:

1. Meeting name, date, time and place (or the meeting link — "place" is a URL now).
2. Attendance — present, absent with apologies, and any guests. In formal meetings, note whether quorum was reached.
3. Approval of the previous minutes — formal bodies open by approving the last meeting's record, with corrections noted.
4. Agenda items, in order — one block per item, each with a short neutral summary of the discussion. Two or three sentences; positions, not a play-by-play.
5. Decisions — each decision stated in one sentence, with how it was reached ("agreed by consensus", "carried 5–2"). Decisions are the reason minutes exist; never bury them inside discussion text.
6. Action items — owner, task, deadline. One line each. An action item with no owner is a wish, not a record.
7. Next meeting — date and time if set.
8. Time of adjournment and who recorded the minutes.

What stays out: verbatim quotes (unless someone asks to be minuted), tone and emotion, opinions of the minute-taker, and anything said off the record. Minutes are neutral by construction — a reader should not be able to tell from the text whose side the writer was on.

How to write them: before, during, after

Before the meeting, steal the structure. Take the agenda and turn it into your minutes skeleton: one heading per item, attendance list pre-filled from the invitation, previous minutes linked. Ninety percent of the formatting work happens before anyone speaks. If there's no agenda, that's the first finding to raise — minutes without an agenda become a chronology of whoever talked loudest.

During the meeting, write decisions, not dialogue. The craft of taking minutes is aggressive filtering in real time: for each agenda item you need the positions raised (attributed only when it matters), the decision, and the actions. When a decision is made, read it back aloud — "so we're recording: X, agreed by all, Anna to deliver by the 15th" — and let the room correct it while everyone still remembers. That single habit removes most of the disputes that otherwise surface when the minutes circulate.

After the meeting, publish the same day. Clean up the notes while context is fresh, get the chair's review if your process requires it, and send the minutes to everyone invited — including, especially, the people who missed the meeting. Then store them where the next meeting will find them: minutes that live in one person's inbox are minutes the organization doesn't have.

A meeting minutes template

Organization / team — Minutes of meeting nameDate: date · Time: start–end · Place: room / meeting linkPresent: names · Apologies: names · Guests: namesChair: name · Minutes: name

1. Approval of previous minutes The minutes of date were approved as circulated / with the following correction: ….

2. Agenda itemTwo–three sentence neutral summary of the discussion.Decision: one sentence — what was decided and how: consensus / vote count. Action: name — task — by date.

3. Agenda itemSummary.Decision: decision, or "deferred to date". Action: name — task — by date.

Next meeting: date, time. The meeting was adjourned at time.

A filled-in example

Aster GmbH — Minutes of the product councilDate: 28 August 2026 · Time: 14:00–14:50 · Place: meeting link Present: L. Ortega (chair), M. Bauer, K. Sato, P. Nowak (minutes) · Apologies: J. Lindqvist

1. Approval of previous minutes The minutes of 14 August were approved as circulated.

2. Q4 pricing revision Bauer presented the revised tiers; Sato raised the impact on annual renewals. The council agreed the revision should not apply to contracts signed before October. Decision: revised tiers adopted for new contracts from 1 October — carried 3–0. Action: M. Bauer — updated price list to sales — by 5 September.

3. Support coverage in Japanese Sato reported current response times. Discussion deferred pending the September hiring round. Decision: deferred to the next council.

Next meeting: 11 September 2026, 14:00. The meeting was adjourned at 14:50.

Notice what the example doesn't contain: nobody's exact words, no adjectives, no atmosphere. Fifty minutes of meeting became fourteen lines that a person who wasn't there can act on — that's the entire job.

Board minutes: what formality adds

For a board, council or association, the same skeleton picks up legal duties, and the details vary by jurisdiction and by your own bylaws — check both. The additions are consistent across most rulebooks: record that notice was properly given and quorum reached; record motions verbatim — who moved, who seconded, and the vote tally, with abstentions and any recusals named; record dissent when a member asks for it. Approved minutes typically become the organization's official evidence of its decisions, which is why boards approve the previous meeting's minutes as their first item — the record itself needs a decision.

The discipline that follows from legal weight is the same one that makes everyday minutes good: neutral language, decisions over dialogue, and nothing in the record you wouldn't want read back in two years.

Who writes them now — and in whose language

In 2026 the writing itself is increasingly automated: the meeting is transcribed, a model drafts the summary, and the minute-taker's job shifts from stenography to editing. What the automation has mostly not changed is the assumption underneath the format — that the meeting, and therefore its record, happens in one language. Run a meeting in English with a team that thinks in Portuguese, Polish and German, and the minutes arrive in English: accurate, official, and a second-language document for most of the people bound by it. We documented what each major platform actually keeps after a call, per vendor and with sources, in the recap guide — the shape is the same everywhere: one record, one language — and how much of the meeting still exists in your language a week later is a question with a measured answer.

We built InterMIND so that the record doesn't have that assumption. It's a communication space where the meeting runs in each participant's own language — voice, chat and notes — and when the call ends, the summary already exists: overview, points marked agreed, open or disputed, action items with owners, each line keeping its timestamp. Signed-in members get it by email, in the meeting's chat and in the calendar event, and every member reads it in their own language — the record is translated per reader, not written once in the room's loudest language. Any member can edit it, every edit keeps author and revision history, and a channel keeps the record of every past session. (A participant who joins as a guest without an account gets the fully translated meeting live, but no record afterwards — the account is free, and it's what makes the record reachable.) The summary model runs EU-hosted with zero data retention on the request.

Minutes as a craft survive the automation — somebody still has to decide what the meeting meant. What shouldn't survive is the idea that the official record of a multilingual room can only exist in one language.

• Open a complete example — a real record rendered by the same code that writes yours, timestamps included.
• Try the live demo — no signup; speak, and hear the room translated per listener.

FAQ

What are meeting minutes?

Meeting minutes are the official written record of a meeting: the date and attendance, the items discussed, the decisions made (with vote counts where votes were taken), and the action items with owners and deadlines. They record outcomes, not conversation — a reader who missed the meeting should be able to act on them without hearing what anyone said.

Why are they called "minutes"?

From the Latin minuta, "small" — minuta scriptura was the rough note taken in small writing during the proceedings, formalized afterwards. The name refers to compact notes, not to units of time.

What should be included in meeting minutes?

Eight things: meeting name/date/time/place; attendance (present, apologies, guests, quorum where relevant); approval of the previous minutes; each agenda item with a short neutral summary; decisions, stated in one sentence each with how they were reached; action items with owner and deadline; the next meeting's date; and adjournment time plus who recorded the minutes.

What should NOT be included in meeting minutes?

Verbatim dialogue, tone, emotion, the minute-taker's opinions, and off-the-record remarks. Attribute positions only where it matters or where a member asks to be minuted. Minutes are neutral: the text should not reveal whose side the writer was on.

What is the difference between meeting minutes and a meeting recap?

Minutes are the fuller, formal record — attendance, agenda items, decisions, votes, actions — and in formal bodies they carry legal weight after approval. A recap is a one-screen working summary (decisions, action items, open questions) sent the same day. For working calls a recap gets read more; for anything with a chair and votes, write minutes. We keep a separate guide to recaps.

How detailed should meeting minutes be?

Detailed enough that an absent member can act on them; short enough that they get read. The working rule: two-three neutral sentences of discussion per agenda item, every decision in exactly one sentence, every action item on one line. A fifty-minute meeting should usually fit on one to two pages.

Who should take the minutes?

Formal bodies name a secretary or rotate the duty; in working meetings it's whoever is designated — ideally not the chair, who is busy running the discussion. In 2026 a growing share of the first draft is machine-written from the meeting itself, and the human role shifts to editing: verifying decisions, owners and dates before the record circulates.

Sources: Merriam-Webster — "minute" (noun): "the official record of the proceedings of a meeting", from Latin minutus, "small". Board-minute requirements vary by jurisdiction and bylaws — check yours. Checked September 2026.