Meeting minutes are the official written record of what happened during a meeting. They capture the key discussion points, decisions made, action items assigned, and any blockers or risks that were raised. Without well-structured minutes, important decisions get forgotten, action items slip through the cracks, and attendees leave with different recollections of what was agreed.
This generator helps you produce clean, consistently formatted meeting minutes without spending time wrestling with document templates or formatting. Simply fill in your meeting details, enter your notes for each section, and the tool produces a structured text output that you can copy and paste into an email, shared document, or project management tool.
Good meeting minutes serve three purposes. First, they provide an authoritative record for anyone who attended, confirming what was decided and what each person committed to. Second, they bring absent colleagues up to speed quickly. Third, they create accountability by documenting who owns each action item and when it is due.
Generator
Separate names with commas
One point per line for best formatting
One decision per line
Action item 1
One item per line
One item per line
Copied
How to Use
Using this generator is straightforward. Follow these steps to produce well-formatted meeting minutes in under a minute.
Fill in the meeting metadata. Enter the meeting title, date, time, location or link, facilitator name, and the list of attendees. The date defaults to today, so you only need to change it if you are writing up minutes from a previous meeting.
Summarise the discussion. In the "Key discussion points" field, write a brief summary of each major topic that was covered. Use one line per point for clean formatting in the output.
Record decisions. List each decision that was agreed upon during the meeting. Be specific: "Agreed to postpone the launch by two weeks" is far more useful than "Discussed the launch timeline".
Add action items. For each action item, enter a clear description of the task, assign an owner, and set a due date. Click "Add item" to create additional action items as needed.
Note blockers and follow-ups. Capture any risks, blockers, or dependencies that were raised, along with items that need to be revisited in a future meeting.
Generate and copy. Click "Generate minutes" to produce the formatted output, then use "Copy to clipboard" to paste it wherever you need it.
Example Output
Here is an example of the formatted minutes this tool produces. The output follows a consistent structure that is easy to scan and suitable for sharing via email, Slack, or a shared document.
MEETING MINUTES
=====================================
Title: Weekly Product Sync
Date: 13 March 2026
Time: 10:00
Location: Room 4B, London Office
Facilitator: Sarah Chen
Attendees: Sarah Chen, James Park, Priya Sharma, Tom Walsh
-------------------------------------
KEY DISCUSSION POINTS
-------------------------------------
- Reviewed progress on the Q2 roadmap. Three of five initiatives are on track.
- Discussed customer feedback from the latest NPS survey. Onboarding scores dropped by 4 points.
- Priya presented the updated design mockups for the dashboard redesign.
-------------------------------------
DECISIONS MADE
-------------------------------------
- Agreed to prioritise the onboarding flow improvements over the reporting feature.
- Approved the new dashboard layout with minor adjustments to the navigation.
-------------------------------------
ACTION ITEMS
-------------------------------------
1. [James Park] Draft a revised onboarding flow proposal (Due: 20 March 2026)
2. [Priya Sharma] Update dashboard mockups with navigation feedback (Due: 18 March 2026)
3. [Tom Walsh] Schedule user testing sessions for the following week (Due: 17 March 2026)
-------------------------------------
BLOCKERS / RISKS
-------------------------------------
- The analytics API migration is delayed by one week, which may affect the reporting feature timeline.
- Still waiting on legal sign-off for the updated terms of service.
-------------------------------------
FOLLOW-UP ITEMS
-------------------------------------
- Revisit the reporting feature priority at the next sync.
- Tom to share user testing results once available.
=====================================
Minutes prepared on 13 March 2026
Best Practices for Writing Good Minutes
Meeting minutes are only valuable if they are accurate, clear, and easy to act upon. These practices will help you produce minutes that your team actually reads and uses.
Write minutes on the same day. Memory fades quickly. The longer you wait, the more details you lose and the less accurate your record becomes. Ideally, distribute minutes within a few hours of the meeting ending.
Focus on outcomes, not the play-by-play. Minutes should capture what was decided and what needs to happen next, not a transcript of who said what. Summarise discussions in two to three sentences rather than recording every comment.
Make action items specific and measurable. "Look into the API issue" is vague. "James to investigate the API timeout errors and report findings by Friday" is actionable. Every action item should have a clear owner and a due date.
Use consistent formatting. A standard structure makes minutes easy to scan across multiple meetings. This generator handles that for you, but the principle applies even if you are writing minutes manually.
Separate decisions from discussion. Decisions deserve their own section so they are easy to find later. When someone asks "Did we agree to do X?", they should not have to wade through paragraphs of discussion notes to find the answer.
Note who was present. The attendee list establishes who was part of the decisions made. It also tells absent colleagues that they missed the meeting and should review the minutes.
Include context for absent readers. Write minutes as though the reader was not in the room. Avoid shorthand or references that only make sense if you were there.
Review before distributing. A quick read-through catches errors, fills in gaps, and ensures action items are correctly attributed. Two minutes of review can prevent confusion that takes much longer to resolve.
Store minutes in a shared, searchable location. Email is convenient for distribution but poor for retrieval. Keep a shared folder, wiki page, or project management space where all minutes are archived and easily searchable.
Common Mistakes
These are the pitfalls that undermine the value of meeting minutes. Avoiding them makes the difference between minutes that gather dust and minutes that drive accountability.
Writing a transcript instead of a summary. Minutes are not a verbatim record. Recording every exchange produces a document that nobody reads. Distil the conversation into its essential points and outcomes.
Vague action items without owners. "We should follow up on this" is not an action item. If there is no named owner and no due date, it will not get done. Be explicit about who is responsible and when it is expected.
Waiting too long to write them up. Minutes written three days after the meeting are unreliable. Details blur, recollections diverge, and the minutes lose their authority as a factual record.
Omitting decisions. The single most important function of minutes is recording what was decided. If attendees leave with different interpretations of the outcome, the meeting has failed, and poor minutes make that worse.
Skipping the attendee list. Without knowing who was present, it is impossible to determine whether the right people were involved in the decisions. The attendee list also signals to absent colleagues that they should review the notes.
Burying action items in prose. Action items scattered throughout discussion notes are easy to miss. Always collect them in a dedicated section with clear formatting so nothing falls through the cracks.
Not distributing minutes at all. Minutes that sit in a personal notebook help nobody. The value of minutes comes from sharing them promptly with all attendees and relevant stakeholders.
Including unnecessary detail about disagreements. Unless the disagreement is relevant to the decision, there is no need to record who argued what. Focus on the conclusion, not the debate that led to it.