AI Meeting Minutes Template: A Practical Format for Clear Notes

A summary describes a meeting. A minute is the record of it — the version people rely on months later when they disagree about what was agreed.

Company law in many jurisdictions puts a floor under that. The UK Companies Act 2006, section 248, requires every company to cause minutes of all proceedings at meetings of its directors to be recorded, and to keep those records for at least ten years from the date of the meeting. That is a UK provision quoted here as a concrete illustration of the standard, not as advice about your own entity — check the rule that applies where your company is incorporated.

The practical consequence is the same everywhere: a minute needs to be attributable, complete on decisions, and stable once approved. That is what the template below is shaped around, and it is why the approval field is not optional decoration.

Sources: ^[5]

Copy this structure. It fits a one-page document and it survives being pasted into email, a Doc or a wiki.

1. Meeting identity — title, date, start and end time, location or platform, and who chaired.

2. Attendance — present, apologies, and anyone who joined partway. Note the point they joined if a decision happened before it.

3. Agenda item — one heading per item. Everything below repeats under each heading.

4. Discussion summary — three to six lines. What was raised, the main positions, and any figure or date that was quoted. Not a transcript.

5. Decisions — written as a completed statement: "Approved the revised delivery date of 14 October." If nothing was decided, write "No decision; carried to next meeting."

6. Action items — one line each, with a named owner and a due date. "Team" is not an owner.

7. Follow-ups and open questions — things nobody could answer in the room, with who will find out.

8. Approval — who prepared the minute, who checked it against the recording or transcript, and the date it was approved.

Field 8 is the one people delete first and miss most. It is what separates a draft that circulated from a record that was accepted.

Sources: ^[1,3]

The tools are good at the middle of the template and weak at both ends, and their own documentation says so.

Memora's staff guide describes the review screen as holding the audio, transcript, summary, action items and decisions — fields 4, 5 and 6 — and puts the review step after upload completes, not before.

Google's Meet help page says "Take notes for me" automatically captures notes organised in Google Docs, gives late joiners a "Summary so far", and sends the organiser an email containing a link to the notes document, a meeting summary and suggested next steps. It also states that the summary can be incomplete, inaccurate or not generated.

Microsoft's recap page says Copilot can tell you what you missed, including whether you were mentioned and which action items were assigned — and then tells you to verify the results, because AI-generated content could be incorrect.

What none of them decides is fields 1, 2 and 8. Attendance in particular is where generated drafts go wrong most quietly: speaker labels come from the transcript, and Microsoft's transcription documentation notes that speaker attribution and timestamps are what the saved transcript provides — so anyone dialling in on a shared line, or speaking from another person's laptop, will be attributed to the wrong name unless someone corrects it.

Sources: ^[1,2,3,4]

The mechanics differ slightly by platform, and both need one thing set before the meeting rather than after.

Microsoft Teams. Open the meeting chat, select the Recap tab, select Copilot, select View prompts, then Recap the meeting. Paste the decisions and action items into fields 5 and 6, then read them against the transcript rather than from memory. Microsoft's note on that page is explicit about verifying the output.

Google Meet. The notes document is generated shortly after the meeting ends and saved in the meeting organiser's Drive, inside the "Google Meet" folder, in a sub-folder for that meeting. It is automatically attached to the Calendar event, and who can open it is decided by the sharing settings chosen when note-taking started — Google notes that notes are shared only with individuals added to the calendar invite, and that a group email does not by itself grant access. Google also records that the notes document follows the Meet retention policy your organisation has configured.

In both cases the draft arrives structured but unowned. Fields 1, 2 and 8 are still empty, and they are the ones a reader will check first.

Sources: ^[2,3]

Meeting identity — Weekly delivery review. 27 August 2026, 10:00–10:35. Meeting room 2, Petaling Jaya. Chaired by the operations lead.

Attendance — Present: operations lead, project manager, two engineers. Apologies: finance manager. The client success lead joined at 10:12, after item 1.

Item 1 — Revised delivery date

• *Discussion:* The integration slipped by nine days because a third-party API change required rework. The project manager proposed 14 October. The engineers confirmed the rework is scoped but not yet started.
• *Decision:* Approved the revised delivery date of 14 October.
• *Actions:* Project manager to reissue the schedule to the client by 29 August. Lead engineer to confirm the rework estimate by 1 September.
• *Follow-up:* Whether the API change affects the reporting module — lead engineer to confirm at the next meeting.

Approval — Drafted from the meeting recording by the project manager. Checked against the transcript by the operations lead on 28 August 2026.

Notice how little of that is prose. Minutes that read like an article get skimmed; minutes that read like a list get used.

Sources: ^[1]

One person, one pass, before it is sent. Compare six things against the transcript or recording rather than against your memory of the meeting: names, figures, dates, decisions, action owners and deadlines. Those six are where a generated draft is most often confidently wrong.

Memora's guide places the review after upload completes — open Meetings, check the audio, transcript, summary, action items and decisions — and notes that email is only sent when you enable it, so distribution is a deliberate step rather than an automatic one.

Then fill field 8 and stop editing. A minute that keeps changing after approval is not a record.

If you want the wider view of what can and cannot be automated across platforms, see How AI Can Automate Your Meeting Minutes.

Sources: ^[1,2,3]