
Meet → action

Meet → action
A meeting can produce excellent notes and still achieve very little. The problem usually appears afterwards: a decision has no owner, a deadline was only implied, or a client is waiting for a follow-up that nobody has written.
Google Workspace is starting to connect those steps. On 12 October 2026, Google announced new Google Meet routines that can draft Gmail follow-ups and export action items to Google Tasks. The rollout began on 5 October and may take longer than 15 days, so the options may not appear in every eligible account yet. Read Google’s announcement.
Here is a practical way to use that capability in a small team, with a manual route that works when the new routines are unavailable. Start with one repeatable meeting type, such as a client project review, and give one person responsibility for checking the output.
1. Check access before changing your process
The announcement lists Business Standard and Plus, Enterprise Standard and Plus, and Google AI Pro for Education. Business Starter is not listed. Administrators can control availability through Workspace Studio or the note-taking setting. Confirm your edition and settings before promising this workflow to the team. Check the release details.
Google’s current requirements also include a computer, a Calendar-backed meeting, enabled Workspace smart features, and both Take notes for me and Ask Gemini enabled during the meeting. The automatic email draft has narrower conditions: you must host a meeting outside a repeating series, with at least one participant from outside your organisation. Check the prerequisites.
That distinction matters. A weekly internal team meeting and a one-off client call should not be expected to offer identical routines. Choose a suitable pilot and keep your existing follow-up process available.
2. Make the meeting easier to turn into actions
Before the call, put three questions in the agenda: What must we decide? What is blocking progress? What should happen next? Ask the person leading the meeting to close each topic with an explicit outcome.
For example, “We should improve the homepage” is difficult to execute. “Priya will send two revised homepage headlines to the client by 16 October; the client will choose one before design starts” gives the team a deliverable, an owner and a dependency.
Avoid using “we” when assigning work. Name the person who has accepted responsibility. If a date is provisional, say so. If the group is discussing an option without approving it, make that clear too. These habits improve the underlying record before any AI is involved.
In Meet, open Take notes for me and review the recipients and language before starting. Google supports one language at a time; multiple languages in the same meeting are currently unsupported. Keep a manual record for multilingual meetings and verify the output carefully. Tell participants that notes are being captured. See Google’s note-taking instructions.
Treat sharing as part of meeting preparation. A client may need the agreed decisions and next steps without needing your internal discussion about delivery capacity.
3. Review the record before using it
After the meeting, use the notes attached to the Calendar event. Google’s generated notes are also stored in the organiser’s Google Meet folder in Drive. Access follows the selected sharing settings; seeing an attachment on the invitation does not itself grant access to its contents. Learn where notes are saved.
The meeting lead should check four things: decisions, names, dates and unresolved questions. A particularly useful distinction is between an idea that was discussed and a commitment somebody accepted.
For example, if the team considered adding a booking system but deferred the decision, the follow-up should say “Confirm whether booking is in scope.” It should not say “Build the booking system.” Keep uncertainty visible so that a polished summary does not become an accidental promise.
4. Turn the notes into a usable action list
If your account includes Gemini in Docs, open the notes and choose Ask Gemini. Google supports asking questions about the document and generating text from the side panel. See how Gemini in Docs works.
Try this prompt:
The prompt asks for evidence because the reviewer needs a quick way to check each item. It does not guarantee that every answer will be correct. Compare the result with the notes and confirm ambiguous commitments with the people involved.
Keep the finished list short enough to review at the next meeting. An action called “Marketing” is too vague. “Send the client the approved campaign copy” describes an observable result.
5. Use a routine, then check what it produced
After an eligible call, look for Routines for this meeting on the exit screen and enable the useful option. Suggestions depend on the meeting’s content and settings. For a repeating meeting, enabling a routine applies it to future meetings in that series. Review how next steps work.
Open any resulting email draft and check its recipients, commitments and dates before sending. Remove internal observations that would be inappropriate for the client. Check generated tasks for duplicates and confirm that each person can find the work they own. Do not assume an export has established responsibility across the whole team.
When an email routine is unavailable, use the reviewed notes to prepare a draft in Docs:
Copy the approved text into Gmail. For tasks, open the Tasks side panel and add the item with its details and date. If you need a shared assignment, Google Chat spaces support group tasks with an assignee. Follow Google’s task instructions.
6. Run a small pilot and review the results
Try the workflow across five meetings. Record how long review takes, which commitments needed correction, whether follow-ups went out when intended, and which tasks still had no clear owner. This is a suggested pilot, not a claimed productivity benchmark.
Inspect routine history through Workspace Studio: open Flows, find the system flow, and use Manage flow to view Activity. The same controls let you turn it off; Google’s built-in post-meeting routines cannot be edited. Manage your meeting routines.
At the next meeting, begin with the previous action list. Mark completed work, resolve blocked items and reconfirm anything that has changed. That review closes the loop between a useful summary and actual progress.
Need help checking eligibility, configuring Gemini or building a workflow your team can maintain? Explore Re-solve’s Google Workspace services.

Altaf Nadaf
Altaf Nadaf
Google Workspace Expert & Founder, Re-solve
Google Workspace Expert & Founder, Re-solve

