The weekly meeting begins. The host switches on AI notes, a notice pops up on everyone’s screen, and no one objects. The first twenty minutes cover project progress, and everything goes smoothly. Then a manager says: “Since everyone’s here, let’s talk about how one of our colleagues has been doing lately.” The AI keeps taking notes. Afterward, a summary that includes this discussion is sent automatically to every invitee, including an outside consultant who didn’t attend that day.
The notice that appears when AI notes start is easy to read as “everyone agreed, and only the people here will see it.” Neither has actually been confirmed. The notice only shows that the tool is in a certain state; where the record goes afterward and who receives it are separate settings. So before starting, the host should settle four things: which part gets recorded, who can stop it, who receives it afterward, and where it’s stored. When the agenda turns to sensitive topics, stop first.
A notice is not consent
A notice handles “letting people know,” not “getting people to agree where the record goes.” Google Meet’s help page is clear: once note-taking starts, all participants are notified and a pencil icon appears on screen. But the notes document is saved in the organizer’s Google Drive afterward, and who receives it is chosen by the host when starting: all invitees (including people outside the organization), invitees within the organization, or only hosts and co-hosts. That option is visible only to hosts.
Microsoft Teams recordings work similarly: everyone is notified automatically when recording starts, the file is saved in the organizer’s OneDrive, and by default only organizers and co-organizers can download or delete it.
In other words, the people who saw the notice in a meeting don’t necessarily get the same record afterward, and the invitees on the calendar weren’t necessarily all present. The notice itself says none of this, and it may not meet the consent requirements of company policy or local law.
Settle four things before starting
These four can go at the top of the meeting invitation or agenda, so every time notes start there’s the same checkpoint.
Which part gets recorded. Which agenda item it starts at and which item it stops before; whether it captures a summary, a transcript, a recording, or only some of these. If that can’t be stated clearly, try it only on segments known to be low-sensitivity.
Who can stop it. Besides the host, who can stop it immediately, and how attendees can raise a concern. Don’t leave this to “someone will probably handle it.”
Who receives it afterward. Only the host, invitees within the organization, or all invitees; and what happens with external guests. If unsure, pick the narrowest option and let a person decide afterward whether to widen it.
Where it’s stored and who owns it. Which account or folder holds the notes, transcript, and recording, who is responsible for deleting them, and when.
If attendees include outside consultants, job candidates, clients, or people who joined at the last minute, don’t judge by company domain alone. Write down the specific sharing step, such as “the host receives it first, reviews it, and only then shares it with the project members who actually attended.”
When the agenda shifts, check again
The most common problem isn’t the pre-meeting setup but the transitions during a meeting, like the weekly meeting above. The host can ask the same question at each change of agenda item: “Is the next part still within what we’re recording today? Do the recipients or storage location need to change?” If the answer isn’t clear, stop first.
Stopping doesn’t mean the whole meeting can’t use AI. The lines can be practical: project progress gets a summary; individual performance isn’t recorded; client requirements are noted only as anonymized conclusions; contract amounts are decided and written down by a designated person. Moving a sensitive segment into a separate, smaller meeting is usually far more reliable than deleting it afterward from summaries, transcripts, recordings, notification emails, and shared documents one by one.
The AI Risk Management Framework from the U.S. National Institute of Standards and Technology (NIST) also stresses that processes, roles, and responsibilities for human oversight should be defined and documented, rather than assuming someone in front of the screen will always notice.
These four things don’t settle legal consent
These four only cover the scope and destination of the record; they don’t handle legal consent. If a meeting involves health, legal, HR, financial, or client-confidential matters, ask the data or legal owner to confirm company policy and local rules. This list is not a consent form.
Also, checking every item for every meeting is a real burden for someone with back-to-back meetings. A practical start is one regular, low-risk, internal-only weekly meeting. Afterward, open the notes file and check whether its owner, recipients, link permissions, and storage location match what was stated beforehand. If any of them differ, fix the settings first before expanding to other meetings.
Before turning on AI notes in your next meeting, write those four things into the invitation. If document permissions turn out to be wider than expected, the fix is to correct the original sharing settings, not just ask the AI not to show things; see When AI Search Can Read Your Mailbox, What People Can See Isn’t What AI Should Handle. AI devices that record home life call for the same data-minimization principle; see If Free Cleaning Means Filming Your Home, Ask Who the Footage Is Licensed to and Whether You Can Delete It.
AI handoff card
Before turning on AI notes in a meeting, I want to settle the scope and destination of the record.
The method comes from this article: https://boosterminiclass.com/en/posts/ai-meeting-notetaker-boundary-card/
Its view: the notice when notes start only shows the tool's status; it doesn't mean everyone agreed where the record goes. Before starting, settle four things: which part gets recorded (summary, transcript, recording), who can stop it, who receives it afterward, and where it's stored and who owns it. Stop when the agenda turns to sensitive topics.
Ask me 3 questions first:
1. Which meeting is it, what are its agenda items, and are there any external attendees?
2. Which meeting platform do we use, and who do the current notes or recording settings send to and where are they stored (say "unknown" if I don't know)?
3. Might the agenda touch on HR, clients, contracts, health, or other sensitive topics?
Based on my answers, give me:
- A four-part note to paste into the invitation: segments recorded, who can stop it, recipients, storage location and owner, writing "to confirm" for anything missing;
- Which agenda items should not be recorded, or should be noted by a person instead;
- Three things to check by hand after the meeting;
- If there are external guests, sensitive agenda items, unclear sharing scope, or nobody who can stop it, recommend not turning on notes for this meeting.
Don't change any settings or share any files for me. Consent and retention must be confirmed under organizational policy and by the legal owner.
References
- Google Meet Help: Take notes for me in Google Meet — https://support.google.com/meet/answer/14754931 [accessed: 2026-10-11]
- Microsoft Support: Record a meeting in Microsoft Teams — https://support.microsoft.com/en-us/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24 [accessed: 2026-10-11]
- NIST: Artificial Intelligence Risk Management Framework (AI RMF 1.0) — https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf [accessed: 2026-10-11]
