Google Chat Meeting Recaps: Decisions and Action Items Posted to the Meeting Chat Automatically
After a Meet call, the decisions and who owns each action item land in the meeting’s Chat conversation, so nobody has to write the recap message.
What happened
On October 19, 2026, Google announced meeting recaps in Google Chat: after a Meet call, a recap card appears in the meeting’s Chat conversation with a summary, key decisions and action items with owners. The card links straight to the notes document, the recording and the transcript. Recaps appear automatically for meetings with "Take notes for me" turned on and a meeting chat, and there is no setting for users; if the host sends notes to hosts and co-hosts only, no card is posted. Cards arrive silently without an unread badge, and any participant can delete the card while the notes document stays in Google Drive. The rollout started October 16, 2026 for Rapid Release domains and starts October 27, 2026 for Scheduled Release domains, with up to 15 days for the feature to appear. Source: Google Workspace Updates: Follow through on your meeting tasks with meeting recaps in Google Chat (October 19, 2026).
Who gets it, and what it costs
- Google Workspace: Business Standard and Plus, Enterprise Standard and Plus, and Frontline Plus.
- Needed: "Take notes for me" turned on during the Meet call, and a Chat space linked to the meeting.
- Admins: on by default for organizations with Gemini for Google Workspace turned on. It follows the existing "Take notes for me" and Gemini settings.
Google lists no separate price. It comes with the Workspace editions above.
What it means for an office team
The basic case is the weekly team meeting. Today someone types "thanks all, here is what we agreed" into the chat an hour later, or nobody does. With recaps the card is waiting in the meeting chat with each action item and its owner.
Read the card before the next meeting starts. An owner or a date that is wrong in the recap becomes the version people remember, so fix it in the chat thread while the call is still fresh.