From team meeting notes to minutes with actions, without inventing agreements

Reading time: about 11 minutes

The situation. A forty-minute team meeting before opening: August rotas, the new sunscreen display, a customer complaint, what to do about the stockroom expiry checks and a couple of other things. You took notes in a notebook, half-finished and full of arrows. A week later nobody remembers what was decided, and everyone remembers something different.

Turning messy notes into clean minutes is one of the tasks where AI saves the most time for the least risk, because you were at the meeting and know perfectly well whether the minutes say what happened. But it has a tendency worth knowing about: models want the text to feel finished. Where your notes say "shall we do it this way? — we’ll think about it", the minutes tend to say "it was agreed to do it this way". And minutes that turn doubts into agreements are worse than no minutes, because they are the version that sticks.

What you need to hand: Your meeting notes (photographed or typed), twenty minutes and the lesson on reviewing what you already wrote. Before pasting anything, remove two things from the notes: any health information about a colleague (sick leave, a medical appointment) and any identifiable customer details (the complaint gets described, without a name).

Step by step

Clean the notes before you paste them

Team meeting notes carry more personal information than they seem to. "Marta off until the 15th, the knee thing" is health information about a colleague. "Complaint from the lady on the 3rd floor about her husband’s order" identifies a customer as soon as anyone in the neighbourhood reads it. And neither is needed to write the minutes.

Replace them with what matters for the organisation: "one team member absent until the 15th" and "customer complaint about an order that did not arrive on time". The minutes work exactly as well and no longer contain anything that should not leave the pharmacy.

If your notes are handwritten you can take a photo, but then the cleaning happens before you shoot: cover or cross out those lines. A photo of a notebook also includes whatever is written on the facing page.

Ask for minutes that separate what was decided from what was discussed

This is the key to the whole case. Useful minutes have three drawers and the model has to respect them: what was decided, what was left pending, and what was only mentioned. Unless you ask for that explicitly, it puts everything in the first drawer.

Here are my notes from a pharmacy team meeting. They are messy and
incomplete. Turn them into minutes with THREE sections:

