How to use AI for meeting notes, and what to keep out of them

The meeting ends at 10:40. Everyone agreed on something: the supplier gets a call, the quote goes out by Thursday, someone checks the stock count. By Friday nobody can remember who said they would make the call.

That gap between the meeting and the follow-up is where AI note-takers are genuinely useful. They are also the AI tool most likely to record something you did not mean to keep. This guide covers both.

Who this is for and what you need

This is for owners and managers who run regular meetings on Google Meet or Microsoft Teams: weekly team check-ins, calls with suppliers, project meetings with a client. It is not for phone calls on a personal cell, and it is not for meetings you would never want written down. More on those below.

You need a business account on Google Workspace or Microsoft 365, an hour to set things up and test, and someone willing to read the first few summaries carefully. You probably do not need a new app.

Check what you already pay for

Before you sign up for anything, look at what is already in your plan.

Google Meet has a feature called Take notes for me. It writes a summary into a Google Doc while the meeting runs and saves it in the organizer's Google Drive, in a folder called "Google Meet". It needs an eligible Google Workspace edition, so check your plan in the admin console. It works in English, French and several other languages, which matters for a bilingual team.

Microsoft Teams puts its version, AI-generated notes and tasks, in Teams Premium. That is an add-on: each person needs both a regular Teams licence and a Premium one. Microsoft offers an admin trial of 25 licences for 30 days, and individual staff can start their own 60-day trial from inside Teams, so you can test it on real meetings before paying. Microsoft moved some Premium features into Teams Enterprise in April 2026, so check what your current licence includes before you buy.

Standalone note-taking apps exist too, and they work across every platform. They also come with the problem in the next step.

Tell everyone before the notes start

The law sets a low bar. Under the Criminal Code, as employment lawyer Erin Kuzz writes in Canadian HR Reporter, a conversation can legally be recorded if at least one person in it consents. She also warns that automatically recording people who have not agreed may still break the law, and that it damages trust either way.

The tools differ here. Google says Meet shows every participant a notification and a pencil icon when notes are being taken. Some third-party bots are less polite. In August 2025 a California man filed a proposed class action against Otter.ai, the transcription company, alleging that its Otter Notetaker can join a meeting "without obtaining the affirmative consent from any meeting participant, including the host." Otter told NPR it gets explicit permission from users to train its systems, and that audio is de-identified first. Those are allegations, not findings, but they show what goes wrong when a bot is linked to someone's calendar and joins everything.

So do three things:

1. Say it out loud at the start: "I'm using AI to take notes. Anyone mind?"
2. Put the same line in the calendar invite for external meetings.
3. If someone objects, turn it off and take notes by hand. No argument.

PIPEDA, the federal privacy law for businesses, adds the same expectation from another direction. Notes that name customers, suppliers or staff are personal information, and it expects consent and a stated purpose for collecting it. Businesses in Alberta, British Columbia and Quebec answer to their own provincial laws, which are similar.

Decide which meetings stay off the record

This is the step most businesses skip, and it matters more than which tool you pick. Some conversations should never go through an AI note-taker. Make a short list and share it with your team.

The question is not whether the notes are useful. It is whether you want this conversation to exist in writing, on someone else's server.

• HR and discipline. Performance talks, complaints, terminations. A transcript can become evidence, and Kuzz warns that AI transcripts can misidentify a speaker or "misconstrue the meaning".
• Calls with your lawyer. She notes that running solicitor-client conversations through a third-party AI tool can put privilege at risk.
• Health information. A clinic, a physio or a benefits conversation with an employee. Ontario has its own health privacy law for that.
• Pricing and negotiations. Your floor price, a supplier's terms, a bid. Ask first where the vendor stores it.
• Anything with a customer's banking or ID details.

A useful default: internal planning and project meetings, yes. Anything about a person's job, health or legal position, no.

Read the notes before anyone acts on them

AI summaries read as confident and finished. They are neither.

Those figures come from Associated Press reporting on Whisper, OpenAI's widely used transcription model, which researchers found would sometimes write whole sentences nobody said. Whisper is not necessarily the engine behind Meet or Teams, and those tools may do better. Google's own help page still says a Meet summary can be "incomplete, inaccurate, or not generated", and recommends meetings of at least 15 minutes.

In practice the errors that hurt are small ones: a "not" dropped, a date wrong, an action given to the wrong person, a condition ("if the client signs") left off. So the person who ran the meeting reads the notes the same day, while they still remember it. Five minutes is enough. Check every name, number, date and action item, and fix them in the document itself.

Send the follow-up yourself

The point of the notes is the follow-up email: who does what, by when. The AI can draft it, but a person should send it.

A good follow-up is short. List the decisions, then each action with one owner and a date, then anything still open. Delete the rest of the summary before you send it. Recipients do not need a paragraph about who joined late. A customer who receives an AI summary saying you agreed to something you did not will hold you to it.

For external meetings, be careful with Google's sharing setting. Meet lets the organizer send notes to all invited guests, only guests inside the organization, or only the hosts. For anything with a client or supplier, pick hosts only, edit, then send the clean version yourself.

Decide where notes live and when they go

Every meeting you record adds another document to a pile that can be searched, leaked or requested in a dispute. PIPEDA's principles include limiting how long personal information is kept, and the business is accountable for it.

Write down three rules, even on one page:

Kuzz also points out that some AI tools send data to servers outside Canada. Ask the vendor before you connect it to your calendar.

Common mistakes

• Linking a bot to your whole calendar. It then joins every meeting, including the ones on your off-the-record list. Switch it on per meeting.
• Forwarding the raw summary. It goes out with every error in it, under your name.
• Assuming silence is consent. Ask, and give people an easy way to say no.
• Keeping everything forever. Old transcripts are a liability, not an archive.
• Using it on a bad line. Crosstalk, speakerphones and short meetings produce the worst summaries.

Where to start

1. This week, check your Google Workspace edition or start the Teams Premium trial, and test it on one internal meeting where everyone knows it is running.
2. Write your off-the-record list and your storage rules on one page, and share it with the team before anyone else switches a note-taker on.
3. For the first month, have the meeting owner read every summary against their own memory. If it is routinely wrong, stop.

If you want help choosing a tool or setting the rules for your team, you can book a call with Trimotech.