In short. Meeting minutes are a short document saying who was there, what was discussed, what was decided, and who must do what by when. Write them during or right after the meeting, review them with participants, and send them within a day. If minutes contain no decisions and no actions, they are a summary, not minutes.
What minutes are for
Three things. First, memory: after two weeks nobody remembers whether the delay was approved or merely proposed. Second, alignment: anyone who missed the meeting can read in two minutes what changed. Third, accountability: an action with a name and a date next to it is far more likely to get done than a sentence like "we'll think about it".
Minutes are not for recording everything that was said. That is what a transcript is for. Minutes are an editorial choice: they put in order what has consequences.
Minutes, notes and transcript: what's the difference
In everyday use the terms overlap, but it helps to separate them:
- Notes: personal, often incomplete, useful to whoever takes them.
- Transcript: the word-by-word text of what was said. Long and unordered.
- Minutes: an ordered synthesis of topics and conclusions, usually informal, internal to the working group. In some contexts (condominium assemblies, boards, collegial bodies) there are requirements set by law or bylaws: in that case follow your organisation's rules and, in doubt, ask a professional.
This guide covers ordinary work meetings, where minutes are an organisation tool, not a formal obligation.
What minutes must contain
Good minutes have few elements, always the same ones. That way readers know where to look.
Heading
Meeting title, date, start and end time, place or call link, name of whoever wrote the minutes.
Present and absent
List who attended and, if needed, who was invited but absent. If someone joined halfway, write it down: it can matter for understanding who heard what.
Agenda
The planned topics. If one was added during the meeting, flag it as such.
Decisions
This is the most important part. Each decision is a complete sentence, understandable out of context: "The version 2 release is postponed to November 15" rather than "postponement approved". If the decision has a short rationale, add it.
Actions
Every action needs three things: what, who, by when. If one of the three is missing, it is not an action yet. If no deadline was stated, write "deadline to be defined" and ask for it in the cover message.
Open questions and risks
Things that came up and were not resolved. Often the most useful part to re-read at the next meeting.
Next steps
Date of the next meeting and what must be ready by then.
A template to copy
You can paste this text into a document, an email or a notes file and fill it in. Deliberately simple.
MEETING MINUTES
Title:
Date and time:
Place / link:
Minutes written by:
PRESENT
-
ABSENT (invited)
-
AGENDA
1.
2.
DISCUSSION (one or two lines per point)
1.
2.
DECISIONS
- D1:
- D2:
ACTIONS
| What | Who | By when |
| ---- | --- | ------- |
| | | |
OPEN QUESTIONS
-
RISKS / BLOCKERS
-
NEXT MEETING
Date:
To prepare:
How to write minutes in practice, step by step
Before the meeting
- Prepare the heading and the agenda. If the agenda is already in the invite, copy it.
- Choose who writes. Whoever runs the meeting can rarely take good minutes at the same time: if possible, make them two different people.
- Decide whether and how you will record the meeting. If you record, tell participants: more below and in a dedicated article (recording a meeting and the GDPR).
During the meeting
- Write decisions and actions down the moment they are said, not at the end. If you did not understand, ask them to repeat: "To recap for the minutes: Marco sends the quote by Friday, correct?" takes ten seconds and avoids a mistake.
- Note the time, or the minute of the recording, next to important items. When someone disputes a sentence, you will know where to check.
- Do not transcribe discussions. Note the outcome and, if needed, one line on the positions involved.
After the meeting
- Within an hour or two, tidy up your notes while memory is fresh.
- Check that every action has an owner and a date.
- Send the minutes to attendees and interested absentees, asking them to flag mistakes within a precise time (for example one working day). Silence past that deadline counts as confirmation.
- Always archive the document in the same place, with a consistent name (for example
2026-09-29 project-x-meeting.md).
A concrete example
Here is what the central section of real minutes might look like (made-up names):
Decisions
- D1: the client portal release slips from October 30 to November 15, to complete access testing.
- D2: the email provider stays unchanged until year end.
Actions
| What | Who | By when |
|---|---|---|
| Send the client the new timeline | Giulia | Friday October 3 |
| Check the cost of an extra test | Marco | Tuesday October 7 |
Open questions
- Will the client accept acceptance testing in two sessions instead of one?
Thirty seconds to read, and enough to pick up the thread a month later.
Common mistakes
- Minutes that are too long. If nobody reads them, they are useless. One page beats ten.
- Actions with no name. "The team will check" means nobody will check.
- Relative dates. "By Friday" written on September 29 must be translated into a date. A month later nobody will know which Friday.
- Mixing facts and opinions. Write what was decided, not who "won" the discussion.
- Sending them too late. After three days, proofreading the draft becomes a new meeting.
Writing minutes with technical help
A recorder or transcription tool does not write the minutes for you, but removes the hardest part: taking notes while listening. You can replay the doubtful point, copy the exact sentence of a decision, and check who said what. Judgement on what goes into the minutes stays human, and you should always re-read the result before sending. To understand what to expect from these tools, read automatic transcription of meetings in Italian.
Frequently asked questions
Are minutes of a work meeting mandatory?
Usually not: in ordinary meetings they are good practice, not an obligation. For assemblies, boards, collegial bodies and some other cases there are specific rules, set by law or bylaws. In that case ask your organisation or a professional.
Who must sign the minutes?
It depends on the context. In work meetings people usually do not sign: you send them and they count as approved if no corrections arrive. For formal minutes the required signatures (for example chair and secretary) are defined by the body's rules.
How long should minutes be?
As long as needed to answer three questions: what was decided, who does what, by when. For a one-hour meeting one page is often enough.
Better to write them during or after the meeting?
Better both: decisions and actions during, in rough form; the polish right after, within a few hours.
Can I use a recording to write the minutes?
Yes, as long as participants were informed and you follow data-protection rules. You can find general information in this article; for a specific case consult a professional.