What should you check before the meeting?

Check the organizer’s account and your meeting language first. Google requires an eligible Google Workspace edition or Google AI plan for this feature. Having access to ordinary Meet calls does not establish eligibility for automatic notes. Google lists this requirement here.

In this guide, Gemini means the AI assistant preparing notes inside Meet. “Take notes for me” is the feature you switch on; Google Docs holds the written result, and Google Drive stores it. These roles are described in the feature documentation.

Give the notes a specific job

Before changing settings, write down what you want after the call. For a small agency, that might be a checked list of client decisions. For a shop owner, it might be supplier questions that still need answers.

Choose someone to review that output. My recommendation is to keep responsibility with the person who led the discussion, even when somebody else operates the note button. For the wider process, use the guide to automating meeting notes with AI.

Start with an internal meeting where you can compare the document against your own notes. Avoid making an important customer negotiation your first experiment. Define success as a useful, checked handover, rather than simply receiving a document.

How do you turn on “Take notes for me”?

For your first attempt, start the feature manually inside the call. This gives you a clear moment to inspect its settings. Google’s computer instructions provide this sequence:

1. Join the meeting using the account you intend to use.
2. Select “Take notes for me” near the top right.
3. Open the settings and check the meeting language and recipients.
4. Tell the participants that you are starting automatic notes.
5. Select “Start taking notes.”

Host controls are the organizer’s meeting permissions. When they are enabled, only the host and co-hosts can start or stop note-taking. If you cannot operate the feature, ask the organizer to check your role. Google explains these permissions here.

Prepare it in Calendar instead

For a scheduled meeting, edit the Calendar event, add Google Meet conferencing, and open “Video call options.” Under “Meeting records,” select “Take notes with Gemini.” You can also choose the language and sharing settings there. Follow Google’s Calendar instructions.

Use a straightforward opening statement: “We’ll use automatic notes today. I’ll check the decisions before sending the follow-up.” This is a suggested script, not a required Google message. Name the reviewer so everyone knows whom to contact about corrections.

Which language and sharing settings should you choose?

Select the language people will actually speak. The supported list is English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish. The feature supports one language at a time; multilingual conversations are not currently supported. Check the official language list.

Azerbaijani is absent from that list. Do not plan an Azerbaijani meeting around this feature or assume that choosing another language solves the limitation. My advice is to keep the discussion in the language your team uses comfortably and arrange manual notes when necessary.

Choose recipients before you start

Google offers three sharing audiences, shown below. The last column gives my suggested check before selecting each option. The available audiences come from Google’s sharing settings.

“Invited guests” means people on the Calendar invitation, not only those who attended. Check that invitation before choosing broad sharing. Google explicitly makes this distinction.

For an initial trial, I recommend hosts only. Review the document, then decide what the wider group needs. When introducing the process across a team, add this rule to your AI training plan.

You can also choose “Standard” or “Longer” notes. Some section controls are limited to Beta users, meaning a group with access to features being tested. Do not promise colleagues an option you have not checked in your account. Google describes the customization limits here.

Where do the notes go, and what should you review?

Look in the organizer’s Google Drive. The current instructions place the document in a meeting-specific subfolder inside “Google Meet.” The notes are also attached to the Calendar event, and the organizer receives a recap email. See Google’s storage instructions.

A visible attachment is not proof of access. Document permissions determine whether someone can open the notes, even if they can see the attachment in Calendar. If a client reports a problem, check sharing permissions first. Google explains this access distinction.

Check decisions before polishing the wording

Google acknowledges that summaries can be incomplete or inaccurate. Treat the document as material to review before you rely on it. Its troubleshooting section supports that caution.

• Separate suggestions from agreed decisions.
• Confirm the person responsible for each task.
• Check whether a deadline was actually agreed.
• Verify names, amounts, and product references.
• Keep unresolved questions visibly unresolved.

For example, do not turn “Could we launch next week?” into a confirmed launch date. That is an illustrative review check, not a reported Gemini error. Ask the people involved whenever the wording leaves room for doubt.

For editing the checked document, continue with using Gemini in Google Docs. Keep the final handover short: decisions, owners, deadlines, and open questions.

How can a small business run a useful first trial?

Choose one recurring discussion and compare the entire follow-up process. Include time spent checking and correcting the output. Do not judge the trial only by how quickly the draft appears.

Hypothetical example: an online shop and its designer

Imagine a shop owner meeting a freelance designer about a seasonal campaign. This is an invented example for planning, not a customer case study. Both participants are comfortable speaking English, so the owner selects English before starting notes.

Give the meeting three questions: which products will appear, who supplies the photographs, and what still needs approval? At the end, read the agreed actions aloud. Ask each person to confirm their responsibility before leaving.

Afterward, compare the document with those confirmations. If the photography deadline remains undecided, leave it open. Send the designer a checked task list and ask for acknowledgment before treating the handover as complete.

If that acknowledgment needs a separate message, use the guide to Gemini in Gmail for the next stage. Keep the approved decisions as the source material for the message.

Keep a small trial record

• Write down how you prepared follow-ups before the trial.
• Record the time needed to review this document.
• List any missing decisions or incorrect assignments.
• Ask whether each participant can identify their next action.

These are suggested evaluation measures, not promised improvements. If correction takes too much effort, inspect the language choice and meeting structure before extending the process. For clearer ownership, use the guide to delegating tasks as a business owner.

What should you do when the feature is missing?

Check eligibility and permissions before changing the whole workflow. Google lists an unsuitable organizer account, administrator settings, and disabled smart features among reasons the option may be unavailable. Start with its troubleshooting guidance.

1. Identify the account that organized the meeting.
2. Ask the account administrator to check access to “Take notes for me.”
3. Ask the host to start notes if host controls restrict your role.
4. For poor output, compare the selected language with the spoken language.
5. Complete the essential decisions manually before scheduling another test.

You can configure automatic notes for future meetings under Meet settings, then “Meeting records.” Google provides several automatic-start choices there. Review those settings here. I recommend enabling this only after your team has agreed on recipients and review responsibility.