If you want one AI habit that pays for itself within a fortnight, this is it. Not because the technology is impressive, but because taking minutes is a job everyone dislikes, everyone does badly, and everyone secretly skips.
The result is familiar. A meeting happens, four people leave with four different recollections of what was agreed, and the thing everyone thought someone else was doing does not get done. That is not a note-taking problem exactly, but good notes fix it.
The short version
- If you already use Teams or Google Meet, the feature is probably included. Turn it on before buying anything.
- Say it is being recorded, out loud, every time. It is both good manners and good practice.
- The transcript is not the point. The actions are.
- Spend five minutes editing the summary before you send it. Unedited notes teach people to ignore notes.
- Keep the notetaker out of HR meetings and anything about an individual.
How it actually works
Two separate steps, which is worth knowing because they fail differently.
First, transcription: speech converted to text, live. This is a mature technology and it is good. It struggles with three things, and always the same three: proper nouns it has never encountered, several people talking at once, and poor audio.
Second, summarisation: a language model reads the transcript and produces notes, decisions and actions. This is where the interesting failures happen. A summary is a set of judgements about what mattered, and the model is guessing at yours. Ask for something too short and nuance disappears. Leave it on default and you get a bland recap with the one contentious moment smoothed flat.
Transcription errors are obvious and easy to fix. Summary errors are invisible, because the note reads perfectly well; it is just quietly about a different meeting from the one you attended.
Choosing a tool
Start with what you have. Both Microsoft Teams and Google Meet include recording, transcription and AI summaries on business plans. If that covers you, stop. The recording stays inside your existing tenant, under your existing agreement and retention rules, and you have added no new supplier.
Standalone notetakers, the ones that join your call as a participant, are worth it when you need something the built-in tools do not do: meetings across several platforms, a searchable archive of everything, or direct writing into a CRM. The trade-off is a new processor holding recordings of your meetings, which means an agreement to read, a retention setting to configure and a line in your policy.
| Built into Teams or Meet | Standalone notetaker | |
|---|---|---|
| Extra cost | Usually none on business plans | Per seat, monthly |
| Data stays | In your tenant | With a new supplier |
| Works across platforms | Its own only | Usually yes |
| Searchable archive | Basic | Generally the selling point |
| In-person meetings | Rarely | Often, via a phone app |
| Admin overhead | None | Agreement, retention, policy line |
Telling people, properly
This is not a formality and it is not difficult.
For internal meetings, tell the team once that AI notes are now standard, put it in the privacy notice, and have the host say it at the top of the call anyway. Nobody minds being recorded. People mind finding out afterwards.
For external meetings, ask. Out loud, at the start, before anything substantive: "I have got AI notes running so I can pay attention rather than type. Is everyone happy with that?" It takes four seconds. If someone says no, turn it off and take notes by hand. That is the whole procedure.
Two situations where the answer is simply no: anything about an individual's employment, conduct or health, and anything a client's contract says must not be recorded. Check the contract before the call, not after.
Getting notes people actually read
Default summaries are a wall of prose that begins "The team discussed" and lists everything with equal weight. Nobody reads the second one they receive.
Fix it by asking for a shape, once, and saving it as your standard instruction.
From this transcript, produce notes in exactly this order, and nothing else:
DECISIONS - what was actually decided, one line each. If nothing was decided, say so.
ACTIONS - a table of action, owner, and deadline. Only include an action if a person was named. List unassigned actions separately under "needs an owner".
UNRESOLVED - questions raised and not answered.
FOR INFORMATION - anything else worth knowing, maximum four bullets.
Do not include pleasantries, scheduling chat or a general summary of the discussion. If something was ambiguous, write it as ambiguous rather than resolving it.
The last two sentences do most of the work. Left to itself a summariser will tidy an argument into a conclusion, which is precisely the thing you needed to know had not happened.
The five minutes that matter
Do not send the summary unread. Three things to fix, and it genuinely takes five minutes:
- Names and numbers. Transcription mangles both. A wrong figure in the minutes becomes the agreed figure.
- Actions without owners. The commonest failure. "The team will look into pricing" is not an action. Put a name and a date on it, or delete it.
- Anything smoothed over. If two people disagreed and the summary says the team aligned, correct it. Minutes that erase disagreement cause the disagreement to recur in three weeks.
Send within the hour. Notes that arrive next Tuesday are archaeology.
Where the time actually goes
The saving is not really the typing, although a weekly management meeting minuted by hand costs somebody thirty to forty minutes a week. It is the attention.
The person taking notes is not in the meeting. They are transcribing it, half a sentence behind, unable to push back on anything because they are typing the last thing that was said. Give that person their attention back and the meeting itself improves. That is the bit you notice after a month.
It also creates something small businesses rarely have: a searchable record of what was decided and why. Six months on, "when did we agree that?" has an answer.
A sensible first fortnight
- Check whether Teams or Meet already includes it. Usually yes.
- Turn it on for one recurring internal meeting only.
- Add your staff names, product names and local place names to the custom vocabulary.
- Save the summary format above as the standard instruction.
- Set a retention period. Thirty days for routine internal meetings is a reasonable default.
- Add two lines to your AI policy: which meetings are recorded, and which never are.
Then leave it alone for a month before extending it. The thing that makes this stick is not the tool, it is the editing habit, and that takes a few weeks to form. There is more on that in How to train your team to use AI.
Meeting notes are usually the first thing people ask about at the free AI Breakfast Club webinar, and the setup gets demonstrated live. It runs online every other Friday morning.