Work & EmailGuide

Turn messy notes into a clear action list

Half-sentences from a meeting become who does what by when.

6 min read Updated 24 Sep 2026By the AIvelina team
Turn messy notes into a clear action list
Photo: rawpixel (CC0)

Meeting notes are written in a hurry and read never. The useful part is usually three or four actions hiding in a page of fragments. Paste the notes into AI and ask for exactly that: decisions, actions, owners and dates — and a short message you can send to everyone afterwards.

  1. 1

    Paste the raw notes

    Bullet points, abbreviations and typos are fine. Remove anything confidential first.

  2. 2

    Ask for three sections

    Decisions made, actions with owners, and open questions.

  3. 3

    Get the follow-up written

    A five-line summary email saves the next meeting from repeating this one.

Copy-paste prompt

Turn these meeting notes into: (1) decisions, (2) an action list with owner and deadline for each — mark “owner unclear” where I did not write one, (3) open questions. Then draft a short follow-up email to the group. Notes: [paste]

Replace the parts in [brackets] with your own details.

Velina’s tip

Ask it to flag anything in the notes that sounds like a promise to a customer. Those are the ones that hurt when they are forgotten.

Why meetings produce so little

Most meetings end with a feeling of agreement and no record of who will do what. Notes are taken, but they are a transcript of the discussion: half sentences, arrows, a name in the margin. A week later nobody remembers whether “look into pricing” was a decision, an idea or someone’s job. The work that should have followed does not happen, and the next meeting repeats the last one.

The fix is not better note-taking during the meeting. It is five minutes afterwards spent turning raw notes into three short lists. AI does that conversion quickly, and it is honest about gaps in a way people rarely are: it will tell you that a task has no owner.

The three lists

  1. 1

    Decisions

    What was agreed. Written as statements, so that anyone who missed the meeting knows where things stand.

  2. 2

    Actions

    What will be done, by whom and by when. One owner per action. A task that belongs to “the team” belongs to nobody.

  3. 3

    Open questions

    What was raised and not resolved, with the person who will find the answer.

Everything else in the notes, such as the discussion, the tangents and the opinions, can be dropped or kept as a single line of context.

A worked example

The raw notes read: “Budget ok if under 5k. Maria to check supplier. Launch probably March?? Tom worried about support load. Need new landing page, someone ask design. Pricing, discuss next time.”

The structured version says: Decisions: the budget is approved up to 5,000. Actions: Maria to confirm the supplier’s quote by Friday. Landing page request to design, owner missing. Open questions: launch date, with March proposed and not confirmed. Support capacity for launch, raised by Tom. Pricing, deferred to the next meeting. It flags two problems: one action has no owner and none has a firm deadline except Maria’s. You fill those in, and the follow-up email is ready in two minutes.

What makes a good action item

  • It starts with a verb: send, confirm, draft, book, decide.
  • It has exactly one owner, named.
  • It has a date, not “soon” or “as soon as possible”.
  • It is small enough to finish. “Fix the website” is a project. “Send the three broken links to the developer” is an action.
  • It can be checked. Someone else could tell whether it is done.

Follow-up prompts

  • “Write a follow-up email to the attendees with decisions, actions and open questions. Keep it under 150 words.”
  • “Sort the actions by owner so that each person sees only their own list.”
  • “Turn these actions into a simple table: task, owner, deadline, status.”
  • “Which of these items are too vague to act on? Suggest a clearer version of each.”
  • “Based on the open questions, draft an agenda for the next meeting.”
  • “Rewrite these notes as a short update for my manager, who was not there.”
  • “I recorded my own thoughts after a call: [paste]. Pull out what I promised to do.”

Not only for meetings

The same method tidies up almost any pile of thoughts. A long voice memo dictated on a walk. The notes from a phone call with a builder. A page of ideas from a planning session at the kitchen table. A parents’ evening at school. Paste the mess and ask for decisions, actions and questions. For personal use, add one more instruction: “put the actions in the order I should do them, and tell me which takes less than five minutes.” The quick ones can be finished at once, which is the best way to shrink a list.

Check it against your memory

AI reorganises what you give it. It was not in the room. It can misread an abbreviation, attach a task to the wrong person or turn a tentative remark into a firm decision. Read the result once and compare it with what you remember. Where it is unsure, a good prompt tells it to write “unclear” or “owner missing” and never to guess. If it invents a deadline you did not mention, remove it.

If you use a tool that records and transcribes meetings automatically, tell the participants and get their agreement first. In many places recording without consent is against the law or company policy.

Keep confidential things out

Meeting notes often contain names, salaries, customer details, plans that are not public and personal remarks. Before you paste, replace names with initials or roles and remove anything sensitive. Check what your employer allows. Some organisations provide an approved AI tool for internal information and forbid others. When in doubt, summarise the notes yourself in neutral terms first and paste that.

Send it within the hour

A follow-up loses value quickly. Sent the same day, it confirms what people just agreed and catches misunderstandings while they are cheap to fix. Sent a week later, it starts a new debate. Make it a habit: the last five minutes of any meeting you run are for reading the actions aloud, and the first five minutes afterwards are for sending them. People notice the person who does this, and meetings with that person tend to get shorter.

Common mistakes

  • Sending the raw notes and calling it a summary.
  • Actions with no owner, or with two.
  • Deadlines such as “next week” that mean different things to different people.
  • Recording decisions that were not actually made.
  • A follow-up so long that nobody reads it.

Quick questions

  1. 1

    What if my notes are very thin?

    Paste what you have and add what you remember in plain sentences. Even five lines can be structured.

  2. 2

    Should the summary go to everyone?

    To attendees and to anyone who has an action. Others can have the short version.

  3. 3

    Can AI track whether actions get done?

    Not on its own. Put the list in whatever task tool or shared document your team already uses.

Velina’s tip

End your follow-up with one line: “If I have misunderstood anything, reply by tomorrow. Otherwise I will assume this is correct.” It gives people a clear chance to object and turns silence into agreement.

AI assistants can be wrong. Check prices, dates, health and legal details against an official source before you act, and never paste passwords or card numbers into a chat.

Keep going

Free starter pack

Get the free Everyday AI starter pack

Ten prompts that pay for themselves in the first week — dinner, inbox, budget and a weekend away. Then one small tip every week.

No spam. Unsubscribe anytime.