Meet auto-notes rules for standups, one-on-ones, weekly reviews

The calendar already has the meetings that keep a small company honest: standup, one-on-ones, weekly review. When Meet starts leaving notes by default, the admin should decide before rollout which rituals are recorded, who can see the record, and what the note is for.

Default settings decide before the team does

Google announced the three-participant threshold for Meet automatic note-taking on July 16 in the Workspace Updates blog. The new Google Meet automatic note-taking configuration changes become active for end users on September 29, 2026. The end-user control for all hosted meetings with three or more guests starts its rollout on September 29, 2026. Google is introducing an admin option that limits automatic note-taking to calls with at least three participants.

Business Standard and Business Plus customers receive the three-or-more-guest automatic note-taking configuration in the enabled state by default. Enterprise Standard, Enterprise Plus, Frontline Plus, and Google AI Pro for Education add-on customers receive the three-or-more-guest automatic note-taking configuration in the disabled state by default. Changing Meet automatic note-taking settings requires the organization to have Gemini note-taking and Google Workspace smart features enabled. If the plan starts enabled, the first task is to confirm the scope. If it starts disabled, the first task is to confirm the prerequisites.

Three settings keep the record useful

The policy is small enough to test quickly, and it should be written down before the first auto-note appears.

• Scope: limit automatic notes to rituals with three or more guests, so private calls stay outside the default record.
• Visibility: set the notes doc to the smallest group that needs it, and make the sharing rule explicit for standup and weekly review.
• Standing notes: publish which rituals now leave notes, which stay private, and where the record lives.

The policy does not need a long manual for every ritual. It needs a place where the team can check before a meeting starts, and a rule for what to do when the meeting changes.

Make the default visible before it becomes the norm

Small teams often skip the policy because the feature feels small. A note in a standup seems harmless until someone reads a private comment in a shared doc. The default becomes the norm when no one has said what it means. Write the policy in plain language, and put it where the team already looks for meeting expectations.

The policy should answer the questions a new hire would ask: which meetings leave a record, who can open that record, and what happens when a meeting changes shape. If a standup adds guests, the note may need a different audience. If a weekly review adds guests, the record may need a smaller audience. The rule should be easy to apply in the moment.

Make the weekly review ritual legible

A weekly review works when the team can separate what happened, what is decided, and what needs a follow-up. Automatic notes can help with that, but only if the note is treated as a working document, not a full transcript. Put the agenda, the decision log, and the owner for each follow-up in the same place as the notes.

For standup, the record should be short enough to read before the next meeting. If the note captures blockers, owners, and the decision that changed the plan, it has done its job. If it captures every sentence, it becomes a problem. For one-on-ones, the default should be no standing note unless both people agree to keep a note.

Keep the record useful by limiting what it is for. Standup notes can track blockers and decisions. A weekly review note can track progress, risks, and the next owner. A one-on-one note, if kept, should stay between the people who need it. When the purpose is clear, the team can tell when a note has moved into a place where it creates confusion.

Put the policy in the same doc where the weekly review agenda lives, and update it when the ritual changes.