Meeting minutes are the official written record of a meeting’s key decisions, action items, and discussion points. They capture what was agreed and who owns what, not a word-for-word transcript of everything said. This guide gives you a copy-paste template, filled examples for three common meeting types, and the exact reporting verbs and clarification phrases to capture decisions accurately in real time.
Meeting minutes are the official record of what a group decided, who owns each action item, and by when. They’re distinct from personal notes: minutes are shared, approved, and relied on by the whole team.
What good meeting minutes include
Every meeting minutes format covers the same core elements, whether you’re documenting a quick team sync or a formal board session. Missing any one of these turns your minutes from a reliable record into a source of confusion.
- Date, time, and location: Include the full date, start and end times, and whether the meeting was in person, virtual, or hybrid.
- Attendees and absentees: List everyone who joined and anyone who was invited but couldn’t attend.
- Agenda items discussed: Reference the meeting agenda so readers can map each discussion point back to its original purpose.
- Key discussion points: Summarize the substance of each topic in one or two sentences. Capture the reasoning behind decisions, not a verbatim transcript.
- Decisions made: State what was agreed, who approved it, and any conditions attached.
- Action items with owner and deadline: Every action needs a name and a date. Without both, accountability disappears.
- Next meeting date: Confirm when the group will reconvene and flag any pre-work required.
The difference between meeting minutes and meeting notes comes down to status. Minutes are the official, reviewable record that the team or organization can reference for decisions and commitments. Notes are personal memory aids you keep for yourself. In formal settings, the chair or a designated secretary typically takes minutes, and the chair approves them before distribution. In less formal teams, the role often rotates.

