Good meeting notes record what was decided, who does what and by when. They leave out most of the discussion. Send them promptly, while people still remember the meeting.
This page shows a short format built on those three things, with a sample in a table. For what to write before the meeting, see meeting agendas that keep everyone on track.
Record outcomes, not the conversation
Notes are not a transcript. A local government guide for community groups says minutes do not need to be long or written in fancy language. They do need to record clearly what was decided and who will carry it out. The same guide says it is impossible and not useful to write everything down.
A community toolkit from a university says documentation does not need to reproduce everything that happened, and that more detail is not always better. It also says not to record a statement just because it was emotional or memorable.
For many routine meetings, the toolkit suggests a decision and action log. It lists decisions, action items, responsible people, deadlines and significant unresolved issues. It says such a log can be more useful for day-to-day work than long narrative minutes.
Separate a proposal from a decision
Someone suggesting an idea does not mean the group agreed to it. The toolkit says to mark which is which, using labels such as "Proposal discussed" and "Decision".
Before: There was a long talk about planting day, with several views on dates, and it seems most people liked a weekend in April.
After: Decision: Planting day is Saturday, April 10, 10am to noon.
The first version leaves readers to guess whether anything was settled. The second gives them a fact they can act on. Write decisions with an active verb and a clear subject: "The group chose Saturday, April 10." See active voice for when this helps.
A sample set of notes
These notes follow the sample agenda for a community garden group.
Garden group meeting notes. Thursday, March 18, 7pm to 8pm. Present: nine members.
| Type | What | Owner | By when |
|---|---|---|---|
| Decision | Planting day is Saturday, April 10, 10am to noon. | Group | Done |
| Action | Send the planting day invitation. | Planting lead | Friday, March 26 |
| Action | Ask the building office about weekend access to the tool shed. | Shed lead | Friday, April 2 |
| Action | Print the volunteer schedule for the bulletin board. | Chair | Wednesday, April 7 |
| Open question | Who can open and close the tool shed on weekends? The shed lead will bring two options. | Shed lead | Thursday, April 15 |
| Next meeting | Thursday, April 15, 7pm to 8pm | Chair | Set |
The table works because every row answers the same questions. What happened? Who owns it? When is it due? A reader who was absent can still follow it.
The sample also shows a habit worth copying: the open question has an owner and a date, like an action. Unfinished business should not have the owner "everyone".
Give every action an owner and a date
An action with no owner belongs to nobody. Name one owner for each, by role or by name.
The local government guide suggests a narrow column down one side of the page for who has agreed to do what. In a table, that column is the Owner column.
The university tip sheet on meetings adds two points. At the end of the meeting, clearly state the decisions and assign tasks with deadlines. Before the next meeting, check in on the actions.
Write the date in full. Avoid "soon" and "next week". The GOV.UK style guide uses "on or before" for deadlines. It also leaves out "th" and "nd" after dates, and its example is "2 June", not "2nd June". Its examples put the day before the month. Use the order your readers expect, and keep the same order everywhere.
Check it and send it quickly
Before the meeting ends, read the decisions out loud. The toolkit suggests asking when you are unsure, for example by reading back the decision and checking that it is right. Fixing a wrong note in the room is quicker than fixing it later.
Send the notes promptly. The tip sheet asks for key decisions, action items and next steps. Put the key message in the email itself, not only in an attachment. See sending a document by email.
The toolkit also asks groups to identify which record is the official one. If there are chat messages, photos of a whiteboard and typed notes, say which copy counts.
Before you send, run through this list.
- The group name, date, time and place are at the top.
- Each decision is written as a plain statement.
- Each action has one owner and a date.
- Open questions are listed with who will bring an answer.
- The next meeting date is written down.
- Someone who was in the room has checked it.
- The notes fit on one page.
The Easy-Read Editor can flag long sentences and long paragraphs in the notes. Notes written in short lines rarely trigger it.
Common mistakes
- Writing a transcript. Readers cannot find the decisions among the talk.
- Actions with no owner. "We should ask the office" gets done by nobody.
- Vague dates. "Soon" means a different day to each person.
- Mixing proposals and decisions. Readers think something is settled when it is not.
- Quoting by paraphrase. The toolkit warns against putting a paraphrase in quotation marks as if someone said those words.
- Sending notes a week late. Memories fade, and people have already acted on their own version.
- Planning jobs in the notes. A volunteer schedule is its own page. See volunteer schedules and sign-up sheets.
FAQ
How long should meeting notes be?
One page for most meetings. A short decision and action log is enough for routine work. A formal group may need fuller minutes under its own rules.
Do I need to list who attended?
Record the group name, date, time and place. The local government guide suggests listing everyone for a small meeting. For a large one, note the committee members and the total number present.
Should I record the meeting instead?
Usually not. The toolkit says audio and video are more sensitive than ordinary notes. It asks whether a recording is truly needed and says to choose the least intrusive form of record that meets the need.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Capturing What People Say: Tips for Recording a Meeting - Community Tool Box Checked November 19, 2026
- How to hold meetings - Chorley Checked November 19, 2026
- How to Conduct Efficient Meetings - Office of the Executive Vice Chancellor tip sheet Checked November 19, 2026
- A to Z style guide - GOV.UK content and publishing guidance Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.