Meeting notes are a classic task for an AI agent. Everybody agrees they are useful, nobody wants to write them, and the result is often a half-remembered chat afterwards. An agent that joins the call, produces a summary and lists who should do what by when looks like a clear saving of time.
It is, but the work is not in the summarising. It is in the decisions around it: what the agent may do on its own, who needs to know it is there, how errors are caught before they reach forty people, and what happens to the recording afterwards. This article walks through those decisions. It is a practical outline, not legal advice, and your own legal or privacy contact should confirm the rules that apply to you.
Start with what the agent may do alone
Separate the steps and give each one its own level of freedom:
- Listen and transcribe. Allowed only for meeting types you have agreed in advance.
- Draft the summary and the action items. Safe as a draft that only the organiser sees.
- Send notes to participants. This is the step that can do damage, because a wrong sentence in a message from "the meeting" carries weight.
- Create tasks in your task tool or assign people. This changes other people's workload and should start as a suggestion.
A sensible first version does steps 1 and 2 by itself and leaves steps 3 and 4 to a person who clicks "send" after reading. Later you can allow automatic sending for low-risk, internal, recurring meetings such as a weekly team stand-up, while keeping approval for anything with customers, suppliers, money or personnel topics. The same step-by-step logic appears in our piece on choosing a first AI agent process by risk, value and reversibility.
Consent and notice
People speak differently when they are recorded, and some are entitled to know before it happens. Whatever the rules are in your country or sector, the practical minimum is the same:
- Tell people in advance. Put a line in the invitation: an AI agent will transcribe this meeting and produce notes. Do not rely on a bot name appearing in the participant list.
- Say it again at the start. A short sentence from the organiser gives anyone who missed the invitation a chance to object.
- Allow people to say no. Decide what happens then: the agent is switched off, or the person is told the notes will not include their contribution. Agree this before the first awkward case.
- Be careful with external guests. Customers, candidates and partners did not sign your internal policy. Ask them, and accept a refusal without friction.
Write the rule down once, in plain language, and link it from the invitation template. Check the details with whoever handles privacy for your company, especially if participants are in several countries.
Meetings that should never be recorded
Draw the line by meeting type, not case by case. A list that works for many companies:
- Performance reviews, disciplinary talks, pay discussions and anything about named individuals' employment.
- Health or other personal matters.
- Legal advice, disputes and anything the lawyers have asked to keep out of written records.
- Board or investor discussions, unless the secretary has explicitly asked for them to be minuted.
- Security incidents while they are being handled, because the transcript would contain details you may not want spread.
Enforce the list technically where you can: the agent should not be invited to calendar entries with certain labels or in certain rooms, rather than relying on people to remember to remove it. Remember that a rule that exists only in a document will be forgotten in a busy week.
Check accuracy before anything is sent
Speech recognition and summarising are good, not perfect. Typical errors are not spelling mistakes. They are the ones that change meaning:
- A name, a number or a date is wrong. "Ship on the 13th" becomes "the 30th".
- A proposal is recorded as a decision, or a decision as a proposal.
- Two people with similar names are mixed up.
- A joke, a hypothetical or a "maybe we could" turns into a commitment.
- A technical term or product name is replaced with a similar-sounding word.
Build the check into the process. The organiser or another named participant reads the draft within a short window, corrects it and sends it. Ask the agent to help the reader: highlight numbers, dates, names and decisions, and mark statements it was unsure about. Where possible let it link each action item to the timestamp in the transcript so the reader can listen to the original moment in seconds.
Before launch, test on ten to twenty real meetings of different kinds. Let the participants mark every error and note which kind it was. After launch, review a small sample each week at first. If the same type of error keeps returning, change the setup, for example by adding a glossary of product names, rather than asking people to be more careful.
Action items need an owner
An action list without owners is decoration. Set the format and make the agent follow it:
- One owner per item. A team is not an owner. If the agent cannot tell who took the task, it writes "owner not confirmed" and the organiser fills it in.
- A date or a trigger. "Soon" is not a deadline. If none was said, leave the field empty rather than inventing one.
- Heard or inferred. Mark items that someone clearly accepted separately from items the agent derived from the discussion. Only the first group should ever go into a task tool without a human look.
- Close the loop. Before the next meeting of the series, the agent can list open items from the last one. This is often worth more than the summary itself.
Be careful about assigning work to people who were not in the meeting. The agent can propose it, but a human should tell the person.
Retention, access and deletion
A recording and a transcript are records of what people said, often more than anyone remembers. Treat them accordingly:
- Decide what is kept. Many teams keep the notes and delete the audio and full transcript after a short period, since the notes are what people use.
- Set a time limit and make deletion automatic. Write the period in the policy and check that the tool really does it, including copies at the provider.
- Control access. By default, only participants and the organiser should see the material. Do not make every meeting searchable by the whole company without a conscious decision.
- Know where it goes. Find out where the provider stores the data, whether it is used for model training and who at the provider can open it. Write the answers down.
- Handle requests. A participant may ask to see or delete what concerns them. Know who deals with that and how quickly.
The wider questions of storage and retention are covered in AI agent data handling and retention, and the idea of keeping a trace of what the agent did is developed in what an AI agent activity log should record. If the agent can write to your calendar, task tool or shared drive, apply the principles in least-privilege access for AI agents.
Know when to hand over to a person
Some situations should leave the agent's hands. Let it stop and notify the organiser when it detects that a participant objects to the recording, when the conversation turns to a topic on the excluded list, when audio quality is too poor to trust the transcript, or when a participant asks for the notes to be corrected or removed. The organiser, not the agent, decides what happens next. The general triggers are described in when an AI agent should stop and hand over to a person.
A short checklist
- A list of meeting types where the agent may listen, and a list where it may not.
- A notice in the invitation and a sentence at the start of the meeting.
- Notes and tasks sent only after a named person has read them.
- One owner and one date per action item, with inferred items marked.
- A test on real meetings and a weekly sample review at the start.
- A stated retention period, an access rule and a person responsible for deletion.
An agent that writes good notes saves time every week. An agent that sends a wrong note, or records a meeting nobody expected to be recorded, can cost you the trust that makes people speak openly. Begin with drafts, keep a person in the loop and widen the freedom only as the review shows it is earned.
