Meeting notes · Meeting minutes · Team habits
How to write meeting minutes: a format and a full example
Last updated By T. Krause
Meeting minutes record what a meeting decided and who does what next. Here is what to capture before, during and after the meeting, a format you can copy, and a complete set of minutes for an example meeting.
Maybe you've just been handed the job. Someone said "can you take the minutes?" at the start of a call, and now there is a blank page and a meeting already under way.
Minutes are shorter than you might fear. A person who missed the meeting should be able to read them in two minutes and know three things. What did we decide? Who is doing what, by when? When do we meet next? Everything else is support for those answers.
What meeting minutes are, and what they are not
Minutes are the agreed record of a meeting. They say who was there, which topics came up, what the group decided and which actions people took on. They are written so that someone can rely on them later, when memories disagree.
They are not a transcript. Nobody needs to know that the discussion of the launch date took twenty minutes and went in circles twice. They need the outcome, and maybe one line on why. If you catch yourself writing "Tom said... then Priya said... then Tom replied...", stop and write down where the conversation ended up.
Minutes are also different from your personal notes. Your notes can be messy and full of half-sentences. Minutes go to other people, so they need full sentences, names and dates.
Before the meeting
Ten minutes before the meeting makes the write-up much easier.
- Get the agenda. Ask the chair for it, or write it with them. Each agenda item becomes a heading in your minutes, so you are filling in a structure rather than starting from nothing.
- Set up the page. Put in the header block and the agenda headings before anyone joins. The format further down shows what goes in.
- Pull up the last minutes. A recurring meeting should start with the actions from last time. Have that list open so you can mark each one done, in progress or dropped.
- Know the names. If you don't know everyone, get the invite list. Writing "someone from sales" in the minutes helps nobody.
During the meeting
Listen for outcomes. Three kinds matter, and each one has its own place in the minutes.
Decisions. "We'll launch on the 10th." "Supplier photos are fine for now." When you hear one, write it down in plain words, then read it back to the room if it's ambiguous. "So the decision is that the launch moves to 10 November?" That question settles it in the room instead of by email a week later.
Actions. An action needs three parts: what, who and by when. "Someone should look into the photos" is a wish. "Priya gets a quote from the photographer by 21 October" is an action. If the meeting leaves an owner or a date open, ask before the next topic starts.
Open questions. Sometimes a topic ends without a decision. Write that down too, along with what happens next, because "no decision, Priya will bring a quote next week" is useful information.
For everything else, write one or two lines per agenda item on the main points of the discussion. You don't need to attribute every opinion. Name a person when the record needs it, for example when someone disagreed with a decision and wants that noted.
After the meeting
Write the minutes up the same day, while you still remember what your shorthand means. If you set up the page beforehand, this is mostly tidying.
- Turn your notes into full sentences under each agenda heading.
- Move every decision into a clear "Decision:" line.
- Collect all actions into one list at the end, each with an owner and a due date.
- Check names, dates and numbers. A wrong date in an action item causes more trouble than a clumsy sentence.
- If the chair wants to check the minutes before they go out, send them to the chair first.
Then send them. More on that below.
A format for meeting minutes
This structure works for a weekly team meeting, a project meeting or a committee. Copy it and fill in the brackets.
[Meeting name], meeting [number]
Date and time: [day, date, start and end time]
Place: [room or video link]
Chair: [name] Minutes: [name]
Present: [names]
Apologies: [names of people who were expected but couldn't come]
1. Actions from the last meeting
[Each action: done, in progress or dropped]
2. [Agenda item]
[Two or three lines on the discussion]
Decision: [what was decided, or "No decision" and what happens next]
3. [Agenda item]
...
Action items
- [Action]. Owner: [name]. Due: [date]
Next meeting: [date, time, place]
The header block answers "which meeting was this?" six months from now. The attendee list tells readers who agreed to the decisions. Numbered agenda items let people refer to "item 3" in replies. The action list at the end is the part people come back to, so keep it together in one place instead of spread across the agenda items.
A complete example
The meeting, the company and the people below are invented. It's a weekly project meeting at a small garden supplies shop that is relaunching its website.
Website relaunch, project meeting 6
- Date and time: Friday 16 October 2026, 10:00 to 10:45
- Place: Video call
- Chair: Priya Nair. Minutes: Alice Grant
- Present: Priya Nair, Tom Becker, Jonas Weber, Alice Grant
- Apologies: Ruth Osei
1. Actions from meeting 5
- Tom: set up the staging site. Done.
- Jonas: send the customer survey. Sent, 41 replies so far. Jonas will close it on 23 October.
2. Launch date
Tom reported that the checkout needs one more week of testing with the payment provider. Priya asked whether newsletter subscribers could get access before the public launch, to find problems with real orders.
Decision: the public launch moves from 3 November to 10 November. Newsletter subscribers get early access from 6 November.
3. Product photos
90 of the 140 products have new photos. Jonas suggested using the supplier's photos for the other 50 to save time. Priya disagreed, because the supplier photos have white backgrounds and the new ones are shot outdoors, and a mixed catalogue would look unfinished.
No decision. Priya will get a quote from the photographer for the remaining 50 products and bring it to the next meeting.
4. Any other business
Ruth asked by email for the hosting invoices to go to the finance address instead of to Tom. Agreed.
Action items
| Action | Owner | Due |
|---|---|---|
| Finish checkout testing and list any open bugs | Tom | 23 October |
| Get a quote for photographing the last 50 products | Priya | 21 October |
| Write the early-access email to newsletter subscribers | Jonas | 30 October |
| Change the billing address for hosting invoices to finance | Tom | 22 October |
Next meeting: Friday 23 October 2026, 10:00, video call
Look at what is missing. Tom spent ten minutes explaining the payment provider's test process, and none of it is in the minutes, because nobody needs it to act. The disagreement about photos is in there, because the next meeting will pick it up and needs to know both positions.
Formal and informal minutes
For a regular team meeting, informal minutes like the example above are enough. Short, plain language, sent the same day.
A one-on-one needs no minutes at all. Two people keep one running page of topics and follow-ups instead, and the guide to one-on-one meeting questions explains what to ask and how to keep that page going.
Boards, committees and associations keep formal minutes, which record more. They note whether enough members were present for the meeting to make decisions, the exact wording of each motion, who proposed and seconded it, and how the vote went. They usually start by approving the minutes of the previous meeting, and the chair signs them once they are approved. If your organisation has rules for its minutes, in its articles, constitution or standing orders, follow those rules over anything in this article.
How to send and store minutes
Send the minutes to everyone who attended and everyone who sent apologies. Put the decisions and the action list at the top of the message, then link to the full minutes. Some readers stop after the first screen, and they still need to see their actions.
Store every set of minutes in one place, under a name that includes the date. A shared folder of documents works. What fails is minutes scattered across email threads, where nobody can find the decision about the launch date three months later. Decisions that people will question later also belong in a decision log, one list of every decision with its owner and reason. The guide to the decision log template shows one with four example entries.
If your team keeps a wiki, link each meeting series from the page of the project it belongs to. How to build a team wiki people actually use covers how to give pages like that an owner so they stay current.
In Prompt Notebook, which we make, the meeting notes template has the same shape as the format above: agenda, notes, decisions and action items with owners. You can select your notes and pick Find action items in Ask AI to get a first list of actions, then check it and give every item a name. A share link lets people view, comment on or edit the page, and you can export it as Markdown or HTML for anyone outside the workspace.
For a recurring meeting, the meeting notes database keeps every meeting as a row with a date, a type and the attendees, and the minutes live inside each row. A Notes done checkbox shows which meetings still need a write-up. Ask your workspace answers a question like "when did we move the launch date?" with numbered sources that point back to the meeting. Clear decision lines make those answers better, for reasons explained in how AI answers from your notes work.
Frequently asked questions
Who should take the minutes?
Anyone except the person chairing the meeting. Running a discussion and recording it at the same time means one of the two gets done badly. In a team that meets every week, rotate the job so it doesn't always land on the same person.
How detailed should meeting minutes be?
Detailed enough that someone who missed the meeting can act on them. For most meetings that means a few lines per agenda item, every decision in full and every action with an owner and a date. Formal minutes for a board or committee need more, such as the exact wording of motions and the result of each vote.
How soon should minutes be sent?
The same day if you can, and within a day at the latest. Actions often have due dates within the week, and an owner who finds out about their action four days later has lost those four days.
Should minutes say who said what?
Mostly no. Record what the group decided, not each person's contribution. Name people when it matters for the record, for example when someone asks for their disagreement with a decision to be noted.
What is the difference between meeting minutes and meeting notes?
Meeting notes can be anyone's personal record, in any shape. Minutes are the shared, agreed record that goes to the group. In practice, notes taken in a fixed format and sent the same day work as minutes for most team meetings.