Meeting prep and follow-up: agendas, pre-reads, minutes and actions

Meetings create two kinds of admin: the preparation nobody has time for and the follow-up that decides whether anything actually happens. AI is useful at both ends. It drafts a sensible agenda from a goal, condenses a long paper into a pre-read and turns scrappy notes into tidy minutes. The risk is at the follow-up end, where a tool that fills gaps with plausible names can create owners and deadlines nobody agreed.

This guide follows Maya Roberts, Office Manager at Fernway Group (our fictional practice company), through one meeting from invite to chase.

Before the meeting: an agenda with a purpose

A good agenda says what the meeting is for, separates decisions from updates and puts the hard item where people still have energy. AI does this well when you give it the goal and the constraints.

Draft an agenda for a 45-minute meeting. Purpose: decide whether to give notice on our office lease before the 31 August deadline, or ask for a short extension to decide. Attendees: managing director (chair), head of operations, finance lead, office manager.

Finance will present a cost comparison of our current office and two alternative sites.

Put the decision item early, with at least 20 minutes for it. Mark each item as "decision", "discussion" or "update". Add timings. Then list what attendees should read beforehand and one question each person should come ready to answer.

The draft is usually close. Maya checks three things: the timings add up to 45 minutes, nothing on the agenda assumes an outcome ("agree move to site B" would be wrong), and the questions suit the people. She changes one: the tool asked the office manager about "staff sentiment", which Maya has no data on, so she swaps it for "practical move timeline".

Pre-reads people will actually read

Dan's cost comparison is eight pages. Erin will read it; others may not. A one-page pre-read helps, as long as it sticks to what Dan wrote.

Then check every figure in the pre-read against the report. Numbers are where summaries go wrong, and a wrong number in a pre-read shapes the decision.

During the meeting: recording and transcription

AI meeting tools, such as Copilot in Teams, note-taking in Google Meet with Gemini, or a separate transcription app, can produce a transcript and a recap. They save real time. They also capture everything everyone says, which is personal information about the people in the room.

Before you record or transcribe:

• Check your organisation allows it, and which tool is approved. A third-party note-taker that joins calls is still a tool processing your meeting.
• Tell people at the start, in the invite and again out loud. People should know they are being recorded and what happens to the recording.
• Think about the agenda. A personal, HR or commercially sensitive item may need the recording switched off, or no recording at all.
• Take extra care with external guests. Customers and suppliers may have their own rules. Ask.
• Know where the recording and transcript are kept and who can see them afterwards.

Your organisation's recording policy answers these. If you're unsure, ask your data protection lead. Your organisation's policy and approved tools still take priority. For how data protection applies to AI generally, the ICO's guidance on AI and data protection is the official starting point.

After the meeting: notes to minutes and actions

This is the step with the most value and the most risk. The tool is good at structure: decisions, discussion points, actions. It is also inclined to finish things that were left unfinished, by attaching a likely owner or a sensible-sounding date.

Use Fernway's weekly operations sync notes to see this. The notes contain eleven actions. Two have no owner: the August holiday cover rota and booking the summer social venue. A loose prompt will often hand both to Maya, because she is the office manager and her name appears near them. Nobody agreed that.

Turn these rough meeting notes into minutes. Use only what's in the notes.

Structure: date and attendees; decisions (only things the notes say were decided); key discussion points in one line each; an actions table with columns for action, owner and deadline.

Rules: if an action has no clearly named owner, write UNASSIGNED. If there's no deadline in the notes, write "none set". Don't turn a discussion into a decision. Keep the wording neutral.

After the table, list anything that looks unfinished or unclear, so I can check it before sending.

[paste notes]

With the Fernway notes, a good result keeps both unassigned items as UNASSIGNED, lists "bring Harlow renewal numbers next week" as Tom's action without turning it into a decision about the discount, and flags "IT still hasn't confirmed the imaging thing?" as unclear. Maya then asks Priya who should own the rota, before the minutes go out.

A structured template makes this easier every week. Download the minutes and actions template and paste its headings into the prompt so the output always comes back in your house format.

For a full hands-on version with a model answer, try Meeting notes to actions. For what happens when this goes wrong and nobody checks, read The owner nobody agreed.

Checking an AI recap

If Copilot or Gemini produced the recap from a transcript, you still check it. Transcripts mishear names and numbers. Recaps can merge two people's points, miss a quiet "I'm not sure we should" that changed the outcome, or record an idea as an agreement.

Below are a meeting recap and the transcript it came from. Compare them. List any decision, owner, date or figure in the recap that the transcript doesn't clearly support, and quote the relevant transcript lines. Also list any objection or open question in the transcript that the recap leaves out.

Recap: [paste]

Transcript: [paste]

This helps, but it is a second opinion from the same kind of tool. The final check is you, with your own memory of the meeting or a quick word with the chair.

Chasing actions

A week later, the actions table becomes a chase list. Paste the open actions only (not the whole minutes), ask for a short friendly reminder per owner with their action and date, and send them yourself. Check each reminder names the right action for the right person.

What to check

Common mistakes

• Letting the tool fill gaps. It will assign owners and dates to make the table look complete. A complete-looking table with invented entries is worse than an honest one with gaps.
• Recording without telling people. Even with the best intentions, it damages trust and may break policy. Say it at the start, every time.
• Treating a recap as the minutes. An automatic recap is a draft. Minutes are a record someone stands behind, and that someone is you or the chair.
• Pasting the whole transcript into an unapproved tool. Transcripts are full of names, opinions and asides. Use the approved in-app tool, or trim to what the task needs.
• Turning discussion into decisions. "We talked about moving to site B" is not "we agreed to move to site B". Watch the verbs.
• Over-long minutes. Ask for one line per discussion point. Nobody reads a transcript retold in paragraphs.