IN THIS ARTICLE
Meeting Minutes: Complete Guide, Free Template, and Method for SMEs (2026)
Productive meetings
04/15/26
•
10 min
Meeting minutes are a concise document that captures the decisions made, the actions to be taken, and the responsibilities assigned during a meeting. Its purpose: to make sure that what was said turns into what will be done. Because without a reliable written record, meetings disappear. And with them, commitments. The problem is real. According to Fellow.ai, 44% of the actions decided in meetings are never carried out. Not because of bad intentions. Because of a lack of follow-up. Meeting minutes are the only safeguard against this loss. But they still need to be well designed, shared quickly, and above all, remain useful beyond the following week. In small and medium-sized businesses, the challenge is even greater. No dedicated note-taker, no formal process, project managers juggling meeting facilitation and note-taking. Meeting minutes are often seen as a time-consuming chore, written in a rush, then forgotten in a subfolder. This guide gives you a 6-step method, a ready-to-use template, the mistakes to avoid, and a question no one asks: what happens to your meeting minutes once they’re archived?
What is a meeting summary (and what is it not)?
There is a lot of confusion between meeting notes, meeting report, and minutes. These are not three names for the same document. Each has a different role, level of formality, and use.
Notes are a personal memory aid. The meeting report is a shared, structured document that commits the team to actions. The minutes are a formal legal act, required in certain contexts (CSE, general meeting, board of directors).
In SMEs, 90% of situations call for a meeting report, not minutes.
Notes, meeting report, minutes: how do you choose the right format?
Criterion | Notes | Meeting report | Minutes |
|---|---|---|---|
Objective | Remember | Share and commit | Prove and formalize |
Recipient | Yourself | Participants + absentees | Official body |
Level of detail | Freeform, partial | Concise, structured | Comprehensive, faithful to the remarks |
Legal value | None | Low (internal evidence) | Strong (legal commitment) |
Who writes it | Each for themselves | A designated writer | The meeting secretary |
Timing | Immediate | 24 to 48 hours | According to the bylaws |
SME use cases | Brainstorming, quick call | Project meeting, client meeting, team check-in | General meeting, CSE, board of directors |
The rule is simple: if the meeting involves decisions or actions to follow up on, a meeting report is required. If it has a legal or statutory dimension, it's minutes.
The 6 essential elements of a good report
A meeting report that contains only a summary of the discussions is a useless report. What matters is not what was said. It is what was decided, by whom, and for when.
Here are the six elements that a meeting report should always include.
1. The header: date, location (or video link), meeting topic, list of participants and absentees. This is the minimum so that someone who was not present can understand the context.
2. The decisions made. Not the discussions that led to them. The decisions themselves, stated clearly. "It was decided to postpone delivery to March 15" is better than "there was a discussion about the deadlines".
3. The actions with owner and deadline. Each action must have a name and a date. Without that, it is wishful thinking. Teams that use structured templates see 73% more task completion, according to a Resolution study (Atlassian Apps).
4. Open issues. What has not been decided, what is awaiting additional information. Listing open issues avoids rediscovering them three meetings later.
5. Reference documents. Any file, link, or resource mentioned during the meeting. A report without the associated documents forces everyone to dig through their emails.
6. The next step. Date of the next meeting, or the next key deadline. A report that does not point toward what comes next remains a passive record.
According to Atlassian, 54% of participants leave a meeting without clearly knowing what to do or who is responsible. These six elements solve the problem.
How to write a report in 6 steps
Writing good meeting minutes starts before the meeting and doesn't end when you click "send." Here's the complete method.
Before the meeting: prepare the outline
Never go into a meeting with a blank page. Prepare a meeting-minutes outline based on the agenda: topics to cover, outstanding questions, expected decisions. This outline saves you 50% of the writing time after the meeting.
In practical terms, take your standard template and prefill the project name, participants, subject, and agenda items as empty sections. Add the action items left open from the previous meeting: it's the best way to create continuity between two sets of minutes and follow up on unfulfilled commitments.
If there is no agenda, the problem is upstream. It's hard to write good minutes when no one knows why the meeting is taking place.
During the meeting: what to capture (and what can be ignored)
The temptation is to write everything down. That's a mistake. During the meeting, focus on three things: decisions, actions, and unresolved disagreements. The rest (anecdotes, digressions, implicit consensus) can be ignored.
A simple technique: whenever a decision is made, note it immediately by phrasing it as an accomplished fact. "Budget approved at 15,000 euros," not "discussion about the budget." This discipline forces clarity in real time and avoids vague rewording afterward.
In small and midsize businesses, it's often the project manager who leads the meeting and takes notes at the same time. It's a painful exercise, and many people have to go over it several times to get something usable. Two options: rotate the note-taking role within the team, or use an automatic transcription tool that captures the raw material while you stay focused on the discussion. According to Asana (Work Innovation Lab, 2024), France breaks all records with 9.1 hours a week of meetings deemed unproductive. Those hours might as well leave at least something usable behind.
After the meeting: write, approve, distribute within 24 hours
Timing is critical. Minutes sent 5 days after the meeting are practically useless: participants have forgotten the context, actions have fallen behind, and no one bothers to read them.
Best practice: write them within the 2 hours that follow (while memory is fresh), have a key participant review them if needed, and distribute them within 24 hours.
For proofreading, don't aim for total consensus. Send the minutes with a simple note: "please report any errors or omissions within 48 hours." No response means tacit approval. That's enough for 90% of project meetings in small and midsize businesses.
The delivery format matters too. Minutes buried in a 15-line email will be ignored. Prefer a clear, separate document, with a clear email subject: "Minutes — [Project X] — Meeting of [date]." And if you send the minutes by email, put the action items at the top of the message, not at the bottom. That's what recipients look for first.
Meeting minutes template for small and medium-sized businesses
This template is designed for SMBs that operate in project mode. It is deliberately simple: no unnecessary fields, no corporate jargon. The goal is for it to be used, not to look pretty in a folder.
Section | Content |
|---|---|
Project | [Project name] |
Date and time | [DD/MM/YYYY — HH:MM] |
Location / video link | [Room / Teams / Google Meet] |
Participants | [Names + roles] |
Absent | [Names] |
Meeting topic | [Theme or main objective] |
Decisions made | 1. [Clear, clearly worded decision] |
Action items | 1. [Action] — Responsible: [Name] — Due date: [Date] |
Open issues | 1. [Unresolved point + reason] |
Referenced documents | [Links or file names] |
Next step | [Date of next meeting or key deadline] |
The classic trap in SMBs: adapting the template for every meeting. As a result, after three months, no one can find anything because every meeting minutes document has a different format. Choose a template. Stick with it. Format consistency is what makes meeting minutes usable over time.
Another practical tip: name your files systematically. "Minutes — [Project] — [Date YYYY-MM-DD]" enables automatic chronological sorting and quick searching. It's a small detail, but it's this kind of minimal discipline that makes the difference between a usable archive and a folder no one ever opens.
The 5 mistakes that make your reports useless
Writing minutes is not enough. Many teams produce them diligently without ever getting any value from them. Here are the five most common mistakes.
Mistake 1: transcribing everything. Meeting minutes are not a transcript. If your minutes are 3 pages for a one-hour meeting, no one will read them. According to Comet Meetings and YouGov (2024), 86% of French employees regularly consider their meetings useless. Minutes that fully transcribe a meeting perceived as useless make the problem worse instead of solving it. Summarizing is an act of added value: identifying what matters and eliminating the noise.
Mistake 2: forgetting names and dates. “We need to follow up with the client” is not an action. “Marc follows up with client Dupont by April 12” is one. Without an owner or a deadline, the action does not exist. And 44% of actions decided in meetings are never carried out (Fellow.ai). That is no coincidence.
Mistake 3: sending the minutes too late. Every day of delay halves the usefulness of the document. After 48 hours, the minutes become a stylistic exercise that no one consults.
Mistake 4: never rereading past minutes. This is the most common and least visible mistake. Teams produce dozens of minutes per quarter, but never consult them after sending. Decisions are revisited, the same debates come back, commitments are forgotten. On a 12-month project, that is the equivalent of several entire meetings spent rehashing topics already decided. Minutes that are never reread after day 7 should not have been written.
Mistake 5: changing the format every time. One set of minutes in Word, the next by email, the third in a Notion note, the fourth dictated in a voice message. After six months and thirty meetings, the information is scattered across five tools, and finding a specific point becomes archaeology. According to OICN (Mailoop, 2025 benchmark, based on 17,000 workers), French executives already spend more than 36 hours per week in meetings. If you then have to spend an hour digging through the minutes, the hidden cost becomes considerable. Standardizing the format is what turns a collection of documents into a usable system.
And after the meeting minutes? Turn your reports into project memory
That's the question nobody asks. We write the minutes, send them, archive them. And then?
In most small and medium-sized businesses, meeting notes end up in a Google Drive folder or a Teams channel, sorted by date, never reread. Six months of project, thirty meetings, thirty scattered documents. When a new team member joins the project or a client asks "what had we decided in September?", the answer is always the same: we dig, we ask colleagues, we piece it back together from memory.
The real issue with minutes isn't writing them. It's making use of them over time. An isolated set of minutes has a lifespan of a week. A set of minutes connected to the previous ones, linked to ongoing tasks and searchable by keyword, becomes a building block of the project's collective memory.
This is what operational knowledge management is: the ability to retrieve in 30 seconds a decision made four months ago, with its context. For SMBs that manage 6- to 18-month projects with multiple stakeholders, it's the difference between smooth follow-up and chronic information loss.
The problem becomes critical during handovers. A team member leaves the project or the company, and with them all undocumented context disappears: why a given choice was made, what compromise was accepted with the client, which option was ruled out and why. If the minutes are done well and centralized properly, the successor can pick up the thread in a few hours. Otherwise, they have to start from scratch.
A few questions to ask yourself: are your minutes stored in the same place as the project tasks and documents? Can you search for a decision by keyword across all the minutes of a project? Can a newcomer understand a project's history by reading the meeting minutes? If the answer is no to any one of these questions, the problem is not the quality of your minutes. It's the lack of a system to make use of them.
Tools like 5Days make it possible to connect meeting minutes to the entire project and query them via AI, so every meeting feeds a living knowledge base rather than a cemetery of documents.
FAQ — Meeting Minutes
Quelle est la différence entre un compte rendu et un procès-verbal ?
Qui doit rédiger le compte rendu de réunion ?
Dans quel délai faut-il envoyer un compte rendu ?
Un compte rendu de réunion a-t-il une valeur juridique ?
Peut-on utiliser l'IA pour rédiger un compte rendu ?
Quel est le meilleur format pour un compte rendu en PME ?
Faut-il faire approuver un compte rendu ?
Comment retrouver une information dans d'anciens comptes rendus ?
A well-written meeting report should not end up in a forgotten folder. It is the first link in reliable project follow-up, and the best safeguard against the loss of information that drags down long projects. But the meeting report cannot save everything on its own. If your meetings suffer from a deeper problem, the diagnosis may begin there: understanding why your meetings are unproductive, and how to break free from meeting-itis.
