Turn messy meeting notes into decisions and actions

Priya wants three things: what was decided, who is doing what by when, and anything still hanging. The action list is a record people will be held to, so an owner written next to a task is a small commitment made on someone's behalf.

That changes what "good" looks like. A tidy list that fills every box is worse than a slightly untidy one that is true. Your real job is to separate what was agreed from what was said, and to make the gaps visible so Priya can close them.

Reasonable fit. Sorting a page of fragments into decisions, actions and questions is structuring work, and AI is quick at it. The risk is also well known: language models are built to produce complete-looking answers, so they tend to fill an empty owner or deadline with a plausible guess.

Use AI for the first sort. Keep the judgement about who agreed to what, because only you were in the room.

Real meeting notes like these contain colleagues' names, internal plans, a budget figure and a reference to customer messages. That's ordinary internal business information, but it still belongs in a tool your organisation has approved for work, signed in with your work account. Don't paste real internal notes into a personal account on a free consumer tool.

These notes don't contain any customer's details, only the fact that messages exist. If your real notes did (a customer's name, a complaint about a named person, anything about someone's health or performance), take those lines out first or leave the job to a human. Removing a name doesn't always make something anonymous: "the customer in Leamington who complained about the chair" may still identify someone.

The fictional practice file is safe to use in any tool. Your organisation's policy and approved tools still take priority.

Two minutes of preparation saves ten minutes of correction.

Add the attendee list with full names and roles if your notes don't already have it. This is what lets the AI notice there are two people called Sam. Add today's date, so "Friday" and "end of next week" can be turned into dates you then check. Leave the mess in: the half-sentences and question marks are evidence of uncertainty, and you want the AI to see them.

Any general assistant (ChatGPT, Copilot Chat, Claude, Gemini) can do this from pasted notes. What matters more than the tool is the instruction: you need it to report gaps instead of filling them.

The instruction needs to say what to produce and, more importantly, what to do when the notes don't say.

A short, clear instruction is enough here. You don't need a paragraph of role-play.

Below are my rough notes from a project meeting held on [date]. Using only these notes, produce three sections.

Decisions: only things the group clearly agreed. Leave out ideas that were suggested, parked or disputed.

Actions: a table with Action, Owner, Deadline and Notes. If no owner was agreed, write "Not agreed in meeting". If a deadline changed or wasn't settled, write what was said and flag it. Don't infer an owner from someone's job title. If a first name could mean more than one attendee, say so.

Open questions: anything I need to confirm with the chair before sending.

[paste notes, including the attendee list]

Here is the kind of answer a general assistant might give to the weak instruction. It looks finished, which is exactly the problem.

Read it against the notes line by line. Your memory of the meeting isn't the source. Put a mark next to every owner and every date, then find each one in the source.

Eight actions, every box filled. Only two rows (Maya's tracker and Priya's board draft) are fully supported by the notes.

Other things to catch:

• Decision 3 overstates a parked idea. "Let's think about it, park for now" isn't a review.
• "6 October" is the AI's arithmetic for "in two weeks". It's about the meeting date, not when the invite should go.
• Tom's suggestion that account managers ring the bigger accounts has vanished. It was never agreed, so it belongs in open questions.

You can fix this with one follow-up and a few manual edits. The follow-up makes the AI show its evidence, which is quicker to check than its conclusions.

For each action and decision, quote the exact line from my notes that supports the owner and the deadline. Where no line names an owner or a date, change it to "Not agreed in meeting". Two people called Sam are listed (one attended, one sent apologies): flag which Sam is meant wherever it's unclear.

Then do the part only you can do. You were in the room: if you're confident Sam Hollis offered the depot figures, say so, but mark it as your understanding so Priya can correct you. Turn "end of next week" into a date (Friday 2 October) and check it on a calendar. Keep Tom's board request next to it, because the conflict is real and Priya needs to settle it.

Be honest with yourself here. The first draft took under a minute. Checking every owner and date against the notes took most of the time, and you'd have spent some of that time anyway writing it by hand.

Where AI earned its place was the structure: the table made the empty cells obvious, and the evidence follow-up surfaced the second Sam faster than rereading would. Where it cost time was cleaning up confident guesses. With the better instruction from step 6, most of those guesses never appear, so the checking is quicker.

A fair rule: for long or chaotic notes, AI plus a proper check is usually quicker than starting from blank. For a short meeting with clear owners, typing it yourself wins.