How do AI meeting notes work?
AI meeting notes start with a record of what was said, which can be your rough notes, a transcript from your video call or both. Given clear instructions, your AI extracts four things from that record: the decisions made, the actions with an owner and a date, the questions still open and a short summary.
Your AI is good at sorting and organising information, but it is poor at knowing what people meant and didn't say. So the method has one firm rule: the AI records only what is in the notes and marks every gap. A person then checks the result before it goes to the team.
This guide covers the whole loop, from setting up the meeting and handling consent to turning notes into actions that get checked, sent and tracked. Along the way you get two prompts, a meeting summary template and a checklist.
Step 1: Set the meeting up so the notes can work
Good notes depend on a meeting with a clear, agreed goal. If nobody knows what the meeting is for, no AI can find the decisions in it, because there weren't any.
- Write a short agenda in a shared doc that lists the goal and the questions to settle in order. Link the document in the calendar invitation, so that everyone can prepare beforehand.
- Name one owner for the meeting, who is responsible for making sure the notes get checked and sent afterwards.
- Take notes in the agenda doc, because writing under each agenda item keeps the notes and their topics together. That structure makes them far easier for your AI to organise later.
- Say decisions out loud, since a phrase like "So we've decided to..." makes each decision easy to spot in a transcript later.
- Name the owner and date as you go. The sentence "Sam will send the quote by Friday" gives your AI something to record, while "someone should send the quote" gives it a gap.
If you're not sure the meeting is worth holding at all, the free meeting cost calculator shows what a regular meeting costs in people's time over a whole year.
Do you need consent to record a meeting?
Often you do, and the rules depend on where you and the other people in the call are based. Some places let one person in a call record it, while others need everyone's agreement, and workplace and privacy laws can add further rules. We can't tell you the law for your country, so check your local rules or ask a lawyer if you're unsure.
Whatever the law requires in your area, these habits keep you on safe ground:
- Tell everyone at the start that you're recording or using an AI note taker, and explain why.
- Give people a real way to say no, and take notes by hand if anyone does.
- Take extra care with customers, job candidates and anyone else outside your business.
- Don't record private or sensitive talks, such as those about health, pay or discipline, unless everyone has agreed and you have a clear reason.
- Decide in advance how long you will keep recordings and transcripts, and exactly who is allowed to access them.
Some video tools build an automatic notice into the call itself. According to Google Meet Help, as of November 2026, the "Take notes for me" feature tells everyone that notes are being taken and displays an icon on their screens. A built-in notice helps, but it doesn't replace asking people directly.
Step 2: Turn rough notes or a transcript into action items
Paste your notes or transcript with the prompt below, which tells your AI to sort everything into decisions, actions and open questions. It must never invent an owner or a date, so whenever one is missing, the AI writes "no owner" or "no date" for you to fix.
The rule is strict for a practical reason, since an action without an owner rarely gets done. An action with a made-up owner is even worse, because the wrong person ends up with a task they never agreed to.
Prompt: Turn meeting notes into decisions and action items
You are a careful meeting secretary. Turn the notes or transcript below into clear meeting notes. Meeting: [name], on [date]. People there: [names and roles]. Goal of the meeting: [one line]. Steps: 1. Read everything once before you write. 2. List each decision. Quote or closely follow the words used. Only list it if someone clearly agreed to it. 3. List each action. Each action has: what will be done, the owner, the due date and the source line it came from. 4. If no owner was named, write "NO OWNER". If no date was given, write "NO DATE". Never guess either one. 5. List open questions: anything raised but not settled, and who should answer it. 6. Write a summary of no more than five sentences. Rules: - Use only what is in the notes. Do not add tasks, dates or decisions. - Mark anything unclear with [CHECK] and say why. - Leave out side chat, jokes and personal details that aren't needed. Output format: four headed sections (Summary, Decisions, Actions, Open questions). Put the actions in a table with the columns Action, Owner, Due, Source. Notes or transcript: [paste]
Transcripts are long and messy, so if your transcript runs to many pages, ask your AI to work through it one agenda item at a time. Working in smaller sections means fewer actions slip through unnoticed.
A meeting summary template you can reuse
Use an identical structure for every meeting, so people always know where to look for their actions. Paste this template into your agenda doc, or add it to the prompt above as the output format.
Template: Meeting summary
Meeting: [name] Date: [date]. Length: [minutes]. People there: [names]. Notes checked by: [name]. Summary. [Three to five sentences. What was the meeting for, and what came out of it?] Decisions. 1. [Decision], agreed by [names]. 2. [Decision], agreed by [names]. Actions. | Action | Owner | Due | Status | | [What will be done] | [one name] | [date] | Open | Open questions. 1. [Question]. Who answers: [name]. By: [date]. Next meeting: [date], or "none needed".
Assign each action to a single named individual, because "Sam and Alex" often turns out to mean neither of them. If two people share a job, pick one of them to report back on it.
Step 3: Check, send and track the actions
Meeting notes are only useful if the actions in them actually get done. That means checking them, sending them the same day and keeping one running list that you review at the next meeting.
Check before you send
- Every decision was genuinely agreed, rather than simply discussed.
- Every action has one owner and a date, or is marked for you to fix.
- Each owner agreed to their actions during the meeting itself.
- Every [CHECK] mark has been answered and removed.
- Names, numbers and dates match what was actually said.
- Nothing private or sensitive appears in notes that go to a wide group.
Send a short follow-up
Once the notes are correct, ask your AI for a follow-up message. Keep it short and limited to the decisions, each person's actions and the open questions, so nobody has to dig for their part.
Prompt: Write the follow-up and check open actions
You are helping me follow up after a meeting. I've checked the notes below and they are correct. Part 1. Write a follow-up message to everyone who attended. - Start with the decisions, one line each. - Then list the actions, grouped by owner, with due dates. - Then the open questions and who will answer them. - Under 200 words. Plain and friendly. No new tasks. Part 2. Compare these actions with the list from our last meeting, pasted below. - Which earlier actions are done, still open or overdue? - Which earlier actions weren't mentioned at all this time? - Draft a one-line reminder for each overdue action, addressed to its owner. Rules: use only what is in the two lists. If a status is unclear, say "not mentioned" instead of guessing. This meeting's checked notes: [paste] Last meeting's action list: [paste]
Keep one action list
Keep a single running list for each regular meeting, with columns for the action, owner, due date and status. The free meeting action register turns a pasted list into a table and flags any missing owners and due dates. It works in your browser and doesn't send or schedule anything, so open the list at the start of the next meeting and close out whatever is done.
Worked example: GitLab's live doc meetings
GitLab, the software company, publishes its company handbook online, including detailed guidance on how it runs meetings. Its rules make a good model for AI meeting notes, because they make sure the notes exist and are clear before any AI sees them. As of November 2026, the handbook includes these recommendations:
- Every work meeting should have a shared, editable agenda doc linked in the invite. The handbook sums this up as "No agenda, no attenda" (GitLab live doc meetings).
- Notes go inline under each agenda item rather than in a separate notes section, and anyone who isn't talking helps take them.
- Notes don't need to be word for word, but they should be clear on decisions and next steps.
- Each meeting has a DRI, GitLab's term for the one directly responsible person. After the meeting, action items are captured from the notes, for example with TODO and DONE tags or as tasks in GitLab (GitLab all-remote meetings).
- When some people are in other time zones, the handbook suggests leaving 24 to 48 hours for them to respond to decisions and actions.
The handbook doesn't say that GitLab uses AI to write these notes, and we're not claiming it does. A small team could still copy the habits and add an AI step at the end.
What goes in
Say your team copies the format for a weekly planning call, with three numbered items in the agenda doc. Under item 2, the shared notes read as follows (example notes written for this article): "Agreed to move the launch to the 14th. Priya to update the landing page. Need to check stock with the supplier."
What comes out
If you run prompt 1 on those notes, you'd expect something like the table below, which is an example draft and not GitLab's real notes:
| Type | Item | Owner | Due |
|---|---|---|---|
| Decision | Launch moves to the 14th. | Agreed in item 2 | None |
| Action | Update the landing page for the new date. | Priya | NO DATE |
| Action | Check stock with the supplier. | NO OWNER | NO DATE |
The AI hasn't guessed who will call the supplier, and has flagged the gap so the meeting owner can fix it before the follow-up goes out. That small flag is what stops important actions from getting lost.
Common mistakes, and what to do instead
- Trusting the summary without reading it is risky, because AI summaries can sound certain and still miss a point. Read the decisions and actions every time, which typically takes about two minutes.
- Letting the AI fill in owners means it picks the most likely name, which may be the wrong one. Tell it to mark missing owners, and then confirm with the person yourself.
- Treating discussion as a decision creates confusion, because "we talked about raising prices" isn't the same as "we agreed to raise prices". Ask the AI to list a decision only when someone clearly agreed to it.
- Recording without telling people can break the law and always damages trust, so announce it at the start of every meeting.
- Sending notes days later is a problem because people forget what they agreed to, so send the follow-up on the same day.
- Starting a new action list every week lets old actions quietly vanish, so keep one running list and check it at the start of each meeting.
Where AI Blocks helps
All of these are free: you copy the prompt, or download the skill, workflow or specialist, and use it in your own AI. AI Blocks doesn't join your calls, record anything or send messages on your behalf.
- Rough-note meeting minutes writer: paste rough meeting notes to get short minutes with decisions, owners and dates.
- Meeting minutes writer: a skill that turns rough notes into short minutes with decisions, action items with owners and dates, and open questions.
- Action item tracker: share meeting notes or email threads to get action items with owners, deadlines and unresolved commitments.
- Meeting action follow-up writer: a workflow that gives you a sourced action list, clear owners and dates, and follow-up drafts for open items.
- Meeting readiness and action-note planner: decide whether to hold the meeting, plan the pre-reading, then write action notes after it.
- Meeting notes writer specialist: a ready-made specialist that turns a transcript or rough notes into decisions, actions and open questions.
- Otter guide and Granola guide: our guides to two AI note-taking tools, if you want live transcripts or fuller notes.
For more prompts like these, see our list of ChatGPT prompts for work. If you want the notes step to run as part of a bigger routine, read our guide to AI agents for small business.
Questions people ask
Can AI take meeting notes for me?
Yes. Some video tools, such as Google Meet, offer built-in AI note taking, and you can also paste any transcript or rough notes into ChatGPT, Claude or Gemini. Either way, read the result before you share it, because the AI can miss points or mix up who said what.
How do I turn meeting notes into action items?
List each task with one owner, a due date and the line in the notes where it came from. The first prompt above does this for you, and it marks any action that has no owner or date so you can fix it before sending.
What should a meeting summary template include?
A good template covers the meeting name and date, who was there, a short summary, the decisions, the actions with owners and dates, the open questions and the next meeting. Keep the same structure every time, so people know exactly where to find their actions.
Is it legal to record a meeting with AI?
It depends on where you and the other people are, since some places need everyone's consent. Tell people at the start, let them say no and check your local law, and when in doubt, take typed notes instead.
Are AI meeting notes accurate?
They are usually reliable on structure and often weaker on specific details, such as names, numbers and who agreed to what. Ask the AI to quote its source lines and mark anything unclear, so that a quick human check can catch most errors.