Three pages of scribble
Here is the standard meeting outcome. Someone types furiously for an hour. The notes get pasted into an email nobody reads. Two weeks later a thing that was definitely agreed has not happened, and there is a short awkward conversation about who was supposed to do it.
The problem is not the note taking. It is that raw notes are a transcript of what was said, and what you actually need is a much shorter list of what was decided, what happens next, and who owns it. That conversion is dull, mechanical work. Which makes it perfect for AI.
In plain English
- Action item:
- One specific task that came out of a meeting, with a person's name attached and ideally a date.
- Owner:
- The single person responsible for an action item. Not a team, not everyone. One name.
- Transcript:
- A written record of everything that was said, word for word. Longer and messier than notes.
The one prompt that does most of the work
You do not need tidy notes for this. Half sentences, abbreviations, names with no surnames, arrows, all fine. The AI reads them better than a colleague would.
Below are my rough notes from a meeting. Turn them into three sections.
- DECISIONS: what was actually agreed. One line each.
- ACTIONS: each task on its own line, formatted as Task, Owner, Due date.
If no owner or date was mentioned, write UNASSIGNED or NO DATE.
- OPEN QUESTIONS: anything raised but not resolved.
Do not invent anything. If the notes are unclear, say so rather than guessing.
MY NOTES:
[paste them]
That instruction to write UNASSIGNED rather than guess is the important bit. Without it, AI will helpfully assign the task to whoever was mentioned nearest, and you will end up with a list that is subtly wrong in a way nobody catches until the deadline.
Ask for the actions as a table. Task, Owner, Due date, Status. You can paste a table straight into a spreadsheet or a project tool, which turns the summary into something people actually track.
Checkpoint
Meeting notes become useful when they are reduced to three things: decisions made, actions with named owners, and questions still open.
Catching the person who missed it
Someone was off sick, or in another meeting, or on a train. They do not want the full notes. They want to know what changed and whether anything landed on them.
Write a short recap for a colleague who missed this meeting.
Their name is [name] and their role is [role].
Cover, in this order:
- What was decided, in three lines or fewer.
- Anything assigned to them specifically.
- Anything they need to respond to, and by when.
- Everything else, in two lines, as context only.
Under 200 words, friendly, no bullet point padding.
MEETING NOTES:
[paste them]
The role line matters more than you would expect. The same meeting produces a different recap for the finance manager than for the person running the warehouse, because a good recap leads with what affects the reader.
Before the meeting, not just after
The overlooked use is the agenda. Ten minutes before a meeting, paste in the last set of notes and ask what still needs deciding.
Here are the notes from our last meeting. Build an agenda for the next one.
Start with anything from the ACTIONS list that has no evidence of being finished,
then the OPEN QUESTIONS, then leave a slot for new business.
Suggest a rough number of minutes for each item, assuming a [30] minute meeting.
LAST MEETING NOTES:
[paste them]
The privacy part, which is not optional
When you paste meeting notes into a chatbot, you are sending them to a company's servers. Depending on the product and the settings, that text may be stored, reviewed by a human for quality checking, or used to improve the model. Consumer free tiers and paid business accounts often behave quite differently here.
So think for three seconds before you paste. Ask yourself what is actually in these notes.
- A discussion about someone's performance, sickness or salary: do not paste it.
- Anything about a person who has not agreed to it being shared: do not paste it.
- A client's confidential plans, or anything under a signed agreement: do not paste it.
- Legal advice, an ongoing dispute, or a possible redundancy: do not paste it.
- The weekly stand up about which supplier is late: paste away.
If your employer has an approved AI tool, use that one and follow its rules. If it does not have a policy yet, the safe default is simple: strip names and numbers, or do not paste at all. Nobody has ever been disciplined for being slightly slower.
There is a middle path that works well. Rewrite the sensitive bits before pasting: replace names with Person A and Person B, replace the client with Client X, take the money out. The AI does not need to know who anyone is to spot that a decision was made and nobody was assigned to it.
Make it a habit, not a project
The whole thing takes about ninety seconds. Notes in, three sections out, skim it, fix the two things it misread, send it while everyone still remembers the meeting. Sending a summary the same hour is worth more than a beautiful one sent on Thursday.
๐ Quiz
Question 1 of 4Why should your prompt tell the AI to write UNASSIGNED when no owner was named?