How to Check an AI Meeting Summary Before Sending It

Before you send an AI-written meeting summary to stakeholders, check its risky lines against the source, not your memory. Take five minutes: find every name, number, decision, owner and date in the transcript, play that moment in the recording, and cut or mark anything you cannot find. Turn off auto-send first, so nothing leaves before that check.

AI summaries rarely fail in obvious ways. They read cleanly and fail in the details that stakeholders act on. The vendors say so themselves: Google's help page for Gemini notes in Meet says a summary can be incomplete or inaccurate, and Microsoft's page on Teams recap warns that AI content might be inaccurate, incomplete or inappropriate. These are the six errors to look for.

The last three are the dangerous ones. A wrong name gets corrected in a reply. A false agreement gets acted on, because the person reading it assumes they missed the moment it was settled.

You cannot check a summary that has already gone out. Several built-in tools can email notes to attendees automatically, so look at the sharing setting before your next meeting, not after it.

• Google Meet (Gemini “Take notes for me”): the “Send notes to” setting can send the notes doc to all invited guests, including people outside your organization, to guests in your organization, or only to hosts and co-hosts. Pick hosts and co-hosts if you want to review first.
• Zoom (AI Companion meeting summary): under “Share summary with”, choose “Only me (meeting host)”. University IT guides such as Caltech's recommend exactly this, so the host can review and correct the summary before others see it.
• Microsoft Teams (recap): when you share a recap by email, Microsoft's own steps tell you to edit the drafted email for accuracy before you send it.
• Reline: nothing is emailed for you. “Send recap to attendees” is an option in the note menu, you pick the recipients, and after a meeting Reline only asks whether you want to send one. Edit the summary first, then press Send.

Run this on every summary that goes to someone who was not in the room, or to anyone who will act on it. Keep the summary on one side and the transcript on the other.

1. Minute 1, read it as the recipient. Highlight every name, number, date and owner, and every word that commits someone: agreed, approved, decided, will, by.
2. Minute 2, numbers and dates. Search the transcript for each figure and date, then play the line. Write relative dates (“end of next week”) exactly as they were said, or confirm them with the person.
3. Minute 3, owners. For each action item, find the moment the owner accepted it. If they never said yes, write “proposed owner” or ask them before you send.
4. Minute 4, decisions and agreement. Find the words where the decision was made. “We agreed” needs someone saying yes, not a proposal followed by silence. Skim the last ten minutes of the transcript for reversals.
5. Minute 5, what is missing and what should not travel. Look for dropped caveats, conditions and open questions, and delete anything sensitive the recipients should not read.

Searching a long transcript by eye is the slow part. A grounded chat makes it fast, as long as you ask for evidence rather than a verdict. In Reline, ask chat a pointed question about the meeting. The answer quotes the transcript lines with [m:ss] timestamps, and each quoted moment shows as a play chip: click it and the clip plays right there in the chat, so you hear the sentence without hunting for it. A quoted note opens that note.

• “Quote the exact words where we decided to move the launch.”
• “Did anyone give a date for the contract? Quote it with the timestamp.”
• “Quote the moment someone offered to send the pricing deck.”
• “Was any number corrected later in the meeting?”
• “What did we change our mind about near the end?”

Two rules keep this honest. First, the chat answer is also AI output: the play chip, not the answer text, is your proof. Second, if chat cannot find the words, treat that line of the summary as unverified. A missing quote is an answer.

If the same names keep coming out wrong, fix them at the source. Add people, clients and product names to your vocabulary under Settings, Transcription; admins can add shared terms to the workspace glossary, and attendees of the calendar event are added for that recording automatically. Lenses such as Stakeholder Update or Action Items with Owners can redraft the same meeting in the shape your readers expect, but every redraft still gets the five-minute check.

Reline records your microphone and system audio on your computer, with no bot in the call. Transcription and AI run in the cloud and can still make mistakes, which is exactly why the check exists.

Think about the audience too. Clients, investors and other external stakeholders should get a short, checked recap, not the raw transcript or recording, unless everyone on the call agreed to that. In Reline, a recap sent to attendees outside your workspace lists the open action items without owner names, and sending a recap grants no access to the note itself.

• Decisions (confirmed): one line each, as they were said.
• Action items: owner, task, date, and “confirmed” or “proposed”.
• Open questions: what is still undecided, and who will decide it.
• Not covered: anything the meeting ran out of time for.
• A last line: “Drafted with AI, checked against the recording.” It tells readers the text was reviewed and invites corrections.

Do a full re-listen, or send a short holding note instead of a summary, when:

• The summary contains contract terms, prices, or legal and compliance commitments.
• It goes to a client, a board or investors, or it concerns a person (hiring, HR, performance).
• The audio was poor, people talked over each other, or the meeting mixed languages.
• Someone will be named in a way they might dispute.

A holding note is a fine answer: “Recap coming tomorrow, once I have checked the numbers.” Nobody minds a late summary. Everyone remembers a wrong one.

Sources, checked on 2026-10-22: Google Meet Help on Gemini “Take notes for me” (support.google.com), for notes that can be incomplete or inaccurate and the “Send notes to” options; Microsoft Support, “Recap in Microsoft Teams” (support.microsoft.com), for the accuracy warning and the step to edit the recap email before sending; Caltech IMSS, “Zoom AI Companion” (imss.caltech.edu), for choosing “Only me (meeting host)” under “Share summary with”. Menus change; your own admin settings are the source of truth.