Meeting Notes, Minutes and Summaries

Meetings produce decisions that nobody remembers and actions that nobody owns. AI can turn rough notes into clear minutes and condense long documents, but it can also drop a crucial detail or invent a commitment. In this lesson you will learn to structure your notes, extract decisions, actions and owners, summarize faithfully, and handle the privacy side of recorded meetings.

Last lesson was about messages you write. This one is about information you receive: meetings, calls and long documents. The skill is the same: give structure and check the result.

Nadia's weekly meeting

Nadia, the HR officer, attends a weekly meeting with the management team. She types quick notes during the meeting: half sentences, abbreviations, names. Afterwards she spends thirty minutes writing proper minutes. She wonders whether AI could take over. It can help, but only if she gives it the right raw material and asks for a precise structure.

Step 1: structure your note-taking

An assistant can only work with what you give it. If your notes do not contain who decided what, the minutes will not either, and the AI may fill the gap with something plausible. A simple note-taking structure improves everything downstream:

• Header: date, topic, participants (roles are enough if you want to limit personal data).
• D for decisions: "D: budget for training approved, 3 sessions".
• A for actions: "A: Ahmed sends the plan by Friday".
• Q for open questions: "Q: who validates the venue?".
• I for information worth keeping.

Those single letters cost you nothing during the meeting and let the assistant sort without guessing.

Step 2: extract decisions, actions and owners

The most valuable output of a meeting is not a narrative; it is a short list of decisions, actions with an owner and a deadline, and open points. Ask for these explicitly, and tell the assistant to mark what is missing rather than to guess.

A ready-to-use prompt: from notes to minutes

You are helping me write meeting minutes from my rough notes.
Meeting: [topic], date [date]. Participants (roles only): [list].
My notes:
[paste notes, with no unnecessary personal or sensitive data]

Produce:
1. A summary in 3 to 5 sentences.
2. Decisions made (bulleted list).
3. Actions: a table with columns Action / Owner / Deadline. If the owner or deadline is not in my notes, write "to be confirmed" instead of inventing one.
4. Open questions.
Use only information from my notes. Do not add anything that is not there. Keep the language neutral and factual.

The two key sentences are "write 'to be confirmed' instead of inventing one" and "use only information from my notes". Without them, the assistant will happily produce a complete-looking table with invented owners.

Step 3: summarize long documents

Julien, the accountant, receives a forty-page regulatory update. Summarizing it with AI can save time, but a summary is a transformation with possible loss. To get a faithful result:

• Say who the summary is for: a client, a partner, yourself. It changes what matters.
• Specify the format: five bullet points, one page, an executive summary plus key dates.
• Ask for the structure of the document first (section titles), then summaries by section.
• Ask for evidence: "for each point, quote the sentence from the text that supports it".
• Ask what is not covered: "list the topics in the document you have not summarized".

Very long documents may exceed what a tool can read in one go, or details in the middle may be missed. Cut the document into sections and summarize each, then summarize the summaries, checking along the way.

A ready-to-use prompt: faithful summary with evidence

Summarize the document below for [audience, e.g. a client who is not a specialist].
Format: an executive summary of at most 5 sentences, then a list of key points. For each key point, add in brackets the short quote from the document that supports it.
Then list: (a) any dates or deadlines mentioned, (b) any requirement or obligation the reader must act on, (c) topics in the document that you left out of the summary.
If something is unclear or contradictory in the document, say so instead of resolving it.
Document:
[paste the text or the relevant section]

Recorded and transcribed meetings

Many tools can record a meeting, transcribe it and produce a summary automatically. This is convenient, and it raises questions that you should always address before pressing record.

• Information and consent: participants should know that the meeting is recorded or transcribed and for what purpose. The rules on recording conversations vary and depend on the context (internal, with customers, with external partners), so check your organization's policy and the applicable law rather than assuming.
• Personal data: a transcript contains voices, names and opinions, which are personal data under the GDPR. Where it is stored, who can access it and how long it is kept all matter.
• Sensitive meetings: disciplinary discussions, health matters, negotiations or anything confidential may need to stay outside automated tools altogether.
• Which tool: only a tool approved by your organization, configured according to its policy.

This is a general reminder, not legal advice. If you are unsure, ask your data protection officer or the legal contact in your organization, and see the official guidance of your data protection authority (in France, the CNIL).

Bad use versus good use

Bad use	Good use
Pasting a full transcript of an HR meeting with named employees into an unapproved tool.	Using the approved tool, or summarizing from your own anonymized notes, and keeping sensitive items out.
Circulating the AI summary without reading it.	Checking every decision and action against your notes, then circulating it under your name.
"Summarize this document" with no audience.	Specifying the audience, format, evidence and what must not be left out.

Your turn: minutes in two passes

Exercise. Take notes from a real or an invented meeting of about ten minutes (you can write them in the D/A/Q/I format). Use the "from notes to minutes" prompt. Then (1) check each decision and action against your notes and mark any invention, (2) rewrite the prompt to prevent that error, (3) summarize a one- or two-page document with the evidence prompt and verify two quotes in the original.

See a solution

Typical findings: the first draft may add an owner for an action ("Ahmed") because he was mentioned in a related sentence, or turn "we should look at the venue" into "decision: venue approved". These are the classic errors of summarization: promoting a discussion into a decision and assigning ownership by association.

Fixes: add "treat only lines starting with D as decisions", "only lines starting with A are actions", and "never attach an owner that is not named in the same line". For the quotes, you may find one that is a paraphrase rather than an exact sentence: it signals that evidence has to be checked and not only requested.