Meet → action

Meet → action
A meeting can produce excellent notes and still achieve very little. The problem usually appears afterwards: a decision has no owner, a deadline was only implied, or a client is waiting for a follow-up that nobody has written.
Google Workspace is starting to connect those steps. On 12 October 2026, Google announced new Google Meet routines that can draft Gmail follow-ups and export action items to Google Tasks. The rollout began on 5 October and may take longer than 15 days, so the options may not appear in every eligible account yet. Read Google’s announcement.
Here is a practical way to use that capability in a small team, with a manual route that works when the new routines are unavailable. Start with one repeatable meeting type, such as a client project review, and give one person responsibility for checking the output.
1. Check access before changing your process
The announcement lists Business Standard and Plus, Enterprise Standard and Plus, and Google AI Pro for Education. Business Starter is not listed. Administrators can control availability through Workspace Studio or the note-taking setting. Confirm your edition and settings before promising this workflow to the team. Check the release details.
Google’s current requirements also include a computer, a Calendar-backed meeting, enabled Workspace smart features, and both Take notes for me and Ask Gemini enabled during the meeting. The automatic email draft has narrower conditions: you must host a meeting outside a repeating series, with at least one participant from outside your organisation. Check the prerequisites.
That distinction matters. A weekly internal team meeting and a one-off client call should not be expected to offer identical routines. Choose a suitable pilot and keep your existing follow-up process available.
2. Make the meeting easier to turn into actions
Before the call, put three questions in the agenda: What must we decide? What is blocking progress? What should happen next? Ask the person leading the meeting to close each topic with an explicit outcome.
For example, “We should improve the homepage” is difficult to execute. “Priya will send two revised homepage headlines to the client by 16 October; the client will choose one before design starts” gives the team a deliverable, an owner and a dependency.
Avoid using “we” when assigning work. Name the person who has accepted responsibility. If a date is provisional, say so. If the group is discussing an option without approving it, make that clear too. These habits improve the underlying record before any AI is involved.
In Meet, open Take notes for me and review the recipients and language before starting. Google supports one language at a time; multiple languages in the same meeting are currently unsupported. Keep a manual record for multilingual meetings and verify the output carefully. Tell participants that notes are being captured. See Google’s note-taking instructions.
Treat sharing as part of meeting preparation. A client may need the agreed decisions and next steps without needing your internal discussion about delivery capacity.
3. Review the record before using it
After the meeting, use the notes attached to the Calendar event. Google’s generated notes are also stored in the organiser’s Google Meet folder in Drive. Access follows the selected sharing settings; seeing an attachment on the invitation does not itself grant access to its contents. Learn where notes are saved.
The meeting lead should check four things: decisions, names, dates and unresolved questions. A particularly useful distinction is between an idea that was discussed and a commitment somebody accepted.
For example, if the team considered adding a booking system but deferred the decision, the follow-up should say “Confirm whether booking is in scope.” It should not say “Build the booking system.” Keep uncertainty visible so that a polished summary does not become an accidental promise.
4. Turn the notes into a usable action list
If your account includes Gemini in Docs, open the notes and choose Ask Gemini. Google supports asking questions about the document and generating text from the side panel. See how Gemini in Docs works.
Try this prompt:
The prompt asks for evidence because the reviewer needs a quick way to check each item. It does not guarantee that every answer will be correct. Compare the result with the notes and confirm ambiguous commitments with the people involved.
Keep the finished list short enough to review at the next meeting. An action called “Marketing” is too vague. “Send the client the approved campaign copy” describes an observable result.
5. Use a routine, then check what it produced
After an eligible call, look for Routines for this meeting on the exit screen and enable the useful option. Suggestions depend on the meeting’s content and settings. For a repeating meeting, enabling a routine applies it to future meetings in that series. Review how next steps work.
Open any resulting email draft and check its recipients, commitments and dates before sending. Remove internal observations that would be inappropriate for the client. Check generated tasks for duplicates and confirm that each person can find the work they own. Do not assume an export has established responsibility across the whole team.
When an email routine is unavailable, use the reviewed notes to prepare a draft in Docs:
Copy the approved text into Gmail. For tasks, open the Tasks side panel and add the item with its details and date. If you need a shared assignment, Google Chat spaces support group tasks with an assignee. Follow Google’s task instructions.
6. Run a small pilot and review the results
Try the workflow across five meetings. Record how long review takes, which commitments needed correction, whether follow-ups went out when intended, and which tasks still had no clear owner. This is a suggested pilot, not a claimed productivity benchmark.
Inspect routine history through Workspace Studio: open Flows, find the system flow, and use Manage flow to view Activity. The same controls let you turn it off; Google’s built-in post-meeting routines cannot be edited. Manage your meeting routines.
At the next meeting, begin with the previous action list. Mark completed work, resolve blocked items and reconfirm anything that has changed. That review closes the loop between a useful summary and actual progress.
Need help checking eligibility, configuring Gemini or building a workflow your team can maintain? Explore Re-solve’s Google Workspace services.

Altaf Nadaf
Altaf Nadaf
Google Workspace Expert & Founder, Re-solve
Google Workspace Expert & Founder, Re-solve