The short answer to how to write meeting minutes: minutes aren't a transcript of everything said in a meeting; they're a record of the decisions made, the actions assigned and the issues still open. Good minutes include the meeting's name, date and attendees, the agenda items, a short summary and decision for each item, and an action list with an owner and due date. Minutes should go out the same day as the meeting and be clear enough that someone who wasn't there can understand them.
Why minutes matter
Everyone in a meeting hears the same thing, but everyone remembers it differently. "That's not what we discussed" a week later is the classic outcome of a meeting with no written record. Minutes do three jobs:
- Shared memory. When decisions and the reasoning behind them are written down, differences in interpretation shrink later on.
- Accountability. When it's clear who will do what, and by when, actions can be tracked.
- Knowledge transfer. Team members who weren't there learn what happened without having to sit through it.
In some settings, such as company board meetings, shareholder meetings or building management meetings, minutes are an official document and must follow specific formatting requirements. This article focuses on everyday team and project meetings at work; for formal meetings, check the applicable regulations and your organization's legal team.
How to write meeting minutes: the core sections
Header information
- The meeting's name and purpose
- Date, time and location or online platform
- Attendees, absentees and any guests
- Who took the minutes
Agenda and summary
For each agenda item, a short summary: which options were discussed, what information was shared. The summary isn't a chronological record of the discussion; it's the context needed to understand the decision. There's no need to write down who said what; unless there's a formal requirement, summarizing views without attributing them to individuals is usually healthier.
Decisions
Each decision should be a separate, clear sentence. "Pricing was discussed" is not a decision; "The new plan's monthly price will not be set above the current price; the final figure will be confirmed with finance approval" is a decision.
Action items
The action table is the most-read part of the minutes. Every action item needs three things: what will be done, who will do it, and by when.
Open issues and next meeting
Issues that couldn't be settled, the information needed to settle them, and the date of the next meeting.
A meeting minutes template you can copy
Meeting: [Meeting name] Date / time: [MM/DD/YYYY, HH:MM - HH:MM] Location / platform: [Meeting room or online] Attendees: [Full name, Full name] Absent: [Full name] Minutes taken by: [Full name]
Agenda
- [Item 1]
- [Item 2]
- [Item 3]
Summary and decisions
1. [Item 1] Summary: [Two or three sentences] Decision: [Clear decision sentence]
2. [Item 2] Summary: [Two or three sentences] Decision: [Clear decision sentence]
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | [What will be done] | [Name] | [Date] |
| 2 | [What will be done] | [Name] | [Date] |
Open issues: [Issue and information needed] Next meeting: [Date and time]
A filled-in example
Meeting: Website redesign project, weekly status Date / time: Tuesday, 10:00 - 10:30 Attendees: Project manager, designer, software developer, marketing lead Minutes taken by: Project manager
1. Homepage design Summary: Two design alternatives were presented. The team agreed the second alternative is more readable on mobile. Decision: We'll proceed with the second alternative.
2. Launch date Summary: The risk of missing the planned date due to delays in content translation was discussed. Decision: The launch date stands; if translations aren't finished by Friday, launch will be pushed back one week.
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | Share the final homepage design | Designer | Thursday |
| 2 | Confirm translation status with the agency | Marketing lead | Wednesday |
| 3 | Update the test environment | Software developer | Friday |
Open issues: Whether the blog section moves to the new site; waiting on traffic data. Next meeting: Next Tuesday, 10:00
Writing rules for good minutes
- Write during the meeting, tidy up afterward. Open the template before the meeting and fill in the agenda; during the meeting you only fill in the blanks.
- Confirm decisions on the spot. At any fuzzy point, asking "I'm writing this down as the decision, is that right?" heads off later arguments.
- Keep it short. Minutes for a one-hour meeting usually shouldn't run past a page.
- Share them the same day. The longer minutes wait, the more details get forgotten and the more actions slip.
- Allow time for corrections. A note like "If anything is missing or wrong, let me know by noon tomorrow" turns the minutes into a shared document.
- Move action items into your task tool. Minutes are a record; follow-up should happen in your task management tool.
Where should minutes be stored?
When minutes are scattered across inboxes, finding out months later when and why a decision was made gets hard. Set up a shared folder or document space for each project or team and keep all minutes there with the same naming convention, for example with the date at the front. Adding a link to that shared document in the summary you email out handles both notification and archiving at once.
For recurring meetings, keeping all minutes in a single document with the newest at the top also works well. That way you can quickly review the previous meeting's action items at the start of the next one.
If you use meeting recordings or automatic transcripts, remember that they don't replace minutes. Nobody reads the transcript of an hour-long conversation from start to finish. A recording can be a source for going back to the details when needed, but decisions and action items still belong in short minutes that a person has confirmed. If you're recording, don't forget to tell participants in advance.
Meeting minutes checklist
- Header information is complete.
- Every agenda item has a decision or an "open issue" note.
- Every action item has an owner and a due date.
- Someone who wasn't at the meeting could read the minutes and understand what happened.
- The minutes were shared the same day.
To make the meetings themselves more productive, take a look at the effective meetings guide on our blog.
Conclusion
The essence of writing meeting minutes is recording the outcome, not the conversation. Header information, a short summary and decision for each item, action items with owners and dates, and open issues form the backbone of good minutes. Adapt the template to your own team and make sharing it the same day after every meeting a habit.
From Weras Labs
We can help you with this
We turn what you just read into working software for your business. You talk to the person writing the code; price and timeline are clear from day one.
Frequently asked questions
What should meeting minutes include?
The meeting's name and date, attendees, agenda items, a short summary and decision for each item, an action list with owners and due dates, and any open issues. Add the date of the next meeting if relevant.
Who should take meeting minutes?
A note-taker named at the start of the meeting. If this person isn't the facilitator, running the discussion and taking notes don't get in each other's way. In small meetings, the organizer can handle both roles.
When should meeting minutes be shared?
Ideally the same day as the meeting. The longer the delay, the more details get forgotten, the later actions start and the more corrections the minutes need.
What's the difference between meeting notes and meeting minutes?
Meeting notes can be personal and free-form; minutes are a shared document circulated to participants that formally records decisions and action items. In some formal meetings, minutes are also signed and follow specific format requirements.
About the author

Habip Dayan
Founder of Weras Labs
Habip Dayan is the founder of Weras Labs, a company that builds software products for professionals and teams. He has been building software since 2018 and writes about AI, cloud architecture and product design.
Comments
Be respectful; no ads or personal data. Comments that break the rules are removed.



