Nobody enjoys writing minutes, and everybody wants to read them when there is a disagreement three weeks later. AI makes the writing part easy. It does not make the thinking part optional. The aim is minutes that save time and that people trust. Below is a simple meeting minutes template, and how AI can draft it for you to check.
What minutes are for
Minutes have one job: to let someone who was there, or was not, find out what was decided and what happens next. Everything else is optional. A useful set of minutes answers five questions:
- Who was there, and who sent apologies?
- What was decided? Not discussed: decided.
- Who will do what, and by when?
- What was left open, and who will bring it back?
- When and where is the next meeting?
If your minutes are three pages of who said what, almost nobody will read them. If they are five clear lines, they will be used. A decision stated plainly is worth more than a faithful account of the argument that led to it.
Why AI helps, and where it goes wrong
AI is good at the mechanical part. Given a transcript or a page of rough notes, it can pick out the decisions, list the actions with their owners, and write them in a consistent shape. That takes a job that used to be twenty minutes and makes it a two-minute read.
It goes wrong in predictable places:
- Names and numbers. A transcript can mishear a name, or a figure, and the draft will repeat the mistake confidently.
- Who owns an action. If nobody said "I will do that", the draft may guess, or assign it to whoever spoke last.
- Decisions that were only suggested. "We could move the launch to March" is not "the launch moves to March". Check that proposals were not turned into decisions.
- Tone and politics. A draft does not know what is sensitive. Some things belong in the room and not in the record.
So the rule is simple: AI drafts, a person who was there approves. Treat the draft like a colleague's first pass, not like a recording of the truth.
Before the meeting: make the minutes easy
The best minutes start before anyone speaks. A short agenda, with an owner for each item, gives the draft its structure. In nerix, a meeting has a Before tab for exactly this: the agenda with a person for each topic, the guests and whether they are coming.
Then decide how you will capture what happens. There are two practical routes:
- Live notes. One person types short notes during the meeting: decisions, actions and owners. This is the most reliable input, because a human decided what mattered at the time.
- A recording. If everyone knows and agrees the meeting is recorded, the transcript becomes the input. It is more complete and less selective, so the draft needs more checking.
Many teams use both: live notes for decisions and actions, a transcript to settle what was actually said.
During the meeting: capture decisions as they happen
When a decision is made, say it out loud in one sentence and let the note-taker write it down. "So we agreed: the offer goes to the client on Friday, Maya sends it." Saying it twice, once to decide and once to record, removes most of the later arguments.
NXFIG0X In nerix, the During tab has live notes, decisions and action items side by side, so these are captured as separate things rather than buried in a paragraph. That matters later: an action item that exists as an item can become a task with an owner and a date, and a decision that exists as a decision can be found again.