1. DECISIONS: only what the notes clearly show as decided ("we are going
   to", "it is done", "that is settled"). With a person responsible and a
   date ONLY if they appear in the notes.
2. STILL TO DECIDE: anything with a question mark, "we’ll think about it",
   "let’s see", "depends", or no clear conclusion.
3. DISCUSSED: things that were talked about without needing a decision.

Rules:
- If you are unsure which section something belongs in, put it in STILL TO DECIDE.
- Do not invent people responsible or dates. If a decision has nobody
  responsible in the notes, write "responsible: not assigned".
- No more than one page. Neutral tone, no opinions.

Notes:
paste your cleaned notes here

The rule "if unsure, put it in still to decide" reverses the model’s natural tendency. Minutes with too many pending items — which you move to decisions in a minute because you know what happened — are better than minutes with agreements nobody made.

Check the minutes section by section, starting with the decisions

You were at the meeting, so you are the best possible reviewer. But only if you read with intent. Start with the decisions section and, for each one, ask yourself: was this really decided, or was it proposed and nobody objected? They are different things and the minutes have to show that.

Next, look at the people responsible. If a name appears next to a task and you do not remember assigning it, the model has inferred it from the notes — "Luis mentioned the display" becomes "responsible: Luis". Mentioning something is not taking it on.

Finally, the dates. "Before August" in your notes can turn into "by 31 July" in the minutes. It looks the same and it is not: an exact date is a commitment nobody has made.
Add what is missing and assign what is unassigned

With the minutes checked, fill in by hand the two things the model cannot know: who is in charge of each decision without an owner, and by when. If that was not decided at the meeting, do not invent it yourself either: leave it as an item for the next meeting, which is where it gets decided.

If there was disagreement about something — someone was unhappy with the August rota — record it neutrally under still to decide or discussed. Minutes that erase disagreement do not resolve it: they postpone it until it comes back worse, and the person who disagreed does not see themselves reflected.

AI can help with a final pass on form: "cut this down to half a page without removing any decision or any pending item". But compare the result with the long version before you send it.
Send it quickly and ask for corrections

Minutes are only worth as much as how fast they arrive. Sent the same day, everyone remembers the meeting and spots mistakes at a glance; sent a week later, people accept them because they no longer remember. Send them through the team channel with one line: "if anything is not how you remember it, tell me today".

The corrections that come back are the best proof that the method works: they will nearly always be of the kind "that was not decided, it was only discussed". Move them to still to decide and keep the final version with the earlier ones, dated.

After a few sets of minutes done this way, you have something very valuable in a pharmacy: memory. When someone asks in six months why expiry checks are done a certain way, the answer is written down and dated.

A full example, and what is wrong with it

These were the (already cleaned) notes for one item of the meeting: "Stockroom expiry → once a month? Ana says better every 2 weeks in summer. We’ll look at it. Luis: the Excel sheet already exists." And this is what a model returned when simply asked to "turn this into formal minutes". It is shortened.

What it replies

"Item 4. Stockroom expiry checks.

It was agreed to carry out stockroom expiry checks fortnightly during the summer months and monthly for the rest of the year. Luis will manage this using the existing spreadsheet, with the first check to be completed by 15 June.

The team welcomed the proposal, which will reduce losses from expired stock."

And now, what is wrong with that reply:

It has turned a doubt into an agreement. The notes said "once a month?" with a question mark, a suggestion from Ana, and "we’ll look at it". Nothing was decided. The minutes say "it was agreed", with a mixed schedule nobody proposed in those terms: it has merged the question and the suggestion into a decision.
It has assigned someone nobody assigned. Luis only mentioned that the sheet existed. In the minutes he is the one in charge. If they go out like this, Luis has a new task he does not know he accepted — or he sees it, says that is not true, and the minutes lose credibility.
It has added a date that did not exist. "By 15 June" appears nowhere in the notes. It is a plausible date that gives shape to the invented agreement.
It has added the team’s opinion. "The team welcomed the proposal" and "will reduce losses" are filler sentences that take a collective opinion and a benefit for granted. Minutes record what happened, not how someone felt about it.

The whole item is well written and almost none of it is true. And notice why that is dangerous: in a month, if someone asks what was decided about expiry checks, the answer will be this paragraph, because it is the only thing in writing.

With the prompt from step 2, the same item came out under STILL TO DECIDE: "Frequency of stockroom expiry checks (monthly, or fortnightly in summer, suggested by a team member). A spreadsheet already exists. Responsible: not assigned." Less polished, and exactly faithful to what happened.

And if your pharmacy is not like that

If the meeting is just two people. It still works, sometimes better: short conversations are the ones people remember most differently. Five lines of minutes with decisions and pending items, sent by message that same afternoon, prevent half of the "I thought we said…".

If a problem with a team member came up in the meeting. That does not go in the team minutes, nor into the chat. Individual performance or conduct issues are dealt with separately and documented differently. If it appears in your notes, remove it before step 1 and handle it through its own channel.

If you record the meeting as audio. Transcribing a recording with AI is convenient, but it is colleagues’ voices — personal data — and the transcription usually goes through an outside service. Ask permission before recording, use the transcript only for the minutes and delete it afterwards. And note: a transcript is not minutes; step 2 is still needed.

When it does not work first time

The model puts everything under pending and the decisions section is empty.

That is a good failure: it means your notes do not mark decisions clearly. Move them to decisions yourself — you know which they were — and at the next meeting write "DECIDED:" next to whatever gets settled. The minutes improve a lot with that one word.

My notes are illegible and the photo cannot be read.

Dictate them aloud into a document or type them up quickly; they do not need to be tidy. What you should not do is ask the model to interpret illegible handwriting: it will fill in the most likely words, which need not be what you wrote.

A colleague says the minutes do not reflect what they said.

Take it seriously and correct it without arguing: that is exactly why you send them. If the correction moves a decision to pending, do it; if it is a nuance in what was discussed, add it. Corrected minutes are more reliable than perfect-first-time ones.

The minutes come out too long.

Ask for the short version after checking the long one, never instead of it. If you shorten before checking, the first thing lost is the nuance of the pending items, which is exactly what matters.

Before you use what it gave you

The notes contained no health information about colleagues and no identifiable customers.
The minutes have three sections: decisions, still to decide and discussed.
Every decision was genuinely made; none is a proposal nobody answered.
No person responsible and no date appears unless it was assigned at the meeting.
You sent them the same day and asked for corrections.

It closes what was left open. A question, a suggestion and a "we’ll look at it" become "it was agreed". That is its tendency to deliver finished-sounding text, and in minutes it is exactly the opposite of what helps.

It assigns by mention. Whoever raised a topic ends up responsible for it. In a meeting people comment on plenty of things they are not taking on.

It fills in with plausible dates and opinions. "By the 15th", "the team welcomed". None of it was in the notes and all of it sounds like real minutes.

Now, with your own. At the next team meeting take notes as usual, but write "DECIDED:" or "?" next to each point. That same afternoon, remove personal details, run the notes through the prompt from step 2 and send the minutes to the team asking for corrections. Count how many corrections are "that was not decided": it tells you how much not doing it this way would have cost.

← All practical cases Back to the school →

From team meeting notes to minutes with actions, without inventing agreements

Step by step

Clean the notes before you paste them

Ask for minutes that separate what was decided from what was discussed

Check the minutes section by section, starting with the decisions

Add what is missing and assign what is unassigned

Send it quickly and ask for corrections

A full example, and what is wrong with it

And if your pharmacy is not like that

When it does not work first time

Before you use what it gave you