Blog

AI Meeting Notes: The Prompt and the Two Failures

Reliable because the material is supplied. Attribution and decision-vs-discussion are where it goes wrong — plus consent and retention.

Baca 4 menit

Postingan ini belum diterjemahkan ke dalam bahasa Anda — menampilkan versi Inggris.

Turning a meeting transcript into something useful is one of the most reliable AI tasks there is — the material is in front of the model, so it is summarising rather than inventing. The failures come from a small number of avoidable mistakes.

Why this works well

You are giving the model everything it needs. There is no gap for it to fill with plausible invention, which is where most AI errors come from.

The result is that transcript work is meaningfully more trustworthy than general questions — with two specific exceptions covered below.

The prompt that does the work

Do not ask for a summary. Ask for the specific things you need:

From the transcript below, produce:

  1. Decisions made — only ones actually agreed, not discussed
  2. Action items with owner and deadline. If an owner isn't stated, write "unassigned" — do not guess
  3. Open questions left unresolved
  4. Anything flagged as a risk or blocker

Do not include anything not in the transcript.

[transcript]

Two clauses are doing most of the work here:

"Do not guess." Without it, models assign owners based on who spoke most about a topic. That is a fabrication with someone's name on it, and it is the single most damaging failure in meeting notes.

"Only ones actually agreed." Transcripts are full of things considered and dropped. Without this, discussion gets promoted to decision.

The two things it gets wrong

Attribution. If the transcript does not label speakers well — and most do not — the model will assign statements to the wrong person, confidently. Always verify who said what before circulating.

Decision vs discussion. "We could move the launch" and "we're moving the launch" look similar in a transcript full of hedging. This is the error most likely to cause a real problem, because people act on it.

Both are checkable in under a minute if you know to look.

Practical points

Speaker labels matter more than transcript accuracy. A transcript with a few misheard words and clean labels is far more useful than a perfect one where everyone is "Speaker 1."

Long meetings need chunking. Past the context window the beginning silently drops out, and the model will still answer — from what remains, with no indication that anything is missing. Split by agenda item.

Ask for what is missing. "What was raised but never resolved?" is often the most valuable question you can ask a transcript, and nobody asks it.

Generate the follow-up email too. "Write a short email to attendees with decisions and their own action items." You were going to write it anyway.

Do not circulate unedited. Read it. You were in the meeting; you will spot the misattribution in seconds, and nobody else can.

Recording, consent and retention

The part people skip, and the one with actual consequences.

Consent. Many jurisdictions require all-party consent to record. "Recording is on" at the start of a call is both good practice and, in places, a legal requirement. For external calls, ask.

Where the transcript goes. Meeting content is often the most sensitive text your company produces — customer names, pricing, personnel matters, unreleased plans. A free-tier AI tool may train on it. Use a paid or business tier for anything containing those.

Retention. Recordings and transcripts are discoverable. Decide how long you keep them before you accumulate three years of them by accident.

Tell people. Attendees behave differently when they know a permanent searchable record exists. That is their right, and finding out later damages trust more than the record is worth.

Common questions

Can AI summarise meeting notes? Yes, and it is one of the more reliable AI tasks because the material is supplied rather than recalled.

How accurate are AI meeting summaries? Good on content, weak on attribution and on distinguishing decisions from discussion. Verify both.

What is the best prompt for meeting notes? Ask for specific outputs — decisions, actions with owners, open questions — and explicitly instruct it not to guess owners.

Can it identify who said what? Only as well as the transcript labels speakers. Poorly labelled transcripts produce confident misattribution.

Do I need consent to record? Often yes, depending on jurisdiction and whether the call is internal or external. Announce it, and ask on external calls.

Is it safe to put meeting transcripts into AI? Only on a tier that does not train on your data. Meeting content is frequently the most sensitive text a company produces.

What should I always ask a transcript? "What was raised but never resolved?" — usually the most valuable output and almost never requested.

Decisions, owners and open questions

Paste a transcript and ask.

Turn a transcript into actions