Meeting minutes template you can copy right now
This meeting minutes template covers the fields you’ll need for most professional meetings. Copy the structure below and fill it in during or immediately after your next meeting.
| Field | What to write |
|---|---|
| Meeting title | Name of the meeting (e.g., Weekly Product Sync) |
| Date / Time / Location | Include time zone if attendees are remote |
| Attendees | Full names and roles |
| Absentees | Anyone invited but not present |
| Agenda item | Topic heading (repeat this row and the three rows below for each agenda item) |
| Discussion summary | Key points raised, in 2–3 sentences |
| Decision | What the group agreed on, stated clearly |
| Action item / Owner / Deadline | One row per task: what, who, by when |
| Next meeting date | Confirmed date, time, and time zone |
| Minutes prepared by | Your name and the date you distributed the minutes |
This meeting minutes format works for most team meetings. For formal board meetings, add rows for motions, seconds, and vote counts, and follow Robert’s Rules for recording them.
Once your minutes are approved, share them via email or your team’s shared workspace (Google Docs, Notion, or SharePoint) and store them where the team can reference past decisions.
Meeting minutes examples for three common meeting types
A filled meeting minutes example beats a blank template because you can compare your own draft against it and spot what’s missing.
Weekly team sync
Meeting title: Marketing Team Weekly Sync
Date: Tuesday, 14 January 2025
Time: 10:00–10:30 AM (CET)
Location: Zoom (Meeting ID: 845 2901 7733)
Facilitator: Priya Sharma (Team Lead)
Note-taker: Lucas Mendes
Attendees: Priya Sharma, Lucas Mendes, Anna Kowalski, James Chen
Absent: Sofia Reyes (on PTO)
Agenda items discussed:
- Q1 campaign timeline review. Priya confirmed the social media campaign launches on 3 February. Anna noted that creative assets are 80% complete and flagged a delay on the video deliverables from the external agency. The team agreed to move the video launch date from 3 February to 10 February to allow for final edits.
- Blog content calendar. James presented the February content calendar with six posts planned. Priya suggested adding a customer case study to the schedule. James agreed and will identify a suitable customer by Friday.
- Budget reallocation for paid ads. Priya raised the option of shifting €2,000 from the print budget to paid social. Anna supported the proposal based on Q4 performance data. The team approved the reallocation.
Decisions made:
- Video launch date moved from 3 February to 10 February.
- €2,000 reallocated from print budget to paid social ads.
Action items:
| Action item | Owner | Deadline |
|---|---|---|
| Follow up with video agency on revised delivery date | Anna Kowalski | 16 January |
| Identify customer for February case study | James Chen | 17 January |
| Update campaign timeline in Asana and notify Sofia | Lucas Mendes | 15 January |
Next meeting: Tuesday, 21 January 2025, 10:00 AM (CET)
Project kickoff or status update
When running effective meetings with cross-functional teams, structured agendas produce minutes that are far easier to capture accurately.
Meeting title: Website Redesign Project, Sprint 3 Status Update
Date: Thursday, 9 January 2025
Time: 2:00–2:45 PM (EST)
Location: Conference Room B / Microsoft Teams
Facilitator: David Okafor (Project Manager)
Note-taker: Mei Lin Wu
Attendees: David Okafor, Mei Lin Wu, Rachel Adams (Design Lead), Tom Eriksson (Engineering Lead), Carla Díaz (Product Owner)
Absent: None
Agenda items discussed:
- Sprint 2 retrospective. David reviewed Sprint 2 deliverables. All three milestones were completed on schedule. Rachel noted that the design review cycle took longer than estimated and recommended adding a buffer day to future sprints.
- Sprint 3 scope and timeline. Carla presented the Sprint 3 requirements, including the new checkout flow and updated product pages. Tom raised a concern about engineering capacity, noting that two developers are supporting a production issue through 15 January. David proposed reducing Sprint 3 scope to the checkout flow only and deferring product pages to Sprint 4. Carla agreed.
- Resource allocation. David confirmed that a contract front-end developer will join the team on 13 January. Rachel requested that the contractor focus on responsive design implementation. Tom agreed to onboard the contractor during the first two days.
- Stakeholder demo scheduling. Carla requested a stakeholder demo at the end of Sprint 3. The team agreed on 30 January at 11:00 AM (EST). David will send calendar invitations to the leadership team.
Decisions made:
- Sprint 3 scope reduced to checkout flow only. Product pages deferred to Sprint 4.
- Stakeholder demo scheduled for 30 January at 11:00 AM (EST).
- Contract developer to focus on responsive design tasks.
Action items:
| Action item | Owner | Deadline |
|---|---|---|
| Update Sprint 3 backlog in Jira to reflect revised scope | David Okafor | 10 January |
| Prepare onboarding documentation for contract developer | Tom Eriksson | 12 January |
| Share checkout flow wireframes with engineering | Rachel Adams | 13 January |
| Send stakeholder demo invitations | David Okafor | 13 January |
Next meeting: Thursday, 16 January 2025, 2:00 PM (EST)
Formal or board meeting
Formal meetings often follow Robert’s Rules of Order conventions, where decisions are recorded as motions with seconders and vote counts. Every motion, vote outcome, and abstention must appear in the minutes as part of the official record.
Formal meeting minutes record motions, the name of the person who moved each motion, the seconder, and the vote count. Governance teams report spending an average of 10 hours writing up the minutes of a typical board meeting. (Board Intelligence)
Meeting title: Quarterly Board of Directors Meeting
Date: Monday, 6 January 2025
Time: 9:00–10:30 AM (GMT)
Location: Boardroom, 4th Floor, London Office
Chairperson: Margaret Thornton
Secretary: Daniel Ferreira
Directors present: Margaret Thornton, Daniel Ferreira, Helen Park, Richard Bauer, Amina Yusuf, George Whitfield
Directors absent: Catherine Moreau (excused)
Quorum: Confirmed (6 of 7 directors present)
Call to order: The Chairperson called the meeting to order at 9:03 AM.
Approval of previous minutes: The minutes of the 7 October 2024 board meeting were presented. No amendments were proposed. Helen Park moved to approve the minutes as circulated. Richard Bauer seconded. The motion carried unanimously (6-0).
Agenda items discussed:
- Q4 financial report. George Whitfield presented the Q4 financial results. Revenue reached £4.2M, exceeding the forecast by 8%. Operating expenses remained within budget. Amina Yusuf requested a detailed breakdown of the consulting division’s margin improvement. George agreed to circulate a supplementary report within five business days.
- 2025 annual budget approval. The Chairperson presented the proposed 2025 annual budget of £15.8M. Richard Bauer raised a concern regarding the 12% increase in the technology allocation. George Whitfield clarified that the increase reflects the planned CRM migration. After discussion, Amina Yusuf moved to approve the 2025 annual budget as presented. Helen Park seconded. The motion carried (5-1, Richard Bauer opposed).
- Board committee appointments. The Chairperson proposed appointing Amina Yusuf as Chair of the Audit Committee, effective 1 February 2025. Helen Park moved to approve the appointment. George Whitfield seconded. The motion carried unanimously (6-0).
- Policy update on data governance. Daniel Ferreira presented the revised data governance policy. The board reviewed the key amendments regarding data retention periods and third-party access controls. Richard Bauer moved to adopt the revised policy. Amina Yusuf seconded. The motion carried unanimously (6-0).
Action items:
| Action item | Owner | Deadline |
|---|---|---|
| Circulate Q4 consulting division margin report | George Whitfield | 13 January |
| Notify Amina Yusuf formally of Audit Committee appointment | Margaret Thornton | 8 January |
| Distribute revised data governance policy to all staff | Daniel Ferreira | 20 January |
Adjournment: Helen Park moved to adjourn. Richard Bauer seconded. The meeting adjourned at 10:22 AM.
Next meeting: Monday, 7 April 2025, 9:00 AM (GMT)
Reporting verbs and sentence patterns for accurate minutes
The verb you choose to describe what happened in a meeting shapes how neutral and precise your minutes read. When you’re learning how to write meeting minutes in a second language, a reliable bank of reporting verbs removes guesswork and keeps your tone consistently professional.
Reporting verbs in meeting minutes signal the nature of the contribution: “agreed” records a decision, “raised” flags a concern, “clarified” corrects a misunderstanding. Choosing the right verb is what separates clear minutes from vague ones.
The table below groups 15 verbs by function so you can pick the right one quickly while the conversation is still moving.
| Function | Verb | Example sentence |
|---|---|---|
| Decisions | agreed | The team agreed to launch the pilot in Q3. |
| approved | The board approved the revised budget. | |
| resolved | The committee resolved to extend the contract by six months. | |
| rejected | The group rejected the proposal to reduce headcount. | |
| Discussion | noted | Priya noted a potential conflict with the compliance deadline. |
| raised | Tom raised concerns about vendor reliability. | |
| highlighted | Sara highlighted the gap between projected and actual costs. | |
| questioned | David questioned whether the timeline was realistic. | |
| clarified | Maria clarified that the policy applies only to full-time staff. | |
| Actions | assigned | The project lead assigned the risk assessment to Jun. |
| committed | Leo committed to delivering the draft by 14 April. | |
| volunteered | Ana volunteered to coordinate with the legal team. | |
| deferred | The group deferred the pricing discussion to the next meeting. | |
| Information | presented | Carlos presented the Q1 sales results. |
| confirmed | HR confirmed that all contracts had been signed. |
For broader professional vocabulary for meetings, keep a separate reference list you can review before each session.
Once you’ve chosen the right verb, drop it into one of these sentence patterns. They work for any meeting type, from a quick team sync to a formal board session.
Recording a decision: “The team agreed to [action] by [date].”
Example: The team agreed to finalize the vendor shortlist by 18 April.
Assigning an action item: “[Name] will [task] by [deadline].”
Example: Jun will complete the risk assessment by 21 April.
Logging an unresolved issue: “[Topic] was deferred to [next meeting/date].”
Example: Regional pricing was deferred to the 28 April project review.
Recording a formal motion: “[Name] moved to [action]; seconded by [Name]; motion carried [vote count].”
Example: Laura moved to approve the amended charter; seconded by Daniel; motion carried 7–1.
Noting a clarification: “[Name] clarified that [fact or correction].”
Example: Maria clarified that the new policy takes effect on 1 May, not 1 June.
Knowing how to write meeting minutes becomes far easier when you aren’t inventing phrasing on the fly. Copy these patterns into a notes template before the meeting starts, and you’ll spend less energy on language and more on capturing what actually matters.
What to say when you miss something during the meeting
Asking a speaker to repeat or clarify a point is part of your job as the minute-taker, not an interruption. Meeting chairs want accurate records, and they’d rather pause for five seconds than discover a wrong action item in the final minutes. Every experienced note-taker, native speaker or not, asks for clarification regularly.
Keep these phrases ready so you can speak up without hesitating. Group them by situation and use whichever fits the moment.
- Confirming a decision: “Just to confirm for the minutes, the decision is to…” or “So we’re agreeing to proceed with X. Is that correct?”
- Requesting a repeat: “Could you repeat the action item so I can capture it accurately?” or “I want to make sure I have that right. Could you say that once more?”
- Slowing the pace: “Could we pause for a moment so I can capture that?” This is a perfectly professional request. For more strategies on interrupting politely, those techniques transfer directly to minute-taking.
- Verifying names or spelling: “Could you spell that for the minutes?”
You don’t need to memorize all of these. Pick two or three that feel natural and practice saying them aloud before the meeting starts. Once you’ve used a clarification phrase successfully in one meeting, it becomes automatic in the next.
Building this habit does more than improve your minutes. Asking for clarification signals professionalism, not uncertainty, and it builds the confidence to participate actively in any English-language meeting.
Common mistakes in meeting minutes: Before and after rewrites
Even a good template won’t save minutes that use vague language or include content that doesn’t belong. These before/after pairs show the most frequent mistakes and how to fix them quickly.
Before: “Lisa thought the new vendor was way too expensive and everyone seemed to agree it was a bad deal.”
After: “Lisa raised concerns about the vendor’s pricing. The team agreed to request a revised quote before proceeding.”
Before: “We need to update the onboarding flow.”
After: “Priya will redesign the onboarding flow and share a draft with the team by June 20.”
Before: “Marco talked for a while about how the Q2 numbers were disappointing and said we should probably look at what happened in the EMEA region because he felt like the pipeline wasn’t being managed well, and then Jun mentioned that the CRM data might be incomplete, which led to a longer discussion about data hygiene.”
After: “Marco reported that Q2 revenue fell short of target in EMEA. Jun noted that incomplete CRM data may have affected pipeline visibility. The team assigned a data audit to Jun, due July 5.”
Applying concise writing techniques turns transcript-style entries into minutes people actually read.
Before: “Off the record, David mentioned he’s thinking about leaving the company. Sarah also shared salary details for the new hire.”
After: (Omitted. Confidential remarks and off-the-record comments are excluded from meeting minutes.)
One pattern connects all four fixes: good minutes use past tense, name the person responsible, state the decision or action with a deadline, and leave out personal opinions and confidential asides. When you review your draft, scan each entry for those four elements. Any that are missing mark your rewrite target.
How to write meeting minutes faster with AI tools
Transcription tools like Otter.ai, Granola, Microsoft Teams AI, and Google Meet summaries can capture raw meeting content so you’re not typing every word in real time. They’re genuinely useful as a first pass. A human minute-taker still needs to edit that transcript for accuracy, neutrality, and completeness, because no tool reliably distinguishes a final decision from a passing comment.
Pasting rough notes into ChatGPT or a similar tool can reshape them into polished minutes, though you should always verify names, dates, and decisions against what actually happened. AI handles speed well. Choosing the right reporting verb, flagging an unresolved issue, and knowing when to ask “Can I confirm what we agreed?” during the meeting itself are still your calls.
Write minutes that people actually read
Good meeting minutes are a professional communication skill that builds your credibility with every send. When you capture decisions clearly and assign action items with precision, people notice. That visibility matters even more when you’re working in a second language, because well-written minutes demonstrate your command of the conversation. Among Talaera learners, Meetings is the second most-accessed learning category on the platform, which reflects how much room most professionals feel they have to grow here.
Grab the template, keep the reporting-verbs table where you can see it, and don’t hesitate to ask for clarification when the conversation moves faster than your notes. Those three habits will make your minutes the ones people actually open. If writing and communicating in English is part of your daily work, Talaera’s business English training helps professionals contribute confidently in business meetings and documentation.
Frequently asked questions
What is the correct format for meeting minutes?
Meeting minutes follow a consistent structure: meeting title and date, list of attendees and absentees, agenda items discussed, decisions made, action items with owners and deadlines, and the date of the next meeting. You can use a table or a bulleted outline, as long as every decision and action item is easy to find. Formal meetings governed by Robert’s Rules also require a record of motions, seconds, and vote counts.
What should not be included in meeting minutes?
Minutes should leave out personal opinions, side conversations, and word-for-word transcripts of the discussion. Record what was decided and who is responsible, not who said what during the debate. Sensitive or off-the-record remarks should also stay out of the written record.
What is the difference between meeting minutes and meeting notes?
Meeting notes are informal, personal jottings you take to help yourself remember the conversation. Minutes are the official, shared record of decisions, action items, and outcomes that the whole team relies on. If you want to turn rough notes into a clear summary for your team, learning how to summarize a meeting is a useful next step.
How can I get better at writing meeting minutes in English?
Minute-taking in a second language puts real pressure on both your writing and your listening. Talaera’s business English programs include targeted practice on the vocabulary, sentence patterns, and clarification phrases that make minutes accurate and professional. Professionals across 100+ countries use the platform to build exactly these skills in the context of their real work